Hello,
The NAT VM Switch type was originally created to connect Windows Containers to a private IP network while also allowing for network and port address translation (NAT and PAT). However, since the VM Switch operates at Layer 2 in the networking stack and NAT/PAT
operates at Layers 3 and 4 in the network stack, this created a layering violation.
We support two options for creating NAT networks on a host.
1) If you are using containers and wanting to connect your containers to a private IP network via NAT, you can either use the docker network create command or New-ContainerNetwork as documented here: https://msdn.microsoft.com/en-us/virtualization/windowscontainers/management/container_networking
2) If instead you simply want to connect VMs to a NAT network, the documentation to do so is available here: https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/user_guide/setup_nat_network?branch=scooley-client-nat
Hope this helps!
We are thinking long-term about how we will unify our NAT story across the host for both containers and VMs.
