SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #3810429
Ticket Status: Resolved

PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)

POP unreachable
[de] Carmen Sandiego on Thursday, 03 March 2011 23:22:08
This afternoon I lost connectivity on one of my tunnels: The POP side of the tunnel responds to IPv4 pings but not to IPv6 pings: Backstage:~# ping -c 4 PING ( 56(84) bytes of data. 64 bytes from icmp_seq=1 ttl=58 time=16.6 ms 64 bytes from icmp_seq=2 ttl=58 time=21.2 ms 64 bytes from icmp_seq=3 ttl=58 time=17.2 ms 64 bytes from icmp_seq=4 ttl=58 time=16.6 ms --- ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3032ms rtt min/avg/max/mdev = 16.645/17.968/21.259/1.923 ms Backstage:~# ping6 -c4 2a01:198:200:7ee::1 PING 2a01:198:200:7ee::1(2a01:198:200:7ee::1) 56 data bytes --- 2a01:198:200:7ee::1 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3016ms In the tcpdump this looks like this ( is an internal IP of the host but the NAT gateway deals with protocol 41 correctly): 23:16:59.981270 IP > IP6 2a01:198:200:7ee::2 > 2a01:198:200:7ee::1: ICMP6, echo request, seq 11, length 64 23:16:59.998490 IP > ICMP protocol 41 port 0 unreachable, length 132 The tunnel is configured to use 6in4-heartbeat. Any help would be appreciated!
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 04 March 2011 09:03:35
Message is Locked
The state of this ticket has been changed to resolved
POP unreachable
[ch] Jeroen Massar SixXS Staff on Friday, 04 March 2011 09:03:50
You changed it from AYIYA to heartbeat, which is not a direct change.

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

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