From owner-freebsd-stable@FreeBSD.ORG Sun Jul 13 19:32:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2383237B404 for ; Sun, 13 Jul 2003 19:32:00 -0700 (PDT) Received: from sccimhc02.asp.att.net (sccimhc02.asp.att.net [63.240.76.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 117EC43FA3 for ; Sun, 13 Jul 2003 19:31:59 -0700 (PDT) (envelope-from david.fleck@mchsi.com) Received: from grond.sourballs.org (12-216-12-166.client.mchsi.com[12.216.12.166]) by sccimhc02.asp.att.net (sccimhc02) with ESMTP id <20030714023156im200088kte>; Mon, 14 Jul 2003 02:31:57 +0000 Received: from grond.sourballs.org (localhost [127.0.0.1]) by grond.sourballs.org (8.12.3p2/8.12.3) with ESMTP id h6E2VX9Z098611 for ; Sun, 13 Jul 2003 19:31:44 -0700 (PDT) (envelope-from david.fleck@mchsi.com) Received: from localhost (dcf@localhost)ESMTP id h6E2VV5A098608 for ; Sun, 13 Jul 2003 21:31:33 -0500 (CDT) (envelope-from david.fleck@mchsi.com) X-Authentication-Warning: grond.sourballs.org: dcf owned process doing -bs Date: Sun, 13 Jul 2003 21:31:31 -0500 (CDT) From: David Fleck Sender: dcf@mchsi.com To: freebsd-stable@freebsd.org In-Reply-To: <200307132345.h6DNjjl00941@tuscan.xciv.org> Message-ID: <20030713212630.L98478@grond.sourballs.org> References: <13297.1057943729@xciv.org> <20030712160130.GA43097@praxis.lunabase.org> <20030713180605.Y98302@grond.sourballs.org> <200307132345.h6DNjjl00941@tuscan.xciv.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Running ethereal on FBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 02:32:00 -0000 On Mon, 14 Jul 2003, Paul Civati wrote: > You will need to do this as root, what does -D actually do? ethereal man page: Network interface names should match one of the names listed in "tethereal -D". tethereal man page: -D Print a list of the interfaces on which Tethereal can capture, and exit. Note that "can capture" means that Tethereal was able to open that device to do a live capture; if, on your system, a program doing a network capture must be run from an account with special privileges (for example, as root), then, if Tethereal is run with the -D flag and is not run from such an account, it will not list any interfaces. > You need bpf device to capture packets from ethernet interfaces, > do you have bpf in your kernel? ahh, that's it. Time to recompile. Will this require creating the /dev/bpf device file as well? -- David Fleck dcf@aracnet.com