Transmission 1.50 Released: with IPv6 support for peers, and for trackers with explicit IPv6 addresses

Cool: Transmission 1.50 has been released. To me, the most interesting part is "IPv6 support for peers, and for trackers with explicit IPv6 addresses".

Proof that it works: see the included screenshot of transmission connected to another IPv6 bittorrent peer, with happens to be a Vuze (formerly Azureus) 4.1.0.2 client.


Hooray! No more NAT problems thanks to IPv6! :-)

What is my IPv6 address

To find out what your IPv6 address is (and thus whether you have IPv6 connectivity to the Internet), you can visit:

http://ipv6.whatismyipv6.net/

That should work for Linux and Windows XP with Teredo IPv6. It should show your IPv6 address, something like in the picture.

If it doesn't work, it could be that your IPv6 resolving does not work (like on Windows Vista with Teredo), and you visit this site:

http://[2001:4810::110]/

Teredo IPv6 on Windows XP: better than Vista's Teredo?

OMG! I was glad to report that Vista had a (only?) advantage: Teredo IPv6 on by default. However, the strange thing is that Vista won't lookup an IPv6 / AAAA if only Teredo IPv6 is activated. The result is that you cannot visit ipv6.google.com, for example. Very annoying. What's the goal of Vista's Teredo IPv6 then? Yet another closed source Microsoft mystery.

And now I discover this: On Windows XP, if Teredo IPv6 is on (two easy commands, see below), you can ping and visit sites that only have IPv6. Very good. One remark: I believe only the IPv6-only sites like ipv6.google.com are approached via IPv6.

So, does this mean XP is even on this matter better than Vista?

C:\>netsh interface ipv6 install
Ok.


C:\>netsh interface ipv6 set teredo client
Ok.


C:\>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : lokaal
        IP Address. . . . . . . . . . . . : 10.0.2.15
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : fe80::a00:27ff:fe69:bca2%4
        Default Gateway . . . . . . . . . : 10.0.2.2

Tunnel adapter Teredo Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 2001:0:d5c7:a2d6:0:9fa9:3c0e:67f6
        IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
        Default Gateway . . . . . . . . . : ::

Tunnel adapter Automatic Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . : lokaal
        IP Address. . . . . . . . . . . . : fe80::5efe:10.0.2.15%2
        Default Gateway . . . . . . . . . :

C:\>ping ipv6.google.com

Pinging ipv6.l.google.com [2001:4860:0:1001::68] with 32 bytes of data:

Reply from 2001:4860:0:1001::68: time=217ms
Reply from 2001:4860:0:1001::68: time=70ms
Reply from 2001:4860:0:1001::68: time=103ms
Reply from 2001:4860:0:1001::68: time=76ms

Ping statistics for 2001:4860:0:1001::68:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 217ms, Average = 116ms

C:\>

FWIW: the Windows XP above is running on the great VirtualBox on Ubuntu.

Major IPv6 Breakthrough: 1 ‰ of The Pirate Bay peers has IPv6

A major Breakthrough for IPv6: 1 ‰ of The Pirate Bay peers has IPv6 connectivity to the Pirate Bay (TPB). That's a whopping 1 in 1000. Or 0.1%. Or 1000 ppm (parts per million). See included pictures for the development the past day and the past week. The 1‰ was achieved in the past 24 hours.

Statistics from http://thepiratebay.org/ itself:

IPv4 20.400.519 peers
IPv6 21.019 peers

(So: 20 million versus 21 thousand)

IPv6 is growing! ;-)

Teredo IPv6 on Vista: no AAAA resolving by applications ... ?

Can someone please help, or explain? A Windows Vista machine has IPv6 connectivity (using Teredo), it can resolve IPv6/AAAA addresses using nslookup, it can ping literal IPv6 addresses, but ... it can not ping (nor browse) to a IPv6 domain name like ipv6.google.com. See below.

What's causing this? How can I solve this so that a "ping ipv6.google.com" just works?

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.


C:\>nslookup ipv6.google.com
Server:  UnKnown
Address:  192.168.1.254

Non-authoritative answer:
Name:    ipv6.l.google.com
Address:  2001:4860:0:1001::68
Aliases:  ipv6.google.com

C:\>ping ipv6.google.com
Ping request could not find host ipv6.google.com. Please check the name and try again.

C:\>ping 2001:4860:0:1001::68

Pinging 2001:4860:0:1001::68 from 2001:0:d5c7:a2d6:2c9c:d8d7:ad55:e84b with 32 bytes of data:
Reply from 2001:4860:0:1001::68: time=284ms
Reply from 2001:4860:0:1001::68: time=194ms
Reply from 2001:4860:0:1001::68: time=76ms
Reply from 2001:4860:0:1001::68: time=184ms

Ping statistics for 2001:4860:0:1001::68:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 76ms, Maximum = 284ms, Average = 184ms

C:\>

Bus with IPv6 ... ;-)

DynDNS, IPv6, ddclient and dns6.org

Cool: you can store your (static and dynamic) IPv6 addresses on dns6.org. That's easier than typing or even remembering all those hexadecimal bytes.

So create an account on www.dns6.org and create a hostname with your IPv6 address. If you can access the from your IPv6 system, it will fill out your IPv6 address automagically. That's it. It just works.

I'm now playing with ddclient and wget to announce updates of my IPv6 addresses (when working with teredo / miredo).

So far my ddclient.conf looks like this:

sander@flappie:~$ cat /etc/ddclient.conf
# Configuration file for ddclient generated by debconf
#
# /etc/ddclient.conf

pid=/var/run/ddclient.pid
protocol=dyndns2
# use=if, if=
#use=if, if=web
use=web
server=www.dns6.org
login=MyName
password='MyPass'
MyHost.dns6.org
sander@flappie:~$

I'm also trying to do the update with wget:

wget -6 http://www.dns6.org/upd.php?user=MyName&pwd=MyPass&host=MyHost.dns6.org

Results are not yet clear.