SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #3703193
Ticket Status: Resolved

PoP: 

Tunnel not passing data
[gb] Shadow Hawkins on Friday, 18 February 2011 13:18:25
I have read and followed the "Reporting Problems" section on the Contact page. Problem Tunnel doesn't appear to pass data in either direction, despite troubleshooting. Additionally, tcpdump shows protocol 41 unreachable (see end of information for tcpdump information). Without knowledge of how this is supposed to work, I don't know if this is significant. AICCU autotest output: Tunnel Information for T29717: POP Id : usdal01 IPv6 Local : 2001:1938:80:14b::2/64 IPv6 Remote : 2001:1938:80:14b::1/64 Tunnel Type : 6in4-static Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (174.123.188.106) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack PING 174.123.188.106 (174.123.188.106) 56(84) bytes of data. 64 bytes from 174.123.188.106: icmp_req=1 ttl=64 time=0.027 ms 64 bytes from 174.123.188.106: icmp_req=2 ttl=64 time=0.047 ms 64 bytes from 174.123.188.106: icmp_req=3 ttl=64 time=0.024 ms --- 174.123.188.106 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.024/0.032/0.047/0.012 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (209.197.16.66) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur PING 209.197.16.66 (209.197.16.66) 56(84) bytes of data. 64 bytes from 209.197.16.66: icmp_req=1 ttl=57 time=47.0 ms 64 bytes from 209.197.16.66: icmp_req=2 ttl=57 time=47.0 ms 64 bytes from 209.197.16.66: icmp_req=3 ttl=57 time=46.9 ms --- 209.197.16.66 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 46.994/47.012/47.029/0.014 ms ###### ####### [3/8] Traceroute to the PoP (209.197.16.66) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem sh: traceroute: command not found ###### ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.021 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.034 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.021/0.028/0.034/0.005 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1938:80:14b::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:1938:80:14b::2(2001:1938:80:14b::2) 56 data bytes 64 bytes from 2001:1938:80:14b::2: icmp_seq=1 ttl=64 time=0.021 ms 64 bytes from 2001:1938:80:14b::2: icmp_seq=2 ttl=64 time=0.146 ms 64 bytes from 2001:1938:80:14b::2: icmp_seq=3 ttl=64 time=0.079 ms --- 2001:1938:80:14b::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.021/0.082/0.146/0.051 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1938:80:14b::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem PING 2001:1938:80:14b::1(2001:1938:80:14b::1) 56 data bytes From 2001:1938:80:14b::2 icmp_seq=2 Destination unreachable: Address unreachable From 2001:1938:80:14b::2 icmp_seq=3 Destination unreachable: Address unreachable --- 2001:1938:80:14b::1 ping statistics --- 3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2016ms ###### ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:1938:80:14b::2, 30 hops max, 24 byte packets 1 cl-332.dal-01.us.sixxs.net (2001:1938:80:14b::2) 0.043 ms !H * 0.081 ms !H ###### ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2001:1938:80:14b::2, 30 hops max, 24 byte packets 1 cl-332.dal-01.us.sixxs.net (2001:1938:80:14b::2) 0.038 ms !H * 0.068 ms !H ###### ###### ACCU Quick Connectivity Test (done) AICCU Source AICCU came from Gentoo Portage Setup details Connection is direct to internet with a static IPv4 address OS details OS is Gentoo 2.6.36-hardened-r6-selinux Interface details (ifconfig) eth0 Link encap:Ethernet HWaddr 00:1d:09:fe:c7:2c inet addr:174.123.188.106 Bcast:174.123.188.111 Mask:255.255.255.248 inet6 addr: fe80::21d:9ff:fefe:c72c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:498416221 errors:0 dropped:0 overruns:0 frame:0 TX packets:949988072 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:46226526079 (43.0 GiB) TX bytes:1382894607243 (1.2 TiB) Interrupt:16 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:10565094 errors:0 dropped:0 overruns:0 frame:0 TX packets:10565094 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2892295958 (2.6 GiB) TX bytes:2892295958 (2.6 GiB) sixxs Link encap:IPv6-in-IPv4 inet6 addr: fe80::ae7b:bc6a/128 Scope:Link inet6 addr: 2001:1938:80:14b::2/64 Scope:Global UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:312 (312.0 B) Kernel routing table for v6 Kernel IPv6 routing table Destination Next Hop Flag Met Ref Use If ::1/128 :: Un 0 11255794 lo 2001:1938:80:14b::2/128 :: Un 0 1 10 lo 2001:1938:80:14b::/64 :: Un 256 0 1 sixxs fe80::ae7b:bc6a/128 :: Un 0 1 0 lo fe80::21d:9ff:fefe:c72c/128 :: Un 0 1 0 lo fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: Un 256 0 0 sixxs ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 sixxs ::/0 2001:1938:80:14b::1 UG 1024 0 8 sixxs ::/0 :: !n -1 1 9702 lo Firewall details No firewall rules for testing purposes. tcpdump output for "ping6 sixxs.net" 10:50:42.103986 IP 174.123.188.106 > 209.197.16.66: IP6 2001:1938:80:14b::2 > 2001:1af8:4050::2: ICMP6, echo request, seq 2, length 64 0x0000: 4500 007c 0000 4000 4029 ed6b ae7b bc6a E..|..@.@).k.{.j 0x0010: d1c5 1042 6000 0000 0040 3a40 2001 1938 ...B`....@:@...8 0x0020: 0080 014b 0000 0000 0000 0002 2001 1af8 ...K............ 0x0030: 4050 0000 0000 0000 0000 0002 8000 9197 @P.............. 0x0040: 4f95 0002 024f 5e4d 0000 0000 c795 0100 O....O^M........ 0x0050: 0000 0000 1011 1213 1415 1617 1819 1a1b ................ 0x0060: 1c1d 1e1f 2021 2223 2425 2627 2829 2a2b .....!"#$%&'()*+ 0x0070: 2c2d 2e2f 3031 3233 3435 3637 ,-./01234567 10:50:42.150970 IP 209.197.16.66 > 174.123.188.106: ICMP 209.197.16.66 protocol 41 unreachable, length 132 0x0000: 4500 0098 129d 0000 3901 21db d1c5 1042 E.......9.!....B 0x0010: ae7b bc6a 0302 62f7 0000 0000 4500 007c .{.j..b.....E..| 0x0020: 0000 4000 3729 f66b ae7b bc6a d1c5 1042 ..@.7).k.{.j...B 0x0030: 6000 0000 0040 3a40 2001 1938 0080 014b `....@:@...8...K 0x0040: 0000 0000 0000 0002 2001 1af8 4050 0000 ............@P.. 0x0050: 0000 0000 0000 0002 8000 9197 4f95 0002 ............O... 0x0060: 024f 5e4d 0000 0000 c795 0100 0000 0000 .O^M............ 0x0070: 1011 1213 1415 1617 1819 1a1b 1c1d 1e1f ................ 0x0080: 2021 2223 2425 2627 2829 2a2b 2c2d 2e2f .!"#$%&'()*+,-./ 0x0090: 3031 3233 3435 3637 01234567
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 18 February 2011 13:28:57
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