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
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Routing between two Eircom IPs seems to fail

  • 03-03-2015 9:08am
    #1
    Registered Users, Registered Users 2 Posts: 931 ✭✭✭


    Hi guys,

    Could you push this to whoever looks after internal routing:

    =========================================================
    From: 86.43.92.130
    C:\Users\dave>tracert 83.70.181.105

    Tracing route to 83.70.181.105 over a maximum of 30 hops

      1    <1 ms    <1 ms    <1 ms  10.4.55.55
      2    18 ms    19 ms    25 ms  b-ras3.lmk.limerick.eircom.net [159.134.155.10]
      3  ge-6-1-6.pe1.blp.blp-srl.eircom.net [86.43.246.37]  reports: Destination ne
    t unreachable.

    From: 83.70.181.105
    C:\>tracert 86.43.92.130

    Tracing route to 86.43.92.130 over a maximum of 30 hops

      1    <1 ms     1 ms     1 ms  10.5.21.1
      2    13 ms    10 ms    27 ms  95.45.40.1
      3     9 ms     8 ms     8 ms  lag-20.pe2.lmk.lmk-pgs.eircom.net [86.43.10.61]
      4    23 ms    31 ms     9 ms  tenge4-0-0.b-ras3.lmk.limerick.eircom.net [86.43.246.34]
      5     *        *        *     Request timed out.
      6     *        *        *     Request timed out.
      7     *        *        *     Request timed out.
      8     *        *        *     Request timed out.
      9  ^C

    Trace complete.

    =========================================================


    Used to run a VPN between them, havent been able for a while.

    Thank you


