SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1225142
Ticket Status: Resolved

PoP: nlams05 - SURFnet (Amsterdam)

T10670 tunnel fails, no traffic.
[nl] Shadow Hawkins on Friday, 09 October 2009 15:05:36
Dear SixXS, Yesterday I converted my tunnel from a AICCU to a plain 6in4 tunnel. My tunnel had been down for a long time. I think I see corretly encapsulated IPv4 traffic leaving my router but no icmp reply is sent back. Example: On tunnel T10670 node Surfnet nlams05 ping6 2001:610:600:364::1 IPv4 source: 145.103.250.253 Tcpdump on outgoing ethernet interface: 12:59:25.644994 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto IPv6 (41), length 124) 145.103.250.253 > 192.87.102.107: IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:610:600:364::2 > 2001:610:600:364::1: ICMP6, echo request, length 64, seq 400 12:59:26.644992 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto IPv6 (41), length 124) 145.103.250.253 > 192.87.102.107: IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:610:600:364::2 > 2001:610:600:364::1: ICMP6, echo request, length 64, seq 401 I am using a Linux Vyatta based router version 3.4.6 which support 6in4 tunnels. Hope you can help me because I can not debug any further. With kind regards, Paul Boot.
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 09 October 2009 15:21:42
Message is Locked
The state of this ticket has been changed to resolved
T10670 tunnel fails, no traffic.
[ch] Jeroen Massar SixXS Staff on Friday, 09 October 2009 15:22:12
Resynced PoP (tunnel type changes sometimes go wrong), and works now: 64 bytes from 2001:610:600:364::2: icmp_seq=0 ttl=64 time=3.56 ms
T10670 tunnel fails, no traffic.
[nl] Shadow Hawkins on Friday, 09 October 2009 15:23:08
Thanks Jeroen, Happy on IPv6 again;-) With kind regards, Paul Boot.

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

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