Since a few days I have a working IPv6 setup from Hetzner (native ipv6!). It took a bit of playing around with the gateway since that is in a different subnet then the range you get is, but you can get around that pretty well.
All my services (web/mail etc) had been dual-stacked to IPv4 and IPv6. That not only goes for *evilcoder.org, but also for a broad range of different hosts that I am running. Since it’s a great way to give every host it’s own IP, I also made a few more vhosts then I previously had.
And ofcourse JR-Hosting had also been adopted to run on IPv6, there all customers will gain their own IPv6 IP address, next to their current IPv4 address.
Whoehoe!
English 
Nederlands
Can you please provide the additional lines in rc.conf for your hetzner-v6-setup?
Hello,
Yes that would be possible, but do note that I am using a non-documented / supported setup. I have no idea what would happen if it is not a good thing to do and might cause harm.
I have placed my main ip in the router subnet itself, and created routing with that. FreeBSD cannot find the gateway otherwise, on Linux this seems to work but I couldn’t find a way to do it differently. So in the light of their ‘master IP and assigned routed subnet’ I did the same for IPv6:
ipv6_enable=”YES”
ipv6_ifconfig_em0=”2a01:4f8:xx:xxxx::2/59″
ipv6_defaultrouter=”2a01:4f8:xx:xxxx::1″
ipv6_ifconfig_em0_alias0=”2a01:4f8:xx:xxxY::2/64″
and a range of additional IP’s in that regard. Notice that the last alias pasted has an Y on the end, stating that this is from my assigned subnet, where the xxxx network is the router’s network.
Hope this helps and doesnt break anything
Great post ! – Thanks!
Just one note – Where did you get this information – I’m having some issues with the gateway etc, and cant update my interfaces file on ubuntu, so I’m unable to do anything with them.
Do you know if it is posible to do any NAT of the ipv6 pool ?
Hi Henrik,
The information is available from the Robot and the wiki from Hetzner. They have a weird IPv6 setup though, which is a bit weird because normally you have the router in the same subnet, and that’s not the case here.