Maybe some of the TekSavvy guys (TSI Gabe, ahem) could answer this.
Is there any thoughts on improving routing for IPv6 packets? It seems right now all IPv6 is sent to Hurricane Electric, rather than enjoying the existing peering arrangements IPv4 packets have at TORIX.
Example:
$ host www.akamai.com
a152.dscb.akamai.net has address 184.84.243.97
a152.dscb.akamai.net has IPv6 address 2600:1408:e::1700:a053
$ mtr -4 www.akamai.com
1. router.asus.com 0.0% 9 15.4 10.2 4.0 21.3 6.7
2. lo-100.erx04.tor.man.teksavvy.co 0.0% 9 18.3 10.5 9.1 18.3 2.9
3. 2120.ae1.bdr04.tor.man.teksavvy. 0.0% 9 17.2 17.4 8.5 46.6 11.9
4. 69.196.136.131 0.0% 9 15.0 12.0 8.3 15.3 2.9
5. Paix-tor.netarch.akamai.com 0.0% 9 8.9 26.7 8.9 167.9 52.9
6. a184-84-243-97.deploy.static.aka 0.0% 8 8.8 13.5 8.7 20.3 5.0
6 hops and 8.8ms away via TORIX peering on IPv4.
On the other hand:
$ mtr -6 a152.dscb.akamai.net
1. node-77b4p8gf8raogru139k.ipv6.te 0.0% 5 7.8 9.8 4.2 15.8 4.3
2. node-5gv2rma270x9kaok.ipv6.teksa 0.0% 5 21.5 16.7 10.0 21.5 5.4
3. node-66adisk3havm915v.ipv6.teksa 0.0% 5 8.8 9.5 8.5 12.0 1.2
4. gw-he.ip6.torontointernetxchange 0.0% 5 8.8 14.7 8.8 31.0 9.5
5. 100ge1-2.core1.nyc4.he.net 0.0% 5 22.1 25.6 18.6 36.3 6.7
6. twcable-backbone-as7843.10gigabi 0.0% 5 29.4 22.9 18.4 29.4 5.7
7. 2001:1998:0:4::107 0.0% 5 20.0 26.3 20.0 35.5 6.4
8. 2001:1998:0:4::ad 0.0% 5 29.0 31.6 27.4 44.2 7.1
9. 2001:1998:0:4::86 0.0% 5 31.2 31.4 27.9 38.4 4.1
10. 2001:1998:0:4::f2 0.0% 5 37.8 33.3 26.4 39.7 6.3
11. 2001:1998:0:8::b7 0.0% 4 27.8 33.3 27.8 41.9 6.3
12. 2600:1408:e::1700:a053 0.0% 4 25.2 25.8 24.7 28.7 1.7
12 hops and 25ms away. This is going to Hurricane Electric via TORIX, who's then routing it around their network and peering arrangements, and then it's ending up at what is likely the same network as the IPv4 host.
Thanks all. Keep up the great work.
d
↧