Old Trick: this blog via IPv6

You can view this website via IPv6 by using the URL http://ipv6-or-no-ipv6.blogspot.com.ipv6.sixxs.org/

It's an old trick, provided by the people from Sixxs: just fill out "ipv6.sixxs.org" at the end of (the FQDN part) of an URL. Examples:

http://www.cnn.com.ipv6.sixxs.org/
http://geenstijl.nl.ipv6.sixxs.org/

The other way around is possible too: Make an IPv6 site accessible site via IPv4. So: you --- IPv4 --- sixxs --- IPv6 --- website. Example:

http://www.whatismyipv6.net.ipv4.sixxs.org/
http://www.ipv6.surfnet.nl.ipv4.sixxs.org/

Just for fun.

Teredo or no Teredo: that's the question

Grrrrrrrrrr. Suddenly Eva's laptop (the great Dell Studio Laptop: real great machine) hasn't got IPv6 connectivity anymore. And thus news.ipv6.eweka.nl downloads are not working anymore.

Result of ipconfig:

C:\>ipconfig

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : lokaal
   Link-local IPv6 Address . . . . . : fe80::79da:502b:44bc:ff82%12
   IPv4 Address. . . . . . . . . . . : 192.168.1.36
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 6:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 7:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : lokaal

C:\>


What's going on? The only thing that has changed, is a reboot of the Linksys access point. So let's check what happens when I connect the laptop via a wire to the Linksys:

C:\>ipconfig

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : lokaal

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : lokaal
   Link-local IPv6 Address . . . . . : fe80::8478:8ade:811f:2838%11
   IPv4 Address. . . . . . . . . . . : 192.168.1.34
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254

Tunnel adapter Local Area Connection* 7:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2ca:248b:9277:ad55:e84b
   Link-local IPv6 Address . . . . . : fe80::248b:9277:ad55:e84b%10
   Default Gateway . . . . . . . . . : ::

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : lokaal

C:\>

Teredo's back!

That's good news. The bad news:

• Teredo didn't work when connected via wireless, for no clear reason
  
• Windows Vista wasn't saying why there was no Teredo connectivity

Does anybody know if there is any logging about Teredo? Maybe I should have used

C:\>netsh interface teredo show state
Teredo Parameters
---------------------------------------------
Type                    : default
Server Name             : teredo.ipv6.microsoft.com.
Client Refresh Interval : 30 seconds
Client Port             : unspecified


C:\>

Comments please!

Transmission bittorrent client successful with IPv6

Cool: as of December 15 2008, the bittorrent client "Transmission" has IPv6 implemented in the development version. I think it will become public with transmission version 1.5.

I couldn't wait for that, so I activated the "nightly build" on my Ubuntu by add the following lines to /etc/apt/sources.list:

deb http://ppa.launchpad.net/transmissionbt-nightly/ubuntu hardy main
deb-src http://ppa.launchpad.net/transmissionbt-nightly/ubuntu hardy main

I then installed and started Transmission. Version is 1.42+, FWIW.

Result:Transmission works with IPv6. It's connected to other IPv6 peers (using torrent "FreeBSD 7.0-Release i386 CD1" from sixxs IPV6 tracker), both BitTornado and utorrent. And ... over my teredo / miredo connection.

Cool!

uTorrent with Teredo IPv6 on Windows XP ... works!

See the included screenshots: uTorrent with Teredo IPv6 on Windows XP SP3 ... works!

Just install and start uTorrent.
Then, under Options -> Preferences ( -> General) click "Install IPv6/Teredo".

To check the IPv6 functionality, from http://www.sixxs.net/tools/tracker/catalog/ select an active download, for example FreeBSD 7.0-Release i386 CD1


Please note:
1) you need (at least) SP3.
2) it should work on Windows Vista too. A Teredo is activated on Vista by default, I think you won't need to "Install IPv6/Teredo".

Windows Vista Teredo status: "general system failure"

A friend's Windows Vista machine is showing an ugly Teredo status: "general system failure". Needless to say: Teredo is not working. There's even no 2001:0: address. There is, however, strangely enough, a 6to4 2002:-address ...

