New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Ahhh! I'm really sorry @bsh! I though you were advocating for IPv6 NAT, not IPv4 NAT.
Those internal IPs aren't NAT; they're just internal routers. Not all routers need to do NAT... You only need NAT when you have more devices than public IPs. If your server has a public IP (which pretty much all rented servers do), the routers won't be doing NAT, even if they're internal routers.
You should be limiting ports using a firewall, not using NAT. NAT is not a security mechanism.
For HTTP you can use a proxy rather than NAT, but yeah in general I think you're right and you'll use either NAT or a translation technology like 464XLAT to provide outbound IPv4 connectivity to an IPV6-only network.
Agree, and not agree. NAT in general is for translate address, but how we cause it translating is different, inbound or outbound, or both. Routers are devices, as a machine, with OS installed (OpenWRT, *BSD, even Alpine Linux...), with routing rules; doing NAT or not depending on our purposes.
Here, you said NAT in its narrow applying, as I said this network just translating IPv4 from/to outside the IPv6 world. Almost of us, me too, use firewall to control, but there are others to use. And some use cases, firewall could not control IPv6 VMs, then you need a network belonging to the host machine to control.
Instead of having ready resources, you buy or rent a proxy (and proxy is NAT or not?). Returning the OP, I've just proposed many options for her/his beginning of networking. Thank you for your commenting.