Port 80 open externally with config page on TL-R605
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
The TL-R605, which is being managed by my Omada software controller, is serving up a config page on port 80. Not only is this a huge security flaw, but it's likely interfering with authentication for LetsEncrypt. I see no setting to turn off the external accessibility of the config page in the Omada controller.
I am unable to recreate this
Hitting both DDNS and IP (with and without :80) from an foreign network does not resolve for me. It appears to be blocked
Shields up test reports the port as CLOSED, ideally it shouldn't respond at all (stealth) but closed is good
Granted when I hit the external address from internal, NAT resolves this and does prompt the "managed page" but that is to be expected from internal
@aloychan - Are you definitely using an external / foreign connection for the DDNS connection? The fact that you are seeing the 192.168.0.211 address listed makes me think you are connected to the TL-R605 and trying to go OUT then back IN. NAT wont allow you to do this and will just forward you to the LAN interface.
My TL-R605 is facing the exact issue as what BFH reported in this thread. When my DDNS name was used with :80, this page of the TL-R605 showed up.
Btw, I have a Omada controller managing the R506. I need to know to disable port 80 in Controller or R605.
I am unable to recreate this
Hitting both DDNS and IP (with and without :80) from an foreign network does not resolve for me. It appears to be blocked
Shields up test reports the port as CLOSED, ideally it shouldn't respond at all (stealth) but closed is good
Granted when I hit the external address from internal, NAT resolves this and does prompt the "managed page" but that is to be expected from internal
@aloychan - Are you definitely using an external / foreign connection for the DDNS connection? The fact that you are seeing the 192.168.0.211 address listed makes me think you are connected to the TL-R605 and trying to go OUT then back IN. NAT wont allow you to do this and will just forward you to the LAN interface.
Philbert wrote
I am unable to recreate this
Hitting both DDNS and IP (with and without :80) from an foreign network does not resolve for me. It appears to be blocked
Shields up test reports the port as CLOSED, ideally it shouldn't respond at all (stealth) but closed is good
Granted when I hit the external address from internal, NAT resolves this and does prompt the "managed page" but that is to be expected from internal
@aloychan - Are you definitely using an external / foreign connection for the DDNS connection? The fact that you are seeing the 192.168.0.211 address listed makes me think you are connected to the TL-R605 and trying to go OUT then back IN. NAT wont allow you to do this and will just forward you to the LAN interface.
@Philbert - Yes, you are fight I am trying to go OUT and then goes back INto my network. I just tried accessing my DDNS IP with :80 from OUTside my network and its not accessible already. Silly mistakes from my end. Tyvm for the support. Appreciate it.
