PEPLINK HANDBOOK

Port Forwarding Not Working on a Peplink Router? Here's How to Fix It

Most port forwarding failures on Peplink and Pepwave routers come down to one of a small number of causes: the wrong WAN mode, a conflicting firewall rule, or traffic that never reaches the router's public IP in the first place.

QUICK ANSWER

Confirm the WAN is set to NAT mode rather than IP Forwarding or Drop-in, check that no inbound firewall rule is blocking the port, and test from outside your own network using the router's actual current public IP.

Method 1: Confirm the port forward rule itself

Steps

  1. Go to Network > Port Forwarding (sometimes labelled NAT Mappings, depending on firmware).
  2. Check the protocol is correct: TCP, UDP, or both, matching what the service actually needs.
  3. Check the external port and the internal LAN IP and port are correct.
  4. Confirm the target device has a static or reserved LAN IP, so the forward does not silently break after a lease renewal.

Method 2: Check the WAN mode

Under Network > WAN, confirm the connection is set to NAT rather than IP Forwarding or Drop-in mode. In NAT mode, the router opens the necessary inbound state automatically once a port forward is created, so you do not need a separate firewall rule for it. In IP Forwarding mode, all inbound WAN traffic passes through by default, so a missing forward usually is not the issue: an upstream firewall or the target device's own firewall is the more likely cause.

Method 3: Check inbound firewall rules

Port forwards handle their own firewall state automatically. If the default inbound rules have been changed from allow any, add an explicit rule permitting WAN to LAN traffic on the forwarded port, and check the order of rules, since a broader deny rule placed above a more specific allow rule can still block the traffic.

Three different features

Port forwarding, inbound firewall rules and NAT mappings interact but are not the same thing. A port forward opens one specific port. Inbound firewall rules control broader WAN to LAN access. A NAT mapping exposes an entire LAN device on a secondary public IP. Confusing the three is one of the most common causes of "it should be working but isn't."

Method 4: Test from outside your own network

Testing from a device on the same LAN, or from behind the same public IP, often does not reflect what an external user actually sees, due to how NAT loopback behaves. Test instead from a phone on mobile data, or an external port-checking tool, against the router's current public IP shown under Status > Device.

Method 5: Check what happens on WAN failover

If the router has more than one WAN and Outbound Policy is set to load balance or fail over between them, a port forward is only reachable on whichever WAN currently holds the public IP it was configured against. If forwarding "used to work" and has stopped, confirm which WAN is currently active before assuming the forward itself is broken. Our WAN failover guide covers how failover is configured.

Common questions

Do I need a firewall rule as well as a port forward?
Usually not for the specific port itself, since a port forward opens its own inbound firewall state automatically. You only need an extra rule if the default inbound rules have been tightened from allow any.
Why does it work from inside my network but not from outside?
This is usually down to NAT loopback (also called hairpin NAT) rather than a genuine forwarding fault. Test from an external network or device to get an accurate result.
I have a dynamic public IP, will that break my port forward?
No, the forwarding rule itself is not tied to the IP value. External users do need your current public IP, or a dynamic DNS hostname pointing at it, to reach the service.
PEPLINK HANDBOOK

Still not getting through after working down this list? Our engineering team can check your configuration remotely.

Need more in depth help? Looking to buy more devices?