W artykule <cpuil7$av4$1@opal.futuro.pl> Marcin Gontarz napisał(a):
>> ktos cos zaobserwowal ?
>
> hmm
>
> traceroute to 62.75.252.26 (62.75.252.26), 30 hops max, 38 byte packets
> 1 gw-futuro.nowanet.pl (62.233.189.137) 15.620 ms 5.352 ms 3.788 ms
> 2 atm-lub-pub3-lub-cr1.devs.futuro.pl (62.233.128.73) 5.688 ms 5.159 ms
> 4.162 ms
> 3 atm-lub-cr1-waw-br1.devs.futuro.pl (62.233.128.29) 13.052 ms 18.967 ms
> 8.577 ms
> 4 war-b1-geth2-1.telia.net (213.248.79.45) 12.466 ms 8.805 ms 8.153 ms
> 5 hbg-bb2-pos3-2-0.telia.net (213.248.65.33) 248.248 ms 245.409 ms
> 243.921 ms
> 6 hbg-b2-pos0-1-0.telia.net (213.248.65.182) 247.138 ms 260.459 ms
> 254.402 ms
[..]
>
> jak by nie patrzec cos sie zatyka ;-/
>
chyba zalezy gdzie jesteś zapięty

$ traceroute lg.telia.net
traceroute to lg.telia.net (209.170.112.118), 64 hops max, 40 byte packets
1 multiplexer-v1004.core.tvk.wroc.pl (195.140.236.241) 13 ms 0 ms 0 ms
2 AS29512-e3.tvk.wroc.pl (195.140.239.250) 0 ms 0 ms 0 ms
3 Do-ProFuturo.tvk.wroc.pl (62.233.250.97) 17 ms 27 ms 17 ms
4 ge-poz-cr1-poz-br1.devs.futuro.pl (62.233.156.21) 42 ms 73 ms 38 ms
5 pzn-b1-geth1-2.telia.net (213.248.66.81) 29 ms 30 ms 21 ms
6 hbg-bb1-pos1-3-0.telia.net (213.248.64.197) 28 ms 36 ms 30 ms
7 adm-bb1-pos7-0-0.telia.net (213.248.65.153) 36 ms 32 ms 39 ms
[..]