Wifi Router from hell, massive latency and packet loss
by browny_amiga from LinuxQuestions.org on (#56Z3H)
Hi,
I just moved into a new place here and they seem to have a wifi router straight from hell, it is the worse POS I have ever see in my life, the speed is supposed to be around 50 mbit, but it goes down to like 3 kb/s transfer rate, then the latency is through the roof, massive packet loss, when pinging, the latency goes up and down like an akordeon, sometimes reaching stupid 5000 ms.
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=55 ttl=116 time=421 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=56 ttl=116 time=407 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=58 ttl=116 time=241 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=59 ttl=116 time=485 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=60 ttl=116 time=270 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=61 ttl=116 time=222 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=62 ttl=116 time=356 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=63 ttl=116 time=840 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=64 ttl=116 time=331 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=65 ttl=116 time=780 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=67 ttl=116 time=234 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=68 ttl=116 time=1365 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=76 ttl=116 time=2393 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=77 ttl=116 time=1370 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=78 ttl=116 time=348 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=79 ttl=116 time=338 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=83 ttl=116 time=427 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=84 ttl=116 time=666 ms
^C
--- www.google.com ping statistics ---
85 packets transmitted, 50 received, 41.1765% packet loss, time 568ms
rtt min/avg/max/mdev = 125.441/574.320/2393.491/444.944 ms, pipe 3
What is going on here? This is on comcast and using their routers that has a cable modem built in.
I have so far always avoided them and knowing what a horrible company that is, I degraded it as a cable modem only and used my own devices which run OpenWRT, which is excellent.
It is pretty close to that router, I have a strong signal. They are not using a lot of bandwith, the people here are hardly tech savy, so oversaturation can be ruled out. There are also no strong EM fields around, everybody is sleeping right now.
On all my other networks, I usually have ZERO package loss, as this is an indicator of something really going wrong.
I just moved into a new place here and they seem to have a wifi router straight from hell, it is the worse POS I have ever see in my life, the speed is supposed to be around 50 mbit, but it goes down to like 3 kb/s transfer rate, then the latency is through the roof, massive packet loss, when pinging, the latency goes up and down like an akordeon, sometimes reaching stupid 5000 ms.
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=55 ttl=116 time=421 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=56 ttl=116 time=407 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=58 ttl=116 time=241 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=59 ttl=116 time=485 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=60 ttl=116 time=270 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=61 ttl=116 time=222 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=62 ttl=116 time=356 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=63 ttl=116 time=840 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=64 ttl=116 time=331 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=65 ttl=116 time=780 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=67 ttl=116 time=234 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=68 ttl=116 time=1365 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=76 ttl=116 time=2393 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=77 ttl=116 time=1370 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=78 ttl=116 time=348 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=79 ttl=116 time=338 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=83 ttl=116 time=427 ms
64 bytes from sfo07s16-in-f4.1e100.net (216.58.195.68): icmp_seq=84 ttl=116 time=666 ms
^C
--- www.google.com ping statistics ---
85 packets transmitted, 50 received, 41.1765% packet loss, time 568ms
rtt min/avg/max/mdev = 125.441/574.320/2393.491/444.944 ms, pipe 3
What is going on here? This is on comcast and using their routers that has a cable modem built in.
I have so far always avoided them and knowing what a horrible company that is, I degraded it as a cable modem only and used my own devices which run OpenWRT, which is excellent.
It is pretty close to that router, I have a strong signal. They are not using a lot of bandwith, the people here are hardly tech savy, so oversaturation can be ruled out. There are also no strong EM fields around, everybody is sleeping right now.
On all my other networks, I usually have ZERO package loss, as this is an indicator of something really going wrong.