Specific NAT IP based on the destination IP

[bit.gao]

Hi Support,
Current Test Status The Peplink device is currently configured with a single WAN connection. The client’s requirement is to designate a specific NAT IP based on the destination IP, as illustrated in the attached diagram.

The setup should meet the following conditions:

• Regardless of the source IP, traffic destined for Site A should be NAT-ed to 1.1.1.3.
• Similarly, traffic destined for Site B should be NAT-ed to 1.1.1.2.

Is it possible to configure the Peplink to handle the scenario described above?

[WillJones]

I’m not aware of a clean way to implement this on Peplink, there is a workaround mentioned here but it is not ideal, Peplink allows us to configure the outbound NAT mappings based on source IP, but not based on destination IP at the moment.

DNAT Feature for Peplink Products

[DNAT Feature] Hi Team, thank you for your response. Im attaching a diagram that may help to understand the requirement and below is an explanation on what we are trying to achieve. Scenario Explanation: LAN Device (1.1.1.1) This is a laptop/PC connected to the LAN side of the BR1 Pro. It needs to communicate with the FH2 Server (3.3.3.3). Target Server (3.3.3.3) The FH2 server is reachable only through the M2M network (2.2.2.2). There is already an existing NAT rule in the remote net…

Probably will need to see if Peplink add some feature enhancement for this to be done in a nice way, for me that would be done either by adding to the existing NAT mapping config options so they can be based on destination and/or source or add a NAT config option to outbound policy to allow us to override the source IP used to be a secondary IP on the WAN the traffic is routed out of.