Open Port Scan - 53 External
When tapping the "Open Ports" icon, it yields information that the external scan has found port 53 is open. (To the right it says, "Unmanaged.") I do not have any port forwarding enabled on my FWG, nor is UPnP enabled.
I have combed through the rules and have found no rules that allow inbound port 53. What am I missing here? The documentation states that my router might have opened that port. The FWG IS my router...useless, generalized information in my opinion.
<enhancement request>
In an ideal world, instead of merely providing generalized information when tapping the open port listed, the FWG should actually track down WHERE the port is actually opened. As it is in DHCP mode (a superset of Router), it is the master of the universe. As such it should tell me WHY it's open.
</enhancement request>
-
If the port is not managed, it is not opened from firewalla. If you are running FWG in router mode, then likely you do not have a public IP, the open port scan just scanned a shared ISP IP. see https://help.firewalla.com/hc/en-us/articles/360055686674-How-to-see-if-you-have-a-public-IP-address-
-
Hello, thanks. It is a public IP. The IP for the WAN matches the same at WhatsMyIP.
I'm not following the logic that it's not opened from Firewalla. It's a very simple setup: Internet -> ISP -> Cable Modem -> Firewalla Gold -> Internal Network.
As it is a public IP, the ISP is a pass-through. How could it not be the Firewalla? The IP that was scanned was the same IP as shown on the WAN interface as well; I used a third-party to validate what the FWG reported.
When I do a netstat it is showing that the port is open on my local network, and curiously the WAN interface's address as well...for both UDP and TCP.
This is making me a bit nervous now. What am I not seeing that is potentially exposing more than it should?
Please sign in to leave a comment.
Comments
3 comments