Description
This article provides an overview of Network Address Translation (NAT) rules and details the differences between NAT support in MCP 1.0 and MCP 2.0.
Content / Solution:
In the context of Cloud, the NAT (Network Address Translation) function will allow you to map a single public IPv4 address on the Internet to a specific private IP address on the Cloud. Once the mapping is established, all inbound and outbound traffic on all ports will flow through the mapped NAT.
There are some minor differences in how the function works between MCP 1.0 and MCP 2.0 that are described below, but the same articles cover how to create and delete such NAT Rules:
- How to Create a NAT Rule on a Network or Network Domain
- How to Delete NAT Rules from a Network or Network Domain
MCP 2.0 Details
In MCP 2.0 locations, the NAT is established on a Cloud Network Domain. In MCP 2.0, you can create both NATs to Public IP addresses and to other "external" IP addresses hat are not associated with an Attached VLAN on the same Network Domain. The latter allows you NAT to external networks connected via a CPNC (Cloud Private Network Connection). Once established, all IP traffic directed to the external IPv4 address will be routed to the internal IPv4 address. In addition, using a NAT may affect the source address from which IP traffic originating from the internal IP address will appear. For more more information on this aspect of behavior in MCP 2.0, see Introduction to Routing, Network Domain Static Routes, and SNAT in MCP 2.0 Locations.
MCP 1.0 Details
In MCP 1.0 locations, the NAT is established on a Cloud Network. You can choose any private IP address with the allowed range (.11 through .254) and the system will assign an available public IPv4 address to it. Users cannot choose the public IP address to be assigned. Once established, all IP traffic directed to the public IPv4 address will be routed to the private IPv4 address. In addition, outbound traffic from a Cloud Server associated with the private IPv4 address will leave the Cloud Network appearing to come from the public IPv4 associated with the NAT. However, traffic directed to other private IPv4 addresses will continue to come from the private IPv4 address. For more information on this aspect of the behavior in MCP 1.0, see How does Outbound Traffic Work on a Cloud Network in a MCP 1.0 location
Related Articles