You are not logged in.

Pages: 1

#1 2012-05-04 14:58:05

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

[solved] Huge latency with wicd and netcfg on wifi after few minutes

I am connecting to my personal wifi via wicd or netcfg. Since yesterday, I have noticed that I am having an enormous latency when opening web sites. At first I thought, this might be due to my ISP or my Wifi Router, but restarting both did not do anything. However, if I disconnect my connection to the router and reconnect, latencies are back to normal. This usually lasts a few minutes, before the latencies become unbearable again.

I strongly believe this has something to do with a recent update and/or my system itself, because right after reconnection to the wifi pinging any website works well, and I observe this every single time (without restarting the router or resetting my cable modem).

Here is a ping to google, with my computer being connected to the wifi for a few minutes:

$ ping www.google.com
PING www.l.google.com (173.194.69.147) 56(84) bytes of data.
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=1 ttl=46 time=1777 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=2 ttl=46 time=1869 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=3 ttl=46 time=28.5 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=4 ttl=46 time=30.3 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=5 ttl=46 time=28.7 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=6 ttl=46 time=29.9 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=7 ttl=46 time=30.4 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=8 ttl=46 time=29.7 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=9 ttl=46 time=28.5 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=10 ttl=46 time=29.6 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=11 ttl=46 time=32.5 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=12 ttl=46 time=31.5 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=13 ttl=46 time=363 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=14 ttl=46 time=420 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=15 ttl=46 time=454 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=16 ttl=46 time=490 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=17 ttl=46 time=648 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=18 ttl=46 time=968 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=19 ttl=46 time=1589 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=20 ttl=46 time=1909 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=21 ttl=46 time=1639 ms
64 bytes from bk-in-f147.1e100.net (173.194.69.147): icmp_req=22 ttl=46 time=1064 ms
^C
--- www.l.google.com ping statistics ---
23 packets transmitted, 22 received, 4% packet loss, time 31117ms
rtt min/avg/max/mdev = 28.550/613.479/1909.637/690.699 ms, pipe 2

A ping to the router:

$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_req=1 ttl=64 time=2.33 ms
64 bytes from 192.168.0.1: icmp_req=2 ttl=64 time=2.46 ms
64 bytes from 192.168.0.1: icmp_req=3 ttl=64 time=3.15 ms
64 bytes from 192.168.0.1: icmp_req=4 ttl=64 time=2.14 ms
64 bytes from 192.168.0.1: icmp_req=5 ttl=64 time=2.48 ms
64 bytes from 192.168.0.1: icmp_req=6 ttl=64 time=2.44 ms
64 bytes from 192.168.0.1: icmp_req=7 ttl=64 time=2.14 ms
64 bytes from 192.168.0.1: icmp_req=8 ttl=64 time=2.45 ms
64 bytes from 192.168.0.1: icmp_req=9 ttl=64 time=1.61 ms
64 bytes from 192.168.0.1: icmp_req=10 ttl=64 time=2.46 ms
64 bytes from 192.168.0.1: icmp_req=11 ttl=64 time=2.44 ms
64 bytes from 192.168.0.1: icmp_req=12 ttl=64 time=1.90 ms
64 bytes from 192.168.0.1: icmp_req=13 ttl=64 time=2.47 ms
64 bytes from 192.168.0.1: icmp_req=14 ttl=64 time=2.46 ms
^C
--- 192.168.0.1 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13019ms
rtt min/avg/max/mdev = 1.612/2.356/3.154/0.336 ms

Here is to Google right after I reconnected my computer to the wifi:

$ ping www.google.com
PING www.l.google.com (173.194.69.106) 56(84) bytes of data.
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=1 ttl=46 time=29.2 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=2 ttl=46 time=29.0 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=3 ttl=46 time=28.8 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=4 ttl=46 time=32.1 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=5 ttl=46 time=29.4 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=6 ttl=46 time=29.9 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=7 ttl=46 time=30.2 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=8 ttl=46 time=29.3 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=9 ttl=46 time=29.7 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=10 ttl=46 time=30.5 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=11 ttl=46 time=30.3 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=12 ttl=46 time=30.8 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=13 ttl=46 time=31.5 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=14 ttl=46 time=30.4 ms
64 bytes from bk-in-f106.1e100.net (173.194.69.106): icmp_req=15 ttl=46 time=29.3 ms
^C
--- www.l.google.com ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14021ms
rtt min/avg/max/mdev = 28.878/30.072/32.110/0.917 ms

Router:

$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_req=1 ttl=64 time=2.46 ms
64 bytes from 192.168.0.1: icmp_req=2 ttl=64 time=2.40 ms
64 bytes from 192.168.0.1: icmp_req=3 ttl=64 time=1.38 ms
64 bytes from 192.168.0.1: icmp_req=4 ttl=64 time=2.13 ms
64 bytes from 192.168.0.1: icmp_req=5 ttl=64 time=2.45 ms
64 bytes from 192.168.0.1: icmp_req=6 ttl=64 time=2.44 ms
64 bytes from 192.168.0.1: icmp_req=7 ttl=64 time=2.48 ms
64 bytes from 192.168.0.1: icmp_req=8 ttl=64 time=2.52 ms
64 bytes from 192.168.0.1: icmp_req=9 ttl=64 time=2.46 ms
64 bytes from 192.168.0.1: icmp_req=10 ttl=64 time=2.51 ms
64 bytes from 192.168.0.1: icmp_req=11 ttl=64 time=2.49 ms
64 bytes from 192.168.0.1: icmp_req=12 ttl=64 time=2.47 ms
^C
--- 192.168.0.1 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11015ms
rtt min/avg/max/mdev = 1.385/2.353/2.522/0.313 ms

Last edited by Stalafin (2012-05-05 12:50:24)

Offline

#2 2012-05-05 00:19:32

mr.MikyMaus
Member
From: disabled
Registered: 2006-03-31
Posts: 285

Re: [solved] Huge latency with wicd and netcfg on wifi after few minutes

I'd guess there might be a problem on the router rather than on your desktop as router latencies are the same in both cases. Is the router in your possession or is it ISP's?

What happened to Arch's KISS? systemd sure is stupid but I must have missed the simple part ...

... and who is general Failure and why is he reading my harddisk?

Offline

#3 2012-05-05 12:49:49

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

Re: [solved] Huge latency with wicd and netcfg on wifi after few minutes

Turns out that my observations where purely coincidental (what's the chance of that happening!).

I guess the problem is indeed with my cable modem. I hooked it up to my computer directly via ethernet, and I get random increases in latencies. Let's see how long it's going to take my ISP to sort this out. sad

Offline

Pages: 1

Board footer

Powered by FluxBB