Hi, I'm trying to learn IPv6 and I'm afraid not very successfully. I have a home network, 3 domain controllers 2 with server 2008 and 1 server 2003. Both 2008 servers are running ipv6. The 2003 server is not. I followed all the instructions, and I even used the openVPN for the TAP client, and it appears it connects, but I can't route. One thing to note: I am running my own DNS, and I have Verizon FiOS. I added the Internet Root DNS servers to my root hints, including the IPv6 servers. Now, I am trying to run the aiccu client on one of my 2008 domain controllers, and everything seems to be working correctly, except I can't view any ipv6 sites.. and it doesn't appear I can ping them either. I ran the autotest and outputted it to a log file where you can see everything is fine except when it gets to #7 and 8. Any ideas? ## Begin Log file ## Tunnel Information for Txxxx: PoP Id : usqas01 IPv6 Local : xxxxx IPv6 Remote : xxxxx Tunnel Type : ayiya Adminstate : enabled Userstate : enabled Name : My First Tunnel ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.xx.xx) ### 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 Pinging 192.168.xx.xx with 32 bytes of data: Reply from 192.168.xx.xx: bytes=32 time<1ms TTL=128 Reply from 192.168.xx.xx: bytes=32 time<1ms TTL=128 Reply from 192.168.xx.xx: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.xx.xx: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### ####### [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 Pinging 66.117.47.228 with 32 bytes of data: Reply from 66.117.47.228: bytes=32 time=14ms TTL=54 Reply from 66.117.47.228: bytes=32 time=13ms TTL=54 Reply from 66.117.47.228: bytes=32 time=14ms TTL=54 Ping statistics for 66.117.47.228: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 14ms, Average = 13ms ###### ####### [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 Tracing route to iad0-sixxs.hotnic.net [66.117.47.228] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.6.1 2 20 ms 54 ms 42 ms 10.4.15.42 3 7 ms 4 ms 7 ms g0-3-4-0.bltmmd-lcr-22.verizon-gni.net [130.81.180.68] 4 * * * Request timed out. 5 12 ms 27 ms 12 ms so-11-1-0-0.res-bb-rtr2.verizon-gni.net [130.81.19.76] 6 11 ms 104 ms 12 ms 0.xe-10-0-0.br2.iad8.alter.net [152.63.34.9] 7 11 ms 14 ms 14 ms te-11-0-0.edge1.washington4.level3.net [4.68.111.253] 8 12 ms 14 ms 14 ms ae-13-69.car3.washington1.level3.net [4.68.17.5] 9 13 ms 14 ms 14 ms carpathia-h.car3.washington1.level3.net [4.79.169.26] 10 15 ms 14 ms 14 ms 209.222.144.164 11 15 ms 14 ms 14 ms iad0-sixxs.hotnic.net [66.117.47.228] Trace complete. ###### ###### [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 Pinging ::1 from ::1 with 32 bytes of data: Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Ping statistics for ::1: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (xxxx) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pinging xxxx from xxxx with 32 bytes of data: Reply from xxxx: time<1ms Reply from xxxx: time<1ms Reply from xxxx: time<1ms Ping statistics for xxxx: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (xxxx) ### 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 (both IPv4 and IPv6) of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem Pinging xxxx from xxxx with 32 bytes of data: Reply from xxxx: time=16ms Reply from xxxx: time=15ms Reply from xxxx: time=38ms Ping statistics for xxxx: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 38ms, Average = 23ms ###### ###### [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. ###### ###### [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 ###### ###### 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.