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

Eircom BB traceroutes this evening

Options
  • 21-03-2007 9:56pm
    #1
    pyzon
    Closed Accounts Posts: 178 ✭✭


    Noticed some strange traceroute returns this evening - always the 2nd hop and always around 2-2.5 second response time after that it looks fine - anyone any ideas?

    I'm in Wexford on the Oulart Exchange.

    Tracing route to heanet.webhost.heanet.ie [193.1.219.79]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.1.254
    2 1673 ms 2252 ms 1638 ms b-ras1.chf.cork.eircom.net [159.134.155.21]
    3 17 ms 17 ms 18 ms 83.71.114.93
    4 31 ms 89 ms 22 ms 83.71.115.214
    5 44 ms 25 ms 23 ms hyperion-gige6-1.cwt.core.hea.net [193.242.111.1
    6]
    6 24 ms 24 ms 22 ms gige6-1-ar1-cwt.hea.net [193.1.195.177]
    7 130 ms 23 ms 22 ms blanch-sr1-po1.services.hea.net [193.1.195.139]

    8 * ^C

    Traceroute from teh router shows similar (different destinations used also)

    Traceroute to 89.234.66.107 (timer gran. 10 ms)
    30 hops max, 56 byte packets
    1 159.134.155.21 1480 ms 1680 ms 2100 ms
    2 83.71.114.93 10 ms 20 ms 10 ms
    3 83.71.115.214 30 ms 20 ms 20 ms
    4 193.242.111.20 30 ms 20 ms 30 ms
    5 89.234.66.107 20 ms ! 20 ms ! 30 ms !

    Traceroute complete - host found

    159.134.155.21 is my default gateway, perhaps there are other def g/w I could use?


Comments

  • Options
    #2
    bloke
    Registered Users Posts: 70 ✭✭bloke


    once the subsequent hops are ok it's not really a problem. Just shows the access concentrator is working hard and taking its time replying to traceroute packets. The low pings subsequently show its forwarding packets through it ok. This came up recently:
    http://www.boards.ie/vbulletin/showthread.php?t=2055057177


  • Options
    #3
    pyzon
    Closed Accounts Posts: 178 ✭✭pyzon


    Cheer for the quick reply bloke..yeah didn't notice much while browsing, but was using a MUD client and it seemed a little jerky but a trace to that shows possible issues at the MUD :)


  • Options
    #4
    JNive
    Registered Users Posts: 994 ✭✭✭JNive


    a traceroute like that is perfectly normal since the gateway in churchfield quite naturally is set to prioritise traffic destined for the internet as opposed to itself, therefore pings to it are delayed in favour of traffic/pings going through it.

    The only time things like that should be a concern is if the effect cascades through to all the hops after it, this goes for ping and packet loss readings.


Advertisement