OK, thanks guys.  As I understand it, the FAQ page 16.18 needs some fixing.

First, the note should read something like:

   If you're already using HTTPS (port 443) in the Inbound NAT table,
   you'll need to supply a port number (e.g., 11443) in the General Setup
   page for the webGUIport.  Otherwise you can leave it blank which will
   default to HTTPS (443).  If you have supplied a port number, you will
   need to use that port number (under Destination port range) in place of
   the HTTPS shown in the following example.

Second, it should be noted that section 16.18.2 is obsolete for anyone 
using version 1.2b7 or later.

Please do correct me if I'm wrong.  Otherwise, will someone please amend 
the FAQ accordingly?  We're not all network engineers out here, and so it
is necessary to use words of one syllable or less when explaining things.

NHA
---
Norman H. Azadian    Taegerishalde 13    CH-3110 Muensingen    Switzerland
norman at azadian dot ch      tel: +41 31 721 7855      fax: +41 31 55 898 55


Manuel Kasper wrote:
> On 17.01.2006 17:27 +0100 Peter Allgeyer wrote:
> 
> 
>>you can connect to https://ip-of-firewall:11443/ from inside your
>>LAN. Now make a rule on the WAN interface for the outside IP to go
>>to your firewall external IP (or any, if you have obtained the
>>external IP address dynamically) at port 11443.
> 
> 
> Note: since 1.2b7, you don't even have to use 'any' as the
> destination anymore when you have a dynamic WAN IP address - you can
> simply choose "WAN IP address" from the menu, which will always match
> the current WAN IP address.
> 
> - Manuel
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>