From owner-freebsd-bugs  Thu Jun 15 15:41:24 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id PAA11684
          for bugs-outgoing; Thu, 15 Jun 1995 15:41:24 -0700
Received: from beandorf.epilogue.com (beandorf.epilogue.com [128.224.1.153])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA11674
          for <freebsd-bugs@freefall.cdrom.com>; Thu, 15 Jun 1995 15:41:22 -0700
Received: (from alan@localhost) by beandorf.epilogue.com (8.6.9/8.6.9) id SAA02037; Thu, 15 Jun 1995 18:41:15 -0400
Date: Thu, 15 Jun 1995 18:41:15 -0400
Message-Id: <15Jun1995.180039.Alan@Epilogue.Com>
From: Alan Bawden <Alan@Epilogue.Com>
To: fenner@parc.xerox.com
CC: freebsd-bugs@freefall.cdrom.com
In-reply-to: Bill Fenner's message of Wed, 14 Jun 1995 18:05:27 PDT <95Jun14.180529pdt.49859@crevenia.parc.xerox.com>
Subject: kern/512: writing to bpf(loopback) causes kernel panic 
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

   Date: Wed, 14 Jun 1995 18:05:27 PDT
   From: Bill Fenner <fenner@parc.xerox.com>
   Note that the BPF man page says

	...Currently,  only
	writes to Ethernets and SLIP links are supported.

(Ignoring the fact that the bpf man page is missing from freebsd-2.0...)
Yeah I read that -- but if I believed everything the man pages told me I
wouldn't ever get anything done!  Looking at the kernel sources made it
clear that somebody -thought- that writing to the loopback interface was
supposed to work.

   Try these patches.

Next time I'm in a position to re-boot that machine with a new kernel I'll
give it a try.  Thanks for the prompt response!