Forum - Teredo query :: SixXS - IPv6 Deployment & Tunnel Broker

Teredo query

Shadow Hawkins on Tuesday, 17 February 2009 18:42:31

I know that it's perhaps unwise to promote the use of transition technologies like Teredo but it may save some time for Windows users that merely wish to test IPv6 functionality without going through the trouble of installing software, registering with a tunnel broker, etc. Is there any interest in providing a quick FAQ on the wiki that explains the details of Teredo, why it's a bad idea to promote it for long term use, why you shouldn't use it in the enterprise, etc...? I haven't tested it with Vista or Win7 yet but with XP SP3 I've found that Teredo was fairly easy to configure. Since there are currently active routes being advertised it does provide simple, albeit slow, access to IPv6 only hosts. I didn't have to assign a static IP either -- I just ran 'ipv6 install,' 'netsh interface ipv6 set teredo client teredo.ipv6.microsoft.com,' and after a short pause was able to ping and browse ipv6.google.com using ping -6 and Firefox 3. This may be sufficient for most home users who are also less likely to have symmetrical NAT configurations. Any thoughts? -Gary

Teredo query

Shadow Hawkins on Thursday, 19 February 2009 17:17:15

Hi Gary, i am playing around with teredo on vista and miredo on linux. On linux it run very fine: Just install the packages and surf. On Vista (32-Bit, Business-Edition) i have one big problem: The Teredo-Client launched the connection, ping -6 www.sixxs.net works, but i cant open website with Firefox 3 or download files with utorrent. This may a common problem, see http://www.sixxs.net/forum/?msg=setup-714300 however the workaround does not work on my setup. Have anyone some hints? Many thanks form Hannover, Reik

Teredo query

Shadow Hawkins on Thursday, 19 February 2009 18:49:14

Have you assigned an IPv6 address to your interface? If you don't, Vista won't let you browse the web via IPv6

Teredo query

Shadow Hawkins on Friday, 20 February 2009 13:03:01

Hello Carl, yes, i have assigned an address to my LAN-Connection (2002:c0a8:211::/48 and later 2001:db8:1::1/64). After this, the teredo-client stopped the connection and no application can handle ipv6-requests:

netsh interface ipv6 show teredo

... Status: dormant Clienttype: teredo host-specific relay Netzwerk: unmanaged NAT: none (global connectivity) i am clueless ;) Best, Reik

Teredo query

Shadow Hawkins on Friday, 20 February 2009 15:02:22

Is your machine a member of an AD Domain?

Teredo query

Shadow Hawkins on Friday, 20 February 2009 15:03:12

Above you listed an IPv6 range...I'm assuming you assigned a /128 address, correct?

Teredo query

Shadow Hawkins on Friday, 20 February 2009 16:37:17

The machine is not a member of an AD-Domain, but i have not set an /128-Address. I will try it. Many thanks so long, Reik

Teredo query

Shadow Hawkins on Friday, 20 February 2009 17:06:34

Hello Carl, i have changed the address to 2002:c0a4:211::1/128. Teredo said under Point NAT, that there is "global connectivity". The same as before ... If you want, i can paste my routing-table for diagnostics. Best regards, Reik

Teredo query

Shadow Hawkins on Friday, 20 February 2009 17:49:01

Sure, go ahead and post that. Post the output of ipconfig /all as well

Teredo query

Shadow Hawkins on Friday, 20 February 2009 18:09:27

Well, here are my dumps from ipconfig, route and netsh's teredo context. The output is mostly german:

ipconfig /all

