Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "Wilson G. Hein" <wilson.hein@verizon.net>
To: Ralf Baechle DL5RB <ralf@linux-mips.org>
Cc: Richard Stearn <richard@rns-stearn.demon.co.uk>,
	linux-hams@vger.kernel.org
Subject: Re: AX25 in libpcap, tcpdump & ethereal
Date: Fri, 11 Nov 2005 21:36:03 -0800	[thread overview]
Message-ID: <1131773763.2520.18.camel@CO> (raw)
In-Reply-To: <20051111115014.GB3137@linux-mips.org>

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...

Willie, WJ3G



  reply	other threads:[~2005-11-12  5:36 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 [this message]
2005-11-12 15:17     ` Kjell Jarl
2005-11-13 18:09       ` Douglas Cole
2005-11-13 18:47     ` Ralf Baechle DL5RB
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=1131773763.2520.18.camel@CO \
    --to=wilson.hein@verizon.net \
    --cc=linux-hams@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=richard@rns-stearn.demon.co.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox