5 Dec
2012
5 Dec
'12
1:56 p.m.
I'm aware of some broken fibre hassles last night (GMT) in the Sydney
area that affected international bandwidth going via the US. It is
possible that the problem below is as a result of this event, and that
the dynamic routing did not rebuild properly after the fibre was fixed.
As it is, our routing to our Oz office at /dev/work still goes via a DR
link.
On 2012-12-05 12:28, Phil Clarke wrote:
On 05/12/2012 11:24, Matthew Daubney wrote:
This machine is also in that range. How annoying!
What's the normal
method of resolving these? Harass Telstra?
(forgot to reply all)
On 5 December 2012 11:19, Michael Watkin <michael(a)pasdex.com
<mailto:michael@pasdex.com>> wrote:
I raised this with Andy as IPs in the 1.125.0.0/16
<http://1.125.0.0/16> range (which has been allocated to
Telstra)
seem not to be routed upstream. From my VPS I get:
Telstra are definitely announcing 1.120.0.0/13 as a prefix to the
global
BGP routing tables.
AS PATH 1221>4637>[Level3/Cogent/Sprint/Hurricane Electric/Easynet
Global/other large transity type usual suspects]
From a Virgin Media connection I can trace 1.125.81.4 well into
Telstra
network (Adelaide) and from my work connection I also get a similar
path
[Virgin via C&W and work via Level3]
Suspect an issue closer to home with peering/transit.
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users