Your handy IPv6 checklist

Face it -- IPv6 is about to come into its own in a very big way. Get ready before you're blindsided

1 2 Page 2
Page 2 of 2

The IPv6 checklist

If you want to get started with IPv6, you'll first need an operating system that supports the protocol. Fortunately, you have one. I can almost categorically say so because every Microsoft OS since Windows 2000, Linux kernel since 2.1.8 (1998), and Apple OS X since 10.3 (2005) has had at least some form of support for IPv6. Newer operating systems even have it enabled by default, so it's probably turned on. Oddly enough, if you're reading this on a smartphone with 4G service, there's a pretty good chance you're using IPv6 right now.

Next you'll need an Internet connection that supports delivery of IPv6. This part is a bit trickier. Most subscriber Internet connections don't yet support native IPv6, but that is starting to change (welcome to IPv6, Littleton Colorado!). Many tier 1 and tier 2 ISPs that might be delivering bandwidth to your corporate network will also deliver IPv6 if you ask for it, but chances are you haven't yet. That's OK -- for our purposes, there's an easier way that won't require calling your ISP, replacing your cable modem (or your whole cable company), upgrading your firewall firmware, or hacking around in the configuration of your core router.

That easy way is through the use of an IPv6 tunnel. There are a multitude of different transitional technologies that exist to allow backward and, in a sense, forward compatibility between IPv6 and IPv4. To be precise, there is no real forward compatibility from IPv4 to IPv6 -- a device attached to an IPv4 network that is only running an IPv4 networking stack cannot interact with an IPv6 network at all (though there are tunneling technologies that will allow IPv4 networks to reach each other through an IPv6 network).

However, since almost every device you're likely to come across does have an IPv6 networking stack, you can run both IPv4 and IPv6 at the same time; this is usually referred to as a hybridized or dual-stack configuration. If the network you're attached to isn't already configured to handle IPv6 traffic (including routers, firewalls, and so on), you'll need to build an IPv6 tunnel from your machine through the IPv4 Internet to somewhere else that can act as a gateway onto the IPv6 Internet.

You can use a number of free services to do this, but I'd recommend you try out Hurricane Electric's free IPv6 tunneling service. It's easy to sign up, and between Hurricane Electric's FAQ and video tutorials, you shouldn't have any trouble getting it to run on your own workstation or even on your router or firewall if it supports 6to4 tunnels. One large caveat is that your firewall must support NATing protocol 41 to use Hurricane's service -- some older models do not. In those cases, you'll probably have to use a different service that supports "Teredo" UDP-based IPv6 tunneling.

Once you're rolling along, you can run IPv6 traceroutes to get a feel for how it works and test it by hitting IPv6-only sites. If you're a network admin with access to network hardware (or software) that can run BGP, as well as your own ASN, Hurricane Electric will allow you to advertise your organization's IPv6 prefixes via their tunnel -- also for free. This service can be more than just a testing and educational tool.

Now you're ready for World IPv6 day

If you get a chance to set up your network before June 8, 2011, you'll have a front-row seat for World IPv6 Day. On that day, a raft of major Internet organizations will turn on dual-stack IPv4/IPv6 connectivity on their front-line services in an effort to gauge the true penetration of IPv6 implementations and to help the Internet at large kick IPv6's tires in production. Until then, I'll be using Google at 2001:4860:800f::63. See you there!

This article, "Your handy IPv6 checklist," originally appeared at Read more of Matt Prigge's Information Overload blog and follow the latest developments in storage at For the latest business technology news, follow on Twitter.

Copyright © 2011 IDG Communications, Inc.

1 2 Page 2
Page 2 of 2
How to choose a low-code development platform