Anyone have visibility on Level 3 IPv6 routing? I'm unable to reach http://fedoraproject.org by their primary and ended up having to spoof a secondary in local DNS. Note that this is on HughesNet; multiple levels of support have been clueless or stumped. For the curious: [darton@dkw-vostro ~]$ dig -6 @google-public-dns-a.google.com -t aaaa www.fedoraproject.org ; <<>> DiG 9.9.2-P1-RedHat-9.9.2-3.P1.fc17 <<>> -6 @ google-public-dns-a.google.com -t aaaa www.fedoraproject.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21521 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.fedoraproject.org. IN AAAA ;; ANSWER SECTION: www.fedoraproject.org. 1200 IN CNAME wildcard.fedoraproject.org. wildcard.fedoraproject.org. 1200 IN AAAA 2607:f188::dead:beef:cafe:fed1 wildcard.fedoraproject.org. 1200 IN AAAA 2001:4178:2:1269::fed2 wildcard.fedoraproject.org. 1200 IN AAAA 2610:28:3090:3001:dead:beef:cafe:fed4 ;; Query time: 10 msec ;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888) ;; WHEN: Wed Feb 20 22:13:26 2013 ;; MSG SIZE rcvd: 163 Love the beefy theme there... fed2 is the only one I can't reach, and though the AAAA records are round-robin, fed2 appears to be the one to which HTTP requests get routed and tracing that takes me from Salt Lake to Munich by way of Paris before timing out: [darton@dkw-vostro ~]$ traceroute6 -N 64 fedoraproject.org traceroute to fedoraproject.org (2001:4178:2:1269::fed2), 30 hops max, 80 byte packets 1 2001:5b0:216e:9590:280:aeff:fe3f:4965 (2001:5b0:216e:9590:280:aeff:fe3f:4965) 24.672 ms 24.504 ms 24.506 ms 2 * * * 3 2001:5b0:21ff:fffa::100 (2001:5b0:21ff:fffa::100) 1079.945 ms 1237.825 ms 1290.435 ms 4 vlan122.car1.SaltLakeCity1.Level3.net (2001:1900:2100::d9d) 1341.274 ms 1409.308 ms 1411.624 ms 5 vl-11.car2.SaltLakeCity1.Level3.net (2001:1900:4:1::13e) 1489.445 ms 1508.739 ms 1733.181 ms 6 vl-4043.edge3.Denver1.Level3.net (2001:1900:4:1::142) 1578.809 ms 1639.417 ms 1641.692 ms 7 vl-4081.edge6.Denver1.Level3.net (2001:1900:4:1::32) 1641.783 ms vl-4080.edge6.Denver1.Level3.net (2001:1900:4:1::2e) 1691.372 ms vl-4081.edge6.Denver1.Level3.net (2001:1900:4:1::32) 1698.425 ms 8 vl-4042.edge1.Chicago2.Level3.net (2001:1900:4:1::36) 1745.349 ms 1745.056 ms 1744.322 ms 9 vl-4067.car1.Chicago1.Level3.net (2001:1900:4:1::1d) 1744.410 ms 1744.489 ms 1737.454 ms 10 vl-4061.car2.NewYork2.Level3.net (2001:1900:4:1::22) 1873.919 ms 1873.887 ms 1870.193 ms 11 vl-4080.car1.NewYork2.Level3.net (2001:1900:4:1::f1) 1766.868 ms 1766.506 ms 1765.284 ms 12 vl-4061.edge2.Washington1.Level3.net (2001:1900:4:1::105) 1767.345 ms 1767.463 ms 1767.493 ms 13 vl-4081.edge1.Washington1.Level3.net (2001:1900:4:1::d5) 1767.633 ms vl-4083.edge1.Washington1.Level3.net (2001:1900:4:1::dd) 1801.766 ms vl-4081.edge1.Washington1.Level3.net (2001:1900:4:1::d5) 1801.754 ms 14 vl-4086.edge3.Paris1.Level3.net (2001:1900:6:1::15) 1844.308 ms 1844.440 ms 1844.908 ms 15 vl-4081.edge4.Paris1.Level3.net (2001:1900:5:1::12e) 1844.358 ms 1844.415 ms vl-4080.edge4.Paris1.Level3.net (2001:1900:5:1::12a) 1843.473 ms 16 vl-4060.edge3.Frankfurt1.Level3.net (2001:1900:5:1::215) 1845.091 ms 1845.065 ms 1845.030 ms 17 vl-4043.car1.Munich1.Level3.net (2001:1900:5:1::25e) 1845.052 ms 1845.033 ms 1897.648 ms 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * fed4 is a different route: [darton@dkw-vostro ~]$ traceroute6 2610:28:3090:3001:dead:beef:cafe:fed4 traceroute to 2610:28:3090:3001:dead:beef:cafe:fed4 (2610:28:3090:3001:dead:beef:cafe:fed4), 30 hops max, 80 byte packets 1 2001:5b0:216e:9590:280:aeff:fe3f:4965 (2001:5b0:216e:9590:280:aeff:fe3f:4965) 15.410 ms 15.337 ms 15.269 ms 2 * * * 3 2001:5b0:21ff:fffa::100 (2001:5b0:21ff:fffa::100) 897.468 ms 915.494 ms 975.368 ms 4 vlan122.car1.SaltLakeCity1.Level3.net (2001:1900:2100::d9d) 1026.481 ms 1044.762 ms 1164.987 ms 5 vl-4046.edge5.LosAngeles1.Level3.net (2001:1900:4:1::279) 1198.366 ms 1406.782 ms 1504.377 ms 6 vl-60.edge1.LosAngeles9.Level3.net (2001:1900:12:1::d) 1602.064 ms 789.763 ms 646.960 ms 7 gblx-level3-10G.LosAngeles9.Level3.net (2001:1900:4:3::276) 702.353 ms 733.689 ms 902.689 ms 8 snvang.abilene.ucaid.edu (2001:504:d::bd) 966.739 ms 1006.089 ms 1090.304 ms 9 * * * 10 xe-1-0-2.60.rtr.atla.net.internet2.edu (2001:468:1:60::1) 1260.105 ms 1342.136 ms 1386.991 ms 11 chlt7600-gw-to-chltcrs-gw.ncren.net (2610:28:10c:5::2) 1439.616 ms 1550.497 ms 1630.215 ms 12 manningkid-to-chlt7600-gw.ncren.net (2610:28:10c:7::2) 1034.366 ms 1034.401 ms 1172.668 ms 13 2610:28:3090:23::2 (2610:28:3090:23::2) 1003.700 ms 1017.225 ms * 14 2610:28:3090:3001:dead:beef:cafe:fed4 (2610:28:3090:3001:dead:beef:cafe:fed4) 921.136 ms !X 832.055 ms !X 789.599 ms !X Any ideas/comparisons/insights appreciated. This is so far the only native IPv6 connection I have, despite having access to two datacenters and FiOS, so not much to compare it with. Shameful. Regards, Darton Williams ...Yeah, that guy.
Sorry for the noise, I just looked at Level3 LG again (it returned unknown error messages the last time I tried this). Approximating the same route, their trace reaches fed2 and actually leaves the inter-VLAN whereas mine stops at hop 13 here. I'm guessing the !filtered at the destination is just ICMP. Traceroute results from Salt Lake City, UT to 2001:4178:2:1269::fed2 1 vl-11.car2.SaltLakeCity1.Level3.net (2001:1900:4:1::13E) 0 msec 0 msec 0 msec 2 vl-4043.edge3.Denver1.Level3.net (2001:1900:4:1::142) 56 msec 32 msec 8 msec 3 vl-4080.edge6.Denver1.Level3.net (2001:1900:4:1::2E) 8 msec 12 msec vl-4081.edge6.Denver1.Level3.net (2001:1900:4:1::32) 12 msec 4 vl-4042.edge1.Chicago2.Level3.net (2001:1900:4:1::36) 36 msec 36 msec 36 msec 5 vl-4067.car1.Chicago1.Level3.net (2001:1900:4:1::1D) 36 msec 36 msec 40 msec 6 vl-4061.car2.NewYork2.Level3.net (2001:1900:4:1::22) 88 msec 180 msec 204 msec 7 vl-4081.car1.NewYork2.Level3.net (2001:1900:4:1::F5) 60 msec 56 msec 56 msec 8 vl-4061.edge2.Washington1.Level3.net (2001:1900:4:1::105) 64 msec 60 msec 64 msec 9 vl-4080.edge1.Washington1.Level3.net (2001:1900:4:1::D1) 60 msec 60 msec 64 msec 10 vl-4086.edge3.Paris1.Level3.net (2001:1900:6:1::15) 160 msec 144 msec 144 msec 11 vl-4081.edge4.Paris1.Level3.net (2001:1900:5:1::12E) 140 msec vl-4080.edge4.Paris1.Level3.net (2001:1900:5:1::12A) 144 msec vl-4081.edge4.Paris1.Level3.net (2001:1900:5:1::12E) 140 msec 12 vl-4060.edge3.Frankfurt1.Level3.net (2001:1900:5:1::215) 152 msec 176 msec 148 msec 13 vl-4043.car1.Munich1.Level3.net (2001:1900:5:1::25E) 172 msec 184 msec 220 msec 14 2001:1900:5:2:2::302 156 msec 156 msec 156 msec 15 te9-1-c1.net.muc2.internetx.de (2001:4178:1::6) 160 msec 160 msec 160 msec 16 2001:4178:2:1269::FED2 !filtered !filtered !filtered On Wed, Feb 20, 2013 at 10:39 PM, Darton Williams <dartonw@gmail.com> wrote:
Anyone have visibility on Level 3 IPv6 routing? I'm unable to reach http://fedoraproject.org by their primary and ended up having to spoof a secondary in local DNS. Note that this is on HughesNet; multiple levels of support have been clueless or stumped.
For the curious:
[darton@dkw-vostro ~]$ dig -6 @google-public-dns-a.google.com -t aaaa www.fedoraproject.org
; <<>> DiG 9.9.2-P1-RedHat-9.9.2-3.P1.fc17 <<>> -6 @ google-public-dns-a.google.com -t aaaa www.fedoraproject.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21521 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;www.fedoraproject.org. IN AAAA
;; ANSWER SECTION: www.fedoraproject.org. 1200 IN CNAME wildcard.fedoraproject.org. wildcard.fedoraproject.org. 1200 IN AAAA 2607:f188::dead:beef:cafe:fed1 wildcard.fedoraproject.org. 1200 IN AAAA 2001:4178:2:1269::fed2 wildcard.fedoraproject.org. 1200 IN AAAA 2610:28:3090:3001:dead:beef:cafe:fed4
;; Query time: 10 msec ;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888) ;; WHEN: Wed Feb 20 22:13:26 2013 ;; MSG SIZE rcvd: 163
Love the beefy theme there...
fed2 is the only one I can't reach, and though the AAAA records are round-robin, fed2 appears to be the one to which HTTP requests get routed and tracing that takes me from Salt Lake to Munich by way of Paris before timing out:
[darton@dkw-vostro ~]$ traceroute6 -N 64 fedoraproject.org traceroute to fedoraproject.org (2001:4178:2:1269::fed2), 30 hops max, 80 byte packets 1 2001:5b0:216e:9590:280:aeff:fe3f:4965 (2001:5b0:216e:9590:280:aeff:fe3f:4965) 24.672 ms 24.504 ms 24.506 ms 2 * * * 3 2001:5b0:21ff:fffa::100 (2001:5b0:21ff:fffa::100) 1079.945 ms 1237.825 ms 1290.435 ms 4 vlan122.car1.SaltLakeCity1.Level3.net (2001:1900:2100::d9d) 1341.274 ms 1409.308 ms 1411.624 ms 5 vl-11.car2.SaltLakeCity1.Level3.net (2001:1900:4:1::13e) 1489.445 ms 1508.739 ms 1733.181 ms 6 vl-4043.edge3.Denver1.Level3.net (2001:1900:4:1::142) 1578.809 ms 1639.417 ms 1641.692 ms 7 vl-4081.edge6.Denver1.Level3.net (2001:1900:4:1::32) 1641.783 ms vl-4080.edge6.Denver1.Level3.net (2001:1900:4:1::2e) 1691.372 ms vl-4081.edge6.Denver1.Level3.net (2001:1900:4:1::32) 1698.425 ms 8 vl-4042.edge1.Chicago2.Level3.net (2001:1900:4:1::36) 1745.349 ms 1745.056 ms 1744.322 ms 9 vl-4067.car1.Chicago1.Level3.net (2001:1900:4:1::1d) 1744.410 ms 1744.489 ms 1737.454 ms 10 vl-4061.car2.NewYork2.Level3.net (2001:1900:4:1::22) 1873.919 ms 1873.887 ms 1870.193 ms 11 vl-4080.car1.NewYork2.Level3.net (2001:1900:4:1::f1) 1766.868 ms 1766.506 ms 1765.284 ms 12 vl-4061.edge2.Washington1.Level3.net (2001:1900:4:1::105) 1767.345 ms 1767.463 ms 1767.493 ms 13 vl-4081.edge1.Washington1.Level3.net (2001:1900:4:1::d5) 1767.633 ms vl-4083.edge1.Washington1.Level3.net (2001:1900:4:1::dd) 1801.766 ms vl-4081.edge1.Washington1.Level3.net (2001:1900:4:1::d5) 1801.754 ms 14 vl-4086.edge3.Paris1.Level3.net (2001:1900:6:1::15) 1844.308 ms 1844.440 ms 1844.908 ms 15 vl-4081.edge4.Paris1.Level3.net (2001:1900:5:1::12e) 1844.358 ms 1844.415 ms vl-4080.edge4.Paris1.Level3.net (2001:1900:5:1::12a) 1843.473 ms 16 vl-4060.edge3.Frankfurt1.Level3.net (2001:1900:5:1::215) 1845.091 ms 1845.065 ms 1845.030 ms 17 vl-4043.car1.Munich1.Level3.net (2001:1900:5:1::25e) 1845.052 ms 1845.033 ms 1897.648 ms 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
fed4 is a different route:
[darton@dkw-vostro ~]$ traceroute6 2610:28:3090:3001:dead:beef:cafe:fed4 traceroute to 2610:28:3090:3001:dead:beef:cafe:fed4 (2610:28:3090:3001:dead:beef:cafe:fed4), 30 hops max, 80 byte packets 1 2001:5b0:216e:9590:280:aeff:fe3f:4965 (2001:5b0:216e:9590:280:aeff:fe3f:4965) 15.410 ms 15.337 ms 15.269 ms 2 * * * 3 2001:5b0:21ff:fffa::100 (2001:5b0:21ff:fffa::100) 897.468 ms 915.494 ms 975.368 ms 4 vlan122.car1.SaltLakeCity1.Level3.net (2001:1900:2100::d9d) 1026.481 ms 1044.762 ms 1164.987 ms 5 vl-4046.edge5.LosAngeles1.Level3.net (2001:1900:4:1::279) 1198.366 ms 1406.782 ms 1504.377 ms 6 vl-60.edge1.LosAngeles9.Level3.net (2001:1900:12:1::d) 1602.064 ms 789.763 ms 646.960 ms 7 gblx-level3-10G.LosAngeles9.Level3.net (2001:1900:4:3::276) 702.353 ms 733.689 ms 902.689 ms 8 snvang.abilene.ucaid.edu (2001:504:d::bd) 966.739 ms 1006.089 ms 1090.304 ms 9 * * * 10 xe-1-0-2.60.rtr.atla.net.internet2.edu (2001:468:1:60::1) 1260.105 ms 1342.136 ms 1386.991 ms 11 chlt7600-gw-to-chltcrs-gw.ncren.net (2610:28:10c:5::2) 1439.616 ms 1550.497 ms 1630.215 ms 12 manningkid-to-chlt7600-gw.ncren.net (2610:28:10c:7::2) 1034.366 ms 1034.401 ms 1172.668 ms 13 2610:28:3090:23::2 (2610:28:3090:23::2) 1003.700 ms 1017.225 ms * 14 2610:28:3090:3001:dead:beef:cafe:fed4 (2610:28:3090:3001:dead:beef:cafe:fed4) 921.136 ms !X 832.055 ms !X 789.599 ms !X
Any ideas/comparisons/insights appreciated. This is so far the only native IPv6 connection I have, despite having access to two datacenters and FiOS, so not much to compare it with. Shameful.
Regards,
Darton Williams
...Yeah, that guy.
participants (1)
-
Darton Williams