To whom it may concern, My NIC handle is CWI3-SIXXS. I setup a tunnel here at work similar to the one I setup at home. My home IPv6 is working fine. The problem I'm having is for some reason I just can't ping the other side of my tunnel. I run the AICCU autotest and it fails at 6/8. 5/8 and below work fine. I watched in Wireshark while trying to ping the PoP and I see the IPv6 go out the interface and then I see an IPv4 ICMP come back which states "Destination Unreachable (Port Unavailable)". I have tried this with ip6tables turned off and get the same result. My side of the tunnel is 2001:4978:f:3d6::2 and I'm trying to ping far side 2001:4978:f:3d6::1. I have this setup on RHEL5, output of uname -a "Linux col1-it-2314-r5.kimballmidwest.local 2.6.18-92.1.17.el5_lustre.1.8.0smp #1 SMP Wed Feb 18 18:40:54 MST 2009 i686 i686 i386 GNU/Linux". I have the firewall turned off while trying to get this working and will enable it once I can ping and talk to the far side. Output of the AICCU test: ioctl: No buffer space available RTNETLINK answers: File exists RTNETLINK answers: File exists ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (68.79.74.140) ### 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 68.79.74.140 (68.79.74.140) 56(84) bytes of data. 64 bytes from 68.79.74.140: icmp_seq=1 ttl=64 time=0.067 ms 64 bytes from 68.79.74.140: icmp_seq=2 ttl=64 time=0.040 ms 64 bytes from 68.79.74.140: icmp_seq=3 ttl=64 time=0.040 ms --- 68.79.74.140 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.040/0.049/0.067/0.012 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.14.98.22) ### 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 216.14.98.22 (216.14.98.22) 56(84) bytes of data. 64 bytes from 216.14.98.22: icmp_seq=1 ttl=57 time=18.9 ms 64 bytes from 216.14.98.22: icmp_seq=2 ttl=57 time=17.8 ms 64 bytes from 216.14.98.22: icmp_seq=3 ttl=57 time=18.2 ms --- 216.14.98.22 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 17.820/18.346/18.991/0.485 ms ###### ####### [3/8] Traceroute to the PoP (216.14.98.22) 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 traceroute to 216.14.98.22 (216.14.98.22), 30 hops max, 40 byte packets 1 adsl-68-79-74-142.dsl.wotnoh.ameritech.net (68.79.74.142) 0.871 ms 1.007 ms 1.276 ms 2 192.0.2.100 (192.0.2.100) 9.280 ms 10.355 ms 12.366 ms 3 dist1-vlan62.wotnoh.sbcglobal.net (71.149.193.33) 14.840 ms 16.528 ms 19.994 ms 4 bb2-g8-2.wotnoh.sbcglobal.net (151.164.92.20) 21.205 ms 23.356 ms 25.929 ms 5 151.164.99.129 (151.164.99.129) 39.821 ms 42.326 ms 43.698 ms 6 gige-g2-7.core1.chi1.he.net (64.71.140.137) 44.516 ms 44.409 ms 45.675 ms 7 64.71.148.238 (64.71.148.238) 48.994 ms 43.237 ms 44.460 ms 8 sixxs.cx01.chi.bb.your.org (216.14.98.22) 45.044 ms 44.744 ms 44.559 ms ###### ###### [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=0 ttl=64 time=0.414 ms 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.032 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.031 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.031/0.159/0.414/0.180 ms, pipe 2 ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4978:f:3d6::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:4978:f:3d6::2(2001:4978:f:3d6::2) 56 data bytes 64 bytes from 2001:4978:f:3d6::2: icmp_seq=0 ttl=64 time=0.035 ms 64 bytes from 2001:4978:f:3d6::2: icmp_seq=1 ttl=64 time=0.032 ms 64 bytes from 2001:4978:f:3d6::2: icmp_seq=2 ttl=64 time=0.033 ms --- 2001:4978:f:3d6::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.032/0.033/0.035/0.004 ms, pipe 2 ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4978:f:3d6::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:4978:f:3d6::1(2001:4978:f:3d6::1) 56 data bytes --- 2001:4978:f:3d6::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2000ms ###### ###### [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), 30 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### ###### [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 www.kame.net (2001:200:0:8002:203:47ff:fea5:3085), 30 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### ###### ACCU Quick Connectivity Test (done) ### Either the above all works and gives no problems ### or it shows you where what goes wrong ### Check the SixXS FAQ (http://www.sixxs.net/faq/ ### for more information and possible solutions or hints ### Don't forget to check the Forums (http://www.sixxs.net/forum/) ### for a helping hand. ### Passing the output of 'aiccu autotest >aiccu.log' is a good idea. I hate to bother you all with something like this but I'm at the end of the road and feel I have tried everything. My exact same setup at home came up without a problem. The only difference is I'm on a ATT&T DSL and not Time Warner cable mode. Thanks for all your help in advance, Chad