Date: Tue, 28 Nov 1995 23:40:32 -0500 (EST) From: Robert N Watson <rnw+@andrew.cmu.edu> To: davidg@Root.COM Cc: freebsd-questions@freefall.freebsd.org Subject: Re: 2.1.0-RELEASE, bpfilter w/CAP problem Message-ID: <MkiyF0u00YUz9CgVAp@andrew.cmu.edu> In-Reply-To: <199511290428.UAA00465@corbin.Root.COM> References: <199511290428.UAA00465@corbin.Root.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
Excerpts from mail: 28-Nov-95 Re: 2.1.0-RELEASE, bpfilter.. David
Greenman@Root.COM (773)
> >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...
Is there any way I can find out what the various bpf's are attached to
post-boot, or get them listed in lsdev or such? Also, I noted that
lsdev does not show the presence of device psm, nor does wcd seem to be
listed ammong the probes on boot.. Thanks..
Robert
----
Robert Watson (rnw+@andrew.cmu.edu) * Double major: IDS/CS * H&SS
http://www.watson.org/ robert@fledge.watson.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MkiyF0u00YUz9CgVAp>