From owner-freebsd-net@FreeBSD.ORG Thu Apr 12 01:37:48 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9088916A401 for ; Thu, 12 Apr 2007 01:37:48 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id EEAA113C468 for ; Thu, 12 Apr 2007 01:37:47 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id l3C1bkJG044698 for ; Thu, 12 Apr 2007 09:37:46 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id l3C1bkiC044697 for net@freebsd.org; Thu, 12 Apr 2007 09:37:46 +0800 (KRAST) (envelope-from eugen) Date: Thu, 12 Apr 2007 09:37:46 +0800 From: Eugene Grosbein To: net@freebsd.org Message-ID: <20070412013746.GA44307@svzserv.kemerovo.su> References: <20070411144309.GA3456@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070411144309.GA3456@grosbein.pp.ru> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: ipfw tags & filtering incoming broadcasts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2007 01:37:48 -0000 On Wed, Apr 11, 2007 at 10:43:09PM +0800, Eugene Grosbein wrote: > There is no problem to filter unicasts. But I want also block all > broadcasts except of incoming RIPv2, some of hardware > routers send broadcasts instead of multicasts here. > > I've tried this way: I've just added a copy of rule 50 with number 35: > ipfw add 30 allow tag 1 ip from any to any MAC ff:ff:ff:ff:ff:ff any ipfw add 35 count log ip from any to any tagged 1 > ipfw add 40 allow ip from any to any layer2 > ipfw add 50 count log ip from any to any tagged 1 And I see that tag is kept during layer2 filtering stage but seem to be lost somewhere in space in transition to layer3 stage. So that is the question: is it a bug or featue? Eugene