Port Forwarding Change Made My Router's Web UI Unreachable

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Author Message
djcensored
DD-WRT Novice


Joined: 08 Jun 2012
Posts: 3
Location: Chicago, IL

PostPosted: Fri Jun 08, 2012 14:26    Post subject: Port Forwarding Change Made My Router's Web UI Unreachable Reply with quote
I have a Linksys WRT54G (don't know what version) with six ports forwarded. One of the forwards is for HTTP (80) to a specific server for my personal web site. I added a second server for a game, and the administration UI for the game is also web-based, so I forwarded all incoming port 81 requests to port 80 on that server so I could access the second web site.

The problem started after I decided to change the incoming port forward of 81 to 8008, because 81 is usually reserved for Tor proxies. The change in forwarding for port 8008 worked fine; I can easily view the web site from outside my LAN (I am currently outside it), and all the other port forwards are working properly (HTTP-80, FTP, SSH, etc.).

The issue is that I can now no longer access the web UI for the router from inside OR outside the LAN. I'm currently unable to physically access the router to reset or reboot it, and I don't have SSH access enabled to the router. Is there any history of a problem such as this? Did the change in port numbers somehow mess with the router's web UI?

_________________
"Work is the curse of the drinking classes."
- Oscar Wilde
Sponsor
Fractal
DD-WRT Guru


Joined: 19 Apr 2010
Posts: 1243

PostPosted: Fri Jun 08, 2012 15:10    Post subject: Re: Port Forwarding Change Made My Router's Web UI Unreachab Reply with quote
djcensored wrote:
I have a Linksys WRT54G (don't know what version) with six ports forwarded. One of the forwards is for HTTP (80) to a specific server for my personal web site. I added a second server for a game, and the administration UI for the game is also web-based, so I forwarded all incoming port 81 requests to port 80 on that server so I could access the second web site.

The problem started after I decided to change the incoming port forward of 81 to 8008, because 81 is usually reserved for Tor proxies. The change in forwarding for port 8008 worked fine; I can easily view the web site from outside my LAN (I am currently outside it), and all the other port forwards are working properly (HTTP-80, FTP, SSH, etc.).

The issue is that I can now no longer access the web UI for the router from inside OR outside the LAN. I'm currently unable to physically access the router to reset or reboot it, and I don't have SSH access enabled to the router. Is there any history of a problem such as this? Did the change in port numbers somehow mess with the router's web UI?


I imagine you have a port forward loop possibly.. I would do a 30/30/30 and start over... do each forward until you find which one breaks it.... if you need further help let me know.

-Fractal
djcensored
DD-WRT Novice


Joined: 08 Jun 2012
Posts: 3
Location: Chicago, IL

PostPosted: Fri Jun 08, 2012 16:14    Post subject: Re: Port Forwarding Change Made My Router's Web UI Unreachab Reply with quote
Fractal wrote:
I imagine you have a port forward loop possibly.. I would do a 30/30/30 and start over... do each forward until you find which one breaks it.... if you need further help let me know.

What exactly would you think the port forward loop could be? All the forwards were working fine before the change, and they all work fine after the change. The only thing that's broken is accessing the router web interface.

_________________
"Work is the curse of the drinking classes."
- Oscar Wilde
barryware
DD-WRT Guru


Joined: 26 Jan 2008
Posts: 13049
Location: Behind The Reset Button

PostPosted: Fri Jun 08, 2012 16:25    Post subject: Reply with quote
the routers default http access port is 80. You are using that port to access you server(s).

So you need to change the default http lan port of the router for gui access.

Lets say you want to use port 8080.

from telnet or the commands tab:

nvram set http_lanport="8080"
nvram commit
reboot

you can now access the routers gui via port 8080

http://<router lan ip>:8080

_________________
[Moderator Deleted] Shocked
djcensored
DD-WRT Novice


Joined: 08 Jun 2012
Posts: 3
Location: Chicago, IL

PostPosted: Fri Jun 08, 2012 16:33    Post subject: Reply with quote
barryware wrote:
the routers default http access port is 80. You are using that port to access you server(s).

So you need to change the default http lan port of the router for gui access.

Lets say you want to use port 8080.

from telnet or the commands tab:

nvram set http_lanport="8080"
nvram commit
reboot

you can now access the routers gui via port 8080

http://<router lan ip>:8080

This would seem a likely cause of the issue if it weren't for the fact that the router's web interface was always accessible (internally on 80 and externally on 8080) before the changes while there were two port forwards (external ports 80 and 81) to two separate servers on the LAN. Plus, the router only forwards requests from outside the LAN, correct?

How exactly would this be the problem after only changing the external forward of 81 to 8008?

_________________
"Work is the curse of the drinking classes."
- Oscar Wilde
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum