Re: jakiś fuckup cdp/atm - tpsa ?

Użytkownik "Marek Burzyński" <m.burzynski@cyberbajt.pl> napisał w wiadomości
news:f9pdbg$9ub$1@inews.gazeta.pl...
> [marek@Router_new] tool> traceroute
> address: lg.atman.pl
> ADDRESS STATUS
> 1 80.50.236.117 617ms 307ms timeout
> 2 195.117.0.214 72ms 13ms 13ms
> 3 195.116.0.126 13ms 22ms 14ms
> 4 217.17.32.2 14ms 13ms 13ms
> 5 217.17.34.82 13ms 13ms 14ms
>
> z kolei w druga stronę:
>
> Router: Business.Internet
>
>
> traceroute to 80.50.236.118 (80.50.236.118), 10 hops max, 40 byte packets
> 1 r3.isp-r2.isp.atman.pl (85.232.232.254) 1.042 ms 0.733 ms 0.825 ms
> 2 z-atman.tpnet.pl (195.116.0.125) 3.892 ms 78.931 ms 1.095 ms
> 3 195.117.0.190 (195.117.0.190) 339.881 ms 239.864 ms *
> 4 * * *
> 5 * * *
> 6 * * *
>
> [marek@Router_new] tool> traceroute 89.171.78.202
> ADDRESS STATUS
> 1 80.50.236.117 timeout 255ms timeout
> 2 195.205.0.42 14ms 13ms 13ms
> 3 80.50.236.174 204ms 211ms 211ms
> 4 62.111.222.242 264ms 205ms timeout
> 5 0.0.0.0 timeout timeout timeout
> 6 0.0.0.0 timeout timeout timeout
> 7 0.0.0.0 timeout timeout timeout
> 8 0.0.0.0 timeout timeout timeout
> 9 0.0.0.0 timeout timeout timeout
> 10 0.0.0.0 timeout timeout timeout
> 11 0.0.0.0 timeout timeout timeout
> 12 0.0.0.0 timeout timeout timeout
> 13 0.0.0.0 timeout timeout timeout
> 14 0.0.0.0 timeout timeout timeout
> 15 0.0.0.0 timeout timeout timeout
> 16 0.0.0.0 timeout timeout timeout
> 17 0.0.0.0 timeout timeout timeout
> 18 0.0.0.0 timeout timeout timeout
> 19 0.0.0.0 timeout timeout timeout
> 20 0.0.0.0 timeout timeout timeout
> 21 0.0.0.0 timeout timeout timeout
> 22 0.0.0.0 timeout timeout timeout
> 23 0.0.0.0 timeout timeout timeout
> 24 0.0.0.0 timeout timeout timeout
> 25 0.0.0.0 timeout timeout timeout
> 26 0.0.0.0 timeout timeout timeout
> 27 0.0.0.0 timeout timeout timeout
> 28 0.0.0.0 timeout timeout timeout
> 29 0.0.0.0 timeout timeout timeout
> 30 0.0.0.0 timeout timeout timeout
> max-hops reached
> [marek@Router_new] tool>
>
> i w drugą stronę:
>
>
> C:\Documents and Settings\Marek>tracert 80.50.236.118
>
> Trasa śledzenia do 80.50.236.118 przewyższa maksymalną liczbę przeskoków
> 30
>
> 1 <1 ms <1 ms <1 ms 192.168.1.1
> 2 5 ms 5 ms 5 ms ip-89.171.78.201.crowley.pl
> [89.171.78.201]
> 3 5 ms 5 ms 5 ms jp1-2-r2-core.crowley.pl [62.111.222.241]
> 4 198 ms 200 ms 310 ms z-crowley.tpnet.pl [80.50.236.173]
> 5 * * * Upłynął limit czasu żądania.
> 6 212 ms 215 ms * 80.50.236.118
> 7 213 ms * 212 ms 80.50.236.118
>
> Śledzenie zakończone.
>
> C:\Documents and Settings\Marek>
>
> [marek@Router_new] tool> traceroute onet.pl
> ADDRESS STATUS
> 1 80.50.236.117 389ms 332ms 844ms
> 2 195.117.0.206 20ms 17ms 19ms
> 3 213.77.0.38 18ms 18ms 18ms
> 4 213.180.143.34 21ms 20ms 18ms
> 5 213.180.130.200 18ms 20ms 19ms
>
> [marek@Router_new] tool> traceroute pl-ix.pl
> ADDRESS STATUS
> 1 80.50.236.117 225ms 607ms 348ms network unreachable
> 2 80.50.236.117 273ms 66ms 174ms network unreachable
> 3 80.50.236.117 174ms 122ms 154ms network unreachable
> 4 80.50.236.117 109ms 185ms 177ms network unreachable
> 5 80.50.236.117 107ms 169ms timeout network unreachable
> 6 80.50.236.117 timeout 69ms 124ms network unreachable
> 7 80.50.236.117 233ms 108ms 138ms network unreachable
> 8 80.50.236.117 172ms 139ms 734ms network unreachable
> 9 80.50.236.117 191ms 114ms timeout network unreachable
> 10 0.0.0.0 timeout timeout timeout
> 11 0.0.0.0 timeout timeout timeout
> 12 80.50.236.117 timeout timeout 135ms network unreachable
> 13 80.50.236.117 114ms 112ms 68ms network unreachable
> 14 80.50.236.117 172ms 128ms 156ms network unreachable
> 15 80.50.236.117 138ms 103ms 173ms network unreachable
> 16 80.50.236.117 765ms timeout timeout network unreachable
> 17 0.0.0.0 timeout timeout timeout
> 18 80.50.236.117 timeout timeout 185ms network unreachable
> 19 80.50.236.117 117ms 91ms 527ms network unreachable
> 20 80.50.236.117 496ms 317ms 69ms network unreachable
> 21 80.50.236.117 113ms 113ms 117ms network unreachable
> 22 80.50.236.117 120ms 115ms timeout network unreachable
> 23 0.0.0.0 timeout timeout timeout
> [marek@Router_new] tool>
>
>
> to tylko u mnie ?
>
>
> --
> Marek Burzyński
> www.cyberbajt.pl | www.cyberbajt.com

z lg.tpnet.pl to wyglada dziwnie :

raz tak

1 z-ar2-do-szcz.srd2.tpnet.pl (80.50.231.205) 12 msec 48 msec 72 msec
  2 do-war-r3-war-ar1.tpnet.pl (195.205.0.214) 12 msec 16 msec 12 msec
  3 r3.isp-r2.isp.atman.pl (85.232.232.254) [AS 15694] 12 msec 12 msec 12
msec

a chwile potem tak

1 z-ar2-do-szcz.srd2.tpnet.pl (80.50.231.205) 12 msec 12 msec 12 msec
  2 do-atman-war-ar1.tpnet.pl (195.117.0.30) 12 msec
    do-war-ar1-z-war-r4.war-ar1.tpnet.pl (195.117.0.214) 12 msec
    do-war-r3-war-ar1.tpnet.pl (195.205.0.214) 12 msec
  3 r3.isp-r2.isp.atman.pl (85.232.232.254) [AS 15694] 12 msec 12 msec 12
msec

Load-balancing jakis dziwaczny czy cus ?

CSL
Received on Mon Aug 13 14:20:07 2007