|
IPv6 Installation on Windows XP
![[de]](/s/countries/de.gif) Shadow Hawkins on Thursday, 14 July 2005 14:15:40
Hello,
I've now tried so many times to install IPv6 on my Windows XP that I finally don't see no other chance as to ask you for help.. ;(
First my configurations:
- Netgear Router FWG114P, not able to route Proto41, but I can set a DMZ Server to forward all unknown Packages.
- Pentium II Machine with Windows XP SP2, no changes made until now, except a Kerio Personal Firewall 4.1.3, Windows Firewall is disabled
- Enabled Tunnel with dynamic IP (heartbeat)
The last few days I've tried to get IPv6 to work, with more or less success...
First I've forwarded all traffic to the PC (DMZ) and configured the Firewall to let Proto41 pass through it.
Then I tried to run the configuration script from the sixxs homepage to set up the tunnel:
-----
rem Dynamic tunnels require the use of special configuration tools.
rem Windows XP/.Net IPv6 in IPv4 Tunnel Script
rem Autogenerated by SixXS Website (http://www.sixxs.net)
rem Created at 2005-07-14 13:31:30
netsh interface ipv6 install
netsh interface ipv6 add v6v4tunnel SixXS heartbeat 212.224.0.188
netsh interface ipv6 add address SixXS 2001:6f8:900:54f::2
netsh interface ipv6 add route 2001:6f8:900:54f::2/64 SixXS
netsh interface ipv6 add route 0::/0 SixXS
netsh firewall set adapter SixXS icmp all=enable
-----
But after the IPv6 Installation I get an "wrong parameter" error in the second line of the netsh command. Problems with the "heartbeat" parameter? But I can't enter an IP-Adress, because it's dynamic...
So I tried to install AICCU and at least the heartbeat seems to work. In the tunnel statistics on sixxs.net I can see that every time I run AICCU the loss statistics is not 100%. But there is no other traffic. And ipv6calc shows that I don't have IPv6. And in the statistics there is no "last alive" date. So it seems the tunnel has never been alive, but I already got 5 Credits... for what?? :-/
This is what I get from ipconfig:
-----
C:\>ipconfig
Windows-IP-Konfiguration
Ethernetadapter LAN-Verbindung:
Verbindungsspezifisches DNS-Suffix:
IP-Adresse. . . . . . . . . . . . : 192.168.23.205
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
IP-Adresse. . . . . . . . . . . . : fe80::201:2ff:fef7:30a3%5
Standardgateway . . . . . . . . . : 192.168.23.240
Ethernetadapter GRH LAN-Verbindung:
Verbindungsspezifisches DNS-Suffix: grh
IP-Adresse. . . . . . . . . . . . : 10.81.7.66
Subnetzmaske. . . . . . . . . . . : 255.255.0.0
IP-Adresse. . . . . . . . . . . . : fe80::280:adff:fe78:bcc2%6
Standardgateway . . . . . . . . . : 10.81.0.2
Tunneladapter Teredo Tunneling Pseudo-Interface:
Verbindungsspezifisches DNS-Suffix:
IP-Adresse. . . . . . . . . . . . : fe80::5445:5245:444f%4
Standardgateway . . . . . . . . . :
Tunneladapter Automatic Tunneling Pseudo-Interface:
Verbindungsspezifisches DNS-Suffix: grh
IP-Adresse. . . . . . . . . . . . : fe80::5efe:10.81.7.66%2
Standardgateway . . . . . . . . . :
Tunneladapter Automatic Tunneling Pseudo-Interface:
Verbindungsspezifisches DNS-Suffix:
IP-Adresse. . . . . . . . . . . . : fe80::5efe:192.168.23.205%2
Standardgateway . . . . . . . . . :
-----
Do I need TINC? I thought AICCU sets up the tunnel?!
Any tips/questions? And please no RTFM comments! ;)
Thx a lot, Sascha
IPv6 Installation on Windows XP
RTFM is actually a good idea. Starting with "Reporting Problems" on the contact page, in the end you only need to use AICCU, after having configured your DMZ of course.
The best thing you can do is:
net int ipv6 uninstall
<reboot>
aiccu
Most likely by running the script, which you are not supposed to be running, you added some bogus routes. Next to that check your Kerio Firewall if it is blocking proto-41 packets.
That the loss graph goes to 0 is solely because the interface gets configured on the POP, nothing else.
IPv6 Installation on Windows XP
Shadow Hawkins on Thursday, 14 July 2005 14:49:42
I reinstalled the PC, which is a testmachine only for IPv6, after running the script.
So the only thing I actually did was installing the Kerio Firewall and there I allowed the AICCU tool to send and receive anything. Windows Firewall is off. I also allowed Protocol 41 to be send and received. I'm just blocking incoming connections to local endpoints 135, 139 and 445. Now I've started AICCU and it seems that it is sending the heatbeats. But I can't ping my endpoint.
I didn't want to contact you guys at sixxs because I didn't want to bother you with my not existing knowledge. ;)
Regards, Sascha
|
![[ch]](/s/countries/ch.gif)
on Thursday, 14 July 2005 14:28:38
Posting is only allowed when you are