Lee,

Good idea, but no, that wasn't it. I switched webGUI protocol to https 
and rebooted the firewall. I still get a connection timeout from the 
accessing browser, and no record of the access attempt in the log.

Thanks,
Steve

Lee Sharp wrote:
> From: "Steve Johnson" <sjohnson at warpdriveonline dot com>
>
>
>> Next, I set up a NAT rule to allow WAN traffic to access http on the DMZ
>> web server. I confirmed that m0n0wall also created the firewall rule
>> allowing the access. I modified the rule to log packets handled by this
>> rule.
>
>> Not only can I not access the http server from the WAN interface, I'm
>> not even seeing any inbound http in the log, Nothing, either passed or
>> blocked. I'm seeing typical  probing on ports 1025, 1026, 1027, 1029,
>> 1433, but nothing inbound from the WAN in the lower range.
>
> Is your m0n0wall web interface http or https?  If http, it could be 
> the antilockout rule.  Try changing m0n0wall to https and see if it 
> works.
>
>                        Lee
>
> ---------------------------------------------------------------------
> 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
>
>