Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.




defiant
691 posts

Ultimate Geek
+1 received by user: 331

Lifetime subscriber

Topic # 242389 25-Oct-2018 21:28
Send private message quote this post

This time to an ec2 instance I have running in Sydney, the ipv6 route is going via Tokyo

 

traceroute to 2406:da1c:fb0:8700:x (2406:da1c:fb0:8700:x), 30 hops max, 80 byte packets
1 2406:e001:x (2406:e001:x) 0.313 ms 0.270 ms 0.241 ms
2 2406:e000:2801:c::1 (2406:e000:2801:c::1) 1.934 ms 1.886 ms 1.881 ms
3 as23655.auckland.megaport.com (2001:dea:0:40::4d) 13.682 ms 13.571 ms 13.511 ms
4 2001:7fa:11:6:0:1b1b:0:1 (2001:7fa:11:6:0:1b1b:0:1) 14.333 ms 13.568 ms 14.926 ms
5 10ge2-3.core1.syd1.he.net (2001:470:0:454::1) 36.484 ms 36.293 ms 36.296 ms
6 10ge1-1.core1.tyo1.he.net (2001:470:0:46c::1) 217.713 ms 217.954 ms 217.902 ms
7 asn-telstra-global-as4637.10gigabitethernet5-2.core1.tyo1.he.net (2001:470:0:395::2) 213.530 ms * *
8 * * *
9 2403:e800:ff00:110::3f (2403:e800:ff00:110::3f) 179.176 ms 152.201 ms 178.125 ms
10 2403:e800:ff00:110::3 (2403:e800:ff00:110::3) 180.725 ms 186.530 ms 179.013 ms
11 2403:e800:105:26::2 (2403:e800:105:26::2) 149.544 ms 176.722 ms 178.335 ms
12 2400:6500:0:2::17 (2400:6500:0:2::17) 160.882 ms 180.648 ms 2400:6500:0:2::13 (2400:6500:0:2::13) 162.052 ms
13 2403:b300::5 (2403:b300::5) 152.504 ms 152.058 ms 150.752 ms
14 2400:6500:0:2::20 (2400:6500:0:2::20) 177.887 ms 2400:6500:0:2::f (2400:6500:0:2::f) 177.906 ms 2400:6500:0:2::20 (2400:6500:0:2::20) 150.452 ms
15 2400:6500:0:4201:8000:0:6440:10fe (2400:6500:0:4201:8000:0:6440:10fe) 150.899 ms 2400:6500:0:4201:8000:0:6440:11ae (2400:6500:0:4201:8000:0:6440:11ae) 159.809 ms 2400:6500:0:4201:8000:0:6440:11f8 (2400:6500:0:4201:8000:0:6440:11f8) 186.403 ms
16 2400:6500:0:4201::6440:c36e (2400:6500:0:4201::6440:c36e) 188.249 ms 2400:6500:0:4201::6440:c369 (2400:6500:0:4201::6440:c369) 179.772 ms 2400:6500:0:4201::6440:c36c (2400:6500:0:4201::6440:c36c) 180.261 ms
17 2400:6500:0:4201::6440:c373 (2400:6500:0:4201::6440:c373) 155.777 ms 184.783 ms 2400:6500:0:4201::6440:c363 (2400:6500:0:4201::6440:c363) 160.099 ms
18 2406:da1c:fb0:8700:x 177.976 ms 177.560 ms 152.411 ms

 

Here's the ipv4 for comparison:

 

