Comments on: IPv6 at home, Part 1: Overview, Teredo

By: ipv6 at home, part 3: gogo6 (Hexago) tunnels, freenet6 « Thorsten on (mostly) Tech

Sun, 09 Aug 2009 13:32:57 +0000

[...] home, part 3: gogo6 (Hexago) tunnels, freenet6 This blog post is part of a series on ipv6. In part 1, I provided an overview of ipv6 and looked at Teredo, the technology built into Windows Vista; in [...]

By: ipv6 at home, part 2.5: Google, DHCPv6, speed tests, troubleshooting, various « Thorsten on (mostly) Tech

Sun, 02 Aug 2009 12:27:02 +0000

[...] DHCPv6, speed tests, troubleshooting, various This blog post is part of a series on ipv6. In part 1, I looked at Teredo, the technology built into Windows Vista; in part 2, I looked at AYIYA tunnels [...]

By: Faheem Syed

Faheem Syed — Tue, 28 Apr 2009 06:29:53 +0000

Hi,
The Explanation is great. This gave me an oppurtunity to ask one of a burning issue which I am facing for last 2 months. I need to establish a stateful DHCPv6 in a test lab to gain control over client population using predetermined scopes of IPv6 address. So far Couldnt succeed on windows platform (server 2000, 2003, 2008). Windows 7 Seems to be a good client OS but Servre OS to support DHCPv6 (stateful and to go beyond /64) is not there. Any help on this, pls. It will really be appreciated.
Thanks.
Faheem

By: Marlow

Marlow — Sun, 04 Jan 2009 23:01:18 +0000

Hi,

thanks for a good article. This explained a few issues we were seeing with Vista clients and teredo.

By: petermoses

petermoses — Tue, 21 Oct 2008 17:51:06 +0000

You can check this application which uses teredo to safely access a system over internet & disables it after usage…
http://www.lanoninternet.com

By: Erik Olivenza

Erik Olivenza — Tue, 02 Sep 2008 18:21:50 +0000

So I figured out my Teredo issue and it does make sense.

I had 6to4 enabled on my system which was giving me a valid Global unicast address for my Hamachi interface. When I disabled the 6to4 service, Teredo finally kicked in with a valid 2001::/32 unicast address for my system and now all is well.

I also came across this and might be of help for *some* users who are still experiencing issues.

“NOTE for Windows XP users
Once Teredo became RFC, the old IPv6 prefix from 6BONE (3ffe:8319::/32) has been replaced by the IANA allocated one, 2001::/32. This change, together with the 6Bone phase-out on 6/6/2006, requires a modification in the old Windows XP Teredo Clients to support it. Teredo client in Windows Vista does not require such a modification.
The modification of Windows XP Teredo clients can be done with any of the folowing two ways:
A) Installing the Windows Update KB922819. Note that if you have installed the Peer Name Resolution Protocol (PNRP), which is available in the Windows Update KB920342, then you do not need to install the KB922819 update.
B) Adding or altering the REG_DWORD value of the \HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip6\Parameters\GlobalParams\TeredoPrefix entry in the Windows Registry. The REG_DWORD value is interpreted as a 32 bit prefix, in network byte order. To do that just follow the following steps:
1. Run the regedit.exe program: Start -> Run -> Write regedit.exe and then click on OK button.
2. Browse through the registry tree to check if the
\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip6\Parameters\GlobalParams\TeredoPrefix
entry exists. If don’t so, add it.
3. Add/modify the REG_DWORD value to 0×00000120 (288).
4. Reboot your system.
5. Follow the configuration guides for Windows XP/ Windows 2003 below for configuring your Windows Teredo Client.
For that modification to work it is essential that the Teredo Server advertises the new IPv6 prefix (2001:0000::/32).
Teredo Client implementation in Windows Vista supports the new IPv6 prefix without modifications.”

Source: http://www.ipv6tf.org/index.php?page=using/connectivity/teredo

I hope this information helps someone out there.

Sincerely,
Erik

By: yorickdowne

yorickdowne — Fri, 29 Aug 2008 13:00:40 +0000

I would hazard a guess and say you have a NAT issue. show teredo claims you are behind “restricted” NAT, but that seems unlikely in a home environment. More likely, you are behind some sort of PAT, which Teredo calls “Symmetric NAT”. Teredo on Windows XP does not handle PAT at all.

You don’t necessarily want to have to redesign your entire home network. My recommendation at this point would be to skip to part 2 of the series and configure an AYIYA tunnel – or go even further and look at some of the tunnel brokers mentioned there and set up a static tunnel on a router.

The easiest way to get v6 connectivity at home that I know of, BTW, is to get an Apple Airport Extreme, which has one-click ipv6 tunnel setup built right in. I have not personally used the unit, but online reports of the ipv6 setup are favorable.

By: Erik Olivenza

Erik Olivenza — Fri, 29 Aug 2008 03:15:16 +0000

Here is the output of show teredo:

Teredo Parameters
———————————————
Type : client
Server Name : teredo.ipv6.microsoft.com
Client Refresh Interval : default
Client Port : default
State : qualified
Type : teredo host-specific relay
Network : unmanaged
NAT : restricted

I guess my issue is that I’m not being assigned a valid v6 address.

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4
Default Gateway . . . . . . . . . :

Here’s the output of show routes

Querying active state…

Publish Type Met Prefix Idx Gateway/Interface Name
——- ——– —- ———————— — ———————
no Autoconf 10 2001::/32 4 Teredo Tunneling Pseudo-Interface
yes Manual 1101 ::/0 3 2002:c058:6301::c058:6301
yes Manual 1001 2002::/16 3 6to4 Tunneling Pseudo-Interface

By: yorickdowne

yorickdowne — Thu, 28 Aug 2008 22:58:58 +0000

Teredo relays serve the endpoint you are trying to access, not your client, thus they are not configured on the client. A more in-depth explanation can be found at the wikis, here: http://en.wikipedia.org/wiki/Teredo_tunneling

If the issue you are experiencing has its roots in your client machine configuration, you are likely running into an issue with the “forcing traffic through Teredo by means of a fake v6 address and a route” trick. Is “netsh int ipv6 show teredo” providing any useful information?

By: Erik Olivenza

Erik Olivenza — Thu, 28 Aug 2008 19:34:49 +0000

Hello, thanks for writing this how to on IPv6 and Teredo.

I was wondering if you could help me get Teredo up and running on my system. I followed your instructions and I’m unable to ping any v6 websites. My host system is connected to the internet directly so my home router shouldn’t be an issue. FWs have been disabled to rule that out as well.

Since I know that Teredo requires a Teredo Server and Relay, your instructions for Xp only mentioned the use of teredo.ipv6.microsoft.com as the Teredo server. What relay were you using?

I’m also in Massachusetts, beautiful weather we’re having huh?

Sincerely,

Erik