From owner-freebsd-current Tue Apr 14 13:19:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04975 for freebsd-current-outgoing; Tue, 14 Apr 1998 13:19:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04969 for ; Tue, 14 Apr 1998 20:19:21 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id WAA01121; Tue, 14 Apr 1998 22:18:04 +0200 (CEST) To: sthaug@nethelp.no cc: freebsd-current@FreeBSD.ORG Subject: Re: Fixes for tcpdump with LPIP encapsulation In-reply-to: Your message of "Tue, 14 Apr 1998 00:47:50 +0200." <17850.892507670@verdi.nethelp.no> Date: Tue, 14 Apr 1998 22:18:04 +0200 Message-ID: <1119.892585084@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I fixed the problem with the link layer type by defining a *new* link >layer type (DLT_LPIP). This seems to me to be the cleanest solution >(alternatives: remove the two byte header and use DLT_RAW, or expand it >to four bytes, and use DLT_NULL). Unfortunately it's also the solution >which touches the most files (changes needed for libpcap and tcpdump). >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... Thanks for the attention to this neglegted child of mine... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message