Open VPN client performance terrible under Linux

Red Squirrel

[H]F Junkie
Joined
Nov 29, 2009
Messages
9,211
I just converted my laptop that I use at work to Linux since I had accidentally killed XP and figured I'd install Linux on it instead. Problem is, the network performance is TERRIBLE!

Check this out:

Code:
PING isengard.loc (10.1.1.50) 56(84) bytes of data.
64 bytes from isengard.loc (10.1.1.50): icmp_req=1 ttl=62 time=71.1 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=2 ttl=62 time=82.2 ms
64 bytes from 10.1.1.50: icmp_req=5 ttl=62 time=115 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=6 ttl=62 time=450 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=7 ttl=62 time=38.5 ms
64 bytes from 10.1.1.50: icmp_req=14 ttl=62 time=74.1 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=15 ttl=62 time=29.8 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=16 ttl=62 time=31.9 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=17 ttl=62 time=27.2 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=18 ttl=62 time=68.9 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=19 ttl=62 time=149 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=20 ttl=62 time=162 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=21 ttl=62 time=92.7 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=22 ttl=62 time=55.5 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=23 ttl=62 time=1314 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=24 ttl=62 time=310 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=25 ttl=62 time=34.1 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=26 ttl=62 time=129 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=27 ttl=62 time=131 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=28 ttl=62 time=70.1 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=29 ttl=62 time=168 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=35 ttl=62 time=48.6 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=36 ttl=62 time=239 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=37 ttl=62 time=79.2 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=38 ttl=62 time=28.3 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=39 ttl=62 time=27.2 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=40 ttl=62 time=89.2 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=42 ttl=62 time=688 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=44 ttl=62 time=351 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=45 ttl=62 time=36.9 ms
64 bytes from isengard.loc (10.1.1.50): icmp_req=46 ttl=62 time=197 ms
^C^C64 bytes from 10.1.1.50: icmp_req=49 ttl=62 time=1520 ms
^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^Cc
64 bytes from 10.1.1.50: icmp_req=50 ttl=62 time=573 ms

--- isengard.loc ping statistics ---
50 packets transmitted, 33 received, 34% packet loss, time 67533ms
rtt min/avg/max/mdev = 27.220/226.901/1520.543/341.589 ms, pipe 2

This is completely unusable, I can barely even use SSH because it's so damn slow and choppy.

Anything I can do? I could not find a VPN client that works so I'm just using openvpn directly in a console. Linux is suppose to be better at this stuff. Aparantly not.

The client connection is DSL (12/1) and the DLSAM is literaly like 30 feet away from the modem, my home connection (where I VPN to) is 50/30 fibre. So I know it's not the connection itself, and this only started when I switched to Linux.


Edit: I thought it was the VPN since it seemed ok till I connected, but I think it's actually the network stack itself it's just intermittent. Using ping -f and getting tons of packet loss within VPN but without it as well. Guess it's more a Linux specific issue at this point.
 
Last edited:
My first guess would be a dodgy NIC driver unless you're using a really common NIC. What hardware (machine, NIC, etc.) are you using and what distribution? Wired or wireless?
 
It is a ProBook 6450b. Here is NIC info:

Code:
44:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6200 [8086:4239] (rev 35)
        Subsystem: Intel Corporation Centrino Advanced-N 6200 2x2 AGN [8086:1311]
        Kernel driver in use: iwlwifi


Suspecting driver too. googled and apparantly the only way is to roll back to an older kernel, but I have no idea how I'd go about doing that. I imagine that would break lot of stuff even if I did succeed.
 
Back
Top