traceroute to 13.239.55.x (13.239.55.x), 30 hops max, 60 byte packets
1 192.168.1.1 0.199 ms 0.169 ms 0.235 ms
2 69.7.69.111.static.snap.net.nz (111.69.7.69) 1.720 ms 1.711 ms 1.686 ms
3 * * *
4 23655.syd.equinix.com (45.127.172.156) 36.520 ms 36.533 ms 36.518 ms
5 16509.syd.equinix.com (45.127.172.131) 35.061 ms 35.046 ms 34.986 ms
6 * * *
7 * * *
8 52.95.37.199 (52.95.37.199) 39.605 ms 52.95.37.191 (52.95.37.191) 35.039 ms 52.95.37.181 (52.95.37.181) 43.811 ms
9 52.95.36.113 (52.95.36.113) 36.209 ms 52.95.36.49 (52.95.36.49) 36.127 ms 52.95.36.17 (52.95.36.17) 36.118 ms
10 52.95.36.16 (52.95.36.16) 43.164 ms 52.95.36.66 (52.95.36.66) 37.312 ms 52.95.36.48 (52.95.36.48) 37.955 ms
11 52.95.36.121 (52.95.36.121) 35.887 ms 52.95.36.25 (52.95.36.25) 36.570 ms 52.95.36.73 (52.95.36.73) 36.491 ms
12 52.95.38.140 (52.95.38.140) 35.839 ms 54.240.192.255 (54.240.192.255) 36.088 ms 54.240.192.107 (54.240.192.107) 35.965 ms
13 * * *
14 * * *
15 * * *
16 ec2-13-239-55-x.ap-southeast-2.compute.amazonaws.com (13.239.55.x) 35.896 ms 35.841 ms 35.810 ms

 

Why do HE keep routing Sydney based traffic via Tokyo on ipv6?


Filter this topic showing only the reply marked as answer Create new topic


defiant
691 posts

Ultimate Geek
+1 received by user: 331

Lifetime subscriber

  Reply # 2114530 26-Oct-2018 16:32
Send private message quote this post

Paging the lord ipv6 saviour @NickMack !


273 posts

Ultimate Geek
+1 received by user: 212

Trusted
2degrees

  Reply # 2114562 26-Oct-2018 17:26
5 people support this post
Send private message quote this post

Hiya,

 

It maybe related to this - https://list.waikato.ac.nz/pipermail/nznog/2018-October/022920.html (Hurricane Electric (AS6939) are in the process of connecting to the Auckland Peering Exchange (APE)). I'll see what's possible with the team next week. The ol' chasing your tail.....

 

On another note - Go Canterbury and go the mighty All Blacks this weekend!

 

Even managed to get a snap with Ranfurly Shield at a function last night - Great work Otago!

 

 

Nick


 
 
 
 




defiant
691 posts

Ultimate Geek
+1 received by user: 331

Lifetime subscriber

  Reply # 2114583 26-Oct-2018 17:55
Send private message quote this post

NickMack:

 

Hiya,

 

It maybe related to this - https://list.waikato.ac.nz/pipermail/nznog/2018-October/022920.html (Hurricane Electric (AS6939) are in the process of connecting to the Auckland Peering Exchange (APE)). I'll see what's possible with the team next week. The ol' chasing your tail.....

 

On another note - Go Canterbury and go the mighty All Blacks this weekend!

 

Even managed to get a snap with Ranfurly Shield at a function last night - Great work Otago!

 

 

Nick

 

 

Damn that's front page worthy right there! I'm going to Canterbury too.

 

Thanks for looking into it, the irony is that it hits HE in Sydney before heading off to Tokyo on the next hop -_-


273 posts

Ultimate Geek
+1 received by user: 212

Trusted
2degrees

  Reply # 2116212 29-Oct-2018 13:51
Send private message quote this post

dfnt:

 

This time to an ec2 instance I have running in Sydney, the ipv6 route is going via Tokyo

 

