From: "Dotan Cohen" <dotancohen@xxxxxxxxx>
On 03/07/06, jdow <jdow@xxxxxxxxxxxxx> wrote:
What happens when you ping the router?
$ ping 192.168.123.254
PING 192.168.123.254 (192.168.123.254) 56(84) bytes of data.
64 bytes from 192.168.123.254: icmp_seq=1 ttl=64 time=0.399 ms
64 bytes from 192.168.123.254: icmp_seq=2 ttl=64 time=0.381 ms
64 bytes from 192.168.123.254: icmp_seq=3 ttl=64 time=0.388 ms
64 bytes from 192.168.123.254: icmp_seq=4 ttl=64 time=0.384 ms
64 bytes from 192.168.123.254: icmp_seq=5 ttl=64 time=0.362 ms
64 bytes from 192.168.123.254: icmp_seq=6 ttl=64 time=0.382 ms
64 bytes from 192.168.123.254: icmp_seq=7 ttl=64 time=0.381 ms
64 bytes from 192.168.123.254: icmp_seq=8 ttl=64 time=0.377 ms
64 bytes from 192.168.123.254: icmp_seq=9 ttl=64 time=0.378 ms
64 bytes from 192.168.123.254: icmp_seq=10 ttl=64 time=0.374 ms
--- 192.168.123.254 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9007ms
rtt min/avg/max/mdev = 0.362/0.380/0.399/0.023 ms
If you let it ping a long time and see no lost packets then the
connection to the router is happy. Then you can take the MTR
results and stretch your pings out into the network and see where
the packet loss begins. Just go outwards one hop at a time. When
you find the source of the problem you then know who to bother
about it. (The MTR results MAY be indicative of where the problem
lies. And if you put a "-i 5" in the ping any rate limiting will
probably not be triggered.)
{^_^}
