SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #11073674
Ticket Status: Resolved

PoP: 

Tunnel is up, but no connectivity
[us] Shadow Hawkins on Thursday, 13 February 2014 21:09:34
My tunnel BCV6-SIXXS/T131442 is up, but there seems to be no internet connectivity. Anything I try to reach pretty much comes back the same as this: traceroute to ipv6.l.google.com (2607:f8b0:4002:c07::8b) from 2607:f878:ff00:85: :2, 30 hops max, 16 byte packets 1 2607:f878:ff00:85::1 (2607:f878:ff00:85::1) 59.982 ms 62.561 ms 70.018 m$ 2 2607:f878:4:80::2 (2607:f878:4:80::2) 63.927 ms 61.14 ms 60.785 ms 3 2607:f878:4:2d::1 (2607:f878:4:2d::1) 65.108 ms !N 63.231 ms !N 61.691 m$ !N Trying the other way from an HE-connected host, the trace quits at what looks to be just on the edge of BurstNet: traceroute to fornost.benshome.net (2607:f878:ff00:8085::1) from 2001:470:1f06:8 f8::2, 30 hops max, 24 byte packets 1 Oloryn-3.tunnel.tserv4.nyc4.ipv6.he.net (2001:470:1f06:8f8::1) 5.288 ms 4. 967 ms 4.749 ms 2 ge3-8.core1.nyc4.he.net (2001:470:0:5d::1) 6.2 ms 5.932 ms 0.65 ms 3 level3.gige-g3-5.core1.nyc4.he.net (2001:470:0:202::2) 1.256 ms 12.444 ms 1.142 ms 4 2001:1900:19:6::8 (2001:1900:19:6::8) 0.706 ms 0.716 ms 0.587 ms 5 vl-4061.car1.Newark1.Level3.net (2001:1900:4:1::cd) 1.571 ms 2.321 ms 1.9 55 ms 6 vl-51.edge3.Newark1.Level3.net (2001:1900:34:1::9) 1.437 ms 1.394 ms 1.48 5 ms 7 BURSTNET-TE.edge3.Newark1.Level3.net (2001:1900:2100::1dbe) 7.316 ms 7.37 ms 7.28 ms 8 * * * 9 * * * 10 * * * From a linode host, it dies just when it gets inside 2607:f878::0/32: traceroute to fornost.benshome.net (2607:f878:ff00:8085::1), 30 hops max, 80 byte packets 1 2600:3c02::8678:acff:fe5a:1941 (2600:3c02::8678:acff:fe5a:1941) 1.011 ms 0.982 ms 1.103 ms 2 2604:b900:1::1 (2604:b900:1::1) 0.925 ms 0.877 ms 0.851 ms 3 xe-2-0-5-101.ar1.atl1.us.nlayer.net (2001:590::451f:8729) 1.872 ms 1.846 ms 1.845 ms 4 ae0-60g.cr1.atl1.us.nlayer.net (2001:590::451f:8781) 0.719 ms 0.707 ms 0.676 ms 5 xe-8-3-0.cr1.nyc2.us.nlayer.net (2001:590::4516:8e8d) 17.242 ms 17.225 ms 17.201 ms 6 ae1-60g.cr1.ewr1.us.nlayer.net (2001:590::451f:5fad) 20.865 ms 19.611 ms 17.610 ms 7 xe-0-0-3.cr1.phl1.us.nlayer.net (2001:590::4516:8ea1) 20.513 ms 20.489 ms 20.480 ms 8 2001:590::c62f:6e1e (2001:590::c62f:6e1e) 25.027 ms 25.010 ms 25.108 ms 9 2607:f878::383 (2607:f878::383) 24.851 ms !H * * I think this has been going on for a couple of days, but I didn't connect the problems I was seeing to the IPv6 connection until today. Could be related to the current winter storms in the SouthEast taking out some connections.
Tunnel is up, but no connectivity
[ch] Jeroen Massar SixXS Staff on Thursday, 13 February 2014 21:18:58
Seems there are transit issues there. PoP owner contacted for them to resolve this.

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

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