5 ms·

There are lots of places that have IPv6-only networks and access IPv4 through NAT64. It makes sense for new company networks that can control what software gets

There are lots of places that have IPv6-only networks and access IPv4 through NAT64. It makes sense for new company networks that can control what software gets installed. The main limitation is software that only supports IPv4. This would affect your proposed solution of doing the translation in the stack. There is no way to fix an IPv4-only software that has 32-bit address field.

iso1631 7mo ago
Yes there is, you have the device the software is on do the translation transparently. The software thinks its talking to 1.2.3.4, it's actually talking to ::ffff:1.2.3.4, but the application doesn't need to know that as the translation is occuring in the network stack (driver, module, whatever). > There are lots of places that have IPv6-only networks and access IPv4 through NAT64 I've just deployed a new mostly internal network, and this was my plan. The network itself worked, but the applications wouldn't. Most required applications could cope, but not all, meaning I need to deploy ipv4, meaning that there's no point in deploying ipv6 as well as ipv4, just increases the maintenance and security for no business benefits.