Okay i've switched to AYIYA, but still not working (ping and websites). Here's the autotest log : C:\Windows\system32>aiccu autotest sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs .net)" sock_printf() : "client TIC/draft-00 AICCU/2008.03.15-console-win32 WinNT/6.1.7 600" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1254338262" sock_printf() : "username AVK7-SIXXS" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 b535446adb1a668711eeaafc161e4fd8" sock_printf() : "authenticate md5 0678f9ffc19857b2771c25dd431b38a9" sock_getline() : "200 Succesfully logged in using md5 as AVK7-SIXXS (Arjan van K ranenburg) from 2001:7b8:3:4f:202:b3ff:fe46:bec" sock_printf() : "tunnel show T23321" sock_getline() : "201 Showing tunnel information for T23321" sock_getline() : "TunnelId: T23321" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:610:600:58b::2" sock_getline() : "IPv6 POP: 2001:610:600:58b::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: nlams05" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 192.87.102.107" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: xxxxxxxxxxx" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T23321 sock_printf() : "QUIT I'll be back. Ha, you didn't know I was going to say that !" Tunnel Information for T23321: PoP Id : nlams05 IPv6 Local : 2001:610:600:58b::2/64 IPv6 Remote : 2001:610:600:58b::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled Name : My First Tunnel Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present [warning] Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D 36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1) Found interface named 'sixxs', with guid {72B8D7F9-4D99-4FF1-B3E0-D4343B91865C}, using it [tun-start] Trying \\.\Global\{72B8D7F9-4D99-4FF1-B3E0-D4343B91865C}.tap Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present [AYIYA-start] : Anything in Anything (draft-02) [AYIYA-tun->tundev] : (Socket to TUN) started heartbeat_socket() - IPv4 : 192.168.1.8 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.8) ### 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.1.8 with 32 bytes of data: Reply from 192.168.1.8: bytes=32 time<1ms TTL=128 Reply from 192.168.1.8: bytes=32 time<1ms TTL=128 Reply from 192.168.1.8: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.1.8: 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 (192.87.102.107) ### 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 192.87.102.107 with 32 bytes of data: Reply from 192.87.102.107: bytes=32 time=27ms TTL=57 Reply from 192.87.102.107: bytes=32 time=27ms TTL=57 Reply from 192.87.102.107: bytes=32 time=27ms TTL=57 Ping statistics for 192.87.102.107: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 27ms, Average = 27ms ###### ####### [3/8] Traceroute to the PoP (192.87.102.107) 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 sixxs.surfnet.nl [192.87.102.107] over a maximum of 30 hops: 1 <1 ms 3 ms <1 ms 192.168.1.1 2 25 ms 26 ms 26 ms ip1-176-173-82.adsl2.static.versatel.nl [82.173. 176.1] 3 25 ms 25 ms 25 ms ge-0-1-0-1104.ncr01asd2.versatel.net [217.16.44. 145] 4 28 ms 28 ms 26 ms ge-0-0-0-664.br01sara.versatel.net [212.53.18.2] 5 26 ms 28 ms 27 ms XSR03.Asd001A.surf.net [195.69.144.50] 6 27 ms 26 ms 26 ms AE2.500.JNR01.Asd001A.surf.net [145.145.80.78] 7 39 ms 29 ms 26 ms V1131.sw4.amsterdam1.surf.net [145.145.19.170] 8 26 ms 28 ms 25 ms sixxs.surfnet.nl [192.87.102.107] 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 with 32 bytes of data: General failure. General failure. General failure. Ping statistics for ::1: Packets: Sent = 3, Received = 0, Lost = 3 (100% loss), ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:610:600:58b::2 ) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pinging 2001:610:600:58b::2 with 32 bytes of data: General failure. General failure. General failure. Ping statistics for 2001:610:600:58b::2: Packets: Sent = 3, Received = 0, Lost = 3 (100% loss), ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:610:600:58b::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 (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 2001:610:600:58b::1 with 32 bytes of data: General failure. General failure. General failure. Ping statistics for 2001:610:600:58b::1: Packets: Sent = 3, Received = 0, Lost = 3 (100% loss), ###### ###### [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 connecti on ### If your browser supports IPv6 and uses it of course. 'tracert6' is not recognized as an internal or external command, operable program or batch file. ###### ###### [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 'tracert6' is not recognized as an internal or external command, operable program or batch file. ###### ###### 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. C:\Windows\system32>