Oscillating wireless ping times

[adam_0]

On wired, I get ~75ms ping times to google.com. While on wireless (2.4 GHz or 5 GHz) my ping times vary wildly, but generally oscillate between ~90ms (good) and somewhere around 300ms, for 5 seconds each:

64 bytes from 74.125.21.100: icmp_seq=64 ttl=39 time=420.126 ms
64 bytes from 74.125.21.100: icmp_seq=65 ttl=39 time=510.634 ms
64 bytes from 74.125.21.100: icmp_seq=66 ttl=39 time=950.772 ms
64 bytes from 74.125.21.100: icmp_seq=67 ttl=39 time=117.326 ms
64 bytes from 74.125.21.100: icmp_seq=68 ttl=39 time=85.239 ms
64 bytes from 74.125.21.100: icmp_seq=69 ttl=39 time=86.720 ms
64 bytes from 74.125.21.100: icmp_seq=70 ttl=39 time=139.508 ms
64 bytes from 74.125.21.100: icmp_seq=71 ttl=39 time=182.663 ms
64 bytes from 74.125.21.100: icmp_seq=72 ttl=39 time=222.398 ms
64 bytes from 74.125.21.100: icmp_seq=73 ttl=39 time=276.264 ms
64 bytes from 74.125.21.100: icmp_seq=74 ttl=39 time=236.103 ms
64 bytes from 74.125.21.100: icmp_seq=75 ttl=39 time=283.544 ms
64 bytes from 74.125.21.100: icmp_seq=76 ttl=39 time=77.580 ms
64 bytes from 74.125.21.100: icmp_seq=77 ttl=39 time=75.784 ms
64 bytes from 74.125.21.100: icmp_seq=78 ttl=39 time=76.048 ms
64 bytes from 74.125.21.100: icmp_seq=79 ttl=39 time=74.436 ms
64 bytes from 74.125.21.100: icmp_seq=80 ttl=39 time=81.681 ms
64 bytes from 74.125.21.100: icmp_seq=81 ttl=39 time=111.053 ms
64 bytes from 74.125.21.100: icmp_seq=82 ttl=39 time=167.412 ms
64 bytes from 74.125.21.100: icmp_seq=83 ttl=39 time=205.886 ms
64 bytes from 74.125.21.100: icmp_seq=84 ttl=39 time=282.286 ms
64 bytes from 74.125.21.100: icmp_seq=85 ttl=39 time=519.096 ms
64 bytes from 74.125.21.100: icmp_seq=86 ttl=39 time=375.642 ms
64 bytes from 74.125.21.100: icmp_seq=87 ttl=39 time=304.228 ms
64 bytes from 74.125.21.100: icmp_seq=88 ttl=39 time=348.099 ms
64 bytes from 74.125.21.100: icmp_seq=89 ttl=39 time=79.159 ms
64 bytes from 74.125.21.100: icmp_seq=90 ttl=39 time=79.295 ms
64 bytes from 74.125.21.100: icmp_seq=91 ttl=39 time=82.623 ms
64 bytes from 74.125.21.100: icmp_seq=92 ttl=39 time=80.923 ms

I have:

When I plugged in my computer via ethernet? Instant 75ms ping times, consistently.

The laptop has been about 3 feet from the router during all of this, so I doubt there's a distance issue. I can't think of anything that has caused this change in the last week, and I'm a bit perplexed at how to continue. Please help!

Adam

[Babylon5]

Have you tried any other WiFi devices (computers) for comparison purposes?

[John66]

I have what i think is a similar problem.

this happens if im 2 feet from the router or 20 feet from the router.

I have tested with support for hours.  

we factory reset the router.

upgraded the firmware, downgraded the firmware.

did a factory reset.  

connected to the router via wifi. no network cables plugged in at all. rule out all outside configurtion or environmental issues. this problem exists no matter what.

this happens on all three radios 2.4 and both 5.0

the good thing with me is that my router is under warrentee. they are sending me a new one.

I hope my problem is solved when the new router gets here

64 bytes from 192.168.2.2: icmp_seq=3 ttl=64 time=2757.182 ms

64 bytes from 192.168.2.2: icmp_seq=4 ttl=64 time=1752.776 ms

64 bytes from 192.168.2.2: icmp_seq=5 ttl=64 time=749.171 ms

64 bytes from 192.168.2.2: icmp_seq=6 ttl=64 time=2.956 ms

64 bytes from 192.168.2.2: icmp_seq=7 ttl=64 time=2.034 ms

64 bytes from 192.168.2.2: icmp_seq=8 ttl=64 time=1.855 ms

64 bytes from 192.168.2.2: icmp_seq=9 ttl=64 time=1.860 ms

64 bytes from 192.168.2.2: icmp_seq=10 ttl=64 time=2.139 ms

64 bytes from 192.168.2.2: icmp_seq=12 ttl=64 time=1756.133 ms

64 bytes from 192.168.2.2: icmp_seq=13 ttl=64 time=1010.901 ms

64 bytes from 192.168.2.2: icmp_seq=14 ttl=64 time=13.860 ms

64 bytes from 192.168.2.2: icmp_seq=15 ttl=64 time=4.252 ms

64 bytes from 192.168.2.2: icmp_seq=16 ttl=64 time=1.799 ms

64 bytes from 192.168.2.2: icmp_seq=17 ttl=64 time=4.029 ms

64 bytes from 192.168.2.2: icmp_seq=18 ttl=64 time=1.858 ms

64 bytes from 192.168.2.2: icmp_seq=19 ttl=64 time=3.241 ms

64 bytes from 192.168.2.2: icmp_seq=20 ttl=64 time=1.885 ms

64 bytes from 192.168.2.2: icmp_seq=21 ttl=64 time=1288.081 ms

64 bytes from 192.168.2.2: icmp_seq=22 ttl=64 time=1021.038 ms

64 bytes from 192.168.2.2: icmp_seq=23 ttl=64 time=752.127 ms

64 bytes from 192.168.2.2: icmp_seq=24 ttl=64 time=10.634 ms

64 bytes from 192.168.2.2: icmp_seq=25 ttl=64 time=1.852 ms

64 bytes from 192.168.2.2: icmp_seq=26 ttl=64 time=2.600 ms

64 bytes from 192.168.2.2: icmp_seq=27 ttl=64 time=2.129 ms

64 bytes from 192.168.2.2: icmp_seq=28 ttl=64 time=3.804 ms

64 bytes from 192.168.2.2: icmp_seq=29 ttl=64 time=2.903 ms

64 bytes from 192.168.2.2: icmp_seq=30 ttl=64 time=2.871 ms

64 bytes from 192.168.2.2: icmp_seq=31 ttl=64 time=657.653 ms

64 bytes from 192.168.2.2: icmp_seq=32 ttl=64 time=1048.178 ms

64 bytes from 192.168.2.2: icmp_seq=33 ttl=64 time=47.934 ms

64 bytes from 192.168.2.2: icmp_seq=34 ttl=64 time=36.473 ms

64 bytes from 192.168.2.2: icmp_seq=35 ttl=64 time=4.830 ms

64 bytes from 192.168.2.2: icmp_seq=36 ttl=64 time=1.867 ms

64 bytes from 192.168.2.2: icmp_seq=37 ttl=64 time=1.922 ms

64 bytes from 192.168.2.2: icmp_seq=38 ttl=64 time=2.703 ms

64 bytes from 192.168.2.2: icmp_seq=39 ttl=64 time=3.347 ms

[ElaineM]

Thanks for the info @John66

Let us know if you will be getting the same problem once you have the new one.

[John66]

I have solved this issue at least for my environment.

When the new router showed up i pluged it in and did not change anything. I set up the ping test and the same issue was there. In the end the issue had nothing to do with the router. In my envronment i had more than 1 wireless client displaying the symptoms. This lead me to beleive that it had to be the router. In the end a driver update on the windows wireless client and a firmware update on the macbook corrected my issues. The wireless driver in the macbook was crashing and restarting over and over. it can be confirmed by looking in the console logs. 

[ElaineM]

Thank you for the update.

Do you mind posting the exact model of the wireless client you're using on the windows machine?

This will surely help others too.