Windows Vista - Can't Ping Inner Tunnel
Shadow Hawkins on Saturday, 04 April 2009 23:59:51
Hello,
I'm trying to set up an aiccu ayiya tunnel according to the wiki article at https://www.sixxs.net/wiki/Configuring_Windows_Vista
I've managed to get to step 10 "Start AICCU Utility", but after that I'm unable to ping any IPv6 sites or surf to any
I'm a bit at a loss on what to do now as I don't really see anything wrong right away, hoping someone sees something I've overlooked
What I've done so far:
I installed the latest OpenVPN driver (since I'm on Vista x64)
I've downloaded the aiccu tool and added a config file containing the following:
username <myhandle>-SIXXS
password <mypass>
ipv6_interface IPv6
tunnel_id T<mytunnelnr>
verbose true
daemonize true
automatic true
requiretls false
Then I've run the following commands:
netsh interface ipv6 6to4 set state state=disabled
netsh interface ipv6 isatap set state state=disabled
netsh interface ipv6 set teredo disable
netsh int ipv6 add address "Cable" 2002:81a8:102::
(Cable is the name of my network card)
Running nslookup -type=AAAA www.ipv6.sixxs.net gives the correct result as on the wiki.
And at this point I start it and get the following output:
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.6001-SP1"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1238881073"
sock_printf() : "username xxx-SIXXS"
sock_getline() : "200 Choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 xxxxx"
sock_printf() : "authenticate md5 xxxx"
sock_getline() : "200 Succesfully logged in using md5 as xxx-SIXXS (David Cumps) from 2001:7b8:3:4f:202:b3ff:fe46:bec"
sock_printf() : "tunnel show T20724"
sock_getline() : "201 Showing tunnel information for T20724"
sock_getline() : "TunnelId: Txxxx"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2001:6f8:202:3a5::2"
sock_getline() : "IPv6 POP: 2001:6f8:202:3a5::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: David Cumps"
sock_getline() : "POP Id: bebru01"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 212.100.184.146"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: xxxx"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T20724
sock_printf() : "QUIT Every Time We Live Together"
Tunnel Information for T20724:
PoP Id : bebru01
IPv6 Local : 2001:6f8:202:3a5::2/64
IPv6 Remote : 2001:6f8:202:3a5::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : David Cumps
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 'IPv6', with guid {5A82DA33-7346-4A30-B55E-17A758F93E9D},
using it
[tun-start] Trying \\.\Global\{5A82DA33-7346-4A30-B55E-17A758F93E9D}.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
Vista prompted me to ask if this was a public or private network, I made it private and it aquired the IPv6 IP address listed on my Home page.
And at this point I thought everything was ok, but I can't access any IPv6 things at this point, so I ran the autotest:
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.123.104)
### 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.123.104 with 32 bytes of data:
Reply from 192.168.123.104: bytes=32 time<1ms TTL=128
Reply from 192.168.123.104: bytes=32 time<1ms TTL=128
Reply from 192.168.123.104: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.123.104:
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 (212.100.184.146)
### 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 212.100.184.146 with 32 bytes of data:
Reply from 212.100.184.146: bytes=32 time=24ms TTL=51
Reply from 212.100.184.146: bytes=32 time=26ms TTL=51
Reply from 212.100.184.146: bytes=32 time=25ms TTL=51
Ping statistics for 212.100.184.146:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 26ms, Average = 25ms
######
####### [3/8] Traceroute to the PoP (212.100.184.146) 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 212.100.184.146 over a maximum of 30 hops
1 3 ms 3 ms 3 ms F5d8233-4v3 [192.168.123.1]
2 9 ms 9 ms 12 ms 78-23-128-1.access.telenet.be [78.23.128.1]
3 11 ms 10 ms 11 ms dD5E0FB21.access.telenet.be [213.224.251.33]
4 * * * Request timed out.
5 11 ms 10 ms 13 ms dD5E0FD15.access.telenet.be [213.224.253.21]
6 11 ms 11 ms 12 ms dD5E0FD9A.access.telenet.be [213.224.253.154]
7 12 ms 13 ms 12 ms 212.3.232.9
8 17 ms 24 ms 24 ms ae-6-6.ebr1.London1.Level3.net [4.69.136.246]
9 17 ms 17 ms 19 ms ae-15-51.car5.London1.Level3.net [4.69.139.70]
10 17 ms 16 ms 17 ms EASYNET-GRO.car5.London1.Level3.net [212.187.170.230]
11 22 ms 20 ms 24 ms te0-0-0.gr10.gdbru.be.easynet.net [87.86.77.47]
12 23 ms 21 ms 21 ms ge0-2-0-114.br3.gdbru.easynet.net [87.86.71.165]
13 22 ms 22 ms 21 ms ge0-0.cr3.gdbru.be.easynet.net [212.100.161.14]
14 21 ms 23 ms 23 ms 212.100.184.146
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 (2001:6f8:202:3a5::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pinging 2001:6f8:202:3a5::2 from 2001:6f8:202:3a5::2 with 32 bytes of data:
Reply from 2001:6f8:202:3a5::2: time<1ms
Reply from 2001:6f8:202:3a5::2: time<1ms
Reply from 2001:6f8:202:3a5::2: time<1ms
Ping statistics for 2001:6f8:202:3a5::2:
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 (2001:6f8:202:3a5::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:6f8:202:3a5::1 from 2001:6f8:202:3a5::2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:6f8:202:3a5::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 connection
### 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.
Apparently I'm having problem going over the tunnel to the other side.
I've ran some other commands listed on the wiki to get more debug output:
C:\Windows\system32>netsh int ipv6 show address
Interface 1: Loopback Pseudo-Interface 1
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Preferred infinite infinite ::1
Interface 11: Local Area Connection
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Deprecated infinite infinite fe80::4cea:1173:b944:e5f2%11
Interface 12: Local Area Connection 2
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Deprecated infinite infinite fe80::3151:5904:1648:c5f6%12
Interface 14: Bluetooth Network Connection
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Deprecated infinite infinite fe80::98a8:6b1c:969a:1448%14
Interface 17: Cable
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Manual Preferred infinite infinite 2002:81a8:102::
Other Preferred infinite infinite fe80::e4ee:3a01:a468:821a%17
Interface 34: IPv6
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Manual Preferred infinite infinite 2001:6f8:202:3a5::2
Other Preferred infinite infinite fe80::e50d:11cd:9b90:9f7%34
C:\Windows\system32>netsh int ipv6 show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
Yes Manual 256 ::/0 34 2001:6f8:202:3a5::1
No Manual 256 ::1/128 1 Loopback Pseudo-Interface 1
No Manual 256 2001:6f8:202:3a5::/64 34 IPv6
No Manual 256 2001:6f8:202:3a5::2/128 34 IPv6
No Manual 256 2002:81a8:102::/64 17 Cable
No Manual 256 2002:81a8:102::/128 17 Cable
No Manual 256 fe80::/64 14 Bluetooth Network Connection
No Manual 256 fe80::/64 17 Cable
No Manual 256 fe80::/64 11 Local Area Connection
No Manual 256 fe80::/64 12 Local Area Connection 2
No Manual 256 fe80::/64 34 IPv6
No Manual 256 fe80::3151:5904:1648:c5f6/128 12 Local Area Connection 2
No Manual 256 fe80::4cea:1173:b944:e5f2/128 11 Local Area Connection
No Manual 256 fe80::98a8:6b1c:969a:1448/128 14 Bluetooth Network Connection
No Manual 256 fe80::e4ee:3a01:a468:821a/128 17 Cable
No Manual 256 fe80::e50d:11cd:9b90:9f7/128 34 IPv6
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface 1
No Manual 256 ff00::/8 14 Bluetooth Network Connection
No Manual 256 ff00::/8 17 Cable
No Manual 256 ff00::/8 11 Local Area Connection
No Manual 256 ff00::/8 12 Local Area Connection 2
No Manual 256 ff00::/8 34 IPv6
C:\Windows\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : zoing
Primary Dns Suffix . . . . . . . : heaven.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : heaven.local
Ethernet adapter IPv6:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-5A-82-DA-33
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:6f8:202:3a5::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::e50d:11cd:9b90:9f7%34(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.9.247(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 2001:6f8:202:3a5::1
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Cable:
Connection-specific DNS Suffix . : heaven.local
Description . . . . . . . . . . . : Killer NIC NDIS EDGE Interface
Physical Address. . . . . . . . . : 00-19-03-02-0D-16
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:81a8:102::(Preferred)
Link-local IPv6 Address . . . . . : fe80::e4ee:3a01:a468:821a%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.123.104(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : zaterdag 4 april 2009 12:39:04
Lease Expires . . . . . . . . . . : woensdag 12 mei 2145 6:25:36
Default Gateway . . . . . . . . . : 192.168.123.1
DHCP Server . . . . . . . . . . . : 192.168.123.1
DNS Servers . . . . . . . . . . . : 192.168.123.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 00-1E-4C-CC-A0-C4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet #2
Physical Address. . . . . . . . . : 00-21-9B-FF-7C-10
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 00-21-9B-FF-7C-11
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 13:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{411FE997-364B-4B65-9BEF-2DE4C07A299E}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Would love some advice, did I do something wrong?
Or am I simply impatient after my tunnel request got approved and it needs more than 3 hours to become activated on the PoP end?
Windows Vista - Can't Ping Inner Tunnel
Shadow Hawkins on Sunday, 05 April 2009 01:10:57
I figured it out!
After looking at lots of Wireshark output, I was puzzled about a lot of ARP requests with a strange IP, turned out that IP was one of the automatically assigned Windows IPs, and it was asking for the gateway.
So I manually configured an IP for my ipv6 adapter, in the same ipv4 subnet as my physically connected card and lo and behold, everything is up and running :)
I can ping and surf to the IPv6 sites
Don't really understand the inner workings of what just happened, but I'm happy :)
Posting is only allowed when you are logged in. |