[Sysadmins] Sysadmins Digest, Vol 42, Issue 1

Alan Doherty alan at alandoherty.net
Wed Dec 10 02:29:56 GMT 2014


as both good and bad traceroutes are identical up to 86.43.12.137 

id guess from the names the issue is with one or more routers/switching within eircoms ten gig eithernet core

as the good ones go via 
tenge-3-1-1.core2.dbn.core.eircom.net (86.43.252.101

and the bad ones try to go via
tenge-6-1-1.core1.dbn.core.eircom.net (86.43.253.29

but as so many seem to even filter traceroute nowdays this in not necessarily full or accurate information so my guess is of little real value ;)


At 12:00 09/12/2014  Tuesday, you wrote:
>Date: Mon, 8 Dec 2014 22:13:08 +0000
>From: "Vanush "Misha" Paturyan" <misha at cs.nuim.ie>
>Subject: [Sysadmins] Eircom internet unusable (Maynooth area)
>To: sysadmins at lists.stdlib.net
>Message-ID: <20141208221308.GA4154 at mishap2.cs.nuim.ie>
>Content-Type: text/plain; charset=us-ascii
>
>Hi All,
>
>anyone knows what's going on/anyone else experiencing problems with
>eircom Fibre broadband in Maynooth area?
>
>basically parts of the internet are unaccessible. google.ie works,
>bbc.co.uk doesn't. For sites that work pings are min/avg/max/stddev =
>7.443/21.293/84.127/18.648 ms, with no packet loss within 20 packets,
>for whose that don't pacet loss is 93-95%, but the ones that manage to
>get through are round-tripping at 75ms.
>
>I've ran traceroutes towards to IPs within HEA's AS1213 (but within
>diffrent network prefixes): 193.1.31.74 (no packet loss, round-trip
>8.5/20.9/33.0) and 149.157.245.43 (85% packet loss, round-trip
>70.404/73.769/76.788), and for whatever reason 3rd and 4th hops are
>different. I'm not an expert in complex routing tables, but I always
>thought if both networks are from the same AS, then they should be
>routed the same way to the peering point of that AS?
>
>"good" traceroute
>traceroute to 193.1.31.74 (193.1.31.74), 64 hops max, 52 byte packets
> 1  192.168.1.254 (192.168.1.254)  1.807 ms  1.777 ms  1.499 ms
> 2  95.45.114.1 (95.45.114.1)  12.704 ms  6.642 ms  7.533 ms
> 3  86.43.12.137 (86.43.12.137)  7.073 ms  6.267 ms  7.065 ms
> 4  tenge-3-1-1.core2.dbn.core.eircom.net (86.43.252.101)  29.139 ms  28.992 ms  29.276 ms
> 5  * * tenge-1-2-1.pe2.6cr.6cr-6cr.eircom.net (86.43.255.98)  48.240 ms
> 6  83.71.115.186 (83.71.115.186)  46.801 ms  45.053 ms  44.554 ms
> 7  be-300-cr2-cwt.hea.net (193.242.111.16)  47.652 ms  47.087 ms47.989 ms
> 8  te5-1-blanch-sr1.services.hea.net (193.1.236.2)  47.641 ms 47.966 ms  48.753 ms
> 9  sixxs-tb.hea.net (193.1.31.74)  50.040 ms  47.858 ms  47.245 ms
>
>"bad" traceroute
>traceroute to mishapc.cs.nuim.ie (149.157.245.43), 64 hops max, 52 byte packets
> 1  192.168.1.254 (192.168.1.254)  2.044 ms  1.256 ms  1.753 ms
> 2  95.45.114.1 (95.45.114.1)  6.648 ms  6.525 ms  17.716 ms
> 3  86.43.12.133 (86.43.12.133)  7.169 ms  5.951 ms  6.295 ms
> 4  * * tenge-6-1-1.core1.dbn.core.eircom.net (86.43.253.29) 74.735 ms
> 5  * * *
>
>It looks like parts of the internet that are routed through
>86.43.12.137 -> 86.43.252.101 are accessible, and anything that ends
>up going through 86.43.12.133 -> 86.43.253.29 are end up in a black
>hole of sorts?
>
>Any thoughts? 




More information about the Sysadmins mailing list