Hello all, Im trying to get aiccu to work with Windows 7 32 bit with no luck so far. This is the autotest.txt from aiccu: Tunnel Information for T21377: PoP Id : nlhaa01 IPv6 Local : 2001:1af8:fe00:138::2/64 IPv6 Remote : 2001:1af8:fe00:138::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled Name : My First Tunnel ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.0.0.34) ### 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 Pingen naar 10.0.0.34 met 32 bytes aan gegevens: Antwoord van 10.0.0.34: bytes=32 tijd<1 ms TTL=128 Antwoord van 10.0.0.34: bytes=32 tijd=3 ms TTL=128 Antwoord van 10.0.0.34: bytes=32 tijd<1 ms TTL=128 Ping-statistieken voor 10.0.0.34: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 0ms, Maximum = 3ms, Gemiddelde = 1ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (94.75.219.73) ### 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 Pingen naar 94.75.219.73 met 32 bytes aan gegevens: Antwoord van 94.75.219.73: bytes=32 tijd=25 ms TTL=59 Antwoord van 94.75.219.73: bytes=32 tijd=24 ms TTL=59 Antwoord van 94.75.219.73: bytes=32 tijd=24 ms TTL=59 Ping-statistieken voor 94.75.219.73: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 24ms, Maximum = 25ms, Gemiddelde = 24ms ###### ####### [3/8] Traceroute to the PoP (94.75.219.73) 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 Traceren van de route naar nlhaa01.sixxs.net [94.75.219.73] via maximaal 30 hops: 1 <1 ms <1 ms <1 ms fritz.box [10.0.0.153] 2 23 ms 22 ms 23 ms 82-169-7-254.ip.telfort.nl [82.169.7.254] 3 23 ms 25 ms 24 ms crs-tc2.leaseweb.net [195.69.144.215] 4 24 ms 24 ms 25 ms po80.hv5.evo.leaseweb.net [62.212.80.78] 5 25 ms 24 ms 25 ms nlhaa01.sixxs.net [94.75.219.73] De trace is voltooid. ###### ###### [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 Pingen naar ::1 met 32 bytes aan gegevens: Antwoord van ::1: tijd<1 ms Antwoord van ::1: tijd<1 ms Antwoord van ::1: tijd<1 ms Ping-statistieken voor ::1: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1af8:fe00:138::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pingen naar 2001:1af8:fe00:138::2 met 32 bytes aan gegevens: PING: verzenden mislukt. Algemene fout. PING: verzenden mislukt. Algemene fout. PING: verzenden mislukt. Algemene fout. Ping-statistieken voor 2001:1af8:fe00:138::2: Pakketten: verzonden = 3, ontvangen = 0, verloren = 3 (100% verlies). ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1af8:fe00:138::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 Pingen naar 2001:1af8:fe00:138::1 met 32 bytes aan gegevens: PING: verzenden mislukt. Algemene fout. PING: verzenden mislukt. Algemene fout. PING: verzenden mislukt. Algemene fout. Ping-statistieken voor 2001:1af8:fe00:138::1: Pakketten: verzonden = 3, ontvangen = 0, verloren = 3 (100% verlies). ###### ###### [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. So it seems there is something wrong with my interface or routing table. Ive already tried the netsh int ipv6 reset and then doing step 8 to 12 from https://www.ipv4.sixxs.net/wiki/Configuring_Windows_Vista again but it gets me the same result... Any help would be very much appreciated!