Date: Mon, 08 Feb 1999 08:24:29 +0100 From: sthaug@nethelp.no 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 Message-ID: <7954.918458669@verdi.nethelp.no> In-Reply-To: Your message of "08 Feb 1999 04:53:19 %2B0100" References: <xzpsoch1rgw.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> Dag-Erling Smorgrav <des@flood.ping.uio.no> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7954.918458669>