Attrociously high pings to router with wifi in Debian 64 with Atheros 9k

Jul 18th, 2012 | By | Category: Internet, Linux / Freebsd

Simple little solution that has been plaguing me all week.  We just upgraded our router and after scanning the local networks I found that channel 11 was completely unused so I switched it to that and man oh man that was nothing but a bad idea.  Even though channel 11 was the emptiest channel I’ve been experiencing ping results like this ever since:

64 bytes from 192.168.2.1: icmp_req=288 ttl=64 time=133 ms
64 bytes from 192.168.2.1: icmp_req=289 ttl=64 time=142 ms
64 bytes from 192.168.2.1: icmp_req=290 ttl=64 time=282 ms
64 bytes from 192.168.2.1: icmp_req=291 ttl=64 time=254 ms
64 bytes from 192.168.2.1: icmp_req=292 ttl=64 time=562 ms
64 bytes from 192.168.2.1: icmp_req=293 ttl=64 time=2503 ms
64 bytes from 192.168.2.1: icmp_req=294 ttl=64 time=1582 ms
64 bytes from 192.168.2.1: icmp_req=295 ttl=64 time=588 ms
64 bytes from 192.168.2.1: icmp_req=296 ttl=64 time=83.1 ms
64 bytes from 192.168.2.1: icmp_req=297 ttl=64 time=651 ms
64 bytes from 192.168.2.1: icmp_req=298 ttl=64 time=1118 ms
64 bytes from 192.168.2.1: icmp_req=299 ttl=64 time=980 ms
64 bytes from 192.168.2.1: icmp_req=300 ttl=64 time=1089 ms
64 bytes from 192.168.2.1: icmp_req=301 ttl=64 time=1828 ms
64 bytes from 192.168.2.1: icmp_req=302 ttl=64 time=4305 ms
64 bytes from 192.168.2.1: icmp_req=303 ttl=64 time=4123 ms
64 bytes from 192.168.2.1: icmp_req=304 ttl=64 time=5005 ms

 

After googling around I saw a post of some guy who switched it to channel 4 even though 4 had other competing networks and viola, instantly my pings dropped to 1.5ms.  No idea why it is like this but worked for me.

Other things to try would be:

  • to disable power managment on your card with #iwconfig wlan0 power off
  • Set your wifi to G only. I find that N in apartment complexes is horrendously unreliable and you’re never going to need more than 54mbits anyways unless you are mvoing a lot of files around your lan
  • try disabling ipv6
  • try disabling encryption and just whitelist the computers you want to access your network via mac address filtering.

 

Hope this helps

Tags: , , , , , , ,

Leave a Comment