traceroute to 2406:da1c:fb0:8700:x (2406:da1c:fb0:8700:x), 30 hops max, 80 byte packets
1 2406:e001:x (2406:e001:x) 0.313 ms 0.270 ms 0.241 ms
2 2406:e000:2801:c::1 (2406:e000:2801:c::1) 1.934 ms 1.886 ms 1.881 ms
3 as23655.auckland.megaport.com (2001:dea:0:40::4d) 13.682 ms 13.571 ms 13.511 ms
4 2001:7fa:11:6:0:1b1b:0:1 (2001:7fa:11:6:0:1b1b:0:1) 14.333 ms 13.568 ms 14.926 ms
5 10ge2-3.core1.syd1.he.net (2001:470:0:454::1) 36.484 ms 36.293 ms 36.296 ms
6 10ge1-1.core1.tyo1.he.net (2001:470:0:46c::1) 217.713 ms 217.954 ms 217.902 ms
7 asn-telstra-global-as4637.10gigabitethernet5-2.core1.tyo1.he.net (2001:470:0:395::2) 213.530 ms * *
8 * * *
9 2403:e800:ff00:110::3f (2403:e800:ff00:110::3f) 179.176 ms 152.201 ms 178.125 ms
10 2403:e800:ff00:110::3 (2403:e800:ff00:110::3) 180.725 ms 186.530 ms 179.013 ms
11 2403:e800:105:26::2 (2403:e800:105:26::2) 149.544 ms 176.722 ms 178.335 ms
12 2400:6500:0:2::17 (2400:6500:0:2::17) 160.882 ms 180.648 ms 2400:6500:0:2::13 (2400:6500:0:2::13) 162.052 ms
13 2403:b300::5 (2403:b300::5) 152.504 ms 152.058 ms 150.752 ms
14 2400:6500:0:2::20 (2400:6500:0:2::20) 177.887 ms 2400:6500:0:2::f (2400:6500:0:2::f) 177.906 ms 2400:6500:0:2::20 (2400:6500:0:2::20) 150.452 ms
15 2400:6500:0:4201:8000:0:6440:10fe (2400:6500:0:4201:8000:0:6440:10fe) 150.899 ms 2400:6500:0:4201:8000:0:6440:11ae (2400:6500:0:4201:8000:0:6440:11ae) 159.809 ms 2400:6500:0:4201:8000:0:6440:11f8 (2400:6500:0:4201:8000:0:6440:11f8) 186.403 ms
16 2400:6500:0:4201::6440:c36e (2400:6500:0:4201::6440:c36e) 188.249 ms 2400:6500:0:4201::6440:c369 (2400:6500:0:4201::6440:c369) 179.772 ms 2400:6500:0:4201::6440:c36c (2400:6500:0:4201::6440:c36c) 180.261 ms
17 2400:6500:0:4201::6440:c373 (2400:6500:0:4201::6440:c373) 155.777 ms 184.783 ms 2400:6500:0:4201::6440:c363 (2400:6500:0:4201::6440:c363) 160.099 ms
18 2406:da1c:fb0:8700:x 177.976 ms 177.560 ms 152.411 ms

 

Here's the ipv4 for comparison:

 

traceroute to 13.239.55.x (13.239.55.x), 30 hops max, 60 byte packets
1 192.168.1.1 0.199 ms 0.169 ms 0.235 ms
2 69.7.69.111.static.snap.net.nz (111.69.7.69) 1.720 ms 1.711 ms 1.686 ms
3 * * *
4 23655.syd.equinix.com (45.127.172.156) 36.520 ms 36.533 ms 36.518 ms
5 16509.syd.equinix.com (45.127.172.131) 35.061 ms 35.046 ms 34.986 ms
6 * * *
7 * * *
8 52.95.37.199 (52.95.37.199) 39.605 ms 52.95.37.191 (52.95.37.191) 35.039 ms 52.95.37.181 (52.95.37.181) 43.811 ms
9 52.95.36.113 (52.95.36.113) 36.209 ms 52.95.36.49 (52.95.36.49) 36.127 ms 52.95.36.17 (52.95.36.17) 36.118 ms
10 52.95.36.16 (52.95.36.16) 43.164 ms 52.95.36.66 (52.95.36.66) 37.312 ms 52.95.36.48 (52.95.36.48) 37.955 ms
11 52.95.36.121 (52.95.36.121) 35.887 ms 52.95.36.25 (52.95.36.25) 36.570 ms 52.95.36.73 (52.95.36.73) 36.491 ms
12 52.95.38.140 (52.95.38.140) 35.839 ms 54.240.192.255 (54.240.192.255) 36.088 ms 54.240.192.107 (54.240.192.107) 35.965 ms
13 * * *
14 * * *
15 * * *
16 ec2-13-239-55-x.ap-southeast-2.compute.amazonaws.com (13.239.55.x) 35.896 ms 35.841 ms 35.810 ms

 

Why do HE keep routing Sydney based traffic via Tokyo on ipv6?

 

 

Hiya,

 

Do you have an EC2 instance that you can run a traceroute from?  We want to confirm the path the return traffic is following for both ipv4 and ipv6.  If the return path is the same, then we’ll need to engage with the peering exchanges and start using their control communities to pre-pend our routes to HE as well.

 

Nick.




