I have found that if I open a port and then disable it, the port remains open and accessible.
This isn't the intended behaviour is it?
The port does close if I delete the rule.
Its possible its staying open as a connection is already established. What happens if you disable the rule then try to contact the webserver without an existing open connection?
The port was still open even after I restarted my proxy server, which would have closed the connection if there was one. I also hadn't enabled the rule since I made the post on Friday and was still open Today.
I've also done more testing and found if I move the disabled rule up or down that closes the port. I also found enabling one service rule also enabled another that I hadn't touched.
I assume a reboot of the hub after disabling the rule closes the port?
Yes a reboot does close the port. This reboot has fixed all the issues I've had, ports are now closing after I disabled them and enabling one rule does not do anything to the others.
I still think there is an issue because rebooting the hub was one of the first things I did when I found the issue last week. I will keep an eye of things and see if it starts acting up again.
Didn't take long. I deleted the rule, created it again then disabled it and it's still open.
I have also now managed to open the test2 rule without touching it.