|
Vista 64Bit User Stuck with setting up IPv6.
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Tuesday, 31 March 2009 00:17:21
Hey all!
I'm kind of newish to ipv6 (a)...
I pretty much followed the 10 step minifaq to the letter... and failed.
http://www.sixxs.net/faq/account/?faq=10steps
then I went to the Wiki and tried the Vista setup
http://www.sixxs.net/wiki/Configuring_Windows_Vista
(got stuck at point 9.... fiddled around, changed some stuff althou I cant remember what and managed to move on to next steps)
Got to install the OpenVPN stuff for the 64bit driver (https://www.sixxs.net/wiki/Aiccu/Installing_on_Vista64), and thatone works now.... but basically now i'm stuck at point 11
in simple words it does not work.
So... I turn to the guru's on this forum and hope that they can help me out? :)
My show address and routes....
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
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 15: SixXS
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Manual Preferred infinite infinite 2001:1af8:fe00:e4::2
Other Preferred infinite infinite fe80::9c27:ad76:6909:34ce%15
Interface 11: Local Area Connection 2
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Manual Preferred infinite infinite 2002:81a8:102::
Other Preferred infinite infinite fe80::d59c:4c20:b89c:5a61%11
Interface 16: aiccu
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Preferred infinite infinite fe80::55d6:a90d:c546:d522%16
C:\Windows\system32> netsh int ipv6 show routes
The following command was not found: int ipv6 show routes.
C:\Windows\system32> ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : AReality-C1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter aiccu:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-29-CC-34-0C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::55d6:a90d:c546:d522%16(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.213.34(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 2001:1af8:fe00:e4::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 Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether
net Controller
Physical Address. . . . . . . . . : 00-1A-92-21-DC-62
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:81a8:102::(Preferred)
Link-local IPv6 Address . . . . . : fe80::d59c:4c20:b89c:5a61%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.22(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 88.159.1.200
88.159.1.201
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter SixXS:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:1af8:fe00:e4::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::9c27:ad76:6909:34ce%15(Preferred)
Default Gateway . . . . . . . . . : 2001:1af8:fe00:e4::1
DNS Servers . . . . . . . . . . . : 88.159.1.200
88.159.1.201
NetBIOS over Tcpip. . . . . . . . : Disabled
and ofcourse my aiccu log.
Tunnel Information for T20533:
PoP Id : nlhaa01
IPv6 Local : 2001:1af8:fe00:e4::2/64
IPv6 Remote : 2001:1af8:fe00:e4::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 (192.168.1.22)
### 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.22 with 32 bytes of data:
Reply from 192.168.1.22: bytes=32 time<1ms TTL=128
Reply from 192.168.1.22: bytes=32 time<1ms TTL=128
Reply from 192.168.1.22: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.22:
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 (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
Pinging 94.75.219.73 with 32 bytes of data:
Reply from 94.75.219.73: bytes=32 time=4ms TTL=52
Reply from 94.75.219.73: bytes=32 time=5ms TTL=52
Reply from 94.75.219.73: bytes=32 time=5ms TTL=52
Ping statistics for 94.75.219.73:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 4ms
######
####### [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
Tracing route to nlhaa01.sixxs.net [94.75.219.73]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 1-92-ftth.onsneteindhoven.nl [88.159.92.1]
3 <1 ms <1 ms <1 ms 172.17.162.161
4 1 ms <1 ms <1 ms 172.17.162.157
5 <1 ms <1 ms <1 ms 172.17.162.153
6 1 ms 1 ms 1 ms 172.17.0.205
7 1 ms 1 ms 1 ms 172.17.0.145
8 1 ms 1 ms 1 ms ge3-10.bb1-ehv-r05.edutel.nl [88.159.2.1]
9 4 ms 4 ms 4 ms ge3-24.bb1-asd-nkh.edutel.nl [88.159.0.172]
10 5 ms 4 ms 4 ms te1-3.bb1-asd-nkh.edutel.nl [88.159.0.166]
11 5 ms 5 ms 5 ms 20ge-chnl.amsix.nkf.leaseweb.net [195.69.145.215]
12 4 ms 5 ms 5 ms po100.hv5.evo.leaseweb.net [85.17.100.214]
13 4 ms 4 ms 5 ms nlhaa01.sixxs.net [94.75.219.73]
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:1af8:fe00:e4::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pinging 2001:1af8:fe00:e4::2 from 2001:1af8:fe00:e4::2 with 32 bytes of data:
Reply from 2001:1af8:fe00:e4::2: time<1ms
Reply from 2001:1af8:fe00:e4::2: time<1ms
Reply from 2001:1af8:fe00:e4::2: time<1ms
Ping statistics for 2001:1af8:fe00:e4::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:1af8:fe00:e4::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:1af8:fe00:e4::1 from 2001:1af8:fe00:e4::2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:1af8:fe00:e4::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.
######
###### [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.
Vista 64Bit User Stuck with setting up IPv6.
Shadow Hawkins on Tuesday, 31 March 2009 00:17:47
./me looks for edit button... mmm none... ok repost then...
after a quick reboot... the pinging works... but no Ie7 connectivity.... :(
new aiccu.log
Tunnel Information for T20533:
PoP Id : nlhaa01
IPv6 Local : 2001:1af8:fe00:e4::2/64
IPv6 Remote : 2001:1af8:fe00:e4::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 (192.168.1.22)
### 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.22 with 32 bytes of data:
Reply from 192.168.1.22: bytes=32 time<1ms TTL=128
Reply from 192.168.1.22: bytes=32 time<1ms TTL=128
Reply from 192.168.1.22: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.22:
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 (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
Pinging 94.75.219.73 with 32 bytes of data:
Reply from 94.75.219.73: bytes=32 time=4ms TTL=52
Reply from 94.75.219.73: bytes=32 time=4ms TTL=52
Reply from 94.75.219.73: bytes=32 time=4ms TTL=52
Ping statistics for 94.75.219.73:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 4ms, Average = 4ms
######
####### [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
Tracing route to nlhaa01.sixxs.net [94.75.219.73]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 1-92-ftth.onsneteindhoven.nl [88.159.92.1]
3 1 ms <1 ms <1 ms 172.17.162.161
4 1 ms <1 ms <1 ms 172.17.162.157
5 1 ms <1 ms <1 ms 172.17.162.153
6 1 ms 1 ms 1 ms 172.17.0.205
7 2 ms 1 ms 2 ms 172.17.0.145
8 1 ms 1 ms 1 ms ge3-10.bb1-ehv-r05.edutel.nl [88.159.2.1]
9 4 ms 3 ms 3 ms ge3-24.bb1-asd-nkh.edutel.nl [88.159.0.172]
10 4 ms 4 ms 4 ms te1-3.bb1-asd-nkh.edutel.nl [88.159.0.166]
11 5 ms 5 ms 7 ms 20ge-chnl.amsix.nkf.leaseweb.net [195.69.145.215]
12 5 ms 4 ms 4 ms po100.hv5.evo.leaseweb.net [85.17.100.214]
13 4 ms 4 ms 6 ms nlhaa01.sixxs.net [94.75.219.73]
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:1af8:fe00:e4::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pinging 2001:1af8:fe00:e4::2 from 2001:1af8:fe00:e4::2 with 32 bytes of data:
Reply from 2001:1af8:fe00:e4::2: time<1ms
Reply from 2001:1af8:fe00:e4::2: time<1ms
Reply from 2001:1af8:fe00:e4::2: time<1ms
Ping statistics for 2001:1af8:fe00:e4::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:1af8:fe00:e4::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:1af8:fe00:e4::1 from 2001:1af8:fe00:e4::2 with 32 bytes of data:
Reply from 2001:1af8:fe00:e4::1: time=4ms
Reply from 2001:1af8:fe00:e4::1: time=4ms
Reply from 2001:1af8:fe00:e4::1: time=4ms
Ping statistics for 2001:1af8:fe00:e4::1:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 4ms, Average = 4ms
######
###### [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.
Vista 64Bit User Stuck with setting up IPv6.
![[us]](/s/countries/us.gif) Shadow Hawkins on Monday, 30 March 2009 20:09:30
Can you post the output of ipconfig?
Vista 64Bit User Stuck with setting up IPv6.
Shadow Hawkins on Tuesday, 31 March 2009 00:15:49ofcourse.
ipconfig /all
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : AReality-C1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter aiccu:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-29-CC-34-0C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:1af8:fe00:e4::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::55d6:a90d:c546:d522%16(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.213.34(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 2001:1af8:fe00:e4::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 Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether
net Controller
Physical Address. . . . . . . . . : 00-1A-92-21-DC-62
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d59c:4c20:b89c:5a61%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.22(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 88.159.1.200
88.159.1.201
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter SixXS:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::9c27:ad76:6909:34ce%15(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 88.159.1.200
88.159.1.201
NetBIOS over Tcpip. . . . . . . . : Disabled
C:\Windows\system32>
Vista 64Bit User Stuck with setting up IPv6.
The IE problems is because of the missing global address on the "Local Area Connection 2". See the wiki entry for details on how to add one, do note that your interface name contains a '2'.
Tunnel adapter SixXS:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
Why typed that description line? "Adapater" is definitely a typo.
It looks like that is some kind of VPN interface.
btw, you can use "[ code ] txt txt txt [ /code ]" (minus the spaces of course) for code and outputs like that.
Vista 64Bit User Stuck with setting up IPv6.
Shadow Hawkins on Tuesday, 31 March 2009 07:29:39
Yay! thnx.... >.< it was in the wiki (a) just my connection was named differently aparantly... heheh..
sorry bout the quoting stuff :) i was more used to that, will use [ code ] and [ /code ] in the future :).... (if needed)...
myah that adapter, no idea on the name actually, lol... maybe it came with installing OpenVPN? hrmz... time to find out.
Vista 64Bit User Stuck with setting up IPv6.
Shadow Hawkins on Tuesday, 31 March 2009 00:15:29Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>netsh interface ipv6 show address
Interface 1: Loopback Pseudo-Interface 1
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Preferred infinite infinite ::1
Interface 15: SixXS
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Preferred infinite infinite fe80::9c27:ad76:6909:34ce%15
Interface 11: Local Area Connection 2
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Preferred infinite infinite fe80::d59c:4c20:b89c:5a61%11
Interface 16: aiccu
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Manual Preferred infinite infinite 2001:1af8:fe00:e4::2
Other Preferred infinite infinite fe80::55d6:a90d:c546:d522%16
C:\Windows\system32>
Vista 64Bit User Stuck with setting up IPv6.
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Sunday, 26 April 2009 12:04:20
It took a while, but I followed the instruction for Vista found here
This also works for Windows 7 x64 RC1 build 7100
Hope this helps
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 31 March 2009 00:15:01
Posting is only allowed when you are