4 ms·
Do you mean NAT46? NAT64 is for IPv6 clients to access IPv4 servers, no? And how would you assign, e.g., port 80 to more than one IPv6 IPs in the backend? The
by lxgr 3y ago
Do you mean NAT46? NAT64 is for IPv6 clients to access IPv4 servers, no? And how would you assign, e.g., port 80 to more than one IPv6 IPs in the backend?
The other option are application-level proxies/load balancers etc., but that's not easy if you want to support all possible protocols.
- wmf 3y agoThe "official" solution is SIIT-DC but it looks like AWS would prefer that you use ALBs.
- lxgr 3y agoTIL about SIIT-DC, thank you. This still requires mapping tables similar to explicit port forwarding, and also does not help with e.g. a scenario where all hosts need a specific port (e.g. 443) to be v4 reachable, right?
- ianburrell 3y agoI'm talking about IPv6-only instances needing to access IPv4. Github is the big example. Network load balancers (NLB) are for other protocols.
- lxgr 3y agoSure, but NAT64 is much easier than NAT46 or application-level load balancing. It’s probably been how most people in the world access the internet for a while, to say nothing about NAT44.