Firstly for those wondering about Courier-IMAP / authlib / maildrop+authlib packages for Leonidas: I’ve built them successfully – only a minor adjustment needed after all that – and it’s available in the usual place. Enjoy, and let me know if there’s any bugs / issues.
(For a change I managed to get them out the door before someone emailed me asking where they were. Miracles happen! :-P)
I was quite surprised – and pleased – to check my website stats and find that my most frequent visitor is an IPv6 address:
(If only the GeoIP database had an idea about IPv6 netblock ownership…)
A good friend of mine is a network administrator for a fair size network – two AS’ under his control and a network covering the Australian eastern seaboard. He’s often tasked with finding additional IPv4 address space
Because IPv4 addressing is becoming scarce the registrars in many locales (APNIC in his and my case) set a high bar for new allocations to network service providers (must use 80% of existing allocation, justify new allocations for a max of a /22 last I heard) – and rightfully so. They’re not toffees and they are indeed becoming quite scarce, moreso with increasing takeup of internet-enabled mobile devices and broader broadband availability.
Yes, there are other options such as NAT (Network Address Translation) and name-based virtual hosting to mitigate many issues – but not all applications play nice behind NAT, Voice apps and some games being good examples – and port forwarding isn’t simple for the novice user.
IPv6, step up to the plate! Support in Linux has been around for aeons and it’s rock solid. If you’re already IPv6-enabled, you’re likely talking to me over it now. It’s even on by default with “link-local” fe80:: class addressing ubiquitous on new installs (even if there’s a lot of frankly ordinary advice on turning it off!)
For Fedora, there’s a number of options for public IPv6 – the documents for the “initscripts” package show the basics of IPv6 quasi-native tunnelling and “6to4” tunnelling and are a good starting point
The latter is easier and a good option if you don’t have a nearby tunnel broker / point of presence like SiXXS, Hurricane Electric or a provider offering a Hexago-like service.
(Australia is a good example – the AARNet educational network offers such a service, as does Internode for it’s customers; Telstra may still do so but that’s it, with Hurricane Electric a higher-latency option down here. Other points of presence are just too distant to be useful)
Wolfgang Rupprecht has a Fedora-specific howto, which applies just as well for F11 or even RHEL/CentOS.
The aiccu package is in the Everything repository if you’re eyeing off a SiXXS tunnel connection.
The “go6” client from Hexago is another that hasn’t been packaged yet (to my knowledge and while I use it due to my provider’s use of their broker software I’m not really a fan)
HE.NET (Hurricane Electric) lets you use the standard tools, no extra apps needed (bless ’em!)
The simplest method? 6to4. It’s not as fast as full tunnelling or “native” direct IPv6, but it will get you “on the road” so to speak. Unfortunately NetworkManager currently gets in the way, going from my testing, but on a headless gateway not using NM it works a charm:
- Make sure IPv6 is on in your network config: (NETWORKING_IPV6=”yes” in /etc/sysconfig/network)
- Tell the network the default IPv6 interface to use (set “IPV6_DEFAULTDEV=tun6to4” in the above file)
- Add the following lines to your network interface:
- That’s about it – restart the network service and you should be rollin’.
It will use anycast to 188.8.131.52 (default anycast prefix host for 6to4) to find the nearest 6to4 broker and use it as the endpoint. Test by going to a site like www.kame.net (if you see an animated turtle, it’s working) and enjoy.
I’m moving servers next week (a Xen VPS with a fatter pipe) and rest assured it will be IPv6-aware!
[mfleming@qbert ~]$ host -t AAAA www.thatfleminggent.com www.thatfleminggent.com has IPv6 address 2001:44b8:62:1b0::1