mnathani: Oddly enough, I was looking into this only last night. Yes, it is all quite straightforward to enable.
You need two things from a provider side - first, a NAT64 gateway which takes the v6 packets from your client machines addressed to IPs in a special /96 block and turns them into v4 and dumps them onto the v4 internet. I would use openbsd for that, because pf will just do it with the "af-to" option
Second, you need a way for the client device to be able to find the NAT64 gateway. This can be done with DNS64, which is two lines in unbound.conf to enable.
But since DNS64 creates fake AAAA records where there were none before hand, it breaks DNSSEC. Luckily, you don't need a full DNS64 that works on all zones, if the client has a RFC7050 compliant CLAT in it, then you only need to provide faked AAAA records for a single record in ipv4only.arpa
I believe you should be able to do that with a stub zone in unbound, but haven't proved it yet.
As for client side stuff, you need a CLAT. All Android phones running 4.3 or newer have it built in, but iPhones don't yet. For linux you want to install 'clatd'. I'm not sure about Windows clients.
Apparently Windows Phone 8.1 added a built in CLAT. I don't know if that applies to Windows 8.1 on the desktop too.
thanks plett_
https://gist.github.com/anonymous/4cb544bb2b34d7879609
Gist: "pycrypto error"
how would I go about fixing that error?
I tried installing different python-crypto packages
What packages have you tried?
and/or what's the distro?
Also note that the traceback is for Python 3.x, so you'd want python3-cryptol (most likely, since I'm guessing at your distro)
(At least in Debian-land, it's python3-crypto)
Centos 6 is the distro
however I am experiencing a more severe issue now
I did a yum update and reboot
and ever since, I have no network connectivity
service network restart leads to : bringing up interface eth0: error unknown connection: <bunch of hex>
Failed
same for interface eth1: Error: Connection activation failed: the connection is not for this device
when I reboot, I can ping for a few seconds before the connections time out
I suspect its a networkmanager issue
disabled network manager and back after a reboot - that was scary for a bit