SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #516921
Ticket Status: Resolved

PoP: nlams04 - Stipte B.V. (Amsterdam)

No routing via nlams04
[gb] Shadow Hawkins on Monday, 07 May 2007 22:02:38
I can't seem to route past nlams04, I can ping the remote end of the tunnel (the "1" address but nothing further. A tcpdump from the firewall of a single icmp packet destined for www.kame.net produced the below. (real IP replaced for xxx) firewall# tcpdump -ni gif0 tcpdump: WARNING: gif0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on gif0, link-type NULL (BSD loopback), capture size 96 bytes 19:53:30.987228 IP6 2001:960:2:xxx::2 > 2001:200:0:8002:203:47ff:fea5:3085: ICMP6, echo request, seq 0, length 16 19:53:31.024707 IP6 2001:960:2:xxx::1 > 2001:960:2:xxx::2: ICMP6, destination unreachable, unreachable route 2001:200:0:8002:203:47ff:fea5:3085, length 64 19:53:35.985765 IP6 2001:960:2:xxx::2 > 2001:960:2:xxx::1: ICMP6, neighbor solicitation, who has 2001:960:2:xxx::1, length 24 19:53:36.026515 IP6 2001:960:2:xxx::1 > 2001:960:2:xxx::2: ICMP6, neighbor advertisement, tgt is 2001:960:2:xxx::1, length 24
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Monday, 07 May 2007 22:01:31
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