AuthorTopic: stupid question....windows 7? (Read 4419 times)

this is clearly a stupid question, but google is not cooperating with me right now. How is it that an out-of-the-box windows7 client have a working IPv6 tunnel? ISATAP is pre-configured? Just for kicks I tried ipv6.google.com, which works, so does tracert;

tracert ipv6.google.com

Tracing route to ipv6.l.google.com [2001:4860:800f::67]over a maximum of 30 hops:

Windows 7 is configured to use ipv6 out of the box. It uses ipv6 to communicate between computers on the lan if you turn it off you break windows functionality . If you happen to connect it to a LAN that has IPv6 it will use it and prefer it.

Windows 7 is configured to use ipv6 out of the box. It uses ipv6 to communicate between computers on the lan if you turn it off you break windows functionality . If you happen to connect it to a LAN that has IPv6 it will use it and prefer it.

This is what I realized My question was more around the lines of, why does the tunnel endpoint seem to default to HE (MS has arranged this?) and how does it choose the most efficient or closest endpoint?

can someone educate me as to how win7 chooses its tunnel endpoint, and how it is that he.net is clearly my tunnel endpoint, and if so, why people go through the trouble of signing up for a tunnel here

If you're using teredo, like I'm guessing, there are a few reasons people would sign up for a tunnel here. With teredo, you get one IP address that changes (depending mostly on ports used, which does change.) If you sign up for a tunnel from HE you get STATIC addresses and a whole block if you want. With a tunnel from HE, you can have one computer on your LAN be the local tunnel endpoint, and set that machine to give out IPv6 addresses from your assigned block and to route the resulting traffic through the tunnel. By doing this, all the machines on your LAN can have a static IPv6 address and you only have one tunnel.

You are on 6to4 (2002::/16 space). Your ISP must hear the anycasted announcement of 192.88.99.1/24 from us, so that is why you connected through us.

I am the ISP ( ) Guess its time I get off my rear and start setting up tunnel servers too. Still toying with BGP and dual-stack for now. Plus I need a third peer (Cogent being my first one....) since HE is nicely allowing me to peer over a ipv6ip tunnel, I won't be abusing that tunnel with customer traffic...

As for 192.88.99.1, I local-pref'ed AS6939 via one of my transit peers for pre-determined connectivity to HE for the v6 tunnel, and thus the 192.88.99.0/24 prefix is preferred as well since its being learned from that AS as well....all is explained.

I am learning volumes of info every day lately, it is reminding me of the VLSM days My thanks to HE for making this possible.