I would point it to 127.0.0.1, not your internal LAN IP. (probably not
an issue though)
It is a two-part process to allow what you want. You did step #2, but
missed step #1. :)
Step #1: You need to make sure that you have an INBOUND NAT rule
configured to map incoming WAN conections on port 81 to 127.0.0.1
Step #2: THEN you add the firewall rule to actually alow these
To save time, can even select "Auto-add a firewall rule to permit
traffic through this NAT rule" when adding the INBOUND NAT rule so there
is no need for step #2 in that case. :)
If, however, you are like me and are a bit anal retentive about who is
allowed to connect to your web GUI on the M0n0, you might consider
visiting the firewall rules and limit the SOURCE IP to an IP or block of
IPs that you own so that the whole world is not allowed to hit the web
waa dash m0n0wall at revpol dot com
Peter Parnican wrote:
> Hi guys, pls. could me help someone with this problem:
> I have moved from 1.1 to 1.2b3 and now I have problem to reach m0n0
> webGui from wan side.
> Here are my WAN firewall rules:
> Proto / Source / Port / Destination
> TCP / * / * / 192.168.100.1/ 80 - 81
> (*..only for tests, it will change as soon as it will start working)
> My m0n0 is working at 192.168.100.1 and port 81 - without https, yet).
> All others settings are by defaul.
> My Public (WAN) IP address is 213.215.11X.XXX.
> What i did wrong or what i forgot?
> Thx. in advance, Peter