[youdsmedia]

Hi

Sorry to blag but I can't access port 80 and Google is confusing "web server" with the dd-wrt "web interface" queries so I thought I'd try and write a reasonably informed post with hope of getting an answer for this.

So basically I have Apache running from a stand alone tower server (16GB RAM, 24 Cores, you got it) and want to access the servers web site provision without hitting a failed to load page.

SSH is working so I have the right IP address, tried adding port 80 forwarding rule (did not know what I was doing) and entered 255.255.255.0 for Sub Network and then the IP address and ports for the forwarding rule, appropriately.

If someone can please tell me the answer I hope it helps somebody else spending 1.5 hours finding this info, as well as me.

Kind regards

[kernel-panic69]

It would help to know what router and what build revision number of DD-WRT you are running and from which side of router you are trying to access the apache server.

[mrjcd]

Not sure why some have troubles with such.
I use Port Range Forwarding and have for many years without a problem

NOTE: when you make changes there and Save / Apply Settings it may take 15 ~ 20 seconds before it all take affect.
If you imediately 'Apply Settings' and try to access what is forwarded you will likely get router webif wanting you to login...
... started doing this 'bout a year or so back --- but hell 15 ~ 20 seconds is fine with me

As you can see I have three devices that I forward 80 to depending on what I'm doing to their Apache servers.
Right now the Apache webserver is running to public via a wireless machine I just got & setup yesterday...
...I tend to swap what is running to public when I'm doing updates or whatever but all webservers are synced so it don't make no nevermind.
The other two I have ports 'blocked-out' are OVPN servers running on WAPs within my local net.


Main router is an EA8500 but works same whatever I have in as main gateway router.
I also always access webserver via its public domain name (NAT loopback) and/or I access the others that are not forwarded by their local name via local DNS

[ho1Aetoo]

[youdsmedia]

[kernel-panic69]

Saying "latest firmware" is kind of ambiguous. Do you mean 40559 or do you mean 43192? Also, you have a Marvell device, not Atheros.

[youdsmedia]

So yeah, I went ahead and added in port 80 as in screenshot given but no change.

See attached, contains firmware version too.

[mrjcd]

pic shows that router don't have a public WAN
...so you must forward port 80 to it (192.168.2.7) or put it in DMZ --- and then from router in pic forward port 80 to 192.168.1.129 (if that is the webserver IP)

oh yea, ---- that is a really old - NOT-so-good DD-WRT build showing in the pic

[kernel-panic69]

[youdsmedia]

Thanks guys - hope this forum post helps somebody else.

[youdsmedia]

So I followed the advice and upgraded firmware. Put "7" into the "DMZ" page under "NAT / QoS" and have the following put into "Port Range Forwarding"

Application Start End Protocol IP Address Enable
HTTPD 80 80 192.168.1.129

Now I am going to try and setup a public WAN. I'll update with manipulations made soon(ish).

[youdsmedia]

So the first thing I noticed was that the wiki page returned is out of date by its own recognition (it says it on the page) https://wiki.dd-wrt.com/wiki/index.php/Public_Sub-Net_Over_Dynamic_WAN

I did try and follow the guide and couldn't find anything along the lines of "VLAN" under "Setup" so came back here.

Hoping somebody can point me in the right direction.

[youdsmedia]

Attached are the pages I reference. Enjoy.

[mrjcd]

youdsmedia, I think you a bit confused.

[youdsmedia]

Ahh. OK

And the port triggering is included in that too, is that correct?

I apologise in advance I have never studied networking.

All the best.