From owner-freebsd-security Tue Feb 2 12:34:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28321 for freebsd-security-outgoing; Tue, 2 Feb 1999 12:34:30 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from cc181716-a.hwrd1.md.home.com (cc181716-a.hwrd1.md.home.com [24.3.18.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28313 for ; Tue, 2 Feb 1999 12:34:27 -0800 (PST) (envelope-from woodford@cc181716-a.hwrd1.md.home.com) Received: (from woodford@localhost) by cc181716-a.hwrd1.md.home.com (8.9.1a/8.9.1a) id PAA01200 for security@FreeBSD.ORG; Tue, 2 Feb 1999 15:34:58 -0500 (EST) Date: Tue, 2 Feb 1999 15:34:58 -0500 From: Bill Woodford To: ML FreeBSD Security Subject: tcpdump Message-ID: <19990202153458.A1152@cc181716-a.hwrd1.md.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Forgive my ignorance, but I built tcpdump (3.4a3) and libcap (0.4a1) and it built beautifully. I read the docs, and that mentioned a few things to watch out for. However, when I run tcpdump (as root), it gives me: tcpdump: /dev/bpf0: Device not configured I did a little reading, and realize it's possible that my NIC may not support it (it's a 3com 3c509 combo), but how would one tell. Can anyone enlighten me as to the true nature of this error? Im running natd/ipfw, would that interfere with the functioning of tcpdump? Any help would be appreciated. Thanks. -- Bill Woodford * woodford@cc181716-a.hwrd1.md.home.com * ICQ:14076169 "Windows Multitasking: Messing up several things at once." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message