Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 26 Nov 2005 22:15:56 -0500
From:      Chuck Swiger <cswiger@mac.com>
To:        Alexandre DELAY <alexandre.delay@free.fr>
Cc:        freebsd-ipfw@freebsd.org
Subject:   Re: Protocol filter capabilities
Message-ID:  <438924EC.7000505@mac.com>
In-Reply-To: <MAEBLPAGHGPMOKCBICBNIENPCIAA.alexandre.delay@free.fr>
References:  <MAEBLPAGHGPMOKCBICBNIENPCIAA.alexandre.delay@free.fr>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Alexandre DELAY wrote:
> I am looking for an efficient way to filter different protocols, such as
> edonkey or BEEP.  For the moment, I think that ipfw doesn't support it.

Sure it does.  Start with "deny all" [1] and then add the minimum required open 
ports, preferably only for a proxy server that the clients are required to use 
for all outside access.  Specificly, look at and combine the closed and simple 
firewall types in /etc/rc.firewall.

You might also try to use bandwidth shaping to prioritize P2P behind more 
useful traffic like VOIP.

> Don't you think that it would be a nice thing to be able to include such
> "filters" from, for example, ethereal?
> Ethereal support more than 34k different protocols. It woul be nice to be
> able to choose from those filters and to apply some rules according to those
> filters.

You're talking about a reactive IDS.  You can rig them up using scripts which 
monitor logfiles, or something like /usr/ports/security/snort.

However, I prefer to use IDS for traffic I permit but want to monitor, not 
traffic I already know I want to block.

-- 
-Chuck




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?438924EC.7000505>