amorvivir
join:2004-11-05
Salt Lake City, UT
| rt314 server
Some advice please, I have been trying to configure my home box to be a web server for awhile now. I have cable internet with comcast, and a rt314 router. I have apache installed and can see my site internally (local network). I configured port forwarding in the rt314 for port 80 to go to my server, however, when I do "http://"{external ip} I get the router... My portforwarding config reflects (I think) my server. This is how it looks in rt314 config:
default 0.00.00.00
80 192.168.0.3 (server ip)
00 0000000...
I dont know what I am missing. I even installed an upgreade firmware and still no luck. Does anyone have anysuggestions?
Thanks-
Scott. |
|
Anav
Sarcastic Llama? Naw, Just Acerbic
Premium
join:2001-07-16
Dartmouth, NS | Been awhile. Is there a remote management menu in the RT3114? |
|
decx
Premium
join:2002-06-07
Vancouver, BC
 ·Bell Sympatico
| reply to amorvivir
Are you trying the access the server using the external address from the internal LAN? If so you can't since the RT314 doesn't have a loopback feature. You'll either have to access it with the internal address or by editing your local HOST file to point the URL at the local IP. |
|
amorvivir
join:2004-11-05
Salt Lake City, UT
| thanks for the attention so far to my post, first, there is an interface to the router rt314 and I use that or telnet to it. Secondly, I dont know what you meant by pointing the URL to the local host. I dont know what a loopback feature is either. decx suggested I "access it with the internal address or by editing your local HOST file to point the URL at the local IP," would you please explain these two options?
Thanks again,
Scott. |
|
decx
Premium
join:2002-06-07
Vancouver, BC | Hmm... can you just clear something up first? Are you having problems accessing your server from outside your LAN (on the Internet) or from inside your LAN (your local network)? |
|
Anav
Sarcastic Llama? Naw, Just Acerbic
Premium
join:2001-07-16
Dartmouth, NS | Yes, when other people try to reach your server ie friends from the WAN does it work fine??? |
|
Bobcat
Premium
join:2001-02-04
Bedminster, NJ
·Verizon Online DSL
| reply to amorvivir
You can't access your server when using the regular IP address from within your network. Have a friend try to access your server; it will probably work fine.
--
"I truly am not that concerned about him."
Pres. Bush on Osama bin Laden, March 13, 2002 |
|
amorvivir
join:2004-11-05
Salt Lake City, UT
| Yes that is the problem, I am unable (friends are unable) to get into my server's web page. The result is a page fault "page cannot be displayed..." I can however see my site from within my network. I have two computers on my local network, one is the server and the other is a laptop. The laptop can see the web site on the server with the server's internal IP ie 192.168.0.2. When I try to access the external IP ie 66.249.64.169 with the laptop or the server box I get the router rt314. Hope that explains it.
Scott |
|
decx
Premium
join:2002-06-07
Vancouver, BC
·Bell Sympatico
1 edit | The problems you described are caused by two separate features (or lack of) of the RT314.
1. When you try to access your webserver with the external IP (or URL) you get the router's config page because the RT314 lacks a loopback feature. So you'll have to use the internal address when you want to access your server when inside the LAN. (The other option is editing the HOST file, not really necessary in your case.)
2. Your friends can't access your server from the outside even with your port 80 forward (and assuming your ISP doesn't block port 80) is because of RT314's packet filter. By default the RT314's filter is configure to drop all incoming requests on that port so any web server on the standard port inside the network can't be accessed outside. To make the server accessible you'll need to configure the filter to forward the the packets. The procedure on how to do that is explained here. |
|
Bobcat
Premium
join:2001-02-04
Bedminster, NJ
·Verizon Online DSL
| reply to amorvivir
You say you upgraded the firmware. Was that to version 3.25? When you did that, did you also load the default configuration file?
--
"I truly am not that concerned about him."
Pres. Bush on Osama bin Laden, March 13, 2002 |
|
SYNACK
Just Firewall It
Premium,Mod
join:2001-03-05
Venice, CA
 ·Comcast Formerly ..
Host:
Networking
Virtual Private Ne..
Netgear
ZyXEL
| As other have mentioned, there are two issues:
(1) No loopback support: This causes the router to show its own internal web server if you browse to its public IP from the LAN side.
(2) The packet filter that decx mentioned is obsolete. It was only used on older firmware. Version 3.25 has no need for these packet filters because it allows now to configure the remote administration in menu 24.11. If filter #3 is still activated, it most likely means that you are still running and old configuration because you only updated the firmware but not the configuration file. While you could just edit filter #3, it is highly advised to reset to the 3.25 defaults first, then configure everything from scratch (and never re-use any old configuration files again!). There are quite a few other changes (e.g. to autoexec.net and to the default settings in 24.11) that are highly recommended, but will only be there if you reset to the new 3.25 defaults. |
|
amorvivir
join:2004-11-05
Salt Lake City, UT | reply to amorvivir
Just wanted to thank everyone for their comments. I ll give these filtering ideas a try. |
|
amorvivir
join:2004-11-05
Salt Lake City, UT
| reply to amorvivir
Well you were right SYNACK, I didnt have the new config active. I loaded it and then changed 24.11 #3 to my server box IP. The only change that occured was that now my external IP causes a page default, where as before it took me to the router. PROGRESS, I hope. In case you are wondering if my web page works, it does- atleast it does internally on my laptop with the internal 192.168.0.2 IP.... |
|
SYNACK
Just Firewall It
Premium,Mod
join:2001-03-05
Venice, CA | No, 24.11 is NOT for port forwarding. Leave everything there at the defaults.
You only need to forward port 80 to the LAN ip of the server in menu 15. |
|