I don't know what the cause is. It might be related to his firewall. He's not behind NAT.

Comments / tips welcome.


C:\Users\Alain>netsh interface teredo show

The following commands are available:

Commands in this context:
show state     - Shows Teredo state.

C:\Users\Alain>netsh interface teredo show state
Teredo Parameters
---------------------------------------------

Type                    : default
Server Name             : teredo.ipv6.microsoft.com.
Client Refresh Interval : 30 seconds
Client Port             : unspecified
State                   : offline
Error                   : general system failure


C:\Users\Alain>


C:\Users\Alain>ping 2001:4de0:1::1:1

Pinging 2001:4de0:1::1:1 from 2002:5ed1:bd57::5ed1:bd57 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 2001:4de0:1::1:1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Alain>

Handy IPv6 traceroute site

This is a handy IPv6 traceroute site: http://www.whatismyipv6.net/?s=IPv6_traceroute

BTW: I believe traceroutes with teredo / miredo IPv6 address do a different "to" than "return" trace.

Below is a trace with my sixxs IPv6 connectivity.

Traceroute to 2001:838:3a4:0:218:deff:fe10:c560:

1 gw-1330.ham-01.de.sixxs.net (2001:6f8:900:531::1) 19.834 ms 19.763 ms 20.972 ms 2 vl101.cr21.isham.de.easynet.net (2001:6f8:800:1003::209:55) 20.099 ms 20.588 ms 19.679 ms 3 ge1-3.br2.isham.de.easynet.net (2001:6f8:800:0:1:0:d4e0:49a) 19.615 ms 20.324 ms 18.881 ms 4 2001:6f8:1:0:87:86:71:240 (2001:6f8:1:0:87:86:71:240) 21.309 ms 19.74 ms 20.628 ms 5 2001:6f8:1:0:86:87:77:64 (2001:6f8:1:0:86:87:77:64) 35.091 ms 35.363 ms 36.183 ms 6 2001:6f8:1:0:87:86:77:62 (2001:6f8:1:0:87:86:77:62) 32.454 ms 32.224 ms 32.15 ms 7 2001:6f8:1:0:87:86:77:249 (2001:6f8:1:0:87:86:77:249) 32.383 ms 33.132 ms 30.913 ms 8 de-cix.fra20.ip6.tiscali.net (2001:7f8::cb9:0:1) 32.896 ms 33.107 ms 33.979 ms 9 ge-5-1-0.fra10.ip6.tiscali.net (2001:668:0:2::1:442) 32.287 ms 31.893 ms 33.588 ms 10 so-3-0-0.ams22.ip6.tiscali.net (2001:668:0:2::1:821) 42.155 ms 43.987 ms 43.476 ms 11 so-6-0-0.ams11.ip6.tiscali.net (2001:668:0:2::1:271) 50.227 ms 48.806 ms 49.828 ms 12 xe-1-0-0.ams10.ip6.tiscali.net (2001:668:0:2::1:791) 47.654 ms 45.762 ms 47.045 ms 13 ams-ix.ipv6.concepts.nl (2001:7f8:1::a501:2871:1) 50.09 ms 51.383 ms 51.056 ms 14 2001:838:0:10::2 (2001:838:0:10::2) 52.682 ms 53.334 ms 54.09 ms 15 2001:838:2:1:2a0:24ff:feab:3b53 (2001:838:2:1:2a0:24ff:feab:3b53) 48.505 ms * * 16 cl-701.ams-01.nl.sixxs.net (2001:838:300:2bc::2) 117.907 ms 119.484 ms 122.657 ms 17 2001:838:3a4:0:218:deff:fe10:c560 (2001:838:3a4:0:218:deff:fe10:c560) 115.879 ms 109.118 ms 120.455 ms

Easy IPv6 on Mac OS X: one step

Easy, one step procedure to get IPv6 connectivity on you MacOSX: go to http://www.deepdarc.com/2007/02/21/miredo-osx/ or download http://www.deepdarc.com/miredo-osx-prerelease2.pkg.zip directly, and install it.

That's it. You should now be able to visit ipv6.google.com and ... download from news.ipv6.eweka.nl