PoP: nlede01 TunnelID: T17035 Operating System: Windows Vista Home Premium 32bit with SP1 Antivirus: avast! Firewall: windows firewall Behind NAT: true (no problems before) Aiccu interface: console Adapter name: aiccu Adapter type: TAP-Win32 Adapter V9 Dear, Since today my tunnel stopped working properly, yesterday it was working fine. Aiccu is starting and says that it connected. But I cant ping to ipv6 addresses like ipv6.google.com I included a 'aiccu test' below. Someone has any idea why it is not working, maybe maintenance in the DC? Already tried multiple reboots and 'ipconfig /flushdns'. Kind Regards, Tim Aiccu Test Result (I removed userdata): D:\Mijn Stand Alone Software\ipv6>aiccu test 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.0.6 001-SP1" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1255871977" sock_printf() : "username *****-SIXXS" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 *******************************" sock_printf() : "authenticate md5 ********************************" sock_getline() : "200 Succesfully logged in using md5 as *****-SIXXS (*** *** *** ***) from 2001:7b8:3:4f:202:b3ff:fe46:bec" sock_printf() : "tunnel show T17035" sock_getline() : "201 Showing tunnel information for T17035" sock_getline() : "TunnelId: T17035" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:7b8:2ff:225::2" sock_getline() : "IPv6 POP: 2001:7b8:2ff:225::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: nlede01" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 193.109.122.244" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: xxx" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T17035 sock_printf() : "QUIT And All That Could Have Been..." Tunnel Information for T17035: PoP Id : nlede01 IPv6 Local : 2001:7b8:2ff:225::2/64 IPv6 Remote : 2001:7b8:2ff:225::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 'aiccu', with guid {78D961D5-4C3A-4466-BB72-4939EE35EF07}, using it [tun-start] Trying \\.\Global\{78D961D5-4C3A-4466-BB72-4939EE35EF07}.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.11 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.11) ### 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 192.168.1.11 met 32 bytes aan gegevens: Antwoord van 192.168.1.11: bytes=32 tijd<1 ms TTL=128 Antwoord van 192.168.1.11: bytes=32 tijd<1 ms TTL=128 Antwoord van 192.168.1.11: bytes=32 tijd<1 ms TTL=128 Ping-statistieken voor 192.168.1.11: 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 ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (193.109.122.244) ### 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 193.109.122.244 met 32 bytes aan gegevens: Antwoord van 193.109.122.244: bytes=32 tijd=16 ms TTL=58 Antwoord van 193.109.122.244: bytes=32 tijd=11 ms TTL=58 Antwoord van 193.109.122.244: bytes=32 tijd=11 ms TTL=58 Ping-statistieken voor 193.109.122.244: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 11ms, Maximum = 16ms, Gemiddelde = 12ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (193.109.122.244) 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 nlede01.sixxs.net [193.109.122.244] via maximaal 30 hops: 1 * * * Time-out bij opdracht. 2 * * * Time-out bij opdracht. 3 9 ms 9 ms 9 ms bras5-asd7.wadsl.wanadoo.nl [81.71.128.1] 4 9 ms 9 ms 9 ms G3-5.dr2-asd7.nl.euro.net [194.134.187.54] 5 9 ms 10 ms 9 ms 10GE8-4.cr1-asd6.nl.euro.net [194.134.162.12] 6 10 ms 9 ms * PC18.er1-asd6.nl.euro.net [194.134.161.102] 7 10 ms 12 ms 10 ms amsix-501.xe-0-0-0.jun1.galilei.network.bit.nl [ 195.69.144.35] 8 12 ms 11 ms 11 ms nlede01.sixxs.net [193.109.122.244] De trace is voltooid. ###### Did this work? [Y/n] y ###### [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 van ::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 ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:7b8:2ff:225::2 ) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pingen naar 2001:7b8:2ff:225::2 van 2001:7b8:2ff:225::2 met 32 bytes aan gegeven s: Antwoord van 2001:7b8:2ff:225::2: tijd<1 ms Antwoord van 2001:7b8:2ff:225::2: tijd<1 ms Antwoord van 2001:7b8:2ff:225::2: tijd<1 ms Ping-statistieken voor 2001:7b8:2ff:225::2: 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 ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:7b8:2ff:225::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:7b8:2ff:225::1 van 2001:7b8:2ff:225::2 met 32 bytes aan gegeven s: Time-out bij opdracht. Time-out bij opdracht. Time-out bij opdracht. Ping-statistieken voor 2001:7b8:2ff:225::1: Pakketten: verzonden = 3, ontvangen = 0, verloren = 3 (100% verlies). ###### Did this work? [Y/n]n