Windows-IP-Konfiguration Hostname . . . . . . . . . . . . : cttest-PC-resje Primï¿½res DNS-Suffix . . . . . . . : Knotentyp . . . . . . . . . . . . : Hybrid IP-Routing aktiviert . . . . . . : Nein WINS-Proxy aktiviert . . . . . . : Nein DNS-Suffixsuchliste . . . . . . . : Speedport_W_700V Ethernet-Adapter LAN-Verbindung: Verbindungsspezifisches DNS-Suffix: Speedport_W_700V Beschreibung. . . . . . . . . . . : NVIDIA nForce Networking Controller Physikalische Adresse . . . . . . : 00-1A-4D-FB-E8-4A DHCP aktiviert. . . . . . . . . . : Ja Autokonfiguration aktiviert . . . : Ja IPv6-Adresse. . . . . . . . . . . : 2002:c0a8:211::1(Bevorzugt) Verbindungslokale IPv6-Adresse . : fe80::59b9:42f6:b32:8efb%8(Bevorzugt) IPv4-Adresse . . . . . . . . . . : 192.168.2.17(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.255.0 Lease erhalten. . . . . . . . . . : Freitag, 20. Februar 2009 17:57:49 Lease lï¿½uft ab. . . . . . . . . . : Dienstag, 24. Februar 2009 17:57:48 Standardgateway . . . . . . . . . : 192.168.2.1 DHCP-Server . . . . . . . . . . . : 192.168.2.1 DNS-Server . . . . . . . . . . . : 192.168.2.1 NetBIOS ï¿½ber TCP/IP . . . . . . . : Aktiviert Tunneladapter LAN-Verbindung*: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: Speedport_W_700V Beschreibung. . . . . . . . . . . : isatap.Speedport_W_700V Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja Tunneladapter LAN-Verbindung* 2: Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physikalische Adresse . . . . . . : 02-00-54-55-4E-01 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja IPv6-Adresse. . . . . . . . . . . : 2001:0:d5c7:a2d6:30a4:ec2:3f57:fdee(Bevorzugt) Verbindungslokale IPv6-Adresse . : fe80::30a4:ec2:3f57:fdee%12(Bevorzugt) Standardgateway . . . . . . . . . : NetBIOS ï¿½ber TCP/IP . . . . . . . : Deaktiviert

route print

=========================================================================== Schnittstellenliste 8 ...00 1a 4d fb e8 4a ...... NVIDIA nForce Networking Controller 1 ........................... Software Loopback Interface 1 11 ...00 00 00 00 00 00 00 e0 isatap.Speedport_W_700V 12 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface =========================================================================== IPv4-Routentabelle =========================================================================== Aktive Routen: Netzwerkziel Netzwerkmaske Gateway Schnittstelle Metrik 0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.17 10 127.0.0.0 255.0.0.0 Auf Verbindung 127.0.0.1 306 127.0.0.1 255.255.255.255 Auf Verbindung 127.0.0.1 306 127.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 306 192.168.2.0 255.255.255.0 Auf Verbindung 192.168.2.17 266 192.168.2.17 255.255.255.255 Auf Verbindung 192.168.2.17 266 192.168.2.255 255.255.255.255 Auf Verbindung 192.168.2.17 266 224.0.0.0 240.0.0.0 Auf Verbindung 127.0.0.1 306 224.0.0.0 240.0.0.0 Auf Verbindung 192.168.2.17 266 255.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 306 255.255.255.255 255.255.255.255 Auf Verbindung 192.168.2.17 266 =========================================================================== Stï¿½ndige Routen: Keine IPv6-Routentabelle =========================================================================== Aktive Routen: If Metrik Netzwerkziel Gateway 1 306 ::1/128 Auf Verbindung 12 18 2001::/32 Auf Verbindung 12 266 2001:0:d5c7:a2d6:30a4:ec2:3f57:fdee/128 Auf Verbindung 8 266 2002:c0a8:211::1/128 Auf Verbindung 8 266 fe80::/64 Auf Verbindung 12 266 fe80::/64 Auf Verbindung 12 266 fe80::30a4:ec2:3f57:fdee/128 Auf Verbindung 8 266 fe80::59b9:42f6:b32:8efb/128 Auf Verbindung 1 306 ff00::/8 Auf Verbindung 12 266 ff00::/8 Auf Verbindung 8 266 ff00::/8 Auf Verbindung =========================================================================== Stï¿½ndige Routen: Keine

netsh interface ipv6 show teredo

Teredo-Parameter --------------------------------------------- Typ : client Servername : teredo.ipv6.microsoft.com Clientaktual.-intervall : 30 Sekunden Clientport : unspecified Status : dormant Clienttyp : teredo host-specific relay Netzwerk : managed NAT : none (global connectivity)

Teredo query

Shadow Hawkins on Friday, 20 February 2009 19:57:18

I don't know any German, so that's my disclaimer ;) First off, this is what I did to make teredo work on my site: First, need to set a 2001:/64 address on the local area connection (just convert your ip to hex) so a ipv4 address of 192.168.100.193 would be 2001:c0a8:64c1:: Make sure subnet is /48 Next, figure out what index your teredo adapter isâ¦ do a ânetsh int ipv6 show intâ or âipconfig /allâ Finally, route all traffic through that interface by ânetsh int ipv6 add route ::/0 int (whatever interface #)â (Can check routes by doing a ânetsh int ipv6 show routeâ Wait a couple of seconds for the tunnel to come up ======================================================================= Do you have a line in your routing table that sends all the unknown traffic somewhere?

Teredo query

Shadow Hawkins on Friday, 20 February 2009 19:59:03

Well that doesn't look very pretty. Let me try again and take out the quotation marks First, need to set a 2001:/64 address on the local area connection (just convert your ip to hex) so a ipv4 address of 192.168.100.193 would be 2001:c0a8:64c1:: Make sure subnet is /48 Next, figure out what index your teredo adapter isâ¦ do a netsh int ipv6 show int or ipconfig /all Finally, route all traffic through that interface by netsh int ipv6 add route ::/0 int (whatever interface #) (Can check routes by doing a netsh int ipv6 show route Wait a couple of seconds for the tunnel to come up

Teredo query

Shadow Hawkins on Tuesday, 24 February 2009 00:24:04

Hello, many thanks for these details. My setup is now running, the main problem was the ip-address and my impatience. Best regards, Reik

Please note Posting is only allowed when you are logged in.