I posted a ticket, because that seemed to be what the contact page was telling me to do if I had issues, but it appears to have been closed without comment, so I guess I'll repost here. PoP: usbos01 Greetings. I've read the reporting problems page, here is all the information requested: I am DCU5-SIXXS, and am attempting to open tunnel with ID T44025. I am on Win7x64 with the latest console version of aiccu and installed the TAP driver through OpenVPN's installer, as the tap drivers provided on the Sixxs download page failed to install. When I run aiccu start, the 'sixxs' network connection appears to activate, however in the activity section of the network connection status window, several hundred bytes are shown as having been sent, and 0 having been received. In addition, the ipv6calc webpage reports that I am connecting over IPv4. I am unable to access IPv6 addresses such as http://[2001:4860:0:2001::68]/ (google). I am running Windows Firewall, but tried connecting with it disabled, without success. I am behind a linksys router, but tried connecting directly to the modem, without success. I am an Optimum Online customer, but have also tried opening the connection from my educational institution, without success. I have run aiccu test with verbose enabled (although I have no tracert6), with following output: C:\>aiccu-2008-03-15-windows-console.exe 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.1.7 600" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1294807386" sock_printf() : "username DCU5-SIXXS" sock_getline() : "200 DCU5-SIXXS choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 b1797b26727b1921297bf31d2799f669" sock_printf() : "authenticate md5 4a5755ccaedac9097091faf50a672ad0" sock_getline() : "200 Successfully logged in using md5 as DCU5-SIXXS (Daniel Col lins)" sock_printf() : "tunnel list" sock_getline() : "201 Listing tunnels" sock_getline() : "T44025 2001:4830:1100:e8::2 ayiya usbos01" sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>" sock_printf() : "tunnel show T44025" sock_getline() : "201 Showing tunnel information for T44025" sock_getline() : "TunnelId: T44025" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:4830:1100:e8::2" sock_getline() : "IPv6 POP: 2001:4830:1100:e8::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: usbos01" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 216.93.250.26" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: ..." sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T44025 sock_printf() : "QUIT Stranded" Tunnel Information for T44025: PoP Id : usbos01 IPv6 Local : 2001:4830:1100:e8::2/64 IPv6 Remote : 2001:4830:1100:e8::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 {A369E2DA-B15D-4957-A409-FE574BBAA221}, using it [tun-start] Trying \\.\Global\{A369E2DA-B15D-4957-A409-FE574BBAA221}.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.3 ####### ####### 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 Pinging 192.168.1.3 with 32 bytes of data: Reply from 192.168.1.3: bytes=32 time<1ms TTL=128 Reply from 192.168.1.3: bytes=32 time<1ms TTL=128 Reply from 192.168.1.3: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.1.3: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### Did this work? [Y/n] ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.93.250.26) ### 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 216.93.250.26 with 32 bytes of data: Request timed out. Reply from 216.93.250.26: bytes=32 time=736ms TTL=50 Reply from 216.93.250.26: bytes=32 time=673ms TTL=50 Ping statistics for 216.93.250.26: Packets: Sent = 3, Received = 2, Lost = 1 (33% loss), Approximate round trip times in milli-seconds: Minimum = 673ms, Maximum = 736ms, Average = 704ms ###### Did this work? [Y/n] ####### [3/8] Traceroute to the PoP (216.93.250.26) 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 usbos01.sixxs.net [216.93.250.26] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 899 ms 822 ms 844 ms 10.240.176.17 3 812 ms 885 ms 1008 ms dstswr1-vlan2.rh.nbrgnj.cv.net [67.83.246.161] 4 * * * Request timed out. 5 474 ms 325 ms 282 ms rtr3-tg11-2.wan.prnynj.cv.net [64.15.6.1] 6 266 ms 284 ms 272 ms rtr3-tg9-3.in.nycmny83.cv.net [64.15.0.57] 7 306 ms 289 ms 536 ms pos5-2.pr1.lga1.us.mfnx.net [167.206.8.154] 8 338 ms 72 ms 37 ms xe-1-0-0.er1.lga5.us.above.net [64.125.27.49] 9 35 ms 34 ms 64 ms xe-1-1-0.cr1.lga5.us.above.net [64.125.26.161] 10 181 ms 161 ms 113 ms xe-1-1-0.mpr3.bos2.us.above.net [64.125.25.41] 11 115 ms 50 ms 107 ms xe-0-0-0.mpr4.bos2.us.above.net [64.125.25.62] 12 195 ms 82 ms 36 ms abovenet.ge2-1.ibr01.bos1.twdx.net [64.124.198.4 5] 13 86 ms 168 ms 91 ms OCCAID-230.ibr01.bos1.twdx.net [216.93.255.6] 14 89 ms 102 ms 136 ms usbos01.sixxs.net [216.93.250.26] Trace complete. ###### Did this work? [Y/n] ###### [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: 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 ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4830:1100:e8:: 2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pinging 2001:4830:1100:e8::2 with 32 bytes of data: Reply from 2001:4830:1100:e8::2: time<1ms Reply from 2001:4830:1100:e8::2: time<1ms Reply from 2001:4830:1100:e8::2: time<1ms Ping statistics for 2001:4830:1100:e8::2: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4830:1100:e8:: 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:4830:1100:e8::1 with 32 bytes of data: Reply from 2001:4830:1100:e8::1: time=784ms Reply from 2001:4830:1100:e8::1: time=796ms Reply from 2001:4830:1100:e8::1: time=808ms Ping statistics for 2001:4830:1100:e8::1: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 784ms, Maximum = 808ms, Average = 796ms ###### Did this work? [Y/n] ###### [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. ###### Did this work? [Y/n] ###### [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. ###### Did this work? [Y/n] ###### 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. *** press a key to continue *** I believe I have supplied all the appropriate requested information, and I hope you can provide some advice or pointers. Thanks!