From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ralf Baechle DL5RB Subject: Re: AX25 in libpcap, tcpdump & ethereal Date: Sun, 13 Nov 2005 18:47:37 +0000 Message-ID: <20051113184737.GB3088@linux-mips.org> References: <4373BBBD.10505@rns-stearn.demon.co.uk> <20051111115014.GB3137@linux-mips.org> <1131773763.2520.18.camel@CO> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <1131773763.2520.18.camel@CO> Sender: linux-hams-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "Wilson G. Hein" Cc: Richard Stearn , linux-hams@vger.kernel.org On Fri, Nov 11, 2005 at 09:36:03PM -0800, Wilson G. Hein wrote: > Date: Fri, 11 Nov 2005 21:36:03 -0800 > From: "Wilson G. Hein" > Subject: Re: AX25 in libpcap, tcpdump & ethereal > To: Ralf Baechle DL5RB > Cc: Richard Stearn , > linux-hams@vger.kernel.org > Content-type: text/plain > > On Fri, 2005-11-11 at 03:50, Ralf Baechle DL5RB wrote: > > On Thu, Nov 10, 2005 at 09:29:33PM +0000, Richard Stearn wrote: > > > > > For the foolhardy, desperate or those who just like to live dangerously. > > > > > > To play with this you will need to be comfortable with using tar, patch > > > & make at the very least and using Linux. The system I am using is a > > > Slackware 8.1 install (kernel 2.4.31) > > > > > > Attached is a patch that adds AX.25 to: > > > libpcap - recognition and capture > > > tcpdump - decoding AX.25, to a limited extent > > > - decoding an ARP payload > > > - decoding a TCP/IP payload > > > ethereal - dissection of AX.25 > > > - dissection of an TCP/IP payload > > > > > > All others are treated as having no L3 protocol and printed in hex > > > and ascii. > > > > This is excellent news and I hope it means we can soon retire listen(8) > > in favor of the standard tools tcpdump and ethereal! > > > > Ralf > > - > > I agree that it's good news as far ass the added abilities to tcpdump > and ethereal, but I wholeheartedly disagree with retiring listen. For me > and maybe others, with respect to packet radio, listen is a standard > tool. Even with added abilities to the other tools, only listen provides > me with just what I want to see when monitoring my packet systems on air > activities. Nothing more, nothing less... I realize that people are used to listen, so that would certainly only happen in the distant future. And right now tcpdump and ethereal aren't yet there yet. And finally the listen code isn't exactly a pain to maintain :) 73 de DL5RB op Ralf -- Loc. JN47BS / CQ 14 / ITU 28 / DOK A21