From owner-freebsd-net Fri Mar 26 10:20:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id B27A714C08 for ; Fri, 26 Mar 1999 10:20:13 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id KAA86181; Fri, 26 Mar 1999 10:19:22 -0800 (PST) From: Archie Cobbs Message-Id: <199903261819.KAA86181@bubba.whistle.com> Subject: Re: bpf bug? In-Reply-To: <262C3DA9BE0CD211971700A0C9B413A1CBEF@exchange.maxwell.syr.edu> from Christopher Sedore at "Mar 26, 99 11:17:17 am" To: cmsedore@maxwell.syr.edu (Christopher Sedore) Date: Fri, 26 Mar 1999 10:19:22 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christopher Sedore writes: > I noticed today that when sending a packet through the bpf interface, > the kernel silently resets the ethernet source MAC to the MAC of the > network card doing the send. My impression was that bpf writes should > go direct to the interface without any edits in the kernel--am I wrong > on this? My opinion on this is that yes it's a bug. However, it's not so easy to fix, because other parts of the kernel surely rely on this behavior. To fix it would probably require a new argument to if_output() (or whatever it's called) or perhaps a new mbuf flag. I suggest you file a PR and see what comes back :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message