Hi, I'm Iljitsch van Beijnum. These are all posts about IPv6.
Your current connection to the web server is over IPv4, using address 3.145.103.169. Checking your IPv6 address (this requires javascript)...
Today, the four biggest websites (and 3,000 smaller ones) again enabled IPv6.
Permalink - posted 2012-06-06
The new Internet is upon us. Apple has work to do but there's no reason to fear.
Permalink - posted 2012-05-21
I sometimes get the question whether my book "Running IPv6" is still current. Since publication in 2005, not much has changed with regard to the core IPv6 protocols. I may go over what's new in this regard at some point in the future. However, what has changed significantly are the operating systems and other software mentioned in the book. The main things to be aware of are:
Windows:
In Windows XP, IPv6 is a protocol separate from IPv4 that must be installed explicitly. In Windows Vista and Windows 7, IPv6 support is integrated with IPv4 and enabled by default. Vista/7 use something other than the system's MAC address as the interface identifier in link local addresses and stateless autoconfiguration. Unlike XP, Windows Vista and Windows 7 support DHCPv6 for both address configuration and to learn DNS resolver addresses.
MacOS:
In MacOS 10.7 Apple enabled privacy addresses with stateless autoconfig by default and added DHCPv6 support for address configuration and to learn DNS resolver addresses. Also, the system tries looks at the round trip time towards a destination over IPv6 and IPv4, and will use the protocol that has the lowest RTT. So MacOS 10.7 will often connect over IPv4 to destinations that have both IPv4 and IPv6 in the DNS. This makes things harder to debug, but the upside is that it avoids timeouts with broken IPv6 setups. As of 10.6.5 MacOS will prefer IPv4 over IPv6 if it has 6to4 connectivity.
iOS:
The iPhone, iPod touch and iPad didn't exist yet in 2005. IPv6 support was added for these devices in iOS 4 and is relatively mature in iOS 5, with stateless autoconfig and privacy addresses as well as DHCPv6 support. It looks like iOS 5 also uses the RTT-based IPv4/IPv6 selection mechanism present in MacOS 10.7.
DHCP:
The DHCP software mentioned in the book is quite bad. A much better option is the ISC dhcpd, which now also supports IPv6.
Permalink - posted 2012-02-20
The File Transfer Protocol (FTP) has a very long history, and despite the fact that today other options exist to perform file transfers, FTP is still in common use. As such, in situations where some client computers only have IPv6 connectivity while many servers are still IPv4-only and IPv6-to-IPv4 translators are used to bridge that gap, it is important that FTP is made to work through these translators to the best possible extent.
Permalink - posted 2011-11-05
This document describes stateful NAT64 translation, which allows IPv6-only clients to contact IPv4 servers using unicast UDP, TCP, or ICMP. One or more public IPv4 addresses assigned to a NAT64 translator are shared among several IPv6-only clients. When stateful NAT64 is used in conjunction with DNS64, no changes are usually required in the IPv6 client or the IPv4 server.
Permalink - posted 2011-04-27
DNS64 is a mechanism for synthesizing AAAA records from A records. DNS64 is used with an IPv6/IPv4 translator to enable client-server communication between an IPv6-only client and an IPv4-only server, without requiring any changes to either the IPv6 or the IPv4 node, for the class of applications that work through NATs. This document specifies DNS64, and provides suggestions on how it should be deployed in conjunction with IPv6/IPv4 translators.
Permalink - posted 2011-04-27