[ previous ] [ next ] [ threads ]
 
 From:  "Justin Albstmeijer" <justin at VLAMea dot nl>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] https interface not available
 Date:  Mon, 7 Jun 2004 13:38:10 +0200 (CEST)
doing an arping I see that 2 soekris interfaces are replying to the ip
number of the LAN port.

The WAN/OPT1 ports are in bridging mode, and WAN is configured as DHCP
(see "bridge+filter, without NAT problem" posting)

60 bytes from 00:00:24:c1:66:c0 (192.168.1.3): index=0 time=430.107 usec
60 bytes from 00:00:24:c1:66:c2 (192.168.1.3): index=1 time=517.130 usec

>>
>> It should ALWAYS be possible to connect from the LAN. In fact, there is
>> a builprobablyewall rule for this special case.web interface
>>
>> The source code reads:
>>
>> # make sure the user cannot lock himself out of the webGUI
>> pass in quick from $lansa/$lansn to $lanip keep state group 100
>>
>> Just let me know if I'm wrong...
>
>
> You are probarly right, but still I can't connect to the webinterface.
> So is there a way to debug this problem? without resetting to defaults.
>
>
>>
>> -- Vincent
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> 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
>
>
>