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 network that translates traffic from 2.2.2.2 → 3.3.3.3.
- Peplink BR1 Pro with M2M SIM (2.2.2.2)
- The BR1 receives traffic from the LAN device destined for 3.3.3.3.
- However, the Peplink cannot natively DNAT this traffic directly on the cellular interface.
- Required DNAT Behavior:
- Any packet from the LAN device destined for 3.3.3.3 should first be DNATed to 2.2.2.2 at the BR1.
- Once NATed to 2.2.2.2, the M2M network will forward it using the existing NAT rule to reach the server at 3.3.3.3.
- Workaround from Peplink Support (Dummy WAN):
- Configure a dummy WAN IP for 3.3.3.3 so the router recognizes it as inbound traffic.
- Disable health check so the WAN shows as UP in the IP table.
- Add a NAT Mapping rule: inbound traffic to dummy WAN (3.3.3.3) → forward to 2.2.2.2.
- This allows the BR1 to apply DNAT, but it requires a physical WAN port to be brought up even without Internet access.
Let me know your thoughts and if you have other work around that we can try.