SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #5990922
Ticket Status: Resolved

PoP: 

2001:6f8:1400::/40 unreachable
[be] Shadow Hawkins on Tuesday, 29 November 2011 09:58:06
[admin edit: old subject: "bebru01 disconnected from IPv6 Internet"] Just a quick heads-up: bebru01 seems to have lost its IPv6 connectivity in the last hours. The tunnel itself is up and running but traceroute6 does not go beyond the PoP (see end of message). Thanks in advance -ric (eric@vyncke.org)
# traceroute6 www.ietf.org traceroute6 to www.ietf.org (2001:1890:123a::1:1e) from 2001:6f8:1468:1001:226:bbff:fe4e:9434, 64 hops max, 12 byte packets 1 family.vyncke.org 2.035 ms 0.868 ms 0.880 ms 2 gw-926.bru-01.be.sixxs.net 24.249 ms 24.906 ms 25.317 ms 3 sixxs-gw.gdbru.be.easynet.net 26.338 ms 24.676 ms 24.865 ms 4 * * *
and
Tunnel Information for T20180: POP Id : bebru01 IPv6 Local : 2001:6f8:202:39d::2/64 IPv6 Remote : 2001:6f8:202:39d::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 29 November 2011 09:57:15
Message is Locked
The state of this ticket has been changed to confirmed
2001:6f8:1400::/40 unreachable
[ch] Jeroen Massar SixXS Staff on Tuesday, 29 November 2011 09:59:56
This affects the routing of 2001:6f8:1400::/40, other services (tunnels and the other /40) are unaffected.
2001:6f8:1400::/40 unreachable
[be] Shadow Hawkins on Tuesday, 29 November 2011 14:19:13
Doh ... That explains my issue I guess. Outgoing packets are working fine, but the reply packets never get here. I tought the issue was on my end (since I made firewall change this morning) but turns out I spent the last 3 hours debugging an issue not on my side.
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 29 November 2011 18:08:56
Message is Locked
The state of this ticket has been changed to resolved

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

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