mupuf.org // we are octopimupuf.org

MùPùF.org Is Now Accessible in IPv6. How to Make Your Sever Accessible Too?

Posted by Martin Roukala, né Peres on , In categories mupuf.org .

As of today, mupuf.org should be accessible in IPv6.

How can I access mupuf.org with IPv6?

Please first take the IPv6 test.

Then, just to make sure your dns is ok, run:

$ host mupuf.org
mupuf.org has address 94.23.53.120
mupuf.org has IPv6 address 2001:41d0:2:3678::
mupuf.org mail is handled by 1 redirect.ovh.net.

Now, to really make sure it works, run nmap:

$ nmap -6 -p 80 mupuf.org

Starting Nmap 5.21 ( http://nmap.org ) at 2011-01-15 23:32 CET
Nmap scan report for 2001:41d0:2:3678::
Host is up (0.060s latency).
PORT   STATE SERVICE
80/tcp open  http

If all the above steps succeed, then congratulations, your ISP and OS are IPv6-Ready!
Please report any bug/slow down you may experience.

How to configure my server to be accessible in IPv6?

Is the OS compatible ?

First, you need to make sure Linux has been compiled with ipv6 support. As proposed in this tutorial, you can test that by running this command:

$ test -f /proc/net/if_inet6 && echo "Running kernel is IPv6 ready"

You may also need to load the ipv6 module:

# modprobe ipv6

As we are using OVH’s hardened kernels for mupuf.org, we had to change the netboot to boot with IPv6 support.

Set your IPv6 address

You can set your IPv6 address by running this command:

# ifconfig eth0 inet6 add adr/lg_prefix

In my case, I ran:

# ifconfig eth0 inet6 add 2001:41D0:2:3678::/64

You can now test the OS is ready to be accessed in IPv6 by running this from your computer:

# ping6 adr/lg_prefix

Configure the DNS

You should already be familiar with the DNS’s A-records. A records simply boil down to associate a domain name with an IPv4 address.

What we want is to also associate the domain name to an IPv6 address. Well, we’re lucky, this is super easy! Instead of using an A record, use an AAAA record. See this little tutorial for more details.

Configure your services

I won’t be able to help you a lot on this. Just make sure the services aren’t bound the IPv4, make them listen on every IP.

You may also have to explicitly allow your applications to bind on IPv6 addresses too. In Cherokee, it was just a matter clicking the right checkbox in the general administration panel or modifying /etc/cherokee/cherokee.conf by changing the line

server!ipv6 = 0

to

server!ipv6 = 1

Tests

Remember to test all the hosted services and see if all of them work as they are supposed to.

Conclusion

Congratulations, your server and its hosted services are now IPv6-ready!

Comments