From owner-freebsd-security  Wed Feb  3 06:57:51 1999
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA18184
          for freebsd-security-outgoing; Wed, 3 Feb 1999 06:57:51 -0800 (PST)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from carp.gbr.epa.gov (carp.gbr.epa.gov [204.46.159.110])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18179
          for <security@freebsd.org>; Wed, 3 Feb 1999 06:57:47 -0800 (PST)
          (envelope-from mjenkins@carp.gbr.epa.gov)
Received: (from mjenkins@localhost)
	by carp.gbr.epa.gov (8.8.8/8.8.8) id IAA05247;
	Wed, 3 Feb 1999 08:57:23 -0600 (CST)
	(envelope-from mjenkins)
Date: Wed, 3 Feb 1999 08:57:23 -0600 (CST)
From: Mike Jenkins <mjenkins@carp.gbr.epa.gov>
Message-Id: <199902031457.IAA05247@carp.gbr.epa.gov>
To: jkh@zippy.cdrom.com
Subject: Re: tcpdump
Cc: security@FreeBSD.ORG
In-Reply-To: <9575.918011566@zippy.cdrom.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 02 Feb 1999 "Jordan K. Hubbard" wrote:

> OK, time to raise this topic again.  What to people think about
> enabling bpfilter by default in GENERIC?

When I switched from Linux to FreeBSD, it was disappointing to
find that tcpdump did not work.  It had worked fine under Linux.
I vote to enable bpfilter.

BTW, the "/dev/bpf0: Device not configured" problem is in the FAQ.

Mike

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message