eGospodarka.pl
eGospodarka.pl poleca

eGospodarka.pl › Grupy › pl.internet.polip › jakiś fuckup cdp/atm - tpsa ?
« poprzedni wątek
następny wątek »
Ilość wypowiedzi w tym wątku: 6

  • 1. Data: 2007-08-13 10:55:41
    Temat: jakiś fuckup cdp/atm - tpsa ?
    Od: Marek Burzyński <m...@c...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

    [ pokaż wiadomość z nagłówkami ]
    do góry

  • 2. Data: 2007-08-13 12:00:30
    Temat: Re: jakiś fuckup cdp/atm - tpsa ?
    Od: "Tomasz Śląski" <t...@k...org.pl>

    Marek Burzyński wrote:
    > [marek@Router_new] tool> traceroute
    > address: lg.atman.pl


    U mnie via Pioner SOA#1
    tracert -d ftp.tpnet.pl

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 <1 ms <1 ms <1 ms 194.114.147.241
    3 12 ms 6 ms 4 ms 212.126.28.34
    4 1 ms <1 ms <1 ms 150.254.163.149
    5 4 ms 5 ms 4 ms 212.191.231.89
    6 4 ms 9 ms 9 ms 80.50.231.25
    7 6 ms 6 ms 6 ms 195.117.0.42
    8 6 ms 6 ms 6 ms 80.50.248.77


    > to tylko u mnie ?

    Z noc.gts.pl traceroute nie działa, ale pingi idą
    Pinging ftp.tpnet.pl:
    PING ftp.tpnet.pl (80.50.248.77): 56 data bytes
    64 bytes from 80.50.248.77: icmp_seq=0 ttl=247 time=3.530 ms
    64 bytes from 80.50.248.77: icmp_seq=1 ttl=247 time=10.008 ms
    64 bytes from 80.50.248.77: icmp_seq=2 ttl=247 time=1.726 ms
    64 bytes from 80.50.248.77: icmp_seq=3 ttl=247 time=2.071 ms
    64 bytes from 80.50.248.77: icmp_seq=4 ttl=247 time=3.680 ms
    64 bytes from 80.50.248.77: icmp_seq=5 ttl=247 time=1.741 ms
    64 bytes from 80.50.248.77: icmp_seq=6 ttl=247 time=2.060 ms
    64 bytes from 80.50.248.77: icmp_seq=7 ttl=247 time=1.806 ms
    64 bytes from 80.50.248.77: icmp_seq=8 ttl=247 time=1.870 ms
    64 bytes from 80.50.248.77: icmp_seq=9 ttl=247 time=1.769 ms

    ----ftp.tpnet.pl PING Statistics----
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 1.726/3.026/10.008/2.561 ms
    z lg.tpnet.pl do GTS - idzieTranslating "noc.gts.pl"...domain server
    (194.204.159.1) [OK]

    Type escape sequence to abort.
    Tracing the route to noc.gts.pl (217.153.108.10)

    1 z-ar2-do-szcz.srd2.tpnet.pl (80.50.231.205) 12 msec 16 msec 12 msec
    2 z.gts-ipart.war-ar2.tpnet.pl (80.50.232.198) 12 msec 20 msec 16 msec
    3 157.25.4.53 [AS 6714] 12 msec 12 msec 12 msec
    4 157.25.4.83 [AS 6714] 12 msec 12 msec 16 msec
    5 noc.gts.pl (217.153.108.10) [AS 6714] 12 msec 12 msec 12 msec
    --
    TOM


    [ pokaż wiadomość z nagłówkami ]
    do góry

  • 3. Data: 2007-08-13 12:14:28
    Temat: Re: jakiś fuckup cdp/atm - tpsa ?
    Od: "GRUPPY" <...@e...pl>


    Użytkownik "Marek Burzyński" <m...@c...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


    [ pokaż wiadomość z nagłówkami ]
    do góry

  • 4. Data: 2007-08-13 14:18:48
    Temat: Re: jakiś fuckup cdp/atm - tpsa ?
    Od: "Marcin Kuczera" <m...@l...usun-to.pl>

    nie wiem czym allegro leci, ale (16:18)
    bgp# show ip bgp 193.23.48.134
    % Network not in table

    ups...

    Marcin


    [ pokaż wiadomość z nagłówkami ]
    do góry

  • 5. Data: 2007-08-13 18:09:56
    Temat: Re: jakiś fuckup cdp/atm - tpsa ?
    Od: Marek Burzyński <m...@c...pl>

    a teraz ciekawostka:

    z CDP:

    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 11 ms 5 ms ip-89.171.78.201.crowley.pl [89.171.78.201]
    3 73 ms 14 ms 6 ms r5-waw-2-m120.crowley.pl [62.111.157.233]
    4 90 ms 59 ms 5 ms 212.73.253.137
    5 90 ms 14 ms 5 ms ae-11-11.car2.Warsaw1.Level3.net
    [4.69.134.10]
    6 78 ms 14 ms 18 ms ae-5-5.ebr2.Berlin1.Level3.net
    [4.69.134.18]
    7 27 ms 35 ms 36 ms ae-3.ebr2.Dusseldorf1.Level3.net
    [4.69.133.146]
    8 25 ms 31 ms 35 ms ae-1-100.ebr1.Dusseldorf1.Level3.net
    [4.69.132.129]
    9 36 ms 140 ms 39 ms ae-2.ebr2.Frankfurt1.Level3.net
    [4.69.132.138]
    10 105 ms 61 ms 91 ms ae-2-54.edge2.Frankfurt1.Level3.net
    [4.68.118.110]
    11 179 ms 36 ms 28 ms
    opentransit-level3-oc48.Frankfurt1.Level3.net
    [4.68.127.198]
    12 52 ms * 38 ms
    so-1-2-0-0.fftcr4.Frankfurt.opentransit.net [193
    .251.242.198]
    13 305 ms 189 ms 316 ms tpsa-1.GW.opentransit.net [193.251.250.154]
    14 * 258 ms * 195.117.0.190
    15 77 ms * 43 ms 80.50.236.118


    i inny atm'ik

    C:\Documents and Settings\Marek>tracert 217.98.72.1

    Trasa śledzenia do 217.98.72.1 przewyższa maksymalną liczbę przeskoków 30

    1 1 ms <1 ms <1 ms 192.168.1.1
    2 73 ms 5 ms 5 ms ip-89.171.78.201.crowley.pl [89.171.78.201]
    3 34 ms 5 ms 5 ms r5-waw-2-m120.crowley.pl [62.111.157.233]
    4 5 ms 5 ms 5 ms 212.73.253.137
    5 28 ms 6 ms 6 ms ae-11-11.car2.Warsaw1.Level3.net
    [4.69.134.10]
    6 67 ms 13 ms 14 ms ae-5-5.ebr2.Berlin1.Level3.net
    [4.69.134.18]
    7 36 ms 75 ms 32 ms ae-3.ebr2.Dusseldorf1.Level3.net
    [4.69.133.146]

    8 98 ms 97 ms 89 ms ae-2.ebr1.Amsterdam1.Level3.net
    [4.69.133.89]
    9 * 35 ms 84 ms ae-13-55.car3.Amsterdam1.Level3.net
    [4.68.120.14
    5]
    10 58 ms 164 ms 32 ms
    opentransit-level3-te.Amsterdam1.Level3.net [4.6
    8.111.198]
    11 30 ms 30 ms 30 ms
    so-1-3-0-0.fftcr4.Frankfurt.opentransit.net [193
    .251.241.142]
    12 32 ms 32 ms 33 ms tpsa-1.GW.opentransit.net [193.251.250.154]
    13 90 ms 83 ms 168 ms 195.117.0.166
    14 67 ms 122 ms 63 ms 217.98.72.1


    hmm, chciałem sobie dłużej popracować a tu taki psikus ;-)


    Oczywiście łącze 100% gw. do tpsa ;-)

    ehhh




    --
    Marek Burzyński
    www.cyberbajt.pl | www.cyberbajt.com

    [ pokaż wiadomość z nagłówkami ]
    do góry

  • 6. Data: 2007-08-13 18:44:49
    Temat: Re: jakiś fuckup cdp/atm - tpsa ?
    Od: "Sied@r" <s...@d...lub.pl>

    Marek Burzyński pisze:
    > [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 ?
    >
    >
    dostałem dziś z NOC takie komunikaty:

    1.

    Informujemy, ze uszkodzeniu ulegl jeden z portow na punkcie styku z
    secia TPNET. Moze to spowodowac pogorszenie jakosci swiadczonych Panstwu
    uslug dostepu do zasobow sieci TPNET.

    2.
    Informujemy, ze miejsce awarii swiatlowodu zostalo zlokalizowane.
    Aktualnie prowadzona jest wymiana uszkodzonych wlokien swiatlowodowych.
    Przewidywany czas naprawy - godzina 18:30.

    3.
    O godzinie 19:53 zakonczyly sie prace przy naprawie uszkodzonych wlokien
    swiatlowodowych. Od tego czasu dostep do sieci TPNET realizowany jest
    bez zaklocen.

    D.

    [ pokaż wiadomość z nagłówkami ]
    do góry
strony : [ 1 ]
« poprzedni wątek
następny wątek »


Szukaj w grupach

[ wyszukiwanie zaawansowane ]

Najnowsze wątki

Starsze wątki

Grupy

Szukaj w grupach

Polecamy

Artykuły promowane

newsletter rss

Eksperci egospodarka.pl

1 1 1

Najnowsze w serwisie

Wpisz nazwę miasta, dla którego chcesz znaleźć jednostkę ZUS.

Wzory dokumentów

Bezpłatne wzory dokumentów i formularzy.
Wyszukaj i pobierz za darmo: