Skip to main content
Forum FAQ's
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Smart Hub 7 Pro — port forwarding not working

rushsnacks
Investigator
Investigator

‎31-05-2026 03:59 PM

Ports closed externally despite a valid mapping.

Posting here as I understand this is a known issue and the place it gets escalated to engineers.

Setup: EE FTTP, Smart Hub 7 Pro. (Mesh system in AP mode behind it; the hub is the sole router.)

Problem: Port forwarding doesn't work. Forwarded ports stay closed from outside even when a valid mapping is present on the hub. Confirmed closed externally with an independent port checker.

What I've already ruled out at my end:

- Not CGNAT — I have a genuine public IPv4 address.
- No double-NAT — the hub is the only router on the line.
- The target device has a reserved local IP.
- The mapping shows on the hub, but the firewall isn't passing inbound traffic to it.

So it's not a configuration error my side. I gather from other threads here that EE engineers have acknowledged this as a firmware bug and said it'll be fixed in a firmware update.

Could a moderator please:

- confirm the current fix status / firmware timeline,
- check whether a fixed firmware is available for the 7 Pro and have it pushed to my hub,
- and escalate if needed.

My current firmware version: r4.28.1-R-1882725-PROD-1

Happy to discuss account by private message if a moderator needs my info. Thanks.

0 Helpful
11 REPLIES 11
bobpullen
Star Contributor
Star Contributor
In response to rushsnacks

‎08-06-2026 06:44 PM

@rushsnacks - assume you can reach the target services locally over your own network on their respective ports?

Given yours works, what firmware's your Pro on? Mine's r4.28.1-R-1882725-PROD-1 (GUI 3.14.5)...

Both that build (and all prior builds) have been fine for me. Forwarding TCP 80, 443, 22, 32400 and UDP 47111 to two devices on my local network (both Ethernet connected via switches).

Don't suppose you have the 'Advanced Web Protect' feature turned on in the EE App? If so, it might be worth checking to make sure that's not blocking anything it shouldn't.

0 Helpful
rushsnacks
Investigator
Investigator
In response to bobpullen

‎08-06-2026 07:37 PM

Thanks Bob — that's really helpful.

Yup, I can reach them locally on their ports over the LAN with no issue — it's purely the inbound forward that stays closed from outside.

Given it's working for you on the identical build, guess that pretty much rules out a firmware bug at my end. Advanced Web Protect tip was not in my head at all so will go and check and report back.

If that's not it, I think I'm on to a factory-reset and start again.

0 Helpful