Comments

  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭Xennon


    .. shameless bump


  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭Xennon


    pokes Alan with large stick :D


  • Closed Accounts Posts: 6,831 ✭✭✭eircom: Alan


    Xennon wrote: »
    pokes Alan with large stick :D
    Apologies Xennon :)

    I've requested clarification and now awaiting further information so as soon as I have this I'll be back to you right away

    Thanks!

    Al


  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭Xennon


    shameless bump :)


  • Closed Accounts Posts: 6,831 ✭✭✭eircom: Alan


    Xennon wrote: »
    shameless bump :)
    Hi Xennon

    I have not had an update yet - I'll push for something today though

    Al


  • Advertisement
  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭Xennon


    Thanks Al.


  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭Xennon


    Hey Al!..

    Can you pass this on to whoever, its been a month now.

    Routing between two Eircom IPs still broken 83.70.181.105 and 86.43.92.130.

    Some more info:

    Ping from a server located in Dublin:
    root@######### ~ # ping 83.70.181.105
    PING 83.70.181.105 (83.70.181.105) 56(84) bytes of data.
    64 bytes from 83.70.181.105: icmp_seq=1 ttl=59 time=14.8 ms
    64 bytes from 83.70.181.105: icmp_seq=2 ttl=59 time=14.5 ms
    64 bytes from 83.70.181.105: icmp_seq=3 ttl=59 time=16.3 ms
    64 bytes from 83.70.181.105: icmp_seq=4 ttl=59 time=15.9 ms
    64 bytes from 83.70.181.105: icmp_seq=5 ttl=59 time=20.3 ms

    Ping from my own Eircom connection:
    C:\Users\Dave>ping 83.70.181.105

    Pinging 83.70.181.105 with 32 bytes of data:
    Reply from 86.43.246.37: Destination net unreachable.
    Reply from 86.43.246.37: Destination net unreachable.
    Reply from 86.43.246.37: Destination net unreachable.
    Reply from 86.43.246.37: Destination net unreachable.

    Ping statistics for 83.70.181.105:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Trace from my own Eircom connection:
    C:\Users\Dave>tracert 83.70.181.105

    Tracing route to 83.70.181.105 over a maximum of 30 hops

      1    <1 ms    <1 ms    <1 ms  10.4.55.55
      2    18 ms    18 ms    17 ms  b-ras3.lmk.limerick.eircom.net [159.134.155.10]
      3  tenge-5-2-2.pe2.lmk.lmk-pgs.eircom.net [86.43.246.37]  reports: Destination net unreachable.

    Trace complete.

    Trace from Work IP to my home:
    C:\Users\Dave>tracert 86.43.92.130

    Tracing route to 86.43.92.130 over a maximum of 30 hops

      1     1 ms    <1 ms     1 ms  10.5.21.1
      2     8 ms    11 ms     8 ms  95.45.40.1
      3     9 ms    11 ms     9 ms  lag-20.pe2.lmk.lmk-pgs.eircom.net [86.43.10.61]
      4     9 ms     9 ms     9 ms  tenge4-0-0.b-ras3.lmk.limerick.eircom.net [86.43.246.34]
      5     *        *        *     Request timed out.
      6     *        *        *     Request timed out.
      7     *        *        *     Request timed out.
      8  ^C


  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭Xennon


    Utterly shameless bump


  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭Xennon


    IP1: 83.70.181.105
    IP2: 86.43.92.130

    ping from IP2 to IP1: Reply from 86.43.246.37: Destination net unreachable.

    Ping from server to IP1: 64 bytes from 83.70.181.105: icmp_seq=1 ttl=59 time=14.8 ms


  • Closed Accounts Posts: 6,831 ✭✭✭eircom: Alan


    Xennon wrote: »
    IP1: 83.70.181.105
    IP2: 86.43.92.130

    ping from IP2 to IP1: Reply from 86.43.246.37: Destination net unreachable.

    Ping from server to IP1: 64 bytes from 83.70.181.105: icmp_seq=1 ttl=59 time=14.8 ms


    I'm fully aware of the delays in getting back to you and I sincerely apologise for this Xennon, I am still awaiting clarification on this however I will continue to push for this. Thanks for all your patience :)

    Al


  • Advertisement
  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭Xennon


    Hi Al,

    Bah...fergetitt...Im off to Oz in July anyway and I doubt its gonna be sorted by then.

    Thanks for your help in the past though.

    Dave


  • Closed Accounts Posts: 6,831 ✭✭✭eircom: Alan


    Xennon wrote: »
    Hi Al,

    Bah...fergetitt...Im off to Oz in July anyway and I doubt its gonna be sorted by then.

    Thanks for your help in the past though.

    Dave
    No worries Dave and best of Luck in Oz ...however I would really like to have news on this well before July, you've been very patient and if you don't mind I will continue to chase this up for you!

    Al


  • Registered Users, Registered Users 2 Posts: 931 ✭✭✭Xennon


    Hi Al,

    Thanks.


  • Closed Accounts Posts: 6,831 ✭✭✭eircom: Alan


    Xennon wrote: »
    Hi Al,

    Thanks.
    No worries at all

    Al


  • Registered Users, Registered Users 2 Posts: 2,028 ✭✭✭d31b0y


    Don't know why I did but I pinged & tracert both ips (I'm on an eircom connection)...

    C:\Users\d31b0y>ping 83.70.181.105

    Pinging 83.70.181.105 with 32 bytes of data:
    Reply from 83.70.181.105: bytes=32 time=40ms TTL=58
    Reply from 83.70.181.105: bytes=32 time=39ms TTL=58

    Ping statistics for 83.70.181.105:
        Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 39ms, Maximum = 40ms, Average = 39ms
    Control-C
    ^C
    C:\Users\d31b0y>tracert 83.70.181.105

    Tracing route to 83.70.181.105 over a maximum of 30 hops

      1     3 ms     3 ms     3 ms  192.168.1.254
      2    29 ms    29 ms    29 ms  b-ras1.wtd.waterford.eircom.net [159.134.155.9]
      3    30 ms    29 ms    28 ms  tenge-5-1-1.pe1.wtd.prp-wtd.eircom.net [86.43.247.109]
      4    31 ms    30 ms    31 ms  lag-3.core2.prp.core.eircom.net [86.43.253.96]
      5    37 ms    35 ms    36 ms  tenge-2-2-1.pe2.lmk.lmk-pgs.eircom.net [86.43.253.106]
      6    37 ms    36 ms    37 ms  lag-1.agg2.shn.lmk-pgs.eircom.net [86.43.10.62]
      7    40 ms    40 ms    40 ms  83.70.181.105

    Trace complete.

    C:\Users\d31b0y>ping 86.43.92.130

    Pinging 86.43.92.130 with 32 bytes of data:
    Request timed out.

    Ping statistics for 86.43.92.130:
        Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
    Control-C
    ^C
    C:\Users\d31b0y>tracert 86.43.92.130

    Tracing route to 86.43.92.130 over a maximum of 30 hops

      1     3 ms     3 ms     3 ms  192.168.1.254
      2    33 ms    29 ms    29 ms  b-ras1.wtd.waterford.eircom.net [159.134.155.9]
      3    29 ms    28 ms    29 ms  tenge-4-1-1.pe1.wtd.prp-wtd.eircom.net [86.43.247.105]
      4    31 ms    32 ms    34 ms  lag-3.core2.prp.core.eircom.net [86.43.253.96]
      5    36 ms    36 ms    39 ms  tenge-2-2-1.pe2.lmk.lmk-pgs.eircom.net [86.43.253.106]
      6    38 ms    37 ms    38 ms  tenge5-0-0.b-ras3.lmk.limerick.eircom.net [86.43.246.38]
      7     *        *        *     Request timed out.
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11     *        *     ^C


  • Closed Accounts Posts: 6,831 ✭✭✭eircom: Alan


    d31b0y wrote: »
    Don't know why I did but I pinged & tracert both ips (I'm on an eircom connection)...

    C:\Users\d31b0y>ping 83.70.181.105

    Pinging 83.70.181.105 with 32 bytes of data:
    Reply from 83.70.181.105: bytes=32 time=40ms TTL=58
    Reply from 83.70.181.105: bytes=32 time=39ms TTL=58

    Ping statistics for 83.70.181.105:
        Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 39ms, Maximum = 40ms, Average = 39ms
    Control-C
    ^C
    C:\Users\d31b0y>tracert 83.70.181.105

    Tracing route to 83.70.181.105 over a maximum of 30 hops

      1     3 ms     3 ms     3 ms  192.168.1.254
      2    29 ms    29 ms    29 ms  b-ras1.wtd.waterford.eircom.net [159.134.155.9]
      3    30 ms    29 ms    28 ms  tenge-5-1-1.pe1.wtd.prp-wtd.eircom.net [86.43.247.109]
      4    31 ms    30 ms    31 ms  lag-3.core2.prp.core.eircom.net [86.43.253.96]
      5    37 ms    35 ms    36 ms  tenge-2-2-1.pe2.lmk.lmk-pgs.eircom.net [86.43.253.106]
      6    37 ms    36 ms    37 ms  lag-1.agg2.shn.lmk-pgs.eircom.net [86.43.10.62]
      7    40 ms    40 ms    40 ms  83.70.181.105

    Trace complete.

    C:\Users\d31b0y>ping 86.43.92.130

    Pinging 86.43.92.130 with 32 bytes of data:
    Request timed out.

    Ping statistics for 86.43.92.130:
        Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
    Control-C
    ^C
    C:\Users\d31b0y>tracert 86.43.92.130

    Tracing route to 86.43.92.130 over a maximum of 30 hops

      1     3 ms     3 ms     3 ms  192.168.1.254
      2    33 ms    29 ms    29 ms  b-ras1.wtd.waterford.eircom.net [159.134.155.9]
      3    29 ms    28 ms    29 ms  tenge-4-1-1.pe1.wtd.prp-wtd.eircom.net [86.43.247.105]
      4    31 ms    32 ms    34 ms  lag-3.core2.prp.core.eircom.net [86.43.253.96]
      5    36 ms    36 ms    39 ms  tenge-2-2-1.pe2.lmk.lmk-pgs.eircom.net [86.43.253.106]
      6    38 ms    37 ms    38 ms  tenge5-0-0.b-ras3.lmk.limerick.eircom.net [86.43.246.38]
      7     *        *        *     Request timed out.
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11     *        *     ^C
    Cheers d31b0y

    Al


Advertisement