From owner-freebsd-hackers Sun Feb 7 23:24:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26819 for freebsd-hackers-outgoing; Sun, 7 Feb 1999 23:24:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA26804 for ; Sun, 7 Feb 1999 23:24:31 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 7956 invoked by uid 1001); 8 Feb 1999 07:24:29 +0000 (GMT) To: des@flood.ping.uio.no Cc: fenner@parc.xerox.com, hackers@FreeBSD.ORG, nsouch@FreeBSD.ORG, wpaul@FreeBSD.ORG, jkh@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au Subject: Re: Regarding tcpdump and plip In-Reply-To: Your message of "08 Feb 1999 04:53:19 +0100" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 08 Feb 1999 08:24:29 +0100 Message-ID: <7954.918458669@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Dag-Erling Smorgrav writes: > > The first of the two attached patches (hopefully) fixes the bpf > > problem. It compiles and links, but I haven't tested it yet (waiting > > for make world to complete). > > Well, it's 5 am over here and I finally got it licked :) It was a > little hairier than I thought because a) I can't just barge in and set > LPIPHDRLEN to 4, because it's used by non-bpf-related stuff, and b) > the transmit loop in lpoutput() modified the m_len field in each mbuf > along the chain *before* passing it on to bpf; Yup. Already noted by several people, I sent patches for this (among other things) to -current 14. April last year. Search for "Fixes for tcpdump with LPIP encapsulation". Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message