Friday, February 27, 2009

IPv6 via KPN Hotspots

Nice: IPv6 via KPN Hotspots' Wifi AccessPoints works. As you can see, it's good reliable teredo / miredo that does the trick.

I wonder whether KPN Hotspots has plans to provide native IPv6 from their accesspoints. As they provide NAT-less Internet connectivity (see the public IPv4 address, I guess native IPv6 could also be done. Maybe someone with KPN Hotspots experience can comment on this ... ?

rob@rob-laptop:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0b:5d:72:dd:a9 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth1      Link encap:Ethernet  HWaddr 00:0e:35:64:34:06 
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::20e:35ff:fe64:3406/64 Scope:Link
          RX packets:46764 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40477 errors:0 dropped:6 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:62274668 (62.2 MB)  TX bytes:4514641 (4.5 MB)
          Interrupt:11 Base address:0x2000 Memory:d0214000-d0214fff

lo        Link encap:Local Loopback 
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1782 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1782 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1177684 (1.1 MB)  TX bytes:1177684 (1.1 MB)

teredo    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          inet6 addr: fe80::ffff:ffff:ffff/64 Scope:Link
          inet6 addr: 2001:0:53aa:64c:107d:650f:af9a:1e62/32 Scope:Global
          UP POINTOPOINT RUNNING NOARP  MTU:1280  Metric:1
          RX packets:38260 errors:0 dropped:0 overruns:0 frame:0
          TX packets:34479 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:48627476 (48.6 MB)  TX bytes:2284208 (2.2 MB)


Monday, February 23, 2009

Enabling IPv6 support in Avahi (Zeroconf/Bonjour)

Avahi ( is already installed out of the box on all recent Linux distributions, to enable IPv6 for this service make sure the /etc/avahi/avahi-daemon.conf file contains an active "use-ipv6=yes" line.

To enable m(ulticast)dns resolving of IPv6 addresses change the
"hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4"
line to
"hosts: files mdns_minimal [NOTFOUND=return] dns mdns"
in the /etc/nsswitch.conf file

You probably have to restart nscd if used (/etc/init.d/nscd restart or service nscd restart)

Every IPv6 enabled host using Avahi/Zeroconf/Bonjour should now be pingable as hostname.local and visible using the avahi-discover utility

To add the .local domain as standard domain for dns queries you could add a "search local" to resolv.conf and the host is now pingable as just hostname.

Another useful option for users with a mixed Linux/Microsoft environment is to enable Microsoft hostname resolving by changing the line in /etc/nsswitch.conf to
"hosts: files mdns_minimal [NOTFOUND=return] dns mdns wins", just make sure to install winbind on the Linux host.

AVM partners with Freenet to make Fritz!Box IPv6 enabled'

The good news: AVM is going to provide firmware for their Fritx!Box 7270 that does IPv6. The bad news: the IPv6 is going to be based on 6to4 (with the 2002: addresses), which is horribly unreliable: your 6to4 IPv6 traffic will be handled by unspecified gateways around the world.

From the page 'AVM partners with Freenet to make Fritz!Box IPv6 enabled':

'AVM partners with Freenet to make Fritz!Box IPv6 enabled'

German broadband end-user equipment developer AVM, partnering with the technical department of the German ISP Freenet, has made its DSL modem line Fritz!Box compatible with the IPv6 Internet protocol. IPv6 will also be available for standard DSL connectivity in the future. To achieve this, AVM will use the 6to4 tunnelling technique to allow transport of IPv6 traffic using IPv4 addresses. AVM is placing a premium on transparency in implementation and has incorporated extensive technical documentation (RFC) for IPv6 to this end. AVM will make firmware with IPv6 available for downloading for its frontrunner model, the Fritz!Box Fon WLAN 7270 during this year's CeBIT.

But it is a first IPv6 step, of course coming from technology driven Germany. ;-)

Friday, February 20, 2009

Easy steps for IPv6 enabled Transmission 1.50 on Ubuntu

The Ubuntu repositories stilll have got an older (< 1.50) version of Transmission bittorrent client. I am even not sure which version Jaunty has or will have.

So, to get Transmission 1.50 with IPv6, you'll need to do something else: go to and select the Ubuntu version you've got. Then download &  install the two files. I believe you have to start with the "common" file.

If downloading&installing does not work, download the two files, and the install them by hand like this:

sudo dpkg -i transmission-common_1.50-1~getdeb1_all.deb
sudo dpkg -i transmission-gtk_1.50-1~getdeb1_i386.deb

After that, transmission will do IPv6. That is: *if* you have IPv6 enabled on your Linux or MacOSX.


Thursday, February 19, 2009

Linux Mint ... Anti IPv6?

Yesterday I installed Linux Mint. It's Ubuntu based, and thus good, and hopefully even a little bit better.

Anyway: conclusion on Linux Mint so far: nice looks, but Linux Mint is oh-so anti-IPv6:

  1. ipv6 is blacklisted in /etc/modprobe.d/blacklist
  2. ipv6 name resolution in Firefox is disabled via network.dns.disableIPv6
  3. after installing miredo, miredo does not autostart after a boot
I could solve 1 and 2, but so far not 3. Tips welcome.

Monday, February 16, 2009

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) client.

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

Saturday, February 7, 2009

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:

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:


Friday, February 6, 2009

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, 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 are approached via IPv6.

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

C:\>netsh interface ipv6 install

C:\>netsh interface ipv6 set teredo client


Windows IP Configuration

Ethernet adapter Local Area Connection:

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

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:
        Default Gateway . . . . . . . . . :


Pinging [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


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 itself:

IPv4 20.400.519 peers
IPv6 21.019 peers

(So: 20 million versus 21 thousand)

IPv6 is growing! ;-)

Wednesday, February 4, 2009

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 See below.

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

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

Server:  UnKnown

Non-authoritative answer:
Address:  2001:4860:0:1001::68

Ping request could not find host 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


Sunday, February 1, 2009

DynDNS, IPv6, ddclient and

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

So create an account on 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

# use=if, if=
#use=if, if=web

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

Results are not yet clear.