EE Smart Hub port forwarding not working, but DMZ works

[Rain-or-Dom]

Hi, I'm having an issue with port forwarding on my EE Smart Hub. Has anyone experienced this before?

[Rain-or-Dom]

I have the EXACT same issue!

port forwarding just doesn't work, when I put the ip into dmz it works no problem, i gave up for a few months to hoping it would resolve itself with a patch but nope, when I called EE I got no support at all and they said use port forwarding at my own risk lol

considering leaving EE tbh just a pain

[Rain-or-Dom]

EE Smart Hub port forwarding times out externally, but DMZ works

Hi,

I'm having an issue with port forwarding on an EE Smart Hub and I'm hoping someone can help.

My setup is:

EE FTTP
EE Smart Hub
Firmware r4.27.1-R-1862254-PROD-84001
ONT connected directly to the Smart Hub
No additional router or double NAT
Minecraft server running through Crafty Controller in Docker on an Ubuntu VM
Minecraft uses TCP port 25600

I am trying to forward TCP port 25600 from the internet to the Minecraft VM.

The DNS side is working correctly and resolves to my current public IP.

The Minecraft server itself is working correctly.

Connections to port 25600 from another device on my LAN work successfully.

Docker is publishing port 25600.

UFW is inactive.

I have also used tcpdump on the VM and confirmed that local connections reach the VM successfully.

The problem occurs when using a normal port forwarding rule on the EE Smart Hub.

An external port checker reports that port 25600 cannot be reached. At the same time, tcpdump on the Minecraft VM shows that no connection attempt reaches the VM.

However, if I put the Minecraft VM into the Smart Hub DMZ, the exact same external port test immediately succeeds.

I have therefore established the following.

Normal port forwarding does not work.

DMZ forwarding does work.

The Minecraft server works locally.

Docker works correctly.

The VM networking works correctly.

The public IP is correct.

There is no double NAT.

The ISP does not appear to be blocking the port.

I have already factory reset the Smart Hub, disabled UPnP and tested with DMZ disabled.

Before the factory reset I was also seeing some strange UPnP rules where the external end port was displayed as 0, and the Hub was reporting port overlaps.

The factory reset fixed the port overlap issue, but individual port forwarding still does not work.

The firmware is currently up to date and the Hub does not offer any further firmware update.

Has anyone experienced a similar issue with an EE Smart Hub?

Is there a firewall or NAT setting that I may be missing, or could this be a problem with the Smart Hub itself?

I would prefer to use a normal individual port forwarding rule rather than leave the Minecraft VM exposed through the DMZ.

Thanks.

[XRaySpeX]

@Rain-or-Dom : Show us your Port Forwarding settings.

[JimM11 · Accepted solution]

@Rain-or-Dom Did you not find the post with the PF issues as explained for your EE Smart Hub 7 Plus that did not work?

Linked below with the steps that were required to get PF working correctly and i think without bypassing the firewall that you are doing placing the IP in the DMZ. Issue is still not 100% resolved but see new FW is slated again if it ever get's out there.

Smart Hub 7 Plus Port Forwarding Issue - The EE Community

[Rain-or-Dom]

[Rain-or-Dom]

Oh I see, yeah I did try that without seeing the post actually but I'm happy to know its affecting others, so I need to factory reset and create my rules before it can create a UPnP, I normally turn it off but it seems to create the rule before before I can even turn the setting off, need to try and find out what device is auto connecting to it

thanks so much Jim

[JimM11]

@Rain-or-Dom Seems to be the way Currently with the uPnP that the EE Smart Hub 7 Plus is pulling out some how, or where it's all getting stored mem wise, two thing's and you are correct, get it all reset, nothing connected setup your PF rule and get the IP assigned static so you are just not fighting it all. Hope it all works out for you.👍

The 7+ version seems to be very obstinate with the PF rules more so if the uPnP gets in as a first, hopefully get's sorted out with some later FW updates.... Your posted picture will get cleared once someone checks it is good to be done. 

[JimM11]

@Rain-or-Dom Your image is now through, the area marked with the zero is the possible uPnP problem and from the MAC addresses you see you may be able to work out which is doing the PF auto maping.

Redo picture highlighted.

[Rain-or-Dom]

youre a legend Jim, thanks ive fixed it now!