defiant
691 posts

Ultimate Geek
+1 received by user: 331

Lifetime subscriber

  Reply # 2116295 29-Oct-2018 15:09
Send private message quote this post

Yes I'll PM you the info


273 posts

Ultimate Geek
+1 received by user: 212

Trusted
2degrees

  Reply # 2116386 29-Oct-2018 16:42
Send private message quote this post

dfnt:

 

Yes I'll PM you the info

 

 

Thanks for the details - Configuration is being created now for IPv6 routes advertised by HE, should be submitted and applied before peak time tonight (unless something major comes up).

 

Nick.


273 posts

Ultimate Geek
+1 received by user: 212

Trusted
2degrees

  Reply # 2116419 29-Oct-2018 17:20
Send private message quote this post

Update - This is proving a little more complex than first expected, needing further investigation tomorrow.

 

 

 

Nick.


1292 posts

Uber Geek
+1 received by user: 295


  Reply # 2116421 29-Oct-2018 17:26
Send private message quote this post

You know your routing is as good as Vodafones when your prefixes are advertised with as many BGP communities as theirs:

 

 

9500:900 9500:906 9500:1009 9500:10160 9500:10170 9500:20020 9500:20040 9500:20050 9500:20060 9500:20070 9500:20081 9500:20090 9500:20100 9500:20110 9500:20130 9500:20140 9500:21010 9500:21030 9500:21040 9500:21050 9500:21060 9500:21070 9500:31020 9500:31030 9500:31040 9500:31050 9500:32010 9500:32040 9500:32050 9500:32070 9500:33010 9500:33020 9500:33030 9500:33040 9500:33050

 




defiant
691 posts

Ultimate Geek
+1 received by user: 331

Lifetime subscriber

  Reply # 2116446 29-Oct-2018 18:50
Send private message quote this post

NickMack:

 

Update - This is proving a little more complex than first expected, needing further investigation tomorrow.

 

 

 

Nick.

 

 

All good, just appreciate you guys looking into it.




defiant
691 posts

Ultimate Geek
+1 received by user: 331

Lifetime subscriber

  Reply # 2116447 29-Oct-2018 18:51
Send private message quote this post

yitz: You know your routing is as good as Vodafones when your prefixes are advertised with as many BGP communities as theirs: 9500:900 9500:906 9500:1009 9500:10160 9500:10170 9500:20020 9500:20040 9500:20050 9500:20060 9500:20070 9500:20081 9500:20090 9500:20100 9500:20110 9500:20130 9500:20140 9500:21010 9500:21030 9500:21040 9500:21050 9500:21060 9500:21070 9500:31020 9500:31030 9500:31040 9500:31050 9500:32010 9500:32040 9500:32050 9500:32070 9500:33010 9500:33020 9500:33030 9500:33040 9500:33050

 

 

 

I don't know what any of that means, lol.

 

Is that good or bad?


1292 posts

Uber Geek
+1 received by user: 295


  Reply # 2116457 29-Oct-2018 19:42
One person supports this post
Send private message quote this post

Well BGP communities can be used for traffic engineering to influence preferred paths, so it seems they take a pretty fine grained approach to that, or at least their parent company's international peering backbone does. Not sure if the high number of communities could be hitting some limit for some peers.

273 posts

Ultimate Geek
+1 received by user: 212

Trusted
2degrees

  Reply # 2116701 30-Oct-2018 11:31
3 people support this post
Send private message quote this post

dfnt:

 

NickMack:

 

Update - This is proving a little more complex than first expected, needing further investigation tomorrow.

 

 

 

Nick.

 

 

All good, just appreciate you guys looking into it.

 

 

 

 

Hiya,

 

Should be resolved now.

 

 

 

Nick.


Mr Snotty
8084 posts

Uber Geek
+1 received by user: 4053

Moderator
Trusted
Lifetime subscriber

  Reply # 2116712 30-Oct-2018 11:47
Send private message quote this post


defiant
691 posts

Ultimate Geek
+1 received by user: 331

Lifetime subscriber

  Reply # 2116799 30-Oct-2018 13:08
Send private message quote this post

Likewise, very much appreciated as always @NickMack


Filter this topic showing only the reply marked as answer Create new topic



Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Geekzone Live »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.