Smart Hub 7 Plus Port Forwarding Issue

[jsviper77]

Hi All,

Another Issue with the Hub 7 Plus, probably on others too.

When i create a Port forwarding rule, it always comes up with an error and doesn't save or eventually when it does save, it has created duplicate rules. Try to remove one and it removes both, aaarrrgghh! These EE hub are very frustrating.

I hope someone who can help sees this and my other post, to help fix these issues.

[Pecbeck]

@SamyM 

Which dynamic dns service are you using? Which update client? Have you double checked that the ip address pointed at by your domain matches the external hub address? I had similar problem, and found out the address in my domain was different to the hubs external ip. I noticed this when testing with the signal port checker.

Just a thought. Given port forwarding works for me an Jim on hub 7, there has to be something you are missing in your config somewhere 

[SamyM]

Hi, just to check are you on the EE Hub 7 Plus? I'm not using any DDNS service. Just putting port forwarding to the WD EX2 Ultra Cloud using IP address 192.168.1.155 as a static address. It all works on EE Hub 2 which is what I have reverted to again. I have noticed on EE Hub 7 Plus the only way I can get port forwarding to work is enable DMZ. Obviously, something still wrong on the Hubs firmware. I've been trying to resolve this issue for months on the EE Hub 7 Plus which EE say was the latest one back in December last year. Has anyone else got EE Hub 7 Plus to port forward?  EE have really made a mess of this.
Samy

[JimM11]

@SamyM Can you upload the picture off the network status showing that you have indeed set the address as static and not dhcp assigned, picture earlier in this posting shows, and what to hide to get through the filter!

[XRaySpeX]

The image earlier that was rejected shows the Hub Status page incl. its Serial no. They usually get thro' but maybe someone was over cautious. If the Serial no. were to be obscured it should get approved.

[Pecbeck]

I'm on hub 7, using dynu ddns, works perfectly.  I assume you have your own domain set up, so assume you are setting that to point to the external address of your hub, which of course sometimes changes following reboot

[SamyM]

Hi,  The is the address table for 192.168.1.155 which is my cloud.  The IP address is Static.

 I cannot find anything wrong.  

Samy

[SamyM]

Hi, Checked the port and shows 

Samy

 

[SamyM]

Hi,

The port is closed still

 

[bobpullen]

---

@SamyM wrote:

Hi,  The is the address table for 192.168.1.155 which is my cloud.  The IP address is Static.

---

Slight tangent but this clearly shows that it is your NAS that it automatically opening up that 49592 TCP port using UPnP. Why is it doing this? What access is your NAS expecting to be made over this port? If you try the yougetsignal check on this port, is it open? - That would at least prove that traffic can get to your NAS via a port forwarding rule.

Whilst it really shouldn't be necessary, I still think it's worthwhile you temporarily disabling UPnP in the hub and rebooting it to see if it has any impact.

Can you access the NAS locally over FTP when the 7 Plus is in situ? i.e. by FTP'ing directly to the 192.168.1.155 address? If you can't, then something else is awry as a connection over your LAN has no dependency on port forwarding at all.

A very unlikely angle but do you have the Advanced Web Protect feature enabled in the EE App? Might be worth checking that to make sure the inbound attempts to access your NAS aren't being blocked. 

[Pecbeck]

You may be into something @bobpullen 

Yes, EE’s Advanced Web Protect can block or interfere with traffic on port 21 (the standard FTP port), although it’s not its main focus.
Advanced Web Protect filters inbound and outbound traffic that looks like threats, including connections to suspicious IP addresses or domains, and FTP traffic to dubious hosts can be flagged.
If EE’s security engine thinks an FTP server (or client activity on port 21) is associated with malware or botnet‑like behaviour, it may block or drop the session, even though port 21 itself isn’t “hard‑blocked” like a strict firewall rule.
If you’re trying to run an FTP server on port 21 and it’s blocked or flaky behind the EE Smart Hub 7, common fixes are:
Temporarily turning off Advanced Web Protect in the EE/MyEE app (Manage → Broadband → Advanced Web Protect → Off) to test.
If FTP still fails, check whether EE’s port‑clamping or modem‑level restrictions are also blocking unsolicited inbound traffic on that port (EE does not generally allow raw inbound port forwards as freely as some ISPs).
If you describe what you’re doing with port 21 (e.g., running a home FTP server, BitTorrent, etc.), I can suggest whether it’s more likely to be Web Protect, a misconfigured port‑forward, or wider EE‑network restrictions.