From owner-freebsd-hackers Thu Jun 17 11: 2: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 4D5E515137 for ; Thu, 17 Jun 1999 11:02:02 -0700 (PDT) (envelope-from brooks@one-eyed-alien.net) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id LAA01274; Thu, 17 Jun 1999 11:01:56 -0700 (PDT) From: brooks@one-eyed-alien.net X-Authentication-Warning: orion.ac.hmc.edu: brdavis owned process doing -bs Date: Thu, 17 Jun 1999 11:01:55 -0700 (PDT) X-Sender: brdavis@orion.ac.hmc.edu To: Christopher Sedore Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: changes to ether_output() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Jun 1999, Christopher Sedore wrote: > I filed a kernel bug report about this early this year. This is a bug in > the BPF implementation on FreeBSD (at least this was the consensus of > those who reacted when I posted about it). If you look in the gnats pages > you'll find my report and a patch to fix bpf. I don't remember the code > well enough to envision what your patch does, but you might want to look > over mine just to see what I did (it didn't look to me like you fixed bpf, > but maybe I'm missing that). It looks like they should both work. The difference is that your patch changes bpf to use AF_LINK and adds handling code and mine changes the way AF_UNSPEC is implemented so that the provided ethernet header is actually used. One could argue that if you pass in an ethernet header, you should be able to expect it is acutally used. On the other hand, one could argue that unless you tell the system you want to communicate at the link layer, it shouldn't let you mess with your link layer settings. Does anyone know what the historical answer would be? -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message