From owner-freebsd-net@FreeBSD.ORG Fri Apr 18 21:30:57 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75DF237B401 for ; Fri, 18 Apr 2003 21:30:57 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DB8843FE9 for ; Fri, 18 Apr 2003 21:30:56 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h3J4UtVi031606; Sat, 19 Apr 2003 00:30:55 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h3J4Ut5f031605; Sat, 19 Apr 2003 00:30:55 -0400 (EDT) Date: Sat, 19 Apr 2003 00:30:55 -0400 From: Barney Wolff To: Jeremy Chadwick Message-ID: <20030419043055.GA31406@pit.databus.com> References: <20030418174956.GA71335@parodius.com> <20030418200936.82331.qmail@web10410.mail.yahoo.com> <20030418201645.GA77986@parodius.com> <20030418220229.GB39466@blossom.cjclark.org> <20030418235214.GB85777@parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030418235214.GB85777@parodius.com> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) cc: freebsd-net@freebsd.org Subject: Re: BIND-8/9 interface bug? Or is it FreeBSD? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Apr 2003 04:30:57 -0000 On Fri, Apr 18, 2003 at 04:52:14PM -0700, Jeremy Chadwick wrote: > Since when? :-) That wouldn't make very much sense, and > would be extremely misleading for network administrators. > bpf should have the highest priority, well above ipfw. > > I just verified that fact with a test: blocking any telnet I/O > across my public interface and telnetting in from my home > workstation: You didn't listen to the answer: bpf is closer to the driver than ipfw, so it will see inbound packets that ipfw will block, but not see outbound packets that ipfw has already blocked. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.