This is great news, but does anyone have any idea how to get IPv4-over-IPv6 tunnels to work? I'm in an all-IPv6 network, but unless all websites automatically work flawlessly after Jun 6, 2012, I still need to access IPv4 resources.
I have an IPv4/IPv6 dual-stack server which I can access from home via IPv6. I want to setup an IPv4-over-IPv6 tunnel to connect to the server so that all devices in my home network can still operate in a private IPv4 network (for compatibility), and access to public IPv4 network is routed through the IPv4-over-IPv6 tunnel to the dual-stack server.
The only solution that seems feasible right now is DS-Lite, but I couldn't find any helpful tutorial on how to setup it.
Right now I use DNS64/NAT64 on another server to access IPv4-only resources, but this combination doesn't work all the time. For example, Dropbox client doesn't work because (I suspect) it hard-coded the IPv4 addresses of remote servers. DNS64 cannot intercept direct IPv4 addressing so there is no way to translate it into fake IPv6 addresses to be routable via NAT64. In addition, DNS64/NAT64 requires a full /64 subnet on the remote server, which might not always be possible.
What is the general and practical strategy during the transition from IPv4 to IPv6?
Not sure where the OP is getting ipv6 from, but DS-lite is not actually common, because most ISPs are still providing ipv6 as an extra not exclusive, or people are using tunnel brokers. So most do not provide ipv6 only. However if you have a lot of ipv6 machines behind one ip provided and you want to know what to do the OP's question is sensible. The answer alas seems to be to just run your own NAT alongside ipv6. DS-lite is just getting someone else to do your NAT.
I have an IPv4/IPv6 dual-stack server which I can access from home via IPv6. I want to setup an IPv4-over-IPv6 tunnel to connect to the server so that all devices in my home network can still operate in a private IPv4 network (for compatibility), and access to public IPv4 network is routed through the IPv4-over-IPv6 tunnel to the dual-stack server.
The only solution that seems feasible right now is DS-Lite, but I couldn't find any helpful tutorial on how to setup it.
Right now I use DNS64/NAT64 on another server to access IPv4-only resources, but this combination doesn't work all the time. For example, Dropbox client doesn't work because (I suspect) it hard-coded the IPv4 addresses of remote servers. DNS64 cannot intercept direct IPv4 addressing so there is no way to translate it into fake IPv6 addresses to be routable via NAT64. In addition, DNS64/NAT64 requires a full /64 subnet on the remote server, which might not always be possible.
What is the general and practical strategy during the transition from IPv4 to IPv6?
Edited: here is the relavent link on serverfault.com where I posted the original question http://serverfault.com/questions/326132/ipv6-only-client-to-...