340 reputation
421
bio website ushr.com
location Cambridge, MA | Montreal | Capbreton France
age
visits member for 4 years, 6 months
seen Dec 4 at 13:46

Psychologist turned programmer, developing on the JVM with the Typesafe stack (Akka, Play, and Slick) server-side, and Coffeescript + GruntJS client-side.

Currently hacking on the U.S. Hockey Report, an amateur hockey scouting news service.

For contracting gigs email: admin '@' newmindit.com


Nov
3
answered ESXi :: vmxnet3 vNIC and Linux kernel errors
Nov
3
comment ESXi :: vmxnet3 vNIC and Linux kernel errors
@mdpc, yes, yum updated machine, latest kernel and latest vmware tools. Ethernet ports on the host are fine, no dropped packets or errors of any kind. I have read that only in 2.6.32+ is vmxnet3 built-in to the kernel, that may be the issue, the kernel does not understand a NIC capable of passing 10gb/sec (obviously not realistic in physical network but between VMs, e.g. web server and database, or to a backup VM, it would be nice). Anyway, bringing down affected VM and downgrading the NIC now, will report back results of course...
Nov
2
asked ESXi :: vmxnet3 vNIC and Linux kernel errors
Oct
28
comment Linux route to different subnet
hmmm, not sure what you're talking about ;-) The server is on dmz 172.16 while my vpn user comes in on private 10.1. The whole point of the additional route is to allow traffic initiated by 10.1 to 172.16 to flow back on 10.1 and not 172.16, the default gw. It was a VPN issue, production dmz web server itself is humming along just fine...
Oct
27
comment Linux route to different subnet
@silverfire, "route add default gw 172.16.1.1" is the default gw, eth0 is on dmz 172.16.x.x subnet and therefore any other nic in the system will use 172.16 as its default gw (unless you add a new route to say traffic originating from other-subnet to default-subnet, should go back out on other-subnet and not on default subnet)
Oct
27
comment Linux route to different subnet
@silverfire, yes, I know, added to /etc/init.d/rc.local init script, the route will remain in place (but good to point out for benefit of others, +1)
Oct
27
awarded  Yearling
Oct
26
revised Linux route to different subnet
deleted 153 characters in body
Oct
26
comment Linux route to different subnet
actually it does work, see my answer. VPN user can "see" both subnets, but the lack of a return route on the server was causing traffic to flow back out through the dmz (default gw) rather than to vpn user on 10.1 subnet.
Oct
26
answered Linux route to different subnet
Oct
26
awarded  Critic
Oct
26
comment Linux route to different subnet
There are no separate physical routers, just the ASA and servers (there's a switch involved, but that's on unrelated 192.168.x.x subnet that the ASA knows nothing about). Basically when 10.1 talks to 172.16, then 172.16 should talk back to 10.1 and not itself.
Oct
26
asked Linux route to different subnet
Oct
26
comment Cisco ASA 5505 :: Techniques for limiting consumed hosts (max 10 with base license)
@dunxd, while I disagree with Cisco licensing practices, I have to say, the ASA has several advantages over Linux APF/iptables OS firewall. In other words, I really, really like the power of this little unit ;-) No doubt the learning curve is steep initially, but once you get a few TAC sessions under your belt it starts to click (SmartNET is bar none the best tech support deal on the planet)
Oct
26
comment Cisco ASA 5505 :: Techniques for limiting consumed hosts (max 10 with base license)
@ewwhite, yes, you have to be more strict in your setup (use a single local ntp server, ssh over vpn on an already used interface, etc.) to conserve hosts. I'm actually running 8 host max count now with my changes, so I can roll with the base license for awhile. Once more revenue producing clients come in, sure 50 user license it will be...
Oct
26
awarded  Teacher
Oct
26
comment Cisco ASA 5505 :: Techniques for limiting consumed hosts (max 10 with base license)
actually, as of today $230 off of CDW for 10 to 50 user upgrade...
Oct
26
comment Cisco ASA 5505 :: Techniques for limiting consumed hosts (max 10 with base license)
My hand will be forced soon, enough, looks like I can get 10 to 50 user upgrade for $230 off of CDW, not terrible, but also not great. Just means I can use the device without anxiety of dropped traffic due to exceeding 10 host limit
Oct
26
accepted Cisco ASA 5505 :: Techniques for limiting consumed hosts (max 10 with base license)
Oct
26
answered Cisco ASA 5505 :: Techniques for limiting consumed hosts (max 10 with base license)