Hello there, I've been running the RC for a couple of weeks now and decided to look into IPv6. My whole LAN has been running *native* IPv6 for a few years now. I get a /48 from my ISP, my clients all listen to the RA's from the router, the router routes IPv6 properly ... and all goes well. It was even working fine in XP too (that is, after enabling IPv6 in it of course). Now, in 7, things look a bit different. First of all, I noticed partial lack of IPv6 connectivity: I could ping my LAN but not the outside world. Command prompt "route" showed that the default route was via Teredo. I never asked for Teredo (I do not need nor want it !). So the first question is : why did Teredo come up and grab the default route ? Ok so now I think I found the problem, I decide to put Teredo at bay. I open an administrator's cmd, disable teredo (netsh > interface > teredo > set state disabled) and renew my IPv6 settings (ipconfig /renew6). Checking "route print -6" gets me something more adequate now, with the gateway for ::/0 set to the link-local address of my router. A few ping's and tracert's later, I have confirmed that IPv6 is now working as it should. Then after some time, the default route disappears. It takes a couple of "ipconfig /renew6" to restore it and be able to reach the IPv6 outside world again. Obviously the second question is : why does the IPv6 standard route disappear ? I might add that the router is sending the RA's often enough (600 seconds between each, at a maximum) and that their lifetime is adequate (1800 seconds). I have no experience whatsoever with Vista, but maybe this could apply to Vista as well. You are welcome to check :) Thanks ! LeCoyote

Bump! I'm not as tech-savvy as you, LeCoyote, so you might have to translate for me, but I'd like to know about teredo as well. It didn't work its way into my system while I was on Win 7RC, but all of a sudden it's there in Win7 RTM, and messing up my connection to boot. I deleted it and updated my NIC driver, and am hoping that will do it (since I had updated the driver under RC and teredo never snuck in), but I'd like to know what to do if it comes back. Like you, I neither need nor want it...

You can disable teredo with:netsh interface teredo set state disabledTeredo comes into play when you are behind a NAT firewall (home router).Don Murphy

Thanks, Don. I don't know if it will come back now that I updated the NIC driver, cos it didn't show upthe whole time I was running Win 7 RC. I started second-guessing myself after I deleted it (hence my thread in the Miscelleaneous category, guess I should have put it here); I am behind a home router and I know I am connected with IPv4.Did I make a mistake to delete Teredo?

I would not have deleted it.Doing things like that always come back to bite me.Don Murphy

No problem, I restored from a disk image from before I deleted it and Teredo came back as soon as I connected to the internet again, still with the yellow exclamation point. This time I told it to search for updated drivers but it said "the best software is already installed" so I guess I'll have to disable it, since I haven't been able to find a driver to download. Is it better to disable it with netsh than in Device Manager? Or should I ignore the yellow exclamation point as long as it doesn't affect my connection? I wish I could find more information on this Teredo thing. I wouldn't mind it being there if Windows didn't indicate a problem, and it worked. Edit: I disabled Teredo in netsh, but it still shows with an exclamation point in Device Manager. I guess I have to disable it there as well...or perhaps diabling it in Device Manager is sufficient? I found this link in my quest to discover more about Teredo: http://www.wired.com/threatlevel/2008/07/the-ghost-in-yo . Sounds ominous...well, I know I don't have IP 6 connectivity right now, and I do have the current version of ZoneAlarm--leave Teredo alone or disable?