From owner-freebsd-current Tue Apr 14 13:36:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08315 for freebsd-current-outgoing; Tue, 14 Apr 1998 13:36:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA08303 for ; Tue, 14 Apr 1998 20:36:08 GMT (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 27333 invoked by uid 1001); 14 Apr 1998 20:36:02 +0000 (GMT) To: phk@critter.freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fixes for tcpdump with LPIP encapsulation In-Reply-To: Your message of "Tue, 14 Apr 1998 22:18:04 +0200" References: <1119.892585084@critter.freebsd.dk> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 14 Apr 1998 22:36:02 +0200 Message-ID: <27331.892586162@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Thus I'd like to have some comments from the good people on -current on > >whether this is the correct way of solving the problem, before I feed > >the changes back to the tcpdump/libpcap maintainers. > > I think using DLT_NULL or DLT_RAW is preferable. Changing tcpdump and > libpcap for the sake of LPIP really seems like overdoing it to me... That was my initial reaction too, but then I saw that BSDI had had their PPP and SLIP implementations given special types: #define DLT_SLIP_BSDOS 13 /* BSD/OS Serial Line IP */ #define DLT_PPP_BSDOS 14 /* BSD/OS Point-to-point Protocol */ So I thought - if it makes sense for BSDI, it might make sense for FreeBSD too. I'll look into using DLT_NULL or DLT_RAW. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message