FastNetMon

Sunday 7 March 2010

Мистика с traceroute

Имеем вот такую картину:

while true; do traceroute 192.168.0.2; done
traceroute to 192.168.0.2 (192.168.0.2), 30 hops max, 60 byte packets
1 192.168.0.2 (192.168.0.2) 0.044 ms 0.041 ms 0.039 ms
traceroute to 192.168.0.2 (192.168.0.2), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * 192.168.0.2 (192.168.0.2) 0.042 ms 0.027 ms
traceroute to 192.168.0.2 (192.168.0.2), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * 192.168.0.2 (192.168.0.2) 0.053 ms 0.041 ms
traceroute to 192.168.0.2 (192.168.0.2), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * 192.168.0.2 (192.168.0.2) 0.042 ms 0.044 ms
traceroute to 192.168.0.2 (192.168.0.2), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * 192.168.0.2 (192.168.0.2) 0.046 ms 0.034 ms
traceroute to 192.168.0.2 (192.168.0.2), 30 hops max, 60 byte packets^C


Но при этом mtr выдает нулевые потери и ping также в норме:
ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=0.051 ms
^C
--- 192.168.0.2 ping statistics ---
25 packets transmitted, 25 received, 0% packet loss, time 24018ms
rtt min/avg/max/mdev = 0.038/0.052/0.115/0.018 ms


Что такое может быть и как это диагностировать иначе как while traceroute? Должна же быть тулза :)

No comments :

Post a Comment

Note: only a member of this blog may post a comment.