From owner-freebsd-questions Wed Nov 29 05:05:41 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA13377 for questions-outgoing; Wed, 29 Nov 1995 05:05:41 -0800 Received: from po9.andrew.cmu.edu (PO9.ANDREW.CMU.EDU [128.2.10.109]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA13372 for ; Wed, 29 Nov 1995 05:05:38 -0800 Received: (from postman@localhost) by po9.andrew.cmu.edu (8.7.1/8.7.1) id IAA01594 for freebsd-questions@freefall.FreeBSD.org; Wed, 29 Nov 1995 08:05:34 -0500 Received: via switchmail; Wed, 29 Nov 1995 08:05:34 -0500 (EST) Received: from unix22.andrew.cmu.edu via qmail ID ; Wed, 29 Nov 1995 08:04:03 -0500 (EST) Received: from unix22.andrew.cmu.edu via qmail ID ; Wed, 29 Nov 1995 08:04:01 -0500 (EST) Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.unix22.andrew.cmu.edu.sun4c.411 via MS.5.6.unix22.andrew.cmu.edu.sun4c_411; Wed, 29 Nov 1995 08:04:01 -0500 (EST) Message-ID: Date: Wed, 29 Nov 1995 08:04:01 -0500 (EST) From: Robert N Watson To: freebsd-questions@freefall.FreeBSD.org Subject: Re: 2.1.0-RELEASE, bpfilter w/CAP problem CC: freebsd-questions@freefall.FreeBSD.org In-Reply-To: <199511290428.UAA00465@corbin.Root.COM> References: <199511290428.UAA00465@corbin.Root.COM> Sender: owner-questions@FreeBSD.ORG Precedence: bulk Excerpts from internet.computing.freebsd-questions: 28-Nov-95 Re: 2.1.0-RELEASE, bpfilter.. David Greenman@Root.COM (773) > 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... OK, well, I don't know quite what it was, but suddenly it started working when you said "Hmmm. It should work..." therefore I no longer have a problem. ah well. Some of the things I tried were deleting the bpf/bpfilter /dev entries and recreating, etc. It may just have been a fluke, and unless it ceases working, I'll leave it be. On thing I did note that was weird in my upgrade was this.. Under FreeBSD 2.0.5, the following resolv.conf worked: -- domain watson.org nameserver 127.0.0.1 nameserver 128.2.35.50 searchlist watson.org res.cmu.edu andrew.cmu.edu -- Under 2.1.0, the searchlist entry had to be changed manually to search -- whether this was just a change in the resolve code, an error in my previous file, or whatever, I don't know.. ---- Robert Watson (rnw+@andrew.cmu.edu) * Double major: IDS/CS * H&SS http://www.watson.org/ robert@fledge.watson.org