SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #10183190
Ticket Status: Resolved

PoP: 

Can't reach puck.nether.net or ubuntu repository addresses through usmia01
[us] Shadow Hawkins on Thursday, 26 September 2013 02:50:29
Hi-ho! I am unable to reach the IPv6 addresses for puck.nether.net (prefix 2001:67c:1562) or the ubuntu repositories us.archive.ubuntu.com and security.ubuntu.com (prefixes 2001:67c:1562 and 2001:67c:1360:8c01) out of the usmia01 POP. I'm connecting via my BCV6-SIXXS/T131442 tunnel, which appears to be working fine. I have no problems connecting to ipv6.google.com or to some Linode and Digital Ocean servers that I admin. Relevant traceroutes:
traceroute to puck.nether.net (2001:418:3f4::5) from 2607:f878:ff00:85::2, 30 hops max, 16 byte packets 1 gw-134.mia-01.us.sixxs.net (2607:f878:ff00:85::1) 28.115 ms 28.071 ms 34.613 ms 2 2607:f878:4:80::2 (2607:f878:4:80::2) 29.176 ms 26.786 ms 26.521 ms 3 2607:f878:4:2d::1 (2607:f878:4:2d::1) 26.724 ms 27.876 ms 26.98 ms 4 2607:f878::17e (2607:f878::17e) 28.624 ms 28.907 ms 26.775 ms 5 * * * 6 * * * 7 * * * 8 2607:f878::183 (2607:f878::183) 98.221 ms !N 96.653 ms !N * traceroute to us.archive.ubuntu.com (2001:67c:1562::15) from 2607:f878:ff00:85:: 2, 30 hops max, 16 byte packets 1 gw-134.mia-01.us.sixxs.net (2607:f878:ff00:85::1) 28.199 ms 31.448 ms 28$ 913 ms 2 2607:f878:4:80::2 (2607:f878:4:80::2) 28.771 ms 29.841 ms 30.902 ms 3 2607:f878:4:2d::1 (2607:f878:4:2d::1) 30.23 ms 39.557 ms 30.586 ms 4 2607:f878::17e (2607:f878::17e) 34.839 ms 32.289 ms 31.558 ms 5 2607:f878::183 (2607:f878::183) 99.102 ms !N * * 6 * * * 7 * * * 8 * 2607:f878::183 (2607:f878::183) 104.166 ms !N * 9 2607:f878::183 (2607:f878::183) 98.214 ms !N * * 10 * * * 11 2607:f878::183 (2607:f878::183) 97.222 ms !N * * 12 * * * 13 * 2607:f878::183 (2607:f878::183) 98.791 ms !N * 14 2607:f878::183 (2607:f878::183) 97.399 ms !N * * 15 * * * 16 * * 2607:f878::183 (2607:f878::183) 96.88 ms !N 17 * * * 18 2607:f878::183 (2607:f878::183) 105.18 ms !N * * 19 2607:f878::183 (2607:f878::183) 96.208 ms !N * * 20 2607:f878::183 (2607:f878::183) 106.337 ms !N * * 21 * * * 22 * 2607:f878::183 (2607:f878::183) 103.967 ms !N * 23 * * * 24 * * * 25 * * * 26 2607:f878::183 (2607:f878::183) 140.395 ms !N * 101.535 ms !N security.ubuntu.com traceroute to security.ubuntu.com (2001:67c:1360:8c01::15) from 2607:f878:ff00:85::2, 30 hops max, 16 byte packets 1 gw-134.mia-01.us.sixxs.net (2607:f878:ff00:85::1) 34.938 ms 36.341 ms 28.254 ms 2 2607:f878:4:80::2 (2607:f878:4:80::2) 33.737 ms 28.363 ms 32.22 ms 3 2607:f878:4:2d::1 (2607:f878:4:2d::1) 33.01 ms 28.766 ms 27.833 ms 4 2607:f878::17e (2607:f878::17e) 28.744 ms 34.261 ms 28.927 ms 5 * 2607:f878::183 (2607:f878::183) 98.313 ms !N * 6 * 2607:f878::183 (2607:f878::183) 99 ms !N * 7 * * * 8 2607:f878::183 (2607:f878::183) 110.3 ms !N 107.28 ms !N 97.69 ms !N
Everything appears to stop at 2607:f878::183, with some looping. This has been going on for several days (probably since I set the tunnel up, but I didn't notice it immediately). I tried to see what Looking Glass could tell me, but wasn't able to make much out of it. I presume you'll hand this off to BurstNet, but I thought I should get this reported.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker