Autor: Krzysztof Oledzki (ole_at_a.ns.pl)
Data: Fri 30 Apr 2004 - 12:33:59 MET DST
Przemyslaw Frasunek <venglin_at_pisz.na.niusy> wrote:
> futszaK <futszak_at_post.pl> napisał(a):
>
>> PING rosnowo.jarsat.pl (213.209.165.202): 56 data bytes
>> 64 bytes from 213.209.165.202: icmp_seq=0 ttl=39 time=2986.032 ms
>> 64 bytes from 213.209.165.202: icmp_seq=1 ttl=39 time=2926.096 ms
>> 64 bytes from 213.209.165.202: icmp_seq=2 ttl=39 time=2780.941 ms
>
> 10. 213.156.58.86 0% 3 3 62 62
> 63 63
> 11. 213.209.160.225 0% 3 3 63 61
> 104 187
> 12. 213.209.165.202 0% 3 3 57 49
> 53 57
mtr:
11. 213.156.35.15 0% 3 3 60 49 56 60
12. 213.156.58.86 0% 3 3 66 47 57 66
13. 213.209.160.225 0% 3 3 62 44 60 73
14. 213.209.165.202 0% 2 2 46 45 45 46
ping:
64 bytes from 213.209.165.202: icmp_seq=1 ttl=46 time=738.712 ms
64 bytes from 213.209.165.202: icmp_seq=2 ttl=46 time=723.927 ms
64 bytes from 213.209.165.202: icmp_seq=3 ttl=46 time=801.120 ms
64 bytes from 213.209.165.202: icmp_seq=4 ttl=46 time=842.932 ms
64 bytes from 213.209.165.202: icmp_seq=6 ttl=46 time=685.187 ms
Paaaanie - czary ;-)
..
..
..
Po prostu 213.209.165.202 generuje inne czasy z ICMP echo reply a inne
z ICMP time exceeded, a dla ttl=14, owszem - przychodzi odpowiedz z
adresu 213.209.165.202 ale:
12:28:10.818029 213.209.165.202 > XXX.XXX.XXX.XXX: icmp: time exceeded in-transit [tos 0xc0] (ttl 241, id 24918, len 56)
Co dziwne - ping z ttl=14 generuje wlasnie time exceeded, 15-17 nic, a dopiero 18 echo replay.
Zapewne to jest jakiś DNAT czy co...
Pozdrawiam,
Krzysztof Oledzki
-- Krzysztof Olędzki e-mail address: ole(a-t)ans(d-o-t)pl Linux Registered User: 189200 BSD Registered User: 51140 Nick Handles: KO60-RIPE, KO60-6BONE, KO581 (Network Solutions)
To archiwum zostało wygenerowane przez hypermail 2.1.7 : Wed 19 May 2004 - 18:16:50 MET DST