|
Using Sixxs with Windows 2000
![[de]](/s/countries/de.gif) Shadow Hawkins on Tuesday, 08 March 2011 05:53:55
Hello,
I want to use SixXS with Windows 2000, and I have problems using IPv6 after I set up.
My settings: AICCU + AYIYA over T-Online Germany
Things I have done:
1. Registered at SixXS, requested a tunnel.
2. Installed IPv6 Hotfix for Windows 2000 SP4 (=> Things like ipv6.exe are now existing)
3. Installed IP6 protocol on my Network card (Wireless PCMCIA card)
4. Restart Win2000
5. Run AICCU 2006-07-23-windows-gui, entered access data, selected tunnel
6. Clicked "Enable"
7. Ran following batch:
ipv6.exe rtu ::/0 2/::78.35.24.124 pub
ipv6.exe adu 2/2001:4dd0:xxxx:61c::1 (xxxx = censored part of my IPv6 address)
8. Installed TAP driver 801 for Windows 2000 (OpenVPN). The driver was installed. Now under "Network connections" I see also the "aiccu" network card.
9. Ran "ping6 ipv6.google.com" => Request timeout
10. I repeated all steps (reboot, re-ran rtu+adu, restarted aiccu)
Can somebody help please?
I am sitting behind a router Speedport W700V.
Regards
Daniel Marschall
Using Sixxs with Windows 2000
First of all, Windows 2000's IPv6 stack is really really really reall old, unstable, buggy etc.
Next to that, if you installed it, then you have effectively downgraded all kinds of system components and introduced a lot of vulnerabilities on your system.
In other words don't use it.
Your step 7 and 8 are mutual exclusive. Step 7 would be for a proto-41 static tunnel. Step 8 would be needed for a AYIYA tunnel.
I have a very simple answer to this: Stop using Windows 2000 and upgrade to something from the year 2011 (that is install your favourite Linux flavor or Windows Seven or something like that).
Using Sixxs with Windows 2000
Shadow Hawkins on Wednesday, 09 March 2011 23:04:50
Hello.
I am just a student and have only an old computer with Windows 2000 for testing purposes and 2 computers with Windows XP (production system for software development) and Windows 7 (RAID-storage server). As you could imagine, I use the Win2000 computer to test anything (especiall network changes, which may cause security issues) first on this computer before I will install it to any production system. At the moment I won't install SIXXS software to any production system, since I am to unsure about IPv6 and also have problems with the SIXXS software itself. I am glad my IPv4 network currently works and since I experienced that IPv6 can bring problems in this early stage (missing NAT, incompatible router, unknown if firewall is secure enough and stuff...), I will also NOT change this.
I am sure, Windows 2000 itself is configured correct and that the experimental stack driver does work (even if it is not for productional usage!) I believe the problem is in the configuration itself and not in any bug in the OS-experimental-stack. So, I won't accept this "simple answer". I would have the same problem if I do these steps in Windows XP.
Alas, I have to say, that your documentation about all this is not very good. I could not read anywhere that step 7 and 8 does mutual exclude. So, please tell me, how I can solve this problem now, so that this experimental IPv6 internet access just works. How can I undo step 7 to have AYIYA access?
Also, what I have to do with the TAP driver, so that AICCU works? I don't find any useful documentation about issues with the connection or configuration-tutorials here. (This is also a main reason, why I don't use SIXXS software on stable, functional production systems which are important for me).
Regards
Daniel Marschal
Using Sixxs with Windows 2000
![[us]](/s/countries/us.gif) Shadow Hawkins on Thursday, 10 March 2011 00:59:07So, please tell me, how I can solve this problem now, so that this experimental IPv6 internet access just works. How can I undo step 7 to have AYIYA access?
Replace your obsolete, unsupported Windows 2000 OS with a modern one. This need not cost you any money. Many Linux distributions (Debian, for example) include Aiccu packages that you can install with a few clicks or you could go with one of the BSDs.
Using Sixxs with Windows 2000
Shadow Hawkins on Thursday, 10 March 2011 02:58:27
I feel a bit disappointed about the fact that you are not able to solve my problem. You don't even try to understand the problem.
If you can show me that there is everything correct with my hardware (router) and software configuration, and thus can proof, that my operating system on my experimental computer is the only component which causes that the IPv6 connection doesn't work, I can accept it and can accept that I don't get support for his old operating system.
But at the moment I believe that it is a malconfiguration in the SIXXS/OpenSVN software, since the IPv6 SP4 stack for Windows 2000 itself works without any problems. It is likely that there is a malconfiguration rather than a IPv6-stack-bug, because SIXXS is badly documented for IPv6 newbies and has no tutorial for the installation, so I was very unsure when I installed/configured these things. I would have exactly the same problems on every new OS, if I do the same steps as described above.
So, my simple request is, independent from the operating system, how I can just connect to the IPv6 internet with AYIYA. My question, how I can use AYIYA with the OpenSVN driver and undo my wrong rtu+adu setting, is very independent of the operating system. It is a general problem.
Last point, I don't want resp. can't install Windows XP on a 300 MHz computer. Windows 2000 did its work good to test stuff before it will be used in productional systems. It is used just for these experimental work, which also includes now my first IPv6 tests with SIXXS.
Regards
Daniel Marschall
Using Sixxs with Windows 2000
![[ch]](/s/countries/ch.gif) Shadow Hawkins on Thursday, 10 March 2011 15:28:29
Sorry, I just can't help it but have to add my comments here.
As far as I understand it, SIXXS is a completely volunteer and non-profit operation. Most of the responses and help you get here are from people who do this as a hobby and in their free time. Your messages sound a bit like you expect people to have an obligation to help you. Be careful with this attitude, as people might get pissed off and stop answering you (or worse). If you need "commercial" support, SIXXS might be the wrong place for you.
You demand proof that the fault is with your system, not with aiccu or SIXXS. Well, it is working for me and hundreds of others, so I think it is natural to assume the problem lies with your setup and it is rather you who should present convincing evidence that it is not the case.
I understand your reasons for not wanting to install a newer version of Windows on your test setup and for not wanting to install Aiccu on your "production" systems. Windows 2000 is an out-dated version of Windows and I guess nobody is particularly interested in supporting it. The IPv6 stack for Windows 2000 is at best experimental and there really is no added value for anybody to try to support it. Maybe it works, and if you get it to work on your system, the better. If you do, maybe you can contribute to the documentation of SIXXS and provide some information on what you had to do to get it to work.
When people on this forum tell you to install a more modern version of an operating system, they understand that you don't want to (and maybe can't) install a newer version of Windows. They are hinting at (or outright telling you to) install(ing) Linux (or maybe a variant of the *BSDs). Hint: Windows is not the only operating system. You probably don't know about Linux and are hesitant to try it. Yes, it will take some effort to learn it if you are not already familiar with it, but I think it's easier than you imagine. Plus as a student it would seem a good idea to know and have experience with more than a single operating system. If you are a complete beginner, Ubuntu is a good distribution to start with:
http://www.ubuntu.com/
If you absolutely insist on continuing to experiment with IPv6 and Windows 2000, please understand that not many people will be able to help you. Your best option is to ask for advice on next steps to take. Don't expect a step-by-step receipt on how to do things. Rather, you'd get hints and ideas, and you'll have to learn more about how things work and experiment a bit.
Finally, if you are unhappy with how things work with SIXXS, you can always try one of the other IPv6 access providers (e.g. Hurrican Electric: http://ipv6.he.net/ ). Oh, and maybe you'd like to read the free IPv6 book as well: http://www.secondinternet.org/
Cheers,
Urs
Using Sixxs with Windows 2000
Shadow Hawkins on Friday, 11 March 2011 06:51:01
Hello Urs,
I have actually understand what SIXXS is. I do know that it is non-profit and I do know that the project as well as this forum is lead by users to help users. I do understand that there is no guarantee for getting helped.
The point why I am stressed is another one.
There are 3 ways how people can react to such a problem like mine:
1. Try to help. Try to find out what is wrong - independent from the operating system. Of course, people may tell me that ths OS is old and MIGHT be part of the problem, but as long as it is not 100% clear that the OS causes the malfunction, people willing to help should find out other possible points in the "standard-troubleshooting".
2. People are not able to help, maybe because they don't know how the Win2000 ipv6.exe did work or because they cannot find any other malconfiguration. This is also OK.
3. People first blame everything else like the operating system when there is no proof that the operating system really causes the malfunction. The operating system might be one possible failure, but there are douzend other things which might fail or be wrong configured. I did tell that I was very unsure when I configured the services since I did not had any good tutorial. So it is likely that I did some mistake while configuration, which might be independent of the operating system version.
I would be glad if you could ask me some general questions instead, about the other possible malconfigurations/parameters/router-hardware, to find out, what else could be faulty.
I don't like this jump to conclusions (voreilige Schlsse) "install a new operating system and everything will be fine". In my opinion, this is comparable to following scenario: A friend has a 10 year old LAN-card and cannot access internet, because he configured the wrong subnet mask. I tell him "This card is old - buy a new network card and everything will work." - not knowing (and also not searching) for any other possible reason.
Of course, SIXXS is working for you and hundreds of others. But you also had probably more knowledge when setting up the tunnel/subnet/VPN and stuff at your side. Or my router has problems with the OpenVPN software. I believe, my configuration might be a bit faulty since I did work the very first time with AICCU, AYIYA, OpenVPN and TAP32. And this is where I wish YOUR help, to find it out what might be wrong there. Since I have never worked with IPv6 and these required software (OpenVPN, TAP32, AICCU) and protocols (AYIYA), I am REALLY UNSURE what to do and it was very hard for me to find the correct tutorials here.
As you found out, I already have followed a "wrong" tutorial which showed me how to do stuff with adu+rtu, but which was not made for my purpose, using AYIYA to bypass my NAT at the router. My request is to get help in finding the correct way, using SIXXS behind a router.
And yes, if I will have success, installing SIXXS successfully at this Win2000 behind my router, I will post a step-by-step tutorial in my blog. This tutorial is then also useful for WinXP/7 users.
About linux: I am a computer science student and I do have some knowledge with linux. I also share a dedicated web root server running Debian with a friend. With the time, I learned how to use administrate a root server with a terminal. But at home, I rather stay with Windows, where all my software works. I personally could not imagine using another OS than Windows for a workstation - at the same time, I could not imagine any other OS for web-servers than Linux. (Side-information: This experimental-system, as I told is very old and has beside the 300 MHz only 6 GB laptop HDD. Yes, I know that size it is a joke and not indented for real work. This small HDD is another reason why a dual boot would be not easy)
But again, I want to tell: I do not want that you support the experimental IPv6 stack on Windows 2000 and help me using an outdated operating system. What I wish is that you check my steps I have written above and tell me how YOU did setup your client IF you sit behind a NAT router with DHCP and probably also have similar router hardware (Telekom) as I do.
You have figured out that my adu+rdu (I still don't know what these things mean...) was already wrong, because I followed a wrong tutorial. Was this the only malconfiguration you could see in my steps above? I don't know if this setting of adu+rtu did automatically resets when I restart my computer. I also tried some misc stuff to try to undo these rdu+adu commands, but I really don't know what I am doing. IPv6 and its routing is yet a bit cryptic for me.
I would be glad if you could check my attached informations and tell me if you see something which might cause the malfunction. Maybe it is just a malconfiguration in the config files and no operating system incompatibility.
Even if I know something about Windows networks, sockets (in software development), TLS connections and webserver-setups like Apache, I have to admit, that at the moment I have low knowledge about everything "below" the HTTP(S)/FTP/...-application-layer. The output of "ipv6 if" sounds like Chinese script to me and at the moment I don't understand how the routing works (resp. "should" work for correct SIXXS PoP/VPN usage). This is also why I am using SIXXS at the moment: I want to learn new things about IPv6 and VPN networks - learning by doing.
Regards
Daniel Marschall
--- Attachment: ---
Some information about my hard+software
Router: Telekom Speedport W700V (IPv4, NAT, DHCP)
Network card: PCMCIA WLAN
The WLAN network card has the IPv6 stack installed. ("LAN-Verbindung 4")
The aiccu virtual network card has no IPv6 installed (I did not touch this virtual network card)
After I connected ("Enabled") IPv6 in aiccu, I can present following information:
C:\Dokumente und Einstellungen\Daniel Marschall>ipv6 if
Interface 5 (site 1): LAN-Verbindung 4
uses Neighbor Discovery
link-level address: 00-80-5a-50-90-9b
preferred address fe80::280:5aff:fe50:909b, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff50:909b, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 34500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 4 (site 1): aiccu
cable reconnected
uses Neighbor Discovery
link-level address: 00-ff-bf-fc-c7-7c
preferred address fe80::2ff:bfff:fefc:c77c, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:fffc:c77c, 1 refs, last reporter, 5 seconds until
report
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 27500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 3 (site 1): 6-over-4 Virtual Interface
uses Neighbor Discovery
link-level address: 192.168.69.110
preferred address fe80::c0a8:456e, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ffa8:456e, 1 refs, last reporter
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 37000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 2 (site 0): Tunnel Pseudo-Interface
does not use Neighbor Discovery
link-level address: 0.0.0.0
preferred address 2001:4dd0:ff00:61c::2, infinite/infinite
preferred address ::192.168.69.110, infinite/infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0
Interface 1 (site 0): Loopback Pseudo-Interface
does not use Neighbor Discovery
link-level address:
preferred address ::1, infinite/infinite
link MTU 1500 (true link MTU 1500)
current hop limit 1
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0
C:\Dokumente und Einstellungen\Daniel Marschall>ping6 ipv6.google.com
Pinging ipv6.l.google.com [2a00:1450:8007::6a] with 32 bytes of data:
Request timed out. (<--- Note that these "time-outs" come very fast (1 second! O_o At the blinking light I can see that my WLAN card sends a signal on every ping! )
Request timed out.
Request timed out.
Request timed out.
C:\Dokumente und Einstellungen\Daniel Marschall>ipconfig
Windows 2000-IP-Konfiguration
Ethernetadapter "LAN-Verbindung 4":
Verbindungsspezifisches DNS-Suffix: Speedport_W_700V
IP-Adresse. . . . . . . . . . . . : 192.168.69.110
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.69.1
Ethernetadapter "aiccu":
Verbindungsspezifisches DNS-Suffix:
IP-Adresse. . . . . . . . . . . . : 0.0.0.0
Subnetzmaske. . . . . . . . . . . : 0.0.0.0
Standardgateway . . . . . . . . . :
C:\Dokumente und Einstellungen\Daniel Marschall>ipconfig /all
Windows 2000-IP-Konfiguration
Hostname. . . . . . . . . . . . . : spr4200
Primres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Broadcastadapter
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : Speedport_W_700V
Ethernetadapter "LAN-Verbindung 4":
Verbindungsspezifisches DNS-Suffix: Speedport_W_700V
Beschreibung. . . . . . . . . . . : Conceptronic 54g Wireless PC-Card #2
Physikalische Adresse . . . . . . : 00-80-5A-50-90-9B
DHCP-aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IP-Adresse. . . . . . . . . . . . : 192.168.69.110
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.69.1
DHCP-Server . . . . . . . . . . . : 192.168.69.1
DNS-Server. . . . . . . . . . . . : 192.168.69.1
Lease erhalten. . . . . . . . . . : Freitag, 11. Mrz 2011 00:48:14
Lease luft ab. . . . . . . . . . : Dienstag, 19. Januar 2038 04:14:07
Ethernetadapter "aiccu":
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : TAP-Win32 Adapter V8
Physikalische Adresse . . . . . . : 00-FF-BF-FC-C7-7C
DHCP-aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IP-Adresse (Autokonfiguration). . : 169.254.172.43 (?????)
Subnetzmaske. . . . . . . . . . . : 255.255.0.0 ( NOTE: This address is not inside my subnet mask of my router, which is 255.255.255.0 . Is that still OK???)
Standardgateway . . . . . . . . . :
DNS-Server. . . . . . . . . . . . :
--- End of attachment ---
Using Sixxs with Windows 2000
Shadow Hawkins on Friday, 11 March 2011 12:25:34
Hi Daniel,
Thanks for your message, that was an interesting read. I am not very familiar with Windows, but maybe I can help with some ideas. If I get something wrong here, I'm sure one of the real experts will jump in an correct me :-).
The way I understand how Aiccu works is it establishes a UDP connection to your PoP. This is a two-way connection, so if Aiccu starts without errors, this means that the connection to the PoP is working. Aiccu also creates a virtual network interface using the TUN/TAP drivers. It then encapsulates any IPv6 packet it receives on this virtual interface inside an IPv4 UDP message and sends it to the PoP over the IPv4 UDP connection (using the AYIYA protocol). Essentially, if Aiccu starts, the connection to the PoP works and the virtual interface works as well. The problem is thus most likely a routing problem on your local machine.
Don't worry about the IPv4 address of the aiccu virtual interface, it should not be used (it is an auto-configuration address used by some systems in the absence of DHCP, I forgot the name of the protocol).
The timeout message you get for the ping6 is wired. Possible reasons I can think of are the timeout being too short (no idea on how to change it, though) and something not working with the IPv6 stack on Windows 2000.
Can you ping6 the local address of your aiccu interface? E.g.:
ping6 2001:4dd0:ff00:61c::2
What do you get for "tracert6 ipv6.google.com" ?
I remember having seen in some forum messages that sometimes one is required to manually configure an IPv6 address for a physical interface (e.g., your Ethernet port, I think, any address works) before IPv6 starts working. Maybe this could help (but I don't know how to configure such an address on Windows).
Cheers,
Urs
PS: Maybe there are some ideas for your situation on this web page:
http://www.su4me.de/win_ipv6.html
Using Sixxs with Windows 2000
Shadow Hawkins on Friday, 11 March 2011 18:36:08
Hello and thank you for your reply.
I have increased the timeout with "ping6 -w 10000" to 10 secs. Still request timeout.
Tracert6 also shows request timeout on every "hop".
But: "ping6 2001:4dd0:ff00:61c::2" (my external IPv6) does work! I do not know if this ping is actually sent over the PoP or if it is handled somehow internally. Is this information, that this ping6 works, useful to determinate a possible reason?
I have looked again at "ipv6 if" (and I also attached differences before and after PoP connect)
I am wondering about this part of "ipv6 if":
.. link-level address: 0.0.0.0
.... preferred address ::169.254.172.43, infinite/infinite
.... preferred address 2001:4dd0:ff00:61c::2, infinite/infinite
.... preferred address ::192.168.69.110, infinite/infinite
192.168.69.110 is my IPv4 inside my network. 169.254.172.42 is the random choosen IP of TAP32 (Virtual network card "aiccu") and 2001:4dd0:ff00:61c::2 is my external IPv6.
Question:
- Is this some kind of "network bridge", so that 2001:4dd0:ff00:61c::2 is "connected" with 192.168.69.110 (localhost)?
- Is it OK that there is written 0.0.0.0? Or should there be 192.168.69.110 ?
===============================================
* BEFORE IPv6 AICCU CONNECT *
C:\Dokumente und Einstellungen\Daniel Marschall>ipv6 if
Interface 5 (site 1): 6-over-4 Virtual Interface
uses Neighbor Discovery
link-level address: 192.168.69.110
preferred address fe80::c0a8:456e, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ffa8:456e, 1 refs, last reporter
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 33500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 4 (site 1): LAN-Verbindung 4
cable reconnected
uses Neighbor Discovery
link-level address: 00-80-5a-50-90-9b
preferred address fe80::280:5aff:fe50:909b, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff50:909b, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 35000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 3 (site 1): aiccu
cable unplugged
uses Neighbor Discovery
link-level address: 00-ff-bf-fc-c7-7c
preferred address fe80::2ff:bfff:fefc:c77c, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:fffc:c77c, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 44000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 2 (site 0): Tunnel Pseudo-Interface
does not use Neighbor Discovery
link-level address: 0.0.0.0
preferred address ::192.168.69.110, infinite/infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0
Interface 1 (site 0): Loopback Pseudo-Interface
does not use Neighbor Discovery
link-level address:
preferred address ::1, infinite/infinite
link MTU 1500 (true link MTU 1500)
current hop limit 1
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0
* AFTER IPv6 AICCU CONNECT *
C:\Dokumente und Einstellungen\Daniel Marschall>ipv6 if
Interface 6 (site 1): 6-over-4 Virtual Interface
uses Neighbor Discovery
link-level address: 169.254.172.43
preferred address fe80::a9fe:ac2b, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:fffe:ac2b, 1 refs, last reporter, 6 seconds until
report
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 31000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 5 (site 1): 6-over-4 Virtual Interface
uses Neighbor Discovery
link-level address: 192.168.69.110
preferred address fe80::c0a8:456e, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ffa8:456e, 1 refs, last reporter
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 33500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 4 (site 1): LAN-Verbindung 4
cable reconnected
uses Neighbor Discovery
link-level address: 00-80-5a-50-90-9b
preferred address fe80::280:5aff:fe50:909b, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff50:909b, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 35000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 3 (site 1): aiccu
cable reconnected
uses Neighbor Discovery
link-level address: 00-ff-bf-fc-c7-7c
preferred address fe80::2ff:bfff:fefc:c77c, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:fffc:c77c, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 44000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 2 (site 0): Tunnel Pseudo-Interface
does not use Neighbor Discovery
link-level address: 0.0.0.0
preferred address ::169.254.172.43, infinite/infinite
preferred address 2001:4dd0:ff00:61c::2, infinite/infinite
preferred address ::192.168.69.110, infinite/infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0
Interface 1 (site 0): Loopback Pseudo-Interface
does not use Neighbor Discovery
link-level address:
preferred address ::1, infinite/infinite
link MTU 1500 (true link MTU 1500)
current hop limit 1
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0
Using Sixxs with Windows 2000
Shadow Hawkins on Thursday, 10 March 2011 06:05:35
Additional information:
When AICCU is not started, ping6 outputs "No route to destination". When AICCU is enabled, ping6 outputs "Request timed out".
Using Sixxs with Windows 2000
![[fr]](/s/countries/fr.gif) Shadow Hawkins on Thursday, 31 May 2012 03:15:30
I have exactly the same problem.
I use Windows 2000 SP4.
When I connect SixXS, either with the console or the GUI, I get timeouts and nothing more. The tracert6 command does not reach even the 1st hop! I do not know what is actually the 1st router of the route because it does not respond.
The Tap32 is number 5 in the interface list.
- The default (unicast) IPv6 is fe80::2ff:42ff:febf:4474.
I start the SixXS client.
- I can ping myself (2a01:xxxx:xxxx:xxxx::2) with <1ms: the IPv6 has been correctly obtained.
- I tried to fix manually the IPv6 of the Tap32 interface, thinking about any strange problem:
ipv6.exe adu 5/2a01:xxxx:xxxx:xxxx::2
Time to test, because the interface is ready:
- Then, I should be able to ping or traceroute the PoP IPv6.
ping6 2a01:xxxx:xxxx:xxxx::1
Timeouts...
- No need to try to add routes or anything else, there is a serious communication problem which prevents the Tap32 interface to dialog with the PoP by IPv6. Of course I cannot reach other IPv6 addresses (Facebook, Google and another machine connected with SixXS).
When I try to traceroute my IPv6 from another healthy IPv6 connection with SixXS, I get an unreachable destination notification from the 1st hop (it appears on the 2nd line).
Note: I have an annoying linked problem: PHP cannot reach some IPv6-enabled websites like Facebook. This problem appeared some days ago, either because I used SixXS or because Facebook changed their DNS config. The IPv6 protocol was already installed for a long time but I had no prob...
Thank you all for any other help. I am still looking for the solution, but I am not an expert.
For information, here is the Syntax of ipv6.exe. Very difficult for non expert people...
Estevan
Using Sixxs with Windows 2000
Only the static and heartbeat proto-41 based tunnels where tested under Windows 2000 some 10 years ago. Do not expect AYIYA based tunnels to work at all.
I suggest that you finally upgrade to a current operating system. Using Windows 2000 on the Internet is not safe and the IPv6 stack is not up to par to anything either.
|
on Tuesday, 08 March 2011 09:34:41
Posting is only allowed when you are