Daveo wrote:
I can connect up, the OpenVPN client shows connected, and I'm able to log in to IMAP or SSH servers, but then the connection seems to hang. I can get in via LISH happily enough, and I've update/upgraded and rebooted, restarted all the services etc. and it just continues to happen - nothing I connect through the VPN is able to keep alive for more than a few seconds without stalling.
If I read your post correctly, it also sounds like a straight SSH (without OpenVPN) is also hanging, right? So it's not obvious to me that this is limited to an OpenVPN problem as opposed to a more general one. Out of curiosity what kernel are you running?
It's a long shot and probably completely unrelated, but I had a 2.6.32 (latest stable paravirt) Linode (Ubuntu 8.04 LTS) I brought up earlier this month that after a few days of operation - shortly after it started receiving production traffic - ended up in a state that sounds very similar to what you describe.
I'd be able to connect without a problem, but I/O over the connection would just stop after a short number of operations. At first I thought I was getting wedged in disk I/O somehow and thought it might even be a host issue, but there were other hangs when clearly not waiting on disk I/O and I caught some stats showing large outbound TCP connection queues. It was the oddest behavior, as I could keep recreating connections, just not do much for long over them. I did open a ticket but the host was running fine.
The system was extremely close in configuration to existing Linodes I had but the first to use 2.6.32 (I had some stable 2.6.18s and one stable paravirt 2.6.31 that hadn't been rebooted into 2.6.32 yet). I was firewalled, but the ruleset had a dedicated hole in it for my home location, so very little processing going on. Though, as an aside, there was another post here about trouble getting ufw (simple firewall tool for Ubuntu) to install rules in a 2.6.32 kernel that previously worked with 2.6.31, so maybe a hint of something interesting in netfilter/iptables in 2.6.32.
In my case I couldn't spend too much time fiddling with the Linode as I needed it in production, so safety won and I just went back to 2.6.18 and no burps since. While I've intended to do some testing on a spare configuration, at this point I have no hard data that it was definitely something in 2.6.32, but there weren't a whole lot of other variables compared to my other Linodes.
-- David