Keep Outside Users From Seeing my Router Stuff HELP

[iamdarkyoshi]

I am using freedns for my minecraft server because I have a dynamic IP. However, if I try to visit the URL that I have from freedns in my web browser, it shows my router's config page!!! If I try to click something, THEN it gives me a 401. My router is running DD-WRT Firmware. I followed the guides on the freedns page and the guide on the DDWRT page. I am terrible at networking.

[brwainer]

Test from somewhere else, like the library or from you phone when it it's using cellular to verify that the router page is indeed visible from outside. You might just be seeing unusual behavior by trying to connect to your public IP address from behind the router. If the router page definitely shows up when viewed from another connection, then you need to change the settings on the admin page for remote management. I'm not in front of my DD-WRT router so I don't remember which page that is exactly.

[schizznick]

Typically routers using NAT apply port forward rules to packets hitting the WAN not packets hitting from the LAN side. So as brwainer said you should test from outside your network.

[Wombo]

Check your router settings. If you have an option like "enable configuration from wwan" just disable that, it won't let people connect to the router's management plane unless they are on the local subnet.

[iamdarkyoshi]

Check your router settings. If you have an option like "enable configuration from wwan" just disable that, it won't let people connect to the router's management plane unless they are on the local subnet.

if I visit the psgr internally, it bring up the config menu.once I click anything then it prompts for a password.

[iamdarkyoshi]

Outside of the network (my phone) it does NOT seem to give me my router page. However, nothing else loads on my phone, so there's that.

[brwainer]

Outside of the network (my phone) it does NOT seem to give me my router page. However, nothing else loads on my phone, so there's that.

This makes perfect sense because so far it sound like you have not forwarded port 80 (used for HTTP) to anything inside your network, so the website request is stopping at the router.

[iamdarkyoshi]

This makes perfect sense because so far it sound like you have not forwarded port 80 (used for HTTP) to anything inside your network, so the website request is stopping at the router.

Everything seems to be working properly now.

[Wombo]

This makes perfect sense because so far it sound like you have not forwarded port 80 (used for HTTP) to anything inside your network, so the website request is stopping at the router.

You wouldn't need a port forward to access the web management API from the outside if you have the WAN address and WAN configuration is enabled. You are not connecting to anything inside the network, you're connecting to the external IP of the gateway.

 

I know this isn't totally relevant now as the OP seems to have his issue resolved, but just something to keep in mind.