Windows tries to use 6to4 and Teredo automatically, not always resulting in a good IPv6 experience. To disable both, execute these commands:
netsh interface ipv6 6to4 set state disabled
netsh interface teredo set state disabled
On Windows XP teredo isn’t a context inside interface, but rather a setting in ipv6:
netsh interface ipv6 set teredo disabled
Sources and more information:
I ran into a model symptom of lacking multicast support with IPv6: a system wouldn’t answer to IPv6 traffic it didn’t initiate. But unless you’ve run into the problem before and managed to diagnose it successfully, you might not realize it’s about multicast.
It was my second Debian Linux system with IPv6 connectivity that gave me a start. I built one more system and got the same results. I could have sworn the first one had worked fine without any tricks. I considered it, but decided I’d rather not abandon IPv6 on Linux. After all, I had it running on all the other platforms (NetBSD, Mac OS X, Windows). (more…)
I never seem to be able to remember this, and somehow I end up with new Windows installations without this change:
netsh interface ipv6 set privacy state=disable
This will disable temporary IPv6 addresses. These are especially nasty on desktop systems, where the address will expire from under you. If you find yourself having to restart your SSH terminal connections every 14 hours to 6 days, this is why (as far as I can tell).
I really don’t buy the privacy aspect of generating random IP addresses. If you worry about eavesdropping, encrypt your traffic. If you worry about someone tracking your traffic patterns, stop browsing those questionable sites. :)
I’ve had IPv6 connectivity for over 5 years (first from IIJ, now from SixXS). However, it wasn’t until last night that I finally got my website on IPv6, when some final wrinkles in the web server configuration were ironed out. (more…)