NAT Mappings also known as 1-to-1 NAT allows internal hosts, such as web server and mail server etc., behind Peplink Balance to communicate to the Internet via all protocols. With 1-to-1 NAT, you can:
- For inbound traffic, forwarding all TCP/UDP/IP protocols to the host behind the Peplink units.
- For outbound traffic, you can specify a Public IP address which you defined as "Additional Public IP" via WAN Settings as the source IP address.
Configuring 1-to-1 NAT with Peplink Balance Deployed in Drop-in Mode
When there is a firewall placed on the LAN side of the Peplink Balance, the LAN interface and Drop-in WAN interface are bridged together and they will become same subnet. Therefore, NAT Mappings should only apply to the NATed WAN (non-drop-in WAN). In addition, 1-to-1 NAT should be mapped to the IP address which bound on firewall's external interface (eg: 210.10.10.10 in the diagram), and not the internal LAN client (192.168.1.10 in the diagram) itself.
Setting Up 1-to-1 NAT on Peplink Balance:
To setup 1-to-1 NAT on the Web Admin Interface, go to Network > NAT Mappings, click on Add NAT Rule to add a new rule.
Click Save and Apply Changes to activate this new setting.
Configuring 1-to-1 NAT with Peplink Balance Deployed in NAT Mode (Non-drop-in Mode)
Setting up 1-to-1 NAT on Peplink Balance:
To setup 1-to-1 NAT on the Web Admin Interface, go to Network > NAT Mappings, click on Add NAT Rule to add a new rule.
Click Save to save this new setting.
With the new settings, inbound traffic from the selected IP address(es) will be forwarded to the designated server. If more than one server is selected, Peplink Balance will distribute the requests to servers according to their assigned weights.
Outbound traffic from the designated server will carry the selected IP address of the corresponding WAN.