Routing path to Sydney Hurricane Electric is crap

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Routing path to Sydney Hurricane Electric is crap

1 | 2

Sounddude

I fix stuff!
1935 posts

Uber Geek
+1 received by user: 640

Trusted

2degrees

Lifetime subscriber

#2006286 1-May-2018 21:33

Joelfreak: Saw us being mentioned here, and let me just say I think NZ will soon get much better peering with Hurricane. I don't want to advertise, so I will just say that we have a dot for Auckland on our map, so peering onto our backbone will soon be easier in NZ. I hope this posting doesn't run afoul of the rules, if it does, feel free to remove it. Thanks!

Reid from he.net

Hi @Joelfreak

Thanks for jumping in. Fixing your sydney routing first would be the ideal solution. Most ISP's these days peer in Sydney over Equinix and Megaport. However it seems that for some ISP's who buy HE in the USA, you are sending the return traffic via there rather than back over the peering fabric.

This causes a massive latency jump. ISP's who don't buy HE are getting a better deal than those who do. Which is a bit backwards.

I have raised the issue with the HE NOC, just waiting to hear back.

Joelfreak

6 posts

Wannabe Geek
+1 received by user: 3

Trusted

Hurricane Electric

#2006292 1-May-2018 21:41

We must prefer customer links over peering links, otherwise routing would break.

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#2006301 1-May-2018 22:13

Joelfreak: Saw us being mentioned here, and let me just say I think NZ will soon get much better peering with Hurricane. I don't want to advertise, so I will just say that we have a dot for Auckland on our map, so peering onto our backbone will soon be easier in NZ. I hope this posting doesn't run afoul of the rules, if it does, feel free to remove it. Thanks!

Reid from he.net

Don't think that counts as advertising. Good to see HE making this move, although would be interesting to see where you end up situating that dot...

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

tknz

182 posts

Master Geek
+1 received by user: 7

#2006415 2-May-2018 10:13

@Sounddude

@Joelfreak

To be expected the trace is the same via a 6 figure IP transit connection using Vocus...

Tracing route to tserv1.syd1.he.net [216.218.142.50]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms 172.17.8.1
2 5 ms 4 ms 3 ms x.y.z
3 25 ms 24 ms 25 ms default-rdns.vocus.co.nz [131.203.220.85]
4 30 ms 33 ms 30 ms default-rdns.vocus.co.nz [101.98.19.122]
5 31 ms 31 ms 29 ms default-rdns.vocus.co.nz [101.98.19.121]
6 52 ms 52 ms 55 ms as9790.sydney.megaport.com [103.26.68.73]
7 183 ms 222 ms 180 ms as6939.sydney.megaport.com [103.26.68.236]
8 181 ms 181 ms 180 ms tserv1.syd1.he.net [216.218.142.50]

Trace complete.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Any views and ideas that I have expressed in my comments are my own, and do not represent my place of work.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

5thEntanglement

7 posts

Wannabe Geek

#2020481 22-May-2018 16:06

Any update on this routing problem?

I use bigpipe, but might switch over to slingshot's (callplus, vocus group) gigabit fibre.

**BIGPIPE 100Mbps 22/05/2018**

C:\Users\_\tracert tserv1.syd1.he.net

Tracing route to tserv1.syd1.he.net [216.218.142.50]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms _ [192.168.1.1]
2 3 ms 4 ms 5 ms 100.64.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 8 ms 7 ms 7 ms ae11-201.akbr6.global-gateway.net.nz [122.56.118.145]
6 5 ms 6 ms 9 ms ae7-2.akbr7.global-gateway.net.nz [122.56.119.53]
7 30 ms 30 ms 30 ms xe7-0-2.sgbr3.global-gateway.net.nz [202.50.232.10]
8 30 ms 27 ms 30 ms ae7-10.sebr4.global-gateway.net.nz [122.56.127.214]
9 29 ms 28 ms 29 ms 6939.syd.equinix.com [45.127.173.24]
10 29 ms 30 ms 32 ms tserv1.syd1.he.net [216.218.142.50]

Sounddude

I fix stuff!
1935 posts

Uber Geek
+1 received by user: 640

Trusted

2degrees

Lifetime subscriber

#2020483 22-May-2018 16:10

No updates. Its a challenging issue to solve.

In saying that, do you need to use the HE tunnel broker when we can give native ipv6?

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

MattR

225 posts

Master Geek
+1 received by user: 36

#2055185 12-Jul-2018 16:14

It's an easy issue to solve, if HE wanted to solve it.

Both my upstreams in Sydney (Vocus and TPG) buy from HE in California, and I have a direct peering session with HE in Sydney - yet return traffic still goes via California because HE are getting paid for that traffic, where they wouldn't be getting paid if they hand it over in Sydney. The solution is to advertise more specific prefixes at the IX, but sadly my main prefix is only a /24 so I'm out of luck there.

Joelfreak

6 posts

Wannabe Geek
+1 received by user: 3

Trusted

Hurricane Electric

#2055189 12-Jul-2018 16:21

It's really not that simple. When you run a global network, you have to prefer customer routes over peer routes, or else things would break MASSIVELY.

patrickslee

53 posts

Master Geek
+1 received by user: 9

ID Verified

#2065928 31-Jul-2018 21:53

Out of curiosity I just did a traceroute:

Tracing route to tserv1.syd1.he.net [216.218.142.50]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.181.254
2 * * * Request timed out.
3 * * * Request timed out.
4 8 ms 2 ms 6 ms default-rdns.vocus.co.nz [101.98.5.22]
5 6 ms 5 ms 5 ms BE-101.bdr02.akl05.akl.VOCUS.net.nz [175.45.102.233]
6 122 ms 121 ms 122 ms bundle-10.cor01.akl05.akl.vocus.net.nz [114.31.202.100]
7 121 ms 120 ms 121 ms BE-202.cor01.syd11.nsw.VOCUS.net.au [114.31.202.55]
8 123 ms 126 ms 126 ms bundle-102.cor01.per02.wa.vocus.net.au [114.31.206.129]
9 126 ms 125 ms 126 ms ge-0-2-7.bdr02.per02.wa.VOCUS.net.au [114.31.206.93]
10 214 ms 213 ms 213 ms 6939.sgw.equinix.com [27.111.228.81]
11 212 ms 213 ms 221 ms 100ge13-2.core1.tyo1.he.net [184.105.64.254]
12 213 ms 213 ms 213 ms 100ge11-1.core1.sea1.he.net [184.105.213.117]
13 213 ms 213 ms 214 ms 100ge11-1.core1.sjc2.he.net [184.105.223.217]
14 213 ms 213 ms 214 ms 10ge4-4.core1.sjc1.he.net [72.52.92.117]
15 361 ms 361 ms 362 ms 10ge2-1.core1.syd1.he.net [184.105.222.86]
16 362 ms 360 ms 361 ms tserv1.syd1.he.net [216.218.142.50]

Slingshot UFB Auckland -> Vocus Sydney -> Western Australia -> Singapore -> Tokyo -> Seattle -> San Jose -> Sydney

Somebody in this chain needs to get their sh*t together. Ping is around 360ms.

5thEntanglement

7 posts

Wannabe Geek

#2065975 1-Aug-2018 00:28

I'll bring this up, but I don't really wanna talk about it, so pref if you just read and ignore.

"Blatant ǝɔuɐƖƖᴉǝʌɹnS by Uncle John"

Since we're hopefully not gonna start a large discussion, I could be wrong, I could be right. Each to their own. But now I've let you know of the possibility.

1 | 2