News: This forum is now permanently frozen.
Pages: [1]
Topic: Apache behind m0n0wall?  (Read 4403 times)
« on: April 22, 2007, 16:43:47 »
infernalbyte *
Posts: 3

Hi

I have one problem.I have installed Apache on PC which is behind m0n0WALL and i tried to use no-ip dyndns application to forward requests from internet to my web server.When i type ip address i get m0n0wall login page. I have static LAN IP address on my pc and my m0n0wall pc have dynamic WAN address. How to setup m0n0wall to forward to my internal web server?
« Reply #1 on: April 22, 2007, 22:29:51 »
Mike *
Posts: 11

you must forward PORT 80 (http) at NAT and RULES

edit:
my m0n0wall-webgui runs on PORT 443 (https),
and my apache2 on Debian Box is forward on PORT 80 (http) Wink
« Last Edit: April 23, 2007, 11:57:35 by Mike »

-xdsl (WAN-PPPoE)
-router/firewall (monowall-1.231 WRAP.1E-2)
-LAN (192.168.1.x
« Reply #2 on: April 23, 2007, 03:28:13 »
cmb *****
Posts: 851

What you want is inbound NAT on port 80. You may need to change the port the webGUI uses, on the General page IIRC.
« Reply #3 on: April 23, 2007, 06:59:36 »
clarknova ***
Posts: 148

You may need to change the port the webGUI uses

Or for better security use HTTPS as the webGUI protocol (also on the General setup page) and use the default port. Since http uses port 80 and https uses port 443, port 80 will now be forwarded to your Apache server, assuming you have the right inbound NAT rule, as mentioned above by cmb.
« Reply #4 on: April 23, 2007, 10:27:45 »
bitonw **
Posts: 79

better is make the webGUI run on the following ports:

http 8080
https 1443

now you have the following ports advailable for your apache box

http 80
https 443

forward those ports (80&443) from the m0n0wall to that apache box.

now you can reach your m0n0wall on 8080 or 1443. the best thing is to connect via https (1443) to your m0n0wall, is more secure.
« Reply #5 on: April 24, 2007, 17:50:59 »
infernalbyte *
Posts: 3

here is problem.
my role in inbount nat config is like this:

   If           Proto     Ext. port range     NAT IP     Int. port range      Description
 WAN      TCP/UDP      8080                 10.1.17.2                 8080             my Apache

And,when i try to connect from outside to my Apache on ip - m0n0wall(wan ip address):8080 i get nothing, page not found,i dont know what is the problem. i use this version of m0n0wall -  1.2 built on Sun Oct 9 18:58:35 CEST 2005.

Thanks for all replys.
« Reply #6 on: April 25, 2007, 03:27:07 »
cmb *****
Posts: 851

Is your Apache actually running on port 8080 internally?
« Reply #7 on: April 26, 2007, 15:02:01 »
infernalbyte *
Posts: 3

my Apache is running all the time on my PC on port 8080 and problem is that from outside i cant get my apache hosted web pages. Can someone send example of inbound NAT configuration or to correct mine?
« Reply #8 on: April 26, 2007, 20:27:50 »
cmb *****
Posts: 851

did you check the "auto add firewall rule" box when you added NAT? Do you see anything in your firewall log when you attempt to access it from outside your network?
« Reply #9 on: April 27, 2007, 21:06:36 »
net-0 *
Posts: 5

Heh just messing around and checking m0n0 releases I stumbled onto the new forums woooo.....

Anyways, if you have apache running on port 8080, you know that you would need to specify when looking at it in your browser right?

Like for my webserver, I have http://theneto.com (since you don't need to specify port since 80 is default it would look like this http://theneto.com:80) <---- Ignore this if you already know.

For example my m0n0wall is on port 8080 so

http://theneto.com:8080 <--- m0n0
http://theneto.com:80 <--- apache
http://theneto.com:3784 <--- ventrilo

etc,etc,etc.

But ya, if you already knew this then maybe the above post is correct... when you add a nat rule you also want it to add a firewall rule too.

check that box,

good luck

--neto
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines