Recently in the ipv6 Category

IPV6 migration part 8

DNS for IPV6 is just like IPV4, but longer. In part 2 I discussed DNS quad A records. Now I'll explain IPV6 PTR records.

IPV6 migration part 7

I've broken up with SixXS. Hurricane Electric is my new girl.

IPV6 migration part 6

Liberation! Using IPV6, I have 18,446,744,073,709,551,616 public IP addresses. This is considered a small offering (/64). Normally, an organization would get a /48 network that contains 65536 /64 subnets.

Previously my local IPV6 setup was limited to just my workstation. It initiated the 6in4 tunnel to my IPV6 tunnel broker, Sixxs. Recently this tunnel malfunctioned. I think it was due to it passing through a NAT IPV4 router. I did not discover the problem but, I did move on the next stage. Now my router handles the tunnel and my workstation has a static IPV6 address from the /64 block provided by Sixxs.

My router is an Alix system running Linux. Moving the tunnel from my workstation to the router was quite simple. Note, that in part 1 I was using a static tunnel. With IPV4 addresses in short supply, and poor ISP quality in Canada, I had to move to a dynamic IP address setup. Sixxs provides a daemon called Aiccu to tunnel through dynamic IPV4 setups. Debian has the Aiccu package. With simple apt-get install you are ready to configure your tunnel. The configuration file is /etc/aiccu.conf. Set a username, password, protocol, and server in the file. All of these are provided by Sixxs. The rest of the file can be left at the defaults.


My router has two interfaces. One faces the Internet and the other faces my internal network. The 6in4 tunnel provides an IPV6 address to the external interface. It is not part of the IPV6 subnet provided to me. That subnet is attached to the inside interface. In those simple steps you have your first IPV6 subnet. If you work with IPV4 then this looks familiar. At this level IPV4 and IPV6 work the same way. Don't let the IPV6 address syntax scare you. Just remember that IPV6 requires its own firewall. In Linux that is ip6tables.

IPV6 migration part 5

My email server now functions on both IPV4 and IPV6 networks. Postfix is IPV6 ready but, the configuration needed some adjustments.

In places like mynetworks, found in, IPV6 addresses must be enclosed in square brackets. This does not include the netmask. For example: [::1]/128

In Postfix is told to use IPV6 using inet_protocols. Set this to all and Postfix will listen to IPV4 and IPV6 interfaces.

For more information about Postfix and IPV6 the Postfix web page

In fact a lot of configuration files have special rules to accommodate IPV6 addresses because IPV6 syntax was not a consideration when the configuration syntax was first invented. Read configuration documentation carefully.

IPV6 migration part 4

This website is now dual stacked to both IPV4 and IPV6. In part four of my IPV6 series I'll tell you what I learned during this migration.

IPV6 migration part 3

We continue in this series by having a quick look at a dual stack VPS host.

IPV6 migration part 2

In this part of the series we will learn how to make a service run on an IPV6 address.

IPV6 migration part 1

The first step in my exploration of IPV6 was to get an IPV6 address via an IPV4 to IPV6 tunnel. A little research lead me to the fine folks at SixXS.

Learn IPV6 migration

In the coming weeks or months I will be posting my experiences testing IPV6 and hopefully migrating to IPV6 Internet services, including this website. I hope you will return here and learn from my experiences.