All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: "Wilson G. Hein" <wilson.hein@verizon.net>
Cc: Richard Stearn <richard@rns-stearn.demon.co.uk>,
	linux-hams@vger.kernel.org
Subject: Re: AX25 in libpcap, tcpdump & ethereal
Date: Sun, 13 Nov 2005 18:47:37 +0000	[thread overview]
Message-ID: <20051113184737.GB3088@linux-mips.org> (raw)
In-Reply-To: <1131773763.2520.18.camel@CO>

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" <wilson.hein@verizon.net>
> Subject: Re: AX25 in libpcap, tcpdump & ethereal
> To:	Ralf Baechle DL5RB <ralf@linux-mips.org>
> Cc:	Richard Stearn <richard@rns-stearn.demon.co.uk>,
> 	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

  parent reply	other threads:[~2005-11-13 18:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 21:29 AX25 in libpcap, tcpdump & ethereal Richard Stearn
2005-11-11 11:50 ` Ralf Baechle DL5RB
2005-11-12  5:36   ` Wilson G. Hein
2005-11-12 15:17     ` Kjell Jarl
2005-11-13 18:09       ` Douglas Cole
2005-11-13 18:47     ` Ralf Baechle DL5RB [this message]
2005-11-14  4:13       ` Curt Mills

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051113184737.GB3088@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=richard@rns-stearn.demon.co.uk \
    --cc=wilson.hein@verizon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.