Chris Flugstad wrote:
> Chris Buechler wrote:
>> On Thu, Apr 10, 2008 at 5:01 PM, Chris Flugstad 
>> <chris at cascadelink dot com> wrote:
>>  
>>>  Default GW was setup and correct.  these are ubiquit nano stations 
>>> in AP
>>> mode.  It hasnt worked for them, senao, or even an linksys WRT 
>>> behind it.
>>> but all ap's work behind a linksys WRT.   looks to be a problem with 
>>> m0n0.
>>>
>>>     
>>
>> Delete the NAT rule(s) you created for this, delete any WAN firewall
>> rules created for this, and re-add an Inbound NAT entry. Make sure you
>> check the "auto add firewall rule" box when you add it. Does it work
>> then?  If not, edit that auto-added firewall rule and enable logging
>> on it. Save and apply changes, try again, and check your firewall logs
>> to see if it's getting to you.
>>
>> -Chris
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>   
> So after a long response
>
> this is what nmap spits out.  even though i created a rule to allow on
> 4444 to 192.168.10.2 https
>
> not sure why its still blocking it.
>
> PORT     STATE    SERVICE
> 53/tcp   open     domain
> 443/tcp  open     https
> 1720/tcp filtered H.323/Q.931
> 4444/tcp filtered krb524
> 8000/tcp open     http-alt
>
>
> ---------------------------------------------------------------------
> 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
>
even with a pptp vpn into the m0n0wall, and vpn firewall passthrough 
which should allow me access to all interfaces/services/etc,  i cant 
ping the devices that i want to get to. 

this cant be a cooincedence.  its gotta be a bug.