From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 12:56:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7521516A4CE for ; Wed, 24 Mar 2004 12:56:31 -0800 (PST) Received: from postal1.es.net (proxy.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55B9243D2F for ; Wed, 24 Mar 2004 12:56:31 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Wed, 24 Mar 2004 12:56:30 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id BBEE45D0A; Wed, 24 Mar 2004 12:56:30 -0800 (PST) To: MaNUaL In-reply-to: Your message of "Wed, 24 Mar 2004 11:33:08 PST." <20040324193308.10312.qmail@web40613.mail.yahoo.com> Date: Wed, 24 Mar 2004 12:56:30 -0800 From: "Kevin Oberman" Message-Id: <20040324205630.BBEE45D0A@ptavv.es.net> cc: freebsd-current@freebsd.org Subject: Re: Berkeley packet filter device in kernel config X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Mar 2004 20:56:31 -0000 > Date: Wed, 24 Mar 2004 11:33:08 -0800 (PST) > From: MaNUaL > Sender: owner-freebsd-current@freebsd.org > > Hi. I am using 5.2.1-RELEASE-p3 and in the GENERIC > configuration file of the kernel in > /usr/src/sys/i386/conf there is the following line: > > device bpf # Berkeley packet filter > > Though, in the FreeBSD handbook it says: > > pseudo-device bpf # Berkeley packet filter > > I have used "device bpf" but there is no /dev/bpf* at > all... > > Am i missing something here? How should i define this? > pseudo-device or device? In V4 it's a pseudo-device. In V5, it's a device. In V5 devices are created by devfs and are dynamic. As a result, if you are not using any filer devices, they won't exist. Try running a tcpdump and, while it's running do 'ls /dev/bpf*'. Kill the tcpdump and do it again. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634