pfSense port forwarding is set up under Firewall > NAT > Port Forward, where a rule sends traffic arriving on a WAN port to an internal IP address and port.
These steps match pfSense CE 2.9.0 and pfSense Plus 26.07, the current releases as of November 2026.
I ran pfSense at home for almost four years, mostly on a Netgate 6100, until I switched to UniFi in late 2024, and I genuinely loved it. I never port forwarded to reach my own network, since I got in over a VPN on the firewall itself. Port forwarding exposes a service to the internet, so if reaching your own network is the goal, set up WireGuard on pfSense or set up OpenVPN on pfSense instead.
pfSense Port Forwarding: Step-by-Step Guide
In my opinion, port forwarding on pfSense is drastically more complicated than on probably any other device. Here’s how to port forward on pfSense field by field, with TCP port 32400 and a Plex server at 192.168.1.10 (swap in your own).
Step 1. Open the NAT Port Forward Section
Log in to the pfSense web GUI and select Firewall, then NAT. The Port Forward tab opens by default.

Step 2. Add a New Port Forwarding Rule
Select either Add button (the up arrow adds the rule to the top and the down arrow to the end).

Leave Interface on WAN and Address Family on IPv4. Protocol defaults to Any on 2.9.0, and the port fields appear once you change it to TCP, UDP or TCP/UDP, whichever the service uses.

Leave Destination on WAN address. Under Destination port range, set From port to a named service or to Other with the port in the Custom box, and leave To port empty for a single port. Truthfully, there’s no real difference, but I preferred the Custom box, because you can see at a glance which ports are forwarded.

Step 3. Set the Redirect Target
Under Redirect target IP, keep Address or Alias and enter the device’s internal IP (192.168.1.10). It needs a static IP so you’re always forwarding to the correct device. Set one on it, or add a static mapping under Services > DHCP Server.

Under Redirect target port, enter the port the service listens on, which is usually the same as the From port. If your public IP changes, DDNS on pfSense using Cloudflare gives you a hostname that follows it.

One public IP can’t send the same port to two devices when the forward accepts any source, so give a second server another external From port (8080, say), redirected to the port it listens on. Extra public IPs (Virtual IPs, set as the forward’s Destination) or the HAProxy package sharing 443 by hostname get around that.
Step 4. Add a Description and Save
Enter a Description (Plex here) and keep NAT reflection on Use system default. Leave Filter rule association on Add associated filter rule. pfSense denies everything that isn’t explicitly allowed, which in my opinion is the right default, and this option creates the WAN firewall rule that opens the port on pfSense.
None creates no rule (the traffic is dropped), Add unassociated filter rule creates one you maintain by hand, and Pass does not work properly with Multi-WAN.

Select Save, then Apply Changes.

Step 5. Verify the Firewall Rule Was Created
Select Firewall, then Rules, and finally, WAN, where a new rule named NAT Plex passes traffic to the internal IP and port. It’s linked to the forward, so deleting the forward deletes the rule too (creating firewall rules in pfSense covers more).

Step 6. Restrict Access by Source IP (Recommended)
By default, anyone on the internet can reach the port. To narrow it (skip this for Plex), select the forward’s pencil icon on Firewall > NAT > Port Forward, then Display Advanced next to Source. Change Type from Any to Address or Alias, enter an IP address or alias name, and select Save and Apply Changes.

An IP alias (Firewall > Aliases, IP tab) keeps several addresses in one place.
How to Create a Port Alias in pfSense
A port alias puts several ports under one name.
1. Select Firewall, then Aliases, and finally, the Ports tab, then select Add.
2. Enter a Name (letters, numbers and underscores), set Type to Port(s), and enter one port or range per row (Add Port adds a row), with a colon for a range (1194:1199), then select Save.

In the forward, choose Other for From port and Redirect target port and type the alias name in each Custom box. For a plain range, fill in From port and To port and enter the first internal port as the target.
To map one external port to a different internal port, set the redirect target port to the internal one.
pfSense Plex Port Forward Example
Plex uses TCP port 32400, so a pfSense Plex port forward is Steps 1 to 5 above, without Step 6 (remote viewers connect from IPs you can’t list).
Plex can try UPnP or NAT-PMP, but I’d make the forward by hand, because a rule you create yourself is one you understand and can undo. In Plex Web App, open Settings, then Server, and finally, Remote Access, select Show Advanced, tick Manually specify public port, enter the external port and select Retry. Remote video streaming needs Plex Pass on the server owner’s account, or a Remote Watch Pass or Plex Pass on the viewer’s.
pfSense Port Forwarding Not Working: What to Check
pfSense has a real learning curve, so start with the usual causes of pfSense port forwarding not working from Netgate’s port forward troubleshooting guide:
- Testing from inside. Forwards only work from outside by default, so test from a phone on cellular data.
- A missing or wrong rule. Firewall > Rules > WAN needs the forward’s firewall rule, with the internal IP as its destination.
- Nothing listening. “Connection refused” means the host rejected it, so check the service and the host’s own firewall (Diagnostics > Test Port helps here).
- The wrong gateway. The target has to use pfSense as its default gateway.
- Double NAT. If your ISP’s modem also routes, forward the port there too or put the modem in bridge mode.
- An ISP block. Some ISPs filter well-known ports, so try another one like 8080.
Check Diagnostics > States while you test, and the same guide covers logging and packet captures.
Testing From Inside Your Network: NAT Reflection and Split DNS
NAT reflection lets a LAN device reach a forward through your public IP, and it’s disabled by default under NAT Reflection mode for port forwards (System > Advanced, Firewall & NAT). Turn it on there, or per rule with Step 4’s NAT reflection dropdown.

NAT + Proxy skips ranges over 500 ports and shows the server the firewall as the source, while Pure NAT works with every protocol a forward supports, though clients on the server’s own subnet also need Enable automatic outbound NAT for Reflection.
Netgate calls reflection a hack and recommends split DNS instead, with a host override under Services > DNS Resolver pointing the hostname at the internal IP for devices using pfSense for DNS. Split DNS fails when external and internal ports differ.
What Is the pfSense Default Port?
By default, the pfSense web GUI uses HTTPS on TCP port 443 and redirects port 80 to it. Change the port in the TCP port field under System > Advanced, Admin Access (empty means the default), then reconnect on the new port.

The GUI is not reachable from WAN by default, and Netgate says not to expose it to the internet. A WAN forward for 443 takes over the GUI on WAN, but LAN access keeps working.
Security Considerations
Simply put, if security is important to you, set up a VPN rather than port forwarding. That’s how I reach my own network today, and for apps that aren’t media I use a Cloudflare Tunnel, which needs no forward. A VPN on pfSense itself doesn’t need a forward either, which is how I ran both of mine at home (WireGuard primary, OpenVPN backup). OpenVPN (UDP 1194 by default) needs a WAN rule to the WAN address (the OpenVPN wizard can add it), and a forward on that port would take over from the VPN. The guide to set up OpenVPN on pfSense covers the rest.
If a service has to be public, put it in a DMZ in pfSense, restrict its source where you can, and keep it and pfSense updated (see pfSense update best practices).
The steps for port forwarding in OPNsense are similar.
Security changes all the time and nothing here is guaranteed, so review your forwards and remove any you no longer use (these ways to make your home lab more secure help too).
