b-leaver
25-06-2005, 23:44
Hi there,
just very recently I found, that while connected to the WL500 through wireless interface, the pings fluctuate - see this:
[wl500groot@(none) root]$ ping 10.0.0.12
PING 10.0.0.12 (10.0.0.12): 56 data bytes
64 bytes from 10.0.0.12: icmp_seq=0 ttl=128 time=2.6 ms
64 bytes from 10.0.0.12: icmp_seq=1 ttl=128 time=5019.1 ms
64 bytes from 10.0.0.12: icmp_seq=2 ttl=128 time=4021.2 ms
64 bytes from 10.0.0.12: icmp_seq=3 ttl=128 time=3022.6 ms
64 bytes from 10.0.0.12: icmp_seq=4 ttl=128 time=2023.4 ms
64 bytes from 10.0.0.12: icmp_seq=5 ttl=128 time=1023.9 ms
64 bytes from 10.0.0.12: icmp_seq=6 ttl=128 time=24.9 ms
64 bytes from 10.0.0.12: icmp_seq=7 ttl=128 time=72.0 ms
64 bytes from 10.0.0.12: icmp_seq=8 ttl=128 time=95.3 ms
64 bytes from 10.0.0.12: icmp_seq=9 ttl=128 time=16.4 ms
64 bytes from 10.0.0.12: icmp_seq=10 ttl=128 time=40.3 ms
64 bytes from 10.0.0.12: icmp_seq=11 ttl=128 time=62.7 ms
64 bytes from 10.0.0.12: icmp_seq=12 ttl=128 time=4209.7 ms
64 bytes from 10.0.0.12: icmp_seq=13 ttl=128 time=3212.1 ms
64 bytes from 10.0.0.12: icmp_seq=14 ttl=128 time=2214.6 ms
64 bytes from 10.0.0.12: icmp_seq=15 ttl=128 time=1215.6 ms
64 bytes from 10.0.0.12: icmp_seq=15 ttl=128 time=1217.7 ms (DUP!)
64 bytes from 10.0.0.12: icmp_seq=17 ttl=128 time=10.5 ms
64 bytes from 10.0.0.12: icmp_seq=18 ttl=128 time=22.6 ms
64 bytes from 10.0.0.12: icmp_seq=19 ttl=128 time=47.2 ms
64 bytes from 10.0.0.12: icmp_seq=20 ttl=128 time=70.4 ms
64 bytes from 10.0.0.12: icmp_seq=21 ttl=128 time=93.8 ms
64 bytes from 10.0.0.12: icmp_seq=22 ttl=128 time=4367.8 ms
64 bytes from 10.0.0.12: icmp_seq=23 ttl=128 time=3368.8 ms
64 bytes from 10.0.0.12: icmp_seq=24 ttl=128 time=2382.0 ms
64 bytes from 10.0.0.12: icmp_seq=25 ttl=128 time=1384.3 ms
64 bytes from 10.0.0.12: icmp_seq=26 ttl=128 time=386.2 ms
64 bytes from 10.0.0.12: icmp_seq=27 ttl=128 time=29.8 ms
64 bytes from 10.0.0.12: icmp_seq=28 ttl=128 time=53.5 ms
64 bytes from 10.0.0.12: icmp_seq=29 ttl=128 time=77.3 ms
64 bytes from 10.0.0.12: icmp_seq=30 ttl=128 time=99.5 ms
64 bytes from 10.0.0.12: icmp_seq=31 ttl=128 time=21.4 ms
64 bytes from 10.0.0.12: icmp_seq=32 ttl=128 time=4643.8 ms
64 bytes from 10.0.0.12: icmp_seq=33 ttl=128 time=3644.8 ms
64 bytes from 10.0.0.12: icmp_seq=34 ttl=128 time=2645.7 ms
64 bytes from 10.0.0.12: icmp_seq=35 ttl=128 time=1647.6 ms
64 bytes from 10.0.0.12: icmp_seq=36 ttl=128 time=983.6 ms
64 bytes from 10.0.0.12: icmp_seq=37 ttl=128 time=2.3 ms
64 bytes from 10.0.0.12: icmp_seq=38 ttl=128 time=83.5 ms
64 bytes from 10.0.0.12: icmp_seq=39 ttl=128 time=2.4 ms
64 bytes from 10.0.0.12: icmp_seq=40 ttl=128 time=27.7 ms
64 bytes from 10.0.0.12: icmp_seq=41 ttl=128 time=50.9 ms
64 bytes from 10.0.0.12: icmp_seq=42 ttl=128 time=4712.6 ms
64 bytes from 10.0.0.12: icmp_seq=43 ttl=128 time=3726.3 ms
64 bytes from 10.0.0.12: icmp_seq=44 ttl=128 time=2727.7 ms
64 bytes from 10.0.0.12: icmp_seq=45 ttl=128 time=1728.2 ms
64 bytes from 10.0.0.12: icmp_seq=46 ttl=128 time=730.1 ms
64 bytes from 10.0.0.12: icmp_seq=47 ttl=128 time=73.8 ms
64 bytes from 10.0.0.12: icmp_seq=48 ttl=128 time=10.9 ms
64 bytes from 10.0.0.12: icmp_seq=49 ttl=128 time=34.0 ms
64 bytes from 10.0.0.12: icmp_seq=50 ttl=128 time=58.0 ms
--- 10.0.0.12 ping statistics ---
51 packets transmitted, 50 packets received, 1 duplicates, 1% packet loss
round-trip min/avg/max = 2.3/1322.4/5019.1 ms
[wl500groot@(none) root]$
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
There is no problem while being connected through a network cable.
I tried rebooting the router a few times but it didn't help.
Has anybody experienced that before? Could anyone give me a clue about what could cause this problem or how to fix it?
Any clues would be appreciated.
Thanks
Tom
just very recently I found, that while connected to the WL500 through wireless interface, the pings fluctuate - see this:
[wl500groot@(none) root]$ ping 10.0.0.12
PING 10.0.0.12 (10.0.0.12): 56 data bytes
64 bytes from 10.0.0.12: icmp_seq=0 ttl=128 time=2.6 ms
64 bytes from 10.0.0.12: icmp_seq=1 ttl=128 time=5019.1 ms
64 bytes from 10.0.0.12: icmp_seq=2 ttl=128 time=4021.2 ms
64 bytes from 10.0.0.12: icmp_seq=3 ttl=128 time=3022.6 ms
64 bytes from 10.0.0.12: icmp_seq=4 ttl=128 time=2023.4 ms
64 bytes from 10.0.0.12: icmp_seq=5 ttl=128 time=1023.9 ms
64 bytes from 10.0.0.12: icmp_seq=6 ttl=128 time=24.9 ms
64 bytes from 10.0.0.12: icmp_seq=7 ttl=128 time=72.0 ms
64 bytes from 10.0.0.12: icmp_seq=8 ttl=128 time=95.3 ms
64 bytes from 10.0.0.12: icmp_seq=9 ttl=128 time=16.4 ms
64 bytes from 10.0.0.12: icmp_seq=10 ttl=128 time=40.3 ms
64 bytes from 10.0.0.12: icmp_seq=11 ttl=128 time=62.7 ms
64 bytes from 10.0.0.12: icmp_seq=12 ttl=128 time=4209.7 ms
64 bytes from 10.0.0.12: icmp_seq=13 ttl=128 time=3212.1 ms
64 bytes from 10.0.0.12: icmp_seq=14 ttl=128 time=2214.6 ms
64 bytes from 10.0.0.12: icmp_seq=15 ttl=128 time=1215.6 ms
64 bytes from 10.0.0.12: icmp_seq=15 ttl=128 time=1217.7 ms (DUP!)
64 bytes from 10.0.0.12: icmp_seq=17 ttl=128 time=10.5 ms
64 bytes from 10.0.0.12: icmp_seq=18 ttl=128 time=22.6 ms
64 bytes from 10.0.0.12: icmp_seq=19 ttl=128 time=47.2 ms
64 bytes from 10.0.0.12: icmp_seq=20 ttl=128 time=70.4 ms
64 bytes from 10.0.0.12: icmp_seq=21 ttl=128 time=93.8 ms
64 bytes from 10.0.0.12: icmp_seq=22 ttl=128 time=4367.8 ms
64 bytes from 10.0.0.12: icmp_seq=23 ttl=128 time=3368.8 ms
64 bytes from 10.0.0.12: icmp_seq=24 ttl=128 time=2382.0 ms
64 bytes from 10.0.0.12: icmp_seq=25 ttl=128 time=1384.3 ms
64 bytes from 10.0.0.12: icmp_seq=26 ttl=128 time=386.2 ms
64 bytes from 10.0.0.12: icmp_seq=27 ttl=128 time=29.8 ms
64 bytes from 10.0.0.12: icmp_seq=28 ttl=128 time=53.5 ms
64 bytes from 10.0.0.12: icmp_seq=29 ttl=128 time=77.3 ms
64 bytes from 10.0.0.12: icmp_seq=30 ttl=128 time=99.5 ms
64 bytes from 10.0.0.12: icmp_seq=31 ttl=128 time=21.4 ms
64 bytes from 10.0.0.12: icmp_seq=32 ttl=128 time=4643.8 ms
64 bytes from 10.0.0.12: icmp_seq=33 ttl=128 time=3644.8 ms
64 bytes from 10.0.0.12: icmp_seq=34 ttl=128 time=2645.7 ms
64 bytes from 10.0.0.12: icmp_seq=35 ttl=128 time=1647.6 ms
64 bytes from 10.0.0.12: icmp_seq=36 ttl=128 time=983.6 ms
64 bytes from 10.0.0.12: icmp_seq=37 ttl=128 time=2.3 ms
64 bytes from 10.0.0.12: icmp_seq=38 ttl=128 time=83.5 ms
64 bytes from 10.0.0.12: icmp_seq=39 ttl=128 time=2.4 ms
64 bytes from 10.0.0.12: icmp_seq=40 ttl=128 time=27.7 ms
64 bytes from 10.0.0.12: icmp_seq=41 ttl=128 time=50.9 ms
64 bytes from 10.0.0.12: icmp_seq=42 ttl=128 time=4712.6 ms
64 bytes from 10.0.0.12: icmp_seq=43 ttl=128 time=3726.3 ms
64 bytes from 10.0.0.12: icmp_seq=44 ttl=128 time=2727.7 ms
64 bytes from 10.0.0.12: icmp_seq=45 ttl=128 time=1728.2 ms
64 bytes from 10.0.0.12: icmp_seq=46 ttl=128 time=730.1 ms
64 bytes from 10.0.0.12: icmp_seq=47 ttl=128 time=73.8 ms
64 bytes from 10.0.0.12: icmp_seq=48 ttl=128 time=10.9 ms
64 bytes from 10.0.0.12: icmp_seq=49 ttl=128 time=34.0 ms
64 bytes from 10.0.0.12: icmp_seq=50 ttl=128 time=58.0 ms
--- 10.0.0.12 ping statistics ---
51 packets transmitted, 50 packets received, 1 duplicates, 1% packet loss
round-trip min/avg/max = 2.3/1322.4/5019.1 ms
[wl500groot@(none) root]$
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
There is no problem while being connected through a network cable.
I tried rebooting the router a few times but it didn't help.
Has anybody experienced that before? Could anyone give me a clue about what could cause this problem or how to fix it?
Any clues would be appreciated.
Thanks
Tom