Free binary newsserver via Xsnews and IPv6

This is quite incredible: Xsnews offers free access to their binary newsservers over IPv6. I've measured downloads at linespeed (18 Mbps)! It's Xsnews' way to promote IPv6. It works much better than Eweka's and Xs4all's newszilla free IPv6 newsservice.


It's quite easy to get access: fill out your email address on http://www.xsnews.com/ipv6/ipv6_aanvraag.php , and then wait a few minutes for the mail to arrive with all information.
The information will look like

Hostname: reader.ipv6.xsnews.nl
Username: ipv6-12345
Password: aaa12345bb

Fill out that information in SABnzbd (www.sabnzbd.org) and start downloading! This works on Linux and Mac OS X with IPv6 enabled. If you haven't got IPv6 yet, use miredo.
It works automagically on Windows Vista and Windows 7 thanks to the built-in Teredo IPv6. On Windows XP you have to activate Teredo IPv6 yourself.

If you don't use SABnzbd but an other news downloader, you might need the IPv6 address of reader.ipv6.xsnews.nl, which is: 2a02:d28:5580:c::101:5

Happy downloading!

Cool: IPv6 directly connected to "1-wire" sensors

Cool! Someone has used IPv6 to give each "1-wire" sensor it's own IPv6 address and webserver. He has created an IPv6 stack in a microcontroller. Impressive.

See here: http://www.shapeshifter.se/2009/07/10/1-wire-meets-ipv6/

If you don't want to read the full article, here are the URLs for the sensors:


2001:16d8:ffe5:002:2894:eaf6:100:0c7

2001:16d8:ffe5:002:28c1:b4f6:100:035

2001:16d8:ffe5:002:2809:aef6:100:0ca

2001:16d8:ffe5:002:28c5:a5f6:100:058

2001:16d8:ffe5:002:2813:caf6:100:050


PS: you will get some XML code that will show things like temperature.

All the sensor results are presented in  http://www.lindberg.tl/

Transmission 1.80 released with "Improved IPv6 support" ... still no IPv6 webinterface

Bittorrent client Transmission version 1.80 has been released. The release notes (http://trac.transmissionbt.com/wiki/Changes#version-1.80) say "Improved IPv6 support" ... what would that mean? My hope is of course that the webinterface of Transmission is now IPv6-enabled.

Ubuntu Lucid Lynx (alpha 2) has Transmission 1.80, so I've run Lucid to see if the webinterface is indeed IPv6 enabled ...

But alas: the webinterface is not listening on the IPv6 interface. See tests below; first IPv4 (OK), then IPv6 (no connection).

More waiting before we can access Transmission's webinterface over IPv6. :-(





ubuntu@ubuntu:~$ lynx --dump http://192.168.1.36:9091/ | tail -5
  10. http://192.168.1.36:9091/transmission/web/#save
  11. http://192.168.1.36:9091/transmission/web/#cancel
  12. http://192.168.1.36:9091/transmission/web/#upload
  13. http://192.168.1.36:9091/transmission/web/#cancel
  14. about:blank
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$ lynx --dump http://localhost:9091/ | tail -5
  10. http://localhost:9091/transmission/web/#save
  11. http://localhost:9091/transmission/web/#cancel
  12. http://localhost:9091/transmission/web/#upload
  13. http://localhost:9091/transmission/web/#cancel
  14. about:blank
ubuntu@ubuntu:~$


ubuntu@ubuntu:~$ lynx --dump http://ip6-localhost:9091/ | tail -5

Looking up ip6-localhost:9091
Making HTTP connection to ip6-localhost:9091
Alert!: Unable to connect to remote host.

lynx: Can't access startfile http://ip6-localhost:9091/
ubuntu@ubuntu:~$ lynx --dump http://[::1]:9091/ | tail -5

Looking up [::1]:9091
Making HTTP connection to [::1]:9091
Alert!: Unable to connect to remote host.

lynx: Can't access startfile http://[::1]:9091/
ubuntu@ubuntu:~$ lynx --dump http://[2001:0:53aa:64c:8:cf61:ad55:e84b]:9091/ | tail -5

Looking up [2001:0:53aa:64c:8:cf61:ad55:e84b]:9091
Making HTTP connection to [2001:0:53aa:64c:8:cf61:ad55:e84b]:9091
Alert!: Unable to connect to remote host.

lynx: Can't access startfile http://[2001:0:53aa:64c:8:cf61:ad55:e84b]:9091/
ubuntu@ubuntu:~$


ubuntu@ubuntu:~$ lynx --dump http://ipv6.google.com/  | tail -5
  14. http://ipv6.google.com/intl/en/ads/
  15. http://ipv6.google.com/services/
  16. http://ipv6.google.com/intl/en/about.html
  17. http://www.google.nl/
  18. http://ipv6.google.com/intl/en/privacy.html
ubuntu@ubuntu:~$

main Google search page www.google.com on IPv6 too [UPDATE: Selected ISPs only]

UPDATE: Google is indeed on IPv6, but only via ISPs participating in "Google over IPv6". The post below was on a KPN Hotspot, which is connected to Xs4all, which is such a participator.
Pity. Normal users with non-IPv6 ISPs have to wait. :-(


Wow, even the mainstream Google page is on IPv6, too! So not only ipv6.google.com, but also www.google.com and www.google.nl

See below

sander@quirinius:~$ ping6 -c4 www.google.nl
PING www.google.nl(2a00:1450:8001::6a) 56 data bytes
64 bytes from 2a00:1450:8001::6a: icmp_seq=1 ttl=53 time=163 ms
64 bytes from 2a00:1450:8001::6a: icmp_seq=2 ttl=53 time=76.0 ms
64 bytes from 2a00:1450:8001::6a: icmp_seq=3 ttl=53 time=74.3 ms
64 bytes from 2a00:1450:8001::6a: icmp_seq=4 ttl=53 time=79.2 ms

--- www.google.nl ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 74.303/98.374/163.924/37.887 ms
sander@quirinius:~$

Gmail is on IPv6! [UPDATE: Only selected ISPs]

UPDATE: Gmail is indeed on IPv6, but only via ISPs participating in "Google over IPv6". The post below was on a KPN Hotspot, which is connected to Xs4all, which is such a participator.
Pity. Normal users with non-IPv6 ISPs have to wait. :-(

Wow, Gmail is on IPv6! See the output below, and the screendump with IPv6 addres in right lower corner.

Compliments to Google! Google seems to be the only company that *does* IPv6 instead of only *talks* IPv6.



sander@quirinius:~$ host mail.google.com
mail.google.com is an alias for googlemail.l.google.com.
googlemail.l.google.com has address 74.125.77.83
googlemail.l.google.com has address 74.125.77.18
googlemail.l.google.com has address 74.125.77.19
googlemail.l.google.com has IPv6 address 2a00:1450:8005::53
googlemail.l.google.com has IPv6 address 2a00:1450:8005::11
googlemail.l.google.com has IPv6 address 2a00:1450:8005::12
googlemail.l.google.com has IPv6 address 2a00:1450:8005::13
sander@quirinius:~$

sander@quirinius:~$ ping6 -c4 mail.google.com
PING mail.google.com(2a00:1450:8001::11) 56 data bytes
64 bytes from 2a00:1450:8001::11: icmp_seq=1 ttl=53 time=162 ms
64 bytes from 2a00:1450:8001::11: icmp_seq=2 ttl=53 time=80.2 ms
64 bytes from 2a00:1450:8001::11: icmp_seq=3 ttl=53 time=88.8 ms
64 bytes from 2a00:1450:8001::11: icmp_seq=4 ttl=53 time=75.4 ms

--- mail.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3007ms
rtt min/avg/max/mdev = 75.440/101.726/162.418/35.367 ms
sander@quirinius:~$

Bravo Vista! (Sort of)

I'm typing this on a friend's Windows Vista machine. The strange thing: the machine is directly connected to Internet and thus has a public IPv4 address. The interesting thing: IPv6 works ... not based on the Teredo 2001:0: address, but based on the 6to4 2002: address. The IPv6-only website http://ipv6.ip6.me/ shows my 2002: address.

So: Bravo Vista for the IPv6 connectivity.

Oh, wait: the IPv4 & IPv6 website http://www.ipv6.surfnet.nl/ shows my IPv4 address. Vista thus still likes IPv4 more than IPv6 ... :-(



C:\>ipconfig

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection:

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

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::648d:7e53:7b48:57af%8
   IPv4 Address. . . . . . . . . . . : 94.211.128.15
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   Default Gateway . . . . . . . . . : 94.211.128.1

Tunnel adapter Local Area Connection* 6:

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

Tunnel adapter Local Area Connection* 7:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::200:5efe:94.211.28.10%12
   Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 10:

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

Tunnel adapter Local Area Connection* 9:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:73bc:2873:31a3:a12c:e3f5
   Link-local IPv6 Address . . . . . : fe80::2873:31a3:a12c:e3f5%10
   Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 11:

   Connection-specific DNS Suffix  . :
   Temporary IPv6 Address. . . . . . : 2002:5ed3:1c0a::5ed3:1c0a
   Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301

C:\>