From owner-freebsd-hackers Tue Oct 20 14:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04362 for freebsd-hackers-outgoing; Tue, 20 Oct 1998 14:17:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA04353 for ; Tue, 20 Oct 1998 14:17:19 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA08931; Tue, 20 Oct 1998 20:20:03 +0100 From: Luigi Rizzo Message-Id: <199810201920.UAA08931@labinfo.iet.unipi.it> Subject: Re: bpf write overwrites link level header? To: beekey@clark.net Date: Tue, 20 Oct 1998 20:20:02 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <362CB750.5ECC@clark.net> from "beekey@clark.net" at Oct 20, 98 12:15:57 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > it comes out correct). Looking briefly at the code in > /usr/src/sys/net/bpf.c, it appears that bpf may add its own link level > header. > > Anyone have any experience or fixes/workarounds for this? I don't think > that it is a NIC limitation due to some testing under NT. for sure it isn't a NIC limitation since i do specify my own header when doing bridging. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message