ollowed all of the recipes so far in this book, you have a network that logically looks similar to the following diagram: Hyper-V Hosts Provider Network Tenant B VM1 Tenant B VM1 Tenant A VM1 Tenant A Tenant B Provider Network Live Migration Cluster Management Storage SMB3/FC/FCoE/oSCSI Highly Available Virtual Machine Manager Chapter 3 Adding a HNV gateway to this will allow the VMs within the currently declared VM Networks to communicate outside their VM Network. Within Windows Server 2012 R2, there are two possible implementations of the gateway: Network Address Translation (NAT): This is the traditional edge device implementation that allows VMs on the VM Networks to have Internet access and for inbound NAT translation rules. A NAT-based gateway can handle up to 50 VM Networks by default. Direct Routing: This acts in a traditional router sense connecting networks together; no form of NAT is performed when this implementation is used and the Tenant IP address is used for all communication. For Direct Routing, a dedicated gateway is required per VM Network. For the purpose of this chapter, NAT-based gateways are going to be deployed. Creating a Logical Network, Port Profiles, and Logical Switches for external access All the Logical Networks that have been defined so far are internal networks and the VMs have no external access. This recipe will show you how to create a Logical Network such that HNV gateways can have external access. The logical structure of the gateway is shown in the following diagram: Internet Firewall NVGRE Virtual Device Gateway Machines Using HNV gateways behind NAT devices can lead to difficulties in connecting to VPNs. It is advised in a production environment to ensure that gateways are not behind NAT devices. Getting ready As the gateway will be behind a NAT device, you will need to ensure that the NAT device is not issuing DHCP-based IP addresses. You will need to know the IP range of the NAT device. In the following recipes, the IP ranges will be as follows: Subnet: 192.168.200.0/24 