|
Setting up SixXS/AICCU in Win7x64
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Sunday, 09 January 2011 20:21:46
Hello,
I have followed the setup wiki Configuring Windows Vista
(1)ok
(2)ok
(3)ok
(4)this doesn't work in win7, I typed cmd in the start menu > rightclick cmd and click run as Administrator
(5)installed OpenVPN 2.1.4 -- released on 2010.11.09
(6)ok
(7)ok
(8) netsh interface ipv6 6to4 set state state=disabled gave me the error: "A device attached to the system is not functioning."
the rest went ok
(9)ok
(10)ok
(11)ping -6 returns "Destination host unreachable"
(12)ok
(13)doesn't work
(14)did the reset command, rebooted and retried steps 8-13 to no avail so im posting the logs
(15)ok
logs of the routing + ipconfig /all:
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: Wireless Network Connection
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Preferred infinite infinite fe80::f1da:44e5:b5f8:474a%11
Interface 15: SixXS
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Deprecated infinite infinite fe80::2872:63a3:5385:69fc%15
Interface 14: aiccu
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Manual Preferred infinite infinite 2001:1af8:fe00:280::2
Other Preferred infinite infinite fe80::6d22:ac44:ffa5:aec4%14
C:\Windows\system32>netsh int ipv6 show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
Yes Manual 256 ::/0 14 2001:1af8:fe00:280::1
No Manual 256 ::1/128 1 Loopback Pseudo-Interface
1
No Manual 256 2001:1af8:fe00:280::/64 14 aiccu
No Manual 256 2001:1af8:fe00:280::2/128 14 aiccu
No Manual 256 fe80::/64 15 SixXS
No Manual 256 fe80::/64 14 aiccu
No Manual 256 fe80::/64 11 Wireless Network Connecti
on
No Manual 256 fe80::2872:63a3:5385:69fc/128 15 SixXS
No Manual 256 fe80::6d22:ac44:ffa5:aec4/128 14 aiccu
No Manual 256 fe80::f1da:44e5:b5f8:474a/128 11 Wireless Network Con
nection
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface
1
No Manual 256 ff00::/8 15 SixXS
No Manual 256 ff00::/8 14 aiccu
No Manual 256 ff00::/8 11 Wireless Network Connecti
on
C:\Windows\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : AcerLaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan
Ethernet adapter aiccu:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-6F-A5-EF-13
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:1af8:fe00:280::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::6d22:ac44:ffa5:aec4%14(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.174.196(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 2001:1af8:fe00:280::1
DHCPv6 IAID . . . . . . . . . . . : 419495791
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-59-89-25-00-23-8B-37-5C-1C
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-21-5D-5B-73-56
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f1da:44e5:b5f8:474a%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : zondag 9 januari 2011 19:09:02
Lease Expires . . . . . . . . . . : maandag 10 januari 2011 19:23:32
Default Gateway . . . . . . . . . : 192.168.2.254
DHCP Server . . . . . . . . . . . : 192.168.2.254
DHCPv6 IAID . . . . . . . . . . . : 218112349
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-59-89-25-00-23-8B-37-5C-1C
DNS Servers . . . . . . . . . . . : 192.168.2.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter SixXS:
Media State . . . . . . . . . . . : Media disconnected
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
logs from the autotest run:
Tunnel Information for T50669:
PoP Id : nlhaa01
IPv6 Local : 2001:1af8:fe00:280::2/64
IPv6 Remote : 2001:1af8:fe00:280::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : Leaseweb Tunnel Haarlem
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.2.5)
### 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.2.5 with 32 bytes of data:
Reply from 192.168.2.5: bytes=32 time<1ms TTL=128
Reply from 192.168.2.5: bytes=32 time<1ms TTL=128
Reply from 192.168.2.5: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.2.5:
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=31ms TTL=56
Reply from 94.75.219.73: bytes=32 time=25ms TTL=57
Reply from 94.75.219.73: bytes=32 time=23ms TTL=57
Ping statistics for 94.75.219.73:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 31ms, Average = 26ms
######
####### [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 108 ms 82 ms 107 ms dsldevice.lan [192.168.2.254]
2 26 ms 41 ms 36 ms nl-rt-dc2-isp-bb21.wxs.nl [213.75.64.157]
3 50 ms 26 ms 23 ms nl-rt-dc2-isp-bb21.wxs.nl [213.75.64.157]
4 68 ms 33 ms 51 ms crs-evo.leaseweb.net [195.69.145.215]
5 32 ms 25 ms 81 ms po100.hv5.evo.leaseweb.net [85.17.100.214]
6 31 ms 56 ms 27 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 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:280::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pinging 2001:1af8:fe00:280::2 with 32 bytes of data:
Reply from 2001:1af8:fe00:280::2: time<1ms
Reply from 2001:1af8:fe00:280::2: time<1ms
Reply from 2001:1af8:fe00:280::2: time<1ms
Ping statistics for 2001:1af8:fe00:280::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:280::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:280::1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:1af8:fe00:280::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.
Does anyone know what I'm doing wrong?
Some sidenotes:
A few years ago I used a Hurricane tunnel, since then I switched pc's and routers I recently used Gateway6/GoGo6 but I deinstalled / reset ipv6 settings before switching to SixXS I use a stupid router sent to me by my ISP called "Experiabox". It basicly is a Thompson Speedtouch TG789vn which is locked up by the ISP; I can only change my wireless network name and password. I think it doesnt respond to ICMP so I can't make a Hurricane tunnel does this affect SixXS aswell?
Setting up SixXS/AICCU in Win7x64
![[us]](/s/countries/us.gif) Shadow Hawkins on Monday, 10 January 2011 00:39:36
I seem to recall ipv6 routing problems when there is no default ::0 route assigned to a an actual physical interface, for example even when the ethernet interface is disabled, wireless USB 6LoWPAN routing doesn't work unless
ipv6 rtu ::/0 [ethernet interface index]/[ethernet link-local address] publish
That is the XP command, I can't remember the netsh flavor but it is something like
netsh interface ipv6 add route address=::/0 interface=nn publish=yes
Setting up SixXS/AICCU in Win7x64
Shadow Hawkins on Monday, 10 January 2011 01:43:47
Right, I forgot to mention that I used these codes:
Windows XP / .Net / Vista
On XP it can be installed quite easily by typing "netsh interface ipv6 install" in the command prompt.
For Windows XP/2003/.Net and up, according to Updating IPv6.exe Commands to Netsh Commands this should be:
C:\> netsh interface ipv6 install
C:\> netsh interface ipv6 add v6v4tunnel SixXS [Your IPv4 Endpoint] [PoP IPv4 Endpoint]
C:\> netsh interface ipv6 add address SixXS [Your IPv6 Endpoint]
C:\> netsh interface ipv6 add route [Tunnel Prefix]/[Prefix Length] SixXS
C:\> netsh interface ipv6 add route 0::/0 SixXS publish=yes
I filled the bracket parts with my ip and the ip's from the info page of my account ofcourse.
Is this right? Am I supposed to run these codes at SixXS or aiccu?
Setting up SixXS/AICCU in Win7x64
Are you aware what those 'codes' do and when you need to use them? :)
Setting up SixXS/AICCU in Win7x64
Shadow Hawkins on Monday, 10 January 2011 22:45:00
SixXS not being a physical interface, windows routing may not be activated. Try assigning ::/0 to the ethernet or wireless interface.
Setting up SixXS/AICCU in Win7x64
Shadow Hawkins on Monday, 10 January 2011 22:49:58
Haha, I meant commands ofcourse.
I don't know everything about ipv6 but I suppose these commands make a ipv4 to ipv6 tunnel.
So I think you are pointing out that I got two tutorials mixxed up and that the SixXS interface in the latter part is should be the aiccu interface i'm using?
Setting up SixXS/AICCU in Win7x64
Those commands create a proto-41 tunnel (a static tunnel).
As you have an AYIYA tunnel, you thus can't use those commands, you need to use AICCU and only AICCU.
Do an 'netsh interface ipv6 reset', then reboot, then try starting AICCU again.
Setting up SixXS/AICCU in Win7x64
Shadow Hawkins on Monday, 10 January 2011 23:30:25
I already had tried this a few times. I just tried it again and still no dice.
The console starts the tunnel but I still can't ping ipv6.google.com...
Also: the first time I tried to set up the tunnel I didn't use the static tunnel commands, I only used them after I noticed the rest didn't work.
Before I ran the ipv6 reset command I reinstalled my wireless device just to be sure, however this didn't help.
I just did step 8-12 again after just starting the aiccu console, but this didn't change anything.
|
![[ch]](/s/countries/ch.gif)
on Monday, 10 January 2011 22:24:13
Posting is only allowed when you are