Peter B. wrote:
> Hi all
> I have a problem with monowall
[..]
> This is my setup:
> 
> 
> Internet <-> Monowall <-> LAN
> 
> My LAN Port got ip 172.16.1.1/24
> In the LAN I have a public ip-range on a device where the routing and 
> everything is right configured.
> I can see drops in firewall log when I try to ping something out in the 
> internet or do other communications.
> 
> 
> Now I setup the following rule at the LAN Interface:
> UDP      62.12.146.138       5060       212.55.198.140       5060      
> 62.12.146.138 -> SIP to 212.55.198.140
> 
> The following I see in the filter log:
> LAN      62.12.146.138, port 5060      212.55.198.140, port 5060      UDP
> LAN     62.12.146.138, port 5060     212.55.198.140, port 5060     UDP
> LAN     62.12.146.138, port 5060     212.55.198.140, port 5060     UDP
> 
> (???)
it is ok.
> 
> So why is mono blocking this traffic even when I specify the RIGHT rule 
> on the LAN Interface?

> 
> Do I have to specify the same rule again on the WAN Interface?
> 
> 
> I don't know what more to troubleshoot in this case.
> 
> 
> Remember 62.12.146.138 is routed on my local 172.16.1.0/24 network.
It seems that you have a missmatch between NAT-routing an bridging.
I can see better, if i see your config.xml
bye
Christoph

> 
> 
> Thanks for any answer
> 
> 
> Peter
> 
> ---------------------------------------------------------------------
> 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
> 
> 

-- 
last words:
"let's make the backup tomorrow"