Thank you very much for the help on this. I have another question...
I set up a redirect on the WAN interface to an internal host, but it
does not seem to be working.. I actually have two setup.
One accepts connections on the WAN interface HTTPS port and redirects
it to the m0n0wall box HTTPS port to allow me to access the web interface
externally, as there is no option in m0n0wall to allow this. I did not
really expect this to work, and it doesn't.
The other redirects port 80 on the WAN interface to port 80 on my access
point to allow me to configure this externally. This is not working either.
I figure I must be doing something wrong, but I can't figure out what.
I should note that the "WAN" interface is actually connected to my internal
LAN, which is NAT'd and firewalled, so there is no danger of external
hosts being able to connect to the web configuration interfaces of these
A suggestion to the m0n0wall developers, please add an option to allow
through the WAN for those of us connecting it to a LAN!
> ----- Original Message -----
> From: "edward mzj" <edward underscore mzj at yahoo dot com dot cn>
> To: "Zachary Miller" <znmiller at sbcglobal dot net>; <m0n0wall at lists dot m0n0 dot ch>
> Sent: Tuesday, May 31, 2005 2:55 AM
> Subject: RE:[m0n0wall] Web proxy
> > yes. but not so straight forward.
> > goto diagnotics->backup/restore, download the config.xml. open the file
> an text editor and add
> > the following sentences into the <nat> </nat> section. you have to do so
> 'cause m0n0 doesn't
> > support adding a rdr rule on lan interface through the web gui. remember
> to restore your modified
> > config.xml when done.
> > <rule>
> > <protocol>tcp</protocol>
> > <external-port>80</external-port>
> > <target>your-proxy-server-address</target>
> > <local-port>your-proxy-server-port</local-port>
> > <interface>lan</interface>
> > <descr/>
> > </rule>