From owner-freebsd-questions Thu Jul 27 16:07:57 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id QAA12135 for questions-outgoing; Thu, 27 Jul 1995 16:07:57 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id QAA12129 for ; Thu, 27 Jul 1995 16:07:54 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id IAA08163; Fri, 28 Jul 1995 08:58:04 +0930 From: Michael Smith Message-Id: <199507272328.IAA08163@genesis.atrad.adelaide.edu.au> Subject: Re: bpf woes To: shawnb@ecst.csuchico.edu (Shawn Brown) Date: Fri, 28 Jul 1995 08:58:03 +0930 (CST) Cc: freebsd-questions@freebsd.org In-Reply-To: <199507272238.PAA10750@pitbull.ecst.csuchico.edu> from "Shawn Brown" at Jul 27, 95 03:38:34 pm Content-Type: text Content-Length: 1169 Sender: questions-owner@freebsd.org Precedence: bulk Shawn Brown stands accused of saying: > Recently I've upgraded to 2.0.5-RELEASE from 2.0-RELEASE. For the life of > me I can't figure out why I can't get the bpf devices to attach to my > network interfaces. I have an ep (3c509), sl, ppp, lo, and tun. I have > allocated 6 bpf devices in the kernel config, yet when I boot on the new > kernel, the bpf devices don't attach, and when I try and run tcpdump on > any of the interfaces that are up, it tells me that /dev/bpf? is not > configured. > > Anyone know what's up? Yeah, the bpf pseudo-device isn't configured in your kernel. It wasn't with 2.0R either, IIRC, so you must have gone through this at least once before 8) Read the FAQ on rebuilding your kernel, and study the LINT example to see how to configure bpf. > Shawn -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[