From owner-freebsd-questions  Tue Nov 28 20:28:56 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id UAA07714
          for questions-outgoing; Tue, 28 Nov 1995 20:28:56 -0800
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA07708
          for <freebsd-questions@freefall.freebsd.org>; Tue, 28 Nov 1995 20:28:43 -0800
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id UAA00183; Tue, 28 Nov 1995 20:28:41 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id UAA00465; Tue, 28 Nov 1995 20:28:06 -0800
Message-Id: <199511290428.UAA00465@corbin.Root.COM>
To: Robert N Watson <rnw+@andrew.cmu.edu>
cc: freebsd-questions@freefall.freebsd.org
Subject: Re: 2.1.0-RELEASE, bpfilter w/CAP problem 
In-reply-to: Your message of "Tue, 28 Nov 95 23:02:38 EST."
             <UkixhSO00YUzJCgUQQ@andrew.cmu.edu> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Tue, 28 Nov 1995 20:28:01 -0800
Sender: owner-questions@FreeBSD.ORG
Precedence: bulk

>I upgraded from 2.0.5 to 2.1.0 this afternoon -- I was running CAP to
>provide appleshare for then LAN I'm on, but when I recompiled the 2.1.0
>kernel with pseudo-device bpfilter 12, the bpf's failed to attach to my
>ethernet device on boot.  I deleted the /dev's for bpfilter, bpf0-11,
>and recreated them, and still no improvement.  It simply skips attaching
>them to ed0 (and any other device).  I did a strings of my /kernel, and

   As of FreeBSD 2.1, the bpf attach messages are only displayed with the -v
(verbose) boot option.

>the bpfilter code is definitely in there, as I get several bpfilter
>related messages.  When CAP tries to use bpf0, it gets a device not
>configured error.  Yes, I did copy in the new kernel source :).

   Hmmm. It should work...

-DG