23-06-2026 09:34 PM
Hello
I'm trying to forward port 7777 TCP/UDP to a static IP on my network for a satisfactory server, however the hub simply wont let me do this.
What I have tried without getting the correct result:
I'm at wits end as to why this hub won't let me do something as simple as forward a port. Any help would be much appreciated.
23-06-2026 09:44 PM - edited 23-06-2026 09:54 PM
@Rawazzie Then post a capture off your Port Rules up on the Forum and say what EE Hub you are using, the Forum is not into Guessing what you have. Hide your static IP Address on the capture so it gets through.
23-06-2026 10:17 PM - edited 23-06-2026 10:20 PM
What is the correct result? As you seem to be messing around with browsers while setting the rule(s), It would seem that the correct result you are trying to achieve concerns the actual setting of the rules.
24-06-2026 12:36 AM
So this doesnt work, not allowed to add a TCP/UDP rule for this port for some reason.
I created one of the rules first, and then try to add the next one, it also wont work:
side note: I cannot alter or remove that port_map_UDP_65112 rule. I assume it is mandatory somehow?;
Also cannot add it as a range to include the desired port:
hub info:
Smart Hub SH32B
I want to forward port 7777 for both TCP and UDP protocols but the UI doesn't seem to permit this port to be forwarded for both protocols simultaniously..
24-06-2026 12:39 AM
I've been googling the issue and some people claimed to have worked around the issue by using new or incognito sessions for each rule they wanted to add. Sadly this workaround did not work for myself. I listed the things I've already tried to skip the part where anyone willing to help would tell me to try the things I've already tried.
24-06-2026 12:00 PM
@Rawazzie For a quick test, place you server IP in the DMZ field and see if the connection get's out/in with the firewall bypass, after that you need to concentrate where your fixed IP is assigned in the EE Hub, is it static on the DHCP settings for the wired connection?
24-06-2026 05:08 PM
Thanks for this!
Progress - It already had a static address and a wired connection, but by putting it in the DMZ the server is now visible! unfortunately the server is only visible on its IPv6 binding, and not IPv4. I will leave the server in the DMZ while I troubleshoot and attempt to get IPv4 to pass the traffic through. My friends unfortunately aren't with an ISP that supports IPv6.
At this stage I will simply assume the port forwarding feature is bugged and that the DMZ is the (somewhat drastic) workaround.
24-06-2026 05:47 PM - edited 24-06-2026 05:56 PM
@Rawazzie As you have the SH32B and are now on the latest FW update that has just been pushed out to that version of the EE Hub's within the last few day's or so starting here is the link to what was getting done.... The one you cannot remove is being assigned on a device that is using Universal Plug and Play. That was an issue reported on the newly released 7+ version off the EE hub messing big time with the Port Forwarding rules, just so you are aware.
EE Hub firmware versions - The EE Community
FW: r3.8.30-R-1627300-PROD-83002 and the gui is at App version 3.1.18 05/12/2025
FW: r4.26.1-R-1860948-PROD-83002 and the gui is at App version 3.14.5 25/05/2026 OP Posted Stability Problem
FW: r4.26.3-R-1923144-PROD-83002 and the gui is at App version 3.14.5 12/06/2026 OP Posted
25-06-2026 10:42 AM
@Rawazzie - I am on the same hub/firmware as you and I have no issue creating a TCP/UDP rule for the mentioned port 🤔:-
However, I do encounter the same issue as you if I try entering them seperately i.e. I create the TCP rule, but the second UDP rule isn't allowed.
side note: I cannot alter or remove that port_map_UDP_65112 rule. I assume it is mandatory somehow?;
As @JimM11 has explained, that is a rule that some device on your network has created using UPnP. Not necessarioy a problem but a bug has been observed on the 7 Plus where the presence of a UPnP rule prevents any subsequent port forwarding configuration from working; more detail here.