port forwarding does not open certain port

[#1]

3 ports in port forwarding rules

88 & 8095 are open

but 8090 is closed

what am I doing wrong

[#2]

@mustywalji welcome to the community

Looking at the rules you have created I see no issues, what is telling you port 8090 is closed?

If you check the hubs event log found in >Advanced settings >Technical Log >Event Log > Select category FWRL

you can see if the rule is working, the target device does not need to be switched on for the rule to work

example log entry

08:02:28, 22 Oct. FWL Port Forward Server(192.168.10.201) TCP 8090 accepted a new connection from 198.199.98.246

Can you connect to the device locally on port 8090?

[#3]

@mustywalji 

I'll admit that I don't know much about Port Forwarding, though I have set it up myself for Transmission BitTorrent on our home server.

Looking at your screenshot, the thing that jumps out to me is that the device that is trying to use port 8090 is labelled as "unknown", followed by what I assume is its MAC address, in the second column.

It is probably irrelevant, but have you tried giving that device a name and seeing if there is any change?

.

[#4]

@Mr_Paul 

From what I can make out, if the router does not recognise a MAC address it will make the device name "unknown-<MAC address>"

I always edit the name to match the device.

Randomised MAC addresses of a smart phone is a good example of this 

EDIT: IP addresses can be used as an alternative to device name, for this the device needs a fixed IP Address should be used.

[#5]

@mustywalji , a couple of queries/comments on that,

1. How do you know which ports are open and which are closed?
2. The port would normally only show open if there is something listening on that port on the device that it is being forwarded to.  Something to try and work out is if it is not being forwarded, if it's being forwarded but to the wrong device, or if it's the right device but that isn't listening on that port.

[#6]

@pjmarsh 

The problem here is the Hub two will report the firewall has worked even though the port forward test has failed

Using https://www.yougetsignal.com/tools/open-ports/ 

So a local test on port 8090 needs to be verified

EDIT: if the port forward messages are not been seen the event log, this would suggest something external is preventing traffic on that port, maybe the Broadband Firewall found in members centre is set to High

https://www.plus.net/member-centre/broadband/firewall 

[#7]

@Dan_the_Van 

"I always edit the name to match the device."

So do I - I don't like having "unknown" devices on my network!

.