All of lore.kernel.org
 help / color / mirror / Atom feed
From: gerard borg <gerard.borg@anu.edu.au>
To: Richard Stearn <richard@rns-stearn.demon.co.uk>
Cc: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Ethereal ax25 monitoring
Date: Thu, 01 Sep 2005 10:21:52 +1000	[thread overview]
Message-ID: <1125534112.3594.26.camel@borgcom> (raw)
In-Reply-To: <4316253A.2060009@rns-stearn.demon.co.uk>

Hi 

I have been reading with interest these mails in the quest to
get ethereal to detect AX25 packets. 

I do not know the solution to this problem but what Richard is saying
about libpcap sounds similar to some experiences I have had including a
project to get mkiss to run with ethernet bridging where bridging here
refers to the software described at

http://bridge.sourceforge.net/

I found that the bridge utilities would not recognise an ax25 network
device (such as ax0). The trick with the bridging software is to use
ethernet encapsulation. This implied that in order to bridge an mkiss
tty to an ethernet card, one has to get rid of the ax25 encapsulation
altogether and replace it with ethernet encapsulation. 

In my project I did not need the ax25 MAC anyway and the simplest
solution was to get rid of ax25 from mkiss by rewriting the routines
ax_rebuild_header and ax_header according to a description given in the
network device drivers chapter of A Rubini's book "Linux Device
Drivers". 

Concerning libcap, I also remember trying some software from the book on
open source security tools by Mike Schiffman. This software is based on
these open source packet libraries. Again this software could not see
ax25 packets. This is the same problem with ethereal I guess.

Sorry I cannot be more help this. If anyone is interested however, I do
have the version of mkiss.c that looks like an ethernet device to Linux.
Superficially this sounds like "back to slip.c" but there are some
differences, mainly simplifications and a KISS-like robustness over
wireless links. 
 

Gerard Borg





On Wed, 2005-08-31 at 22:46 +0100, Richard Stearn wrote:
> An update on AX.25 in Ethereal.
> 
> I have enquired on the Ethereal list and the attitude (sample of 1) is
> that "if the protocol exists and is used then it will be accepted".
> Subject to a few pratical provisos.
> 
> The deeper issue I have found is that Ethereal uses libpcap for the
> actual packet capture, and libpcap does not support AX.25 as a packet
> type.
> 
> There appears to a replacement for libpcap in development within Ethereal
> however that is probably a long term project. So my next move is to see
> what the issues are with getting the AX.25 packet type added to libpcap.
> 
> It looks to me that AX.25 on Ethereal is going to be a long time coming.
> 


  reply	other threads:[~2005-09-01  0:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-13 17:43 Ethereal ax25 monitoring Chuck Hast
2005-08-13 21:56 ` Richard Stearn
2005-08-14 21:54   ` Richard Stearn
2005-08-15 10:28     ` Ralf Baechle DL5RB
2005-08-31 21:46     ` Richard Stearn
2005-09-01  0:21       ` gerard borg [this message]
2005-09-01 15:34       ` Ralf Baechle DL5RB
2005-09-07 21:57       ` Richard Stearn

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=1125534112.3594.26.camel@borgcom \
    --to=gerard.borg@anu.edu.au \
    --cc=linux-hams@vger.kernel.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 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.