5 Dec
2012
5 Dec
'12
10:52 a.m.
Is anyone aware of any routing issues from Oz to Bitfolk? I'm doing some
remote support on a machine down there and can't ping any bitfolk ips?
-Matt Daubney
5 Dec
5 Dec
11:19 a.m.
I raised this with Andy as IPs in the 1.125.0.0/16 range (which has been allocated to
Telstra) seem not to be routed upstream. From my VPS I get:
traceroute to 1.125.81.4 (1.125.81.4), 30 hops max, 60 byte packets
1 obstler.bitfolk.com (85.119.80.8) 0.155 ms 0.134 ms 0.123 ms
2 jump-gw-4.lon.bitfolk.com (85.119.80.4) 0.701 ms 0.695 ms 0.684 ms
3 jump-gw-4.lon.bitfolk.com (85.119.80.4) 0.805 ms !H * *
On 5 Dec 2012, at 10:52, Matthew Daubney wrote:
Is anyone aware of any routing issues from Oz to
Bitfolk? I'm doing some remote support on a machine down there and can't ping any
bitfolk ips?
-Matt Daubney
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
11:24 a.m.
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> wrote:
I raised this with Andy as IPs in the 1.125.0.0/16
range (which has been
allocated to Telstra) seem not to be routed upstream. From my VPS I get:
traceroute to 1.125.81.4 (1.125.81.4), 30 hops max, 60 byte packets
1 obstler.bitfolk.com (85.119.80.8) 0.155 ms 0.134 ms 0.123 ms
2 jump-gw-4.lon.bitfolk.com (85.119.80.4) 0.701 ms 0.695 ms 0.684 ms
3 jump-gw-4.lon.bitfolk.com (85.119.80.4) 0.805 ms !H * *
On 5 Dec 2012, at 10:52, Matthew Daubney wrote:
Is anyone aware of any routing issues from Oz to
Bitfolk? I'm doing some
remote support on a machine down there and can't
ping any bitfolk ips?
-Matt Daubney
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
12:28 p.m.
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.
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 
3:47 p.m.
Hello,
On Wed, Dec 05, 2012 at 11:24:22AM +0000, Matthew Daubney wrote:
This machine is also in that range. How annoying!
What's the normal method
of resolving these? Harass Telstra?
This was down to a disagreement between Telstra and Jump over the
form of Telstra's announcement (an excessive number of prepends for
Jump's liking). I have asked Jump to put in an exception while they
argue over it and this has now been done, so it should be working
again.
Apologies for the disruption.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
4170
days inactive
4170
days old
5 comments
5 participants
participants (5)
-
Andy Smith -
jan＠henkins.za.net -
Matthew Daubney -
Michael Watkin -
Phil Clarke