From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: Richard Stearn <richard@rns-stearn.demon.co.uk>
Cc: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: AX.25 in tcpdump.
Date: Sun, 25 Sep 2005 12:56:26 +0200 [thread overview]
Message-ID: <20050925105626.GB4444@linux-mips.org> (raw)
In-Reply-To: <43367A25.70805@rns-stearn.demon.co.uk>
On Sun, Sep 25, 2005 at 11:21:25AM +0100, Richard Stearn wrote:
> Chuck Hast wrote:
> >If you get the info would you do the ROSE stuff (we use FPAC here in FL
> >which is a super set of ROSE which is actually X.25) ?
>
> Chuck
>
> Yes, but a qualified one. Can we establish that it actually needs to be
> done?
>
> A grep for 8208 turns up:
>
> print-llc.c: { LLCSAP_ISO8208, "ISO8208" },
>
> so I would like to try connecting that in as the print routine and have
> someone test the result before I look at coding a print-rose.c. If the
> 8208 implementation in print-llc is close then I could use that as a
> starting
> point and just add the extras to create a print-rose or look at extending
> print-llc (which might be be vetoed by the current maintainer).
ROSE is supposedly the X.25 PLP (Packet Layer Protocol), so I suggest you
get yourself a copy of the ITU's X.25 spec. Fortunately the ITU permits
upto 3 free downloads of their otherwise pricey specs per person and year.
73 de DL5RB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
next prev parent reply other threads:[~2005-09-25 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 22:56 AX.25 in tcpdump Richard Stearn
2005-09-25 0:21 ` Chuck Hast
2005-09-25 10:21 ` Richard Stearn
2005-09-25 10:56 ` Ralf Baechle DL5RB [this message]
2005-09-25 11:47 ` Chuck Hast
2005-09-25 18:08 ` Tomi Manninen
2005-09-25 18:20 ` Richard Stearn
-- strict thread matches above, loose matches on Subject: below --
2010-04-13 22:44 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=20050925105626.GB4444@linux-mips.org \
--to=ralf@linux-mips.org \
--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.