####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.3) ### 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 192.168.1.3 (192.168.1.3): 56 data bytes 64 bytes from 192.168.1.3: icmp_seq=0 ttl=64 time=0.168 ms 64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=0.169 ms 64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.166 ms --- 192.168.1.3 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.166/0.168/0.169/0.001 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (66.117.47.228) ### 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 66.117.47.228 (66.117.47.228): 56 data bytes 64 bytes from 66.117.47.228: icmp_seq=0 ttl=45 time=149.567 ms 64 bytes from 66.117.47.228: icmp_seq=1 ttl=45 time=153.570 ms 64 bytes from 66.117.47.228: icmp_seq=2 ttl=45 time=148.977 ms --- 66.117.47.228 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 148.977/150.705/153.570/2.040 ms ###### ####### [3/8] Traceroute to the PoP (66.117.47.228) 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 66.117.47.228 (66.117.47.228), 64 hops max, 40 byte packets 1 192.168.1.254 (192.168.1.254) 14.171 ms 97.950 ms 99.393 ms 2 10.15.10.29 (10.15.10.29) 154.122 ms 51.425 ms 49.458 ms 3 10.15.10.209 (10.15.10.209) 66.208 ms 42.293 ms 68.053 ms 4 10.9.2.9 (10.9.2.9) 83.180 ms 43.965 ms 45.813 ms 5 10.192.2.121 (10.192.2.121) 54.428 ms 43.709 ms 43.750 ms 6 10.192.2.38 (10.192.2.38) 75.993 ms 44.235 ms 46.862 ms 7 reg-pue-fuertes-24-pos6-2.uninet.net.mx (201.125.242.42) 73.736 ms 65.829 ms 72.954 ms 8 bb-dallas-stemmons-2-pos3-0-0.uninet.net.mx (201.125.50.122) 100.658 ms 102.081 ms 99.076 ms 9 xe-9-2-0.bar2.Houston1.Level3.net (4.59.126.29) 130.330 ms 141.829 ms 131.092 ms 10 * ae-0-11.bar1.Houston1.Level3.net (4.69.137.133) 135.812 ms 128.365 ms 11 ae-13-13.ebr1.Dallas1.Level3.net (4.69.137.138) 130.544 ms 138.155 ms 127.254 ms 12 ae-83-88.ebr3.Dallas1.Level3.net (4.69.146.84) 245.229 ms ae-93-98.ebr3.Dallas1.Level3.net (4.69.146.92) 184.616 ms ae-63-68.ebr3.Dallas1.Level3.net (4.69.146.68) 234.582 ms 13 ae-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 147.574 ms 147.644 ms 156.819 ms 14 ae-2.ebr1.Washington1.Level3.net (4.69.132.86) 150.659 ms 151.596 ms 158.503 ms 15 ae-81-81.csw3.Washington1.Level3.net (4.69.134.138) 150.331 ms ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 149.864 ms ae-81-81.csw3.Washington1.Level3.net (4.69.134.138) 154.234 ms 16 ae-43-99.car3.Washington1.Level3.net (4.68.17.197) 142.046 ms ae-23-79.car3.Washington1.Level3.net (4.68.17.69) 142.149 ms ae-43-99.car3.Washington1.Level3.net (4.68.17.197) 146.164 ms 17 CARPATHIA-H.car3.Washington1.Level3.net (4.79.169.26) 143.471 ms 164.766 ms 172.433 ms 18 209.222.144.164 (209.222.144.164) 210.816 ms 139.668 ms 139.360 ms 19 iad0-sixxs.hotnic.net (66.117.47.228) 146.830 ms 210.104 ms 142.876 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 PING6(56=40+8+8 bytes) ::1 --> ::1 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=0 hlim=64 dst=::1 time=1.011 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=1 hlim=64 dst=::1 time=1.349 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=2 hlim=64 dst=::1 time=1.398 ms --- ::1 ping6 statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 1.011/1.253/1.398 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4830:1600:1d5::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING6(56=40+8+8 bytes) 2001:4830:1600:1d5::2 --> 2001:4830:1600:1d5::2 16 bytes from 2001:4830:1600:1d5::2: Echo Request 16 bytes from 2001:4830:1600:1d5::2, icmp_seq=0 hlim=64 dst=2001:4830:1600:1d5::2 time=0.944 ms 16 bytes from 2001:4830:1600:1d5::2: Echo Request 16 bytes from 2001:4830:1600:1d5::2, icmp_seq=1 hlim=64 dst=2001:4830:1600:1d5::2 time=1.532 ms 16 bytes from 2001:4830:1600:1d5::2: Echo Request 16 bytes from 2001:4830:1600:1d5::2, icmp_seq=2 hlim=64 dst=2001:4830:1600:1d5::2 time=2.421 ms --- 2001:4830:1600:1d5::2 ping6 statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.944/1.632/2.421 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4830:1600:1d5::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 PING6(56=40+8+8 bytes) 2001:4830:1600:1d5::2 --> 2001:4830:1600:1d5::1 16 bytes from 2001:4830:1600:1d5::1, icmp_seq=0 hlim=64 dst=2001:4830:1600:1d5::2 time=147.541 ms 16 bytes from 2001:4830:1600:1d5::1, icmp_seq=1 hlim=64 dst=2001:4830:1600:1d5::2 time=147.404 ms 16 bytes from 2001:4830:1600:1d5::1, icmp_seq=2 hlim=64 dst=2001:4830:1600:1d5::2 time=151.183 ms --- 2001:4830:1600:1d5::1 ping6 statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 147.404/148.709/151.183 ms ###### ###### [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. traceroute6 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:4830:1600:1d5::2, 30 hops max, 12 byte packets 1 gw-470.qas-01.us.sixxs.net 150.416 ms 152.7 ms 151.01 ms 2 sixxs-gw.hotnic.us.occaid.net 150.612 ms 154.311 ms 155.034 ms 3 iad0-b0-ge2.hotnic.net 150.322 ms 154.573 ms 150.842 ms 4 carpathia-gw.hotnic.net 231.708 ms 236.928 ms 243.349 ms 5 * * * 6 * * * ======= TRIMMED ======= ^C ###### ###### [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 traceroute6 to www.kame.net (2001:200::8002:203:47ff:fea5:3085) from 2001:4830:1600:1d5::2, 30 hops max, 12 byte packets 1 gw-470.qas-01.us.sixxs.net 151.913 ms 149.831 ms 154.258 ms 2 sixxs-gw.hotnic.us.occaid.net 150.694 ms 150.41 ms 150.874 ms 3 iad0-b0-ge2.hotnic.net 150.566 ms 150.4 ms 155.024 ms 4 carpathia-gw.hotnic.net 150.432 ms 150.463 ms 220.06 ms 5 xe-3-3.e3.iad1.cirn.net 161.713 ms 157.083 ms 156.573 ms 6 2001:4838:0:1::c:2 154.219 ms 154.4 ms 154.577 ms 7 * * * ======= TRIMMED ======= ^C ###### ###### ACCU Quick Connectivity Test (done)