IPv6 is the next generation of the Internet Protocol. It is intended to completely replace what is now called IPv4, which is the current version of the Internet Protocol which you will be familiar with.
A major reason for the existence of a new Internet protocol is the impending exhaustion of globally unique IPv4 addresses. Recently the lifetime of IPv4 has been extended through use of network address translation (NAT), and classless inter-domain routing (CIDR - a method of allocating smaller subnets to organisations than the original classful networks). NAT allows systems without a globally unique address to access the Internet, but causes significant problems for any peer-to-peer applications such as SIP since it effectively turns the Internet into a client-server, rather than peer-to-peer architecture.
IPv6 solves this problem fairly comprehensively by quadrupling the length of IP addresses from 32 bits (in IPv4) to 128 bits. This gives 3.4x1038 addresses, an extremely huge number indeed. To give you an idea of just how many addresses this is, it allows for approximately 6.67x1017 addresses per square millimetre, or the equivalent of an IPv6 /48 netblock (2.8x1014 more addresses than all the IPv4 addresses in existence) per 100 square metres, of the Earth's surface.
IPv6 also offers other significant improvements over IPv4 such as built in IPSEC VPN support, automatic configuration (plug and play) and improved multicast capabilities.
What IPv6 looks like
The currently ubiquitous dotted-decimal notation for IPv4 addresses is rather awkward when dealing with addresses at a bit level, not to mention being long winded. In dotted decimal notation the IPv6 address of www.kame.net would be 188.8.131.52.0.0.128.2.184.108.40.206.254.165.48.133. In standard IPv6 notation it is:
The leading zeros in any group can be eliminated, thus giving:
In addition, any one series of groups containing only 0 can be omitted:
Note that this can only be done for one group, since it might otherwise represent either of two numbers.
Who can use IPv6?
Whilest the preferred method of using IPv6 is via a native IPv6 network, this is usually not possible since most ISPs don't provide IPv6 connectivity. However, anyone with a global scope IPv4 address and participate in the IPv6 network by using the 6to4 mechanism so long as they don't have to go through a firewall which blocks IPv4 protocol 41 (6-in-4).
This is very easy to set up on most modern systems. For example, under Fedora Core you simply need to edit /etc/sysconfig/network and add:
Please note that if you're using your Linux system as a firewall you will also need to apply firewall rules to the IPv6 network by using ip6tables and if you're routing traffic through the box you'll want to turn on IPv6 forwarding and fiddle with the radvd router advertisement daemon
Setting up IPv6 on Linux
If you already have a globally unique IPv4 address, you can use this to access the IPv6 internet using a scheme called 6to4. This involves IPv6 packets being encapsulated within IPv4 packets and forwarded to an IPv6 aware router. You do need an IPv6 aware router to do this; however, you do not need to know its IP address or who it belongs to, as you can get the packets automagically forwarded to the nearest 6to4 gateway using a special anycast address.
First, you need to generate a 6to4 address for your subnet. To find out your current IP address, type:
ip addr show
Suppose your IPv4 address is 220.127.116.11. If this is globally unique (generally it will be if it isn't in one of the ranges reserved for private networks defined in RFC 1918), you can turn this into a globally unique IPv6 address by simply putting it in IPv6 hexadecimal notation with the prefix 2002::/16, so your Internet-facing address might be 2002:102:304::1. (In fact, 2002:102:304::/48 is your very own subnet which has 28 times more addresses than exist in the whole IPv4 address space. If you own a router that has a globally unique IPv4 address you can theoretically set up its DHCP server to hand out globally unique addresses with this prefix to all the hosts it supports.)
Here is a command you can use to calculate this address, given an IPv4 address of 18.104.22.168:
printf "2002:%02x%02x:%02x%02x::1" `echo 22.214.171.124 | tr "." " "`
Now you know your IPv6 address, you need to create a 6to4 tunneling pseudodevice. This can be done as root with the
ip command like so:
ip tunnel add tun6to4 mode sit ttl 30 remote any local 126.96.36.199
Note that the 'local' address at the end is your IPv4 address. (Side note: ttl is the default Time To Live header for outgoing packets, meaning the maximum number of routers packets are allowed to go through before they get dropped (this is used just as in IPv4, to stop packets going round in circles if they hit a routing loop). 30 should be plenty. In fact, at this point in time you will often be able to get a connection to another IPv6 host over just one hop, with all of the routers in between using IPv4 and therefore not decrementing the TTL - but just in case, and because this will (hopefully!) not be the case in future, 30 is a good default.)
Now bring this tunnel up (don't worry that you can't use it yet):
ip link set dev tun6to4 up
Now you need to assign a 6to4 address to the tunnel. This is the address with the prefix 2002::/16 which you worked out earlier.
ip -6 addr add 2002:102:304::1/16 dev tun6to4
The /16 is important, as it indicates that the 2002 is the 6to4 prefix and not just some arbitrary address. You will still not be able to connect yet, as the network stack doesn't know where to send packets. So you need to set up a default route for Internet traffic. Here is the magic bit. With IPv4 you usually find out the address of your default gateway from DHCP (and in fact you can still do this with IPv6). With 6to4, you can have your upstream router handle IPv6 natively (pretty rare at this point in time), or know the IPv4 address of a 6to4 gateway (which might not be possible or convenient). Or you can send packets out through the IPv4 internet looking for any 6to4 gateway using a special destination address called anycast. This address is 188.8.131.52. Here is how you set it up:
ip -6 route add 2000::/3 via ::184.108.40.206 dev tun6to4 metric 1
Here the 'metric' argument of 1 indicates that the network stack should prefer to use this route if it can.
Now you should be set up and able to access the IPv6 internet. Try a ping:
If you see responses, you can access the v6 internet. You should also try looking at the Kame project website - if you see a dancing turtle at the top, your web browser is using IPv6!