Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Kpnqwest woes continue

Options
  • 21-06-2002 11:52pm
    #1
    spongebob
    Closed Accounts Posts: 6,143 ✭✭✭


    Here we go again

    Looks Like the End

    If you are wondering why I care, and are an Eircom Internet user then go to http://www.traceroute.org and trace from a selection of sites linked there back into yourself or into http://www.eircom.net if you don't know your own IP

    expect funny bizness when it shuts down.............

    Many traces from Europe were still coming thru Kpnqwest tonight.

    M


Comments

  • Options
    #2
    stormkeeper
    Registered Users Posts: 2,633 ✭✭✭stormkeeper


    will all the other Irish ISPs be affected too? (I'm using elive atm) ^ i guss that's a rhetorical question after this point

    and also, what is Kpnqwest called under the traceroute readout?

    Edit: I just did a trace on my current IP addy (under elive), http://eircom.net, http://www.unison.ie and http://www.iol.ie (which also has a server with linx). All of these ISPs share the first 9 peers, so if any of those are kpnqwest, we've got trouble.

    I've also done a check on www.telenet.be, www.xs4all.nl, www.chello.nl and www.casema.net and the first 5-8 peers are the same as ours.


  • Options
    #3
    spongebob
    Closed Accounts Posts: 6,143 ✭✭✭spongebob


    eircom routers appear at the end and are named blah.blah.eircom.net

    if the ones before them are named..say...

    blah.blah.kpnqwest.com

    it means that the primary route from that carrier to eircom runs thru Kpnqwest who have a lot of IP transits in place for the likes of eircom in Europe

    if it is switched off the routes into eircom from those carriers and into all of eircoms customers like Microsoft Europe for example will become funky meaning slower at best...hopping across the atlantic a few times for example

    we'll know soon enuff

    M


  • Options
    #4
    stormkeeper
    Registered Users Posts: 2,633 ✭✭✭stormkeeper


    do either ixprime.net or colt.net go through kpnqwest?


  • Options
    #5
    Tellox
    Registered Users Posts: 2,680 ✭✭✭Tellox


    If eircom even THINK for one moment that Im paying them full-price for a 28.8kps connection, they are VERY VERY WRONG!!

    the least they can do is give us flat-rate at this stage


  • Options
    #6
    stormkeeper
    Registered Users Posts: 2,633 ✭✭✭stormkeeper


    I wouldn't think even with this slowup Eircom would give up that easily...


  • Advertisement
  • Options
    #7
    Matfinn
    Closed Accounts Posts: 364 ✭✭Matfinn


    Just out of curiosity from reading this post I decided to do a traceroute to wanadoo.fr ( France Telecom owned ISP ) and got these results. Seems strange that a connection has to go all the way over to New York in order to get from Ireland to France.
    Heres the result ->>>>>>>>>>>>>>>>>>>>..

    1 131 ms 610 ms 391 ms xxx.yyy.dublin.eircom.net [159.134.333.000]
    2 771 ms 991 ms 1102 ms fe1-0.tr1.exs.dublin.eircom.net [159.134.238.65]

    3 1362 ms 561 ms 140 ms fe6-1-0.core1.exs.dublin.eircom.net [159.134.236
    .1]
    4 1172 ms 1232 ms 1141 ms atm4-1-0-134.core1.cra.dublin.eircom.net [159.13
    4.192.9]
    5 290 ms 1122 ms 711 ms pos5-0-0.core1.8av.newyork.eircom.net [159.134.1
    91.106]
    6 191 ms 190 ms 190 ms acr2-so-3-3-1-0.NewYork.cw.net [206.24.193.157]

    7 741 ms 540 ms 581 ms agr4-loopback.NewYork.cw.net [206.24.194.104]
    8 591 ms 541 ms 450 ms dcr2-so-6-3-0.NewYork.cw.net [206.24.207.189]
    9 250 ms 511 ms * agr2-so-6-0-0.NewYork.cw.net [206.24.207.198]
    10 200 ms 200 ms 180 ms iar1-loopback.NewYork.cw.net [206.24.194.23]
    11 190 ms 541 ms 300 ms 208.173.135.50
    12 331 ms 330 ms 190 ms P2-0.NYKCR2.New-york.opentransit.net [193.251.24
    1.233]
    13 290 ms 361 ms 350 ms P4-0.PASCR1.Pastourelle.opentransit.net [193.251
    .241.133]
    14 220 ms 351 ms 270 ms P15-0.ntsta202.Paris.francetelecom.net [193.251.
    126.57]
    15 320 ms 401 ms 350 ms P9-0.nrsta102.Paris.francetelecom.net [193.251.1
    26.81]
    16 210 ms 200 ms 261 ms P7-0.nafti104.Aubervilliers.francetelecom.net [1
    93.252.99.114]
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.


  • Options
    #8
    spongebob
    Closed Accounts Posts: 6,143 ✭✭✭spongebob


    ....someone musta written a cheque

    Note

    a Trace out (from you to a given website) may not be the same as a trace IN (from a given website to you)

    M


  • Options
    #9
    jd
    Registered Users Posts: 5,695 ✭✭✭jd


    Originally posted by Matfinn
    Just out of curiosity from reading this post I decided to do a traceroute to wanadoo.fr ( France Telecom owned ISP ) and got these results. Seems strange that a connection has to go all the way over to New York in order to get from Ireland to France.
    Heres the result ->>>>>>>>>>>>>>>>>>>>..

    1 131 ms 610 ms 391 ms xxx.yyy.dublin.eircom.net [159.134.333.000]
    2 771 ms 991 ms 1102 ms fe1-0.tr1.exs.dublin.eircom.net [159.134.238.65]

    3 1362 ms 561 ms 140 ms fe6-1-0.core1.exs.dublin.eircom.net [159.134.236
    .1]
    4 1172 ms 1232 ms 1141 ms atm4-1-0-134.core1.cra.dublin.eircom.net [159.13
    4.192.9]
    5 290 ms 1122 ms 711 ms pos5-0-0.core1.8av.newyork.eircom.net [159.134.1
    91.106]
    6 191 ms 190 ms 190 ms acr2-so-3-3-1-0.NewYork.cw.net [206.24.193.157]

    7 741 ms 540 ms 581 ms agr4-loopback.NewYork.cw.net [206.24.194.104]
    8 591 ms 541 ms 450 ms dcr2-so-6-3-0.NewYork.cw.net [206.24.207.189]
    9 250 ms 511 ms * agr2-so-6-0-0.NewYork.cw.net [206.24.207.198]
    10 200 ms 200 ms 180 ms iar1-loopback.NewYork.cw.net [206.24.194.23]
    11 190 ms 541 ms 300 ms 208.173.135.50
    12 331 ms 330 ms 190 ms P2-0.NYKCR2.New-york.opentransit.net [193.251.24
    1.233]
    13 290 ms 361 ms 350 ms P4-0.PASCR1.Pastourelle.opentransit.net [193.251
    .241.133]
    14 220 ms 351 ms 270 ms P15-0.ntsta202.Paris.francetelecom.net [193.251.
    126.57]
    15 320 ms 401 ms 350 ms P9-0.nrsta102.Paris.francetelecom.net [193.251.1
    26.81]
    16 210 ms 200 ms 261 ms P7-0.nafti104.Aubervilliers.francetelecom.net [1
    93.252.99.114]
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.

    it doesn't "have to"

    3 60 ms 10 ms 60 ms atm4-1-0-35.gw01.cra.dublin.te.net [194.125.204.
    13]
    4 <10 ms <10 ms 10 ms 159.134.192.50
    5 20 ms 20 ms 30 ms 159.134.192.226
    6 20 ms 20 ms 30 ms r21-fe0-1-0.asd-ixx.nl.kpnqwest.net [134.222.197
    .33]
    7 30 ms 20 ms 30 ms r16-po4-0.asd-kq1.nl.kpnqwest.net [134.222.229.1
    89]
    8 20 ms 30 ms 20 ms r1-se1-1-0.0.ledn-kq1.nl.kpnqwest.net [134.222.9
    6.37]
    9 20 ms 30 ms 20 ms r2-se0-0-0.0.ledn-kq1.nl.kpnqwest.net [134.222.2
    30.2]
    10 30 ms 30 ms 30 ms r1-se0-0-0.0.ldn-kq1.uk.kpnqwest.net [134.222.23
    0.169]
    11 30 ms 30 ms 30 ms r1-se0-0-0.0.ldn-kq4.uk.kpnqwest.net [134.222.23
    1.14]
    12 31 ms 30 ms 40 ms p0-0.lonbb1.london.opentransit.net [193.251.251.
    233]
    13 30 ms 30 ms 30 ms p13-0.pascr1.pastourelle.opentransit.net [193.25
    1.154.225]
    14 30 ms 30 ms 30 ms p15-0.ntsta202.paris.francetelecom.net [193.251.
    126.57]
    15 30 ms 40 ms 30 ms p9-0.nrsta102.paris.francetelecom.net [193.251.1
    26.81]
    16 30 ms 30 ms 30 ms p7-0.nafti104.aubervilliers.francetelecom.net [1
    93.252.99.114]
    17 * * * Request timed out.


Advertisement