An Omada Fusion Pro behind a router you already run is not broken when your laptop can’t open its web UI. It is a router, and like any router it refuses management traffic that arrives on its WAN port, so the only devices that can reach it are the ones plugged into its own 192.168.188.0/24 side. Omada Fusion Pro port forwarding fixes that without rewiring anything or touching your main firewall.
This guide gives the Fusion Pro a fixed address on your home network and forwards the web UI and the Omada Guard camera ports from that address to the box itself. Then it checks the result from a second machine with curl and nmap. You keep your existing OPNsense, pfSense or UniFi gateway exactly as it is. Everything below was run on a Fusion Pro 2.5G PoE with firmware 4.0.2 behind an OPNsense router in November 2026.
See Why the WAN Side Blocks the Web UI
Plug the Fusion Pro’s WAN1 port into a home LAN and it behaves exactly as it would on a fibre line. It takes an address from the upstream DHCP server, NATs everything on its own LAN behind that address, and drops any connection that starts on the WAN side. Our unit took 192.168.1.126 from the home router, and from a laptop on that same network the address ignored ping and ports 80, 443 and 8043.
A static route doesn’t change that either. We added one on a host on the home LAN, sending 192.168.188.0/24 through the Fusion Pro’s WAN address, and the packets still died, because the gateway’s firewall rejects new inbound sessions on WAN before routing even matters. Follow one HTTPS request from a laptop on the home network and you hit the wall in this order:
- The laptop sends TCP 443 to the Fusion Pro’s WAN address.
- The WAN firewall sees a new session that nothing on the inside opened.
- No forwarding rule matches, so the packet is dropped and the browser times out.
Port forwarding changes step 3. A rule on WAN1 rewrites the destination to the Fusion Pro’s LAN address, 192.168.188.1, and the web UI that already answers there answers your laptop too. The diagram shows the finished path, including the ports Omada reserves for cameras on the WAN side.

Nothing changes on your main router. The Fusion Pro still routes and NATs its own LAN, the cameras on its PoE ports stay on 192.168.188.0/24, and the only new thing your home network sees is one address with a handful of open ports.
What You Need Before You Start
The Fusion Pro has to be set up already, with a local admin account you can log in with. If the app onboarding failed on yours, the Fusion Pro web setup walkthrough gets you there from a laptop on a LAN port. Have these ready:
- A computer on a Fusion Pro LAN port
- WAN1 cabled to your existing router or switch
- One free address outside the router’s DHCP pool
- The router’s own address for gateway and DNS
The computer on the LAN port keeps https://192.168.188.1 reachable while you change the WAN side. Our router’s DHCP leases all fell between 192.168.1.100 and .199, so we used 192.168.1.254, with the router itself at 192.168.1.1 as gateway and DNS. Check the address is really free before you take it. A quick ping 192.168.1.254 from any machine on the home LAN should get no reply, and the router’s DHCP lease list shouldn’t show it either.
Set a Static WAN Address
Every bookmark, every forwarding rule and every camera you point at the Fusion Pro later uses its WAN address, so that address cannot be allowed to drift. A DHCP lease usually renews to the same IP, but “usually” breaks the day the router is rebuilt or the pool is resized. A static address on WAN1 removes the dependency, and a DHCP reservation on your router is the alternative if you would rather manage addresses there.
Open Network Config, then Network Settings, then WAN, and click the edit icon in the WAN1 row. Set the form like this:
- Connection Type: Static IP replaces the default Dynamic IP.
- The IP address is the free address outside the DHCP pool, 192.168.1.254, with subnet mask 255.255.255.0.
- Default Gateway is your existing router, 192.168.1.1. Expand Advanced Settings and put the same address in Primary DNS Server.

- 1Connection Type: Static IP
- 2Free address outside the DHCP pool
- 3Your existing router
Click Apply. Clients on the Fusion Pro LAN lose internet briefly while WAN1 comes back up, and on our bench the laptop on the LAN side was back online when we checked 30 seconds later. The WAN list then shows WAN1 online on the new address with a fresh uptime counter:

Your router may list the Fusion Pro’s MAC on both the old and new address for a while. That is the old DHCP lease waiting to expire, and it clears on its own.
Forward 443, Not Just 8043
Omada’s own guide for adopting WAN-side devices lists TCP 8043 as the controller management port, so forwarding 8043 looks like enough. It is not enough on this firmware. The Fusion Pro’s web UI lives on 443, and 8043 only answers with a redirect to the same host on the default HTTPS port. We forwarded 8043 first and tested it from a Linux host on the home LAN:
curl -sk -o /dev/null -w '%{http_code} %{redirect_url}\n' https://192.168.1.254:8043/
The 302 points at port 443 on the WAN address, not at 8043:
302 https://192.168.1.254/
With only the 8043 rule in place, curl got no answer at all on https://192.168.1.254/ (it printed status 000), and a browser does the same thing after it follows the redirect: it spins and then times out. That is why the rule list in the next section forwards 443 as well as 8043. Keep 8043 anyway, because Omada uses it for controller management and manual firmware uploads.
Create the Omada Fusion Pro Port Forwarding Rules
Two rules give you the web UI. The other four come from Omada’s WAN-side adoption guide: 8044, the firmware upgrade service it lists with the controller ports, and three rules for the Fusion Pro’s Guard application, which manages and records the cameras. All six point at the same destination, the Fusion Pro’s LAN address, and each keeps the same port number on both sides:
| Rule name | Port (TCP) | What it carries |
|---|---|---|
| Omada-Portal-443 | 443 | The web UI itself |
| Omada-Portal-8043 | 8043 | Controller management, redirects browsers to 443 |
| Omada-Firmware-8044 | 8044 | Firmware upgrade service |
| Guard-Discovery-10122-10123 | 10122-10123 | Camera discovery and the long-lived adoption session |
| Guard-Manage-6000 | 6000 | Fusion Pro managing the cameras |
| Guard-Stream-6005 | 6005 | Video from the cameras to the recorder |
Go to Network Config, then Traffic Management, then NAT, and stay on the Port Forwarding tab. Click Create New Rule, give it a name from the table, leave Status enabled, and fill in the rest:
- Source IP set to Limited IP Address with 192.168.1.0/24, so only your home LAN can use the rule.
- Interface WAN1, picked from the drop-down. Leave WAN IP and DMZ empty.
- Source Port and Destination Port both 443, Destination IP 192.168.188.1 (the Fusion Pro LAN address, same port), and Protocol TCP.

- 1Only your home LAN
- 2Interface WAN1
- 3Fusion Pro LAN address, same port
The source restriction matters more than it looks. Behind your router the WAN only ever sees home LAN traffic, but the day someone moves the Fusion Pro onto a modem, a rule with Source IP set to Any would hand the admin page to the internet. With 192.168.1.0/24 in place the same move just makes the rules stop matching. Click Create, then repeat for the other five rows of the table. Each rule saves on its own, and the list ends up like this:

Omada’s guide uses the protocol “All” by default. Every port in this table is TCP, so we picked TCP and kept each rule to the one protocol it needs. If you ever adopt Omada switches or access points that sit on the home LAN, that’s a separate set of controller ports (UDP 29810 and TCP 29811 to 29817, plus the 8043 and 8044 already in the table), and they are not needed for the web UI or for cameras.
Open the Web UI From the Home LAN
From any device on the home network, open https://192.168.1.254/. The certificate is the Fusion Pro’s own self-signed one, so the browser warns once before it shows the Omada login, and the account is the same local admin you use on the LAN side. The dashboard looks exactly as it does on 192.168.188.1, and the address bar is what proves the page was reached through the WAN address: it reads https://192.168.1.254/. The WAN IP line on the gateway card shows the same 192.168.1.254 whichever side you browse from.

Devices on the Fusion Pro’s own LAN can use the WAN address too. A laptop on a LAN port got HTTP 200 from https://192.168.1.254/, so one bookmark works from both sides. If you would rather type a name, add a host override such as omada.home.arpa pointing at 192.168.1.254 in your router’s DNS resolver.
The same reach covers the Omada Guard tab, so live view and playback for the cameras on the PoE ports open from the home network as well. Click the camera icon next to the globe at the top, and Live view through 192.168.1.254 starts both streams in the browser. Our unit showed both cameras online, 8 days 9 hours of recordings combined across both cameras, and 37 GB used of the 930 GB SSD, all loaded through the forwarded 443:

Cameras that sit on the home LAN themselves are what the three Guard rules are for, for example cameras on a UniFi PoE switch that already powers your outdoor runs. Omada’s guide has you enter the Fusion Pro’s WAN IP in each camera’s Controller Inform URL setting, and the two then talk over 10123, 6000 and 6005. The scan below shows those three ports answering from the home LAN. The Omada cameras with Frigate guide covers the RTSP and ONVIF side if you also want the streams in Home Assistant.
Verify the Forwards With nmap
A browser that loads the dashboard proves one rule. A port scan from a second machine on the home network proves all of them, and it also shows which forwarded ports have something listening behind them. We ran it from a Linux host on 192.168.1.0/24 against the WAN address, with SSH and HTTP added as controls that have no rule:
nmap -Pn -p 22,80,443,6000,6005,8043,8044,10122,10123 192.168.1.254
Three different states come back, and each one means something specific:
Starting Nmap 7.92 ( https://nmap.org ) at 2026-11-15 21:48 EAT
Nmap scan report for 192.168.1.254
Host is up (0.00054s latency).
PORT STATE SERVICE
22/tcp filtered ssh
80/tcp filtered http
443/tcp open https
6000/tcp open X11
6005/tcp open X11:5
8043/tcp open fs-server
8044/tcp closed fs-mgmt
10122/tcp closed unknown
10123/tcp open unknown
MAC Address: 00:00:5E:00:53:01 (Icann, Iana Department)
Nmap done: 1 IP address (1 host up) scanned in 1.39 seconds
Ignore the service names in the last column, because nmap guesses them from its port list and the Fusion Pro is not running X11. The STATE column is what matters, and it maps straight back to the rules:
| State | Ports | What it means on the Fusion Pro |
|---|---|---|
| open | 443, 6000, 6005, 8043, 10123 | A rule matched and a service on 192.168.188.1 answered |
| closed | 8044, 10122 | A rule matched, but nothing listens on that port on the LAN side right now |
| filtered | 22, 80 | No rule, so the WAN firewall dropped the probe silently |
The closed ports are not a mistake in the rules. We checked 8044 and 10122 directly against 192.168.188.1 from the LAN side and they refused there too, so the forward works and simply has nothing to deliver to on this firmware. Port 8044 is the firmware upgrade service from Omada’s switch and access point list, and 10122 is the discovery port cameras use when they learn the Guard address through DHCP option 138, so neither has to be up for the web UI. Leave both rules in place for the day those services start.
To undo everything, delete the six rules on the Port Forwarding tab and set WAN1 back to Dynamic IP. The Fusion Pro returns to refusing every connection from the home LAN, which is the behaviour this guide started from. If you are still choosing between this box and a UniFi gateway for the same job, the Omada Fusion Pro review and our Omada vs UniFi comparison cover what you give up either way. The Omada controller in Docker is the route for Omada switches and access points that do not come with a built-in controller.