Tunnel Information for T9710: POP Id : usatl01 IPv6 Local : 2001:4830:1700:34::2/64 IPv6 Remote : 2001:4830:1700:34::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (ayiya) ### 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: unknown host ayiya ###### ####### [2/8] Ping the IPv4 Remote/POP Outer Endpoint (216.10.93.2) ### 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.10.93.2 (216.10.93.2) 56(84) bytes of data. 64 bytes from 216.10.93.2: icmp_seq=1 ttl=48 time=46.3 ms 64 bytes from 216.10.93.2: icmp_seq=2 ttl=48 time=48.5 ms 64 bytes from 216.10.93.2: icmp_seq=3 ttl=48 time=50.7 ms --- 216.10.93.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2011ms rtt min/avg/max/mdev = 46.379/48.568/50.735/1.787 ms ###### ####### [3/8] Traceroute to the POP (216.10.93.2) 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.034 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.043 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.043 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.034/0.040/0.043/0.004 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4830:1700:34::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables connect: Network is unreachable ###### ###### [6/8] Ping the IPv6 Remote/POP Inner Tunnel Endpoint (2001:4830:1700:34::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 connect: Network is unreachable ###### ###### [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. connect: Network is unreachable ###### ###### [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 connect: Network is unreachable ###### ###### 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.