^^^ Rogue players are scanning for any and all ways (ports/services) to penetrate anything listening which is connected to the public facing internet. These routers are our front door and lock! That's why I often double-nat them. Get thru one, well buddy, there's another and it's got a different set of creds and in some cases I even use a different manufacturer.
I am a surprised that the httpd (WebGUI) would even be
listening on the
public/
WAN side of the router when that check box is turned OFF in the setup... RMerlin may have to answer that one. That's the real?
SSHing into the router is a totally different port and service NOT connected with httpd... I think sshd would be reporting kicks to that port...
Only testing or looking at the code can say for sure. Gut says having this value off in Admin > Other would mean httpd is
not listening on the WAN side of the router. I am unsure what "Enable Access Restrictions" does. But maybe it is listening and reporting those port scans... which seem risker than not listening at all!! In other words, the router should should be just dropping all those packets and scans when set to No and operating in "stealth" mode.
You really don't want to give the bad guys a reason to come back to your door b/c they know you have a httpd processes listening. Most commercial FW might log the scans but drop any and all responses.
View attachment 18090