Claude Morin wrote:
> Hi Ugo,
> 
> I ran into this a couple of months ago, and Manuel explained it to me in 
> this mailing list message:
> http://m0n0.ch/wall/list/?action=show_msg&actionargs[]=140&actionargs[]=41
>  
> Briefly: the behaviour you're seeing is normal; reject works only when the 
> protocol is set to TCP or UDP. The firewall rule create/edit page even 
> mentions something about it:
> Reject only works when the protocol is set to either TCP or UDP (but not 
> "TCP/UDP") below.

You're right, sorry.
> 
> BTW, I searched for "reject block" in the mailing list archive to find 
> Manuel's answer.
> 

Effectively, I should have done my homework before posting.

> Hope this helps,
> Claude
> 
> On 4/21/05, Ugo Bellavance <ugob at camo dash route dot com> wrote:
> 
>>Hi,
>>
>>I've created a rule to deny any traffic from my DMZ interface to my
>>LAN, using the Reject option in the WebGUI. However, when I save, I get
>>back to the firewall_rules.php page and there is a red 'X' a the left of
>>my rule, while it should be a yellow 'X'. If i try connect to the lan,
>>it looks like a block as I don't get a rejected connection up front.
>>I've created a Reject rule for my LAN interface and all is ok (yellow
>>'X', immediate rejection).
>>
>>If you need more details, please let me know.
>>
>>Regards,
>>
>>Ugo
>>
>>---------------------------------------------------------------------
>>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 
>>
>>
> 
>