Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Bob Nielsen <nielsen@oz.net>
To: Linux Ham Radio <linux-hams@vger.kernel.org>
Subject: Re: AX25 socket question.
Date: Tue, 16 Jul 2002 18:07:52 -0700	[thread overview]
Message-ID: <20020717010752.GB14695@oz.net> (raw)
In-Reply-To: <3D3480B1.E743CA51@earthlink.net>

That was the other one I referred to (actually it has both versions). 

Bob, N7XY

On Tue, Jul 16, 2002 at 04:23:13PM -0400, jeff wrote:
> You'll find it here:
> 
> http://www.tapr.org/tapr/html/Fax25.html
> 
> Riley Williams wrote:
> > 
> > Hi Timothy.
> > 
> > > Thanks for the information, I didn't realize that I would have to
> > > work at that lower level. But I like challenges. I'm looking for a
> > > book right now to get that will help explain some things to me, I
> > > just wish there was one specific to AX25.
> > 
> > There is a book specific to AX.25, although whether it is still in print
> > is a good question. The book in question is "AX.25 Packet Radio Link
> > Layer Protocol" and explains exactly how the AX.25 protocol works. Also,
> > failing that, just remember that AX.25 is the LAP-B subset of the HDLC
> > protocol that is defined by international standard, and one can work out
> > the relevant details by referring to the HDLC standard and taking the
> > LAP-B subset whherever a choice is presented.
> > 
> > For a less technical (and probably much more understandable) approach, try
> > http://www.rsgb.org/shop/acatalog/RSGB_On_Line_Shop_Packet___APRS_18.html
> > or the equivalent on the ARRL website or your national society if it has
> > one.
> > 
> > > I still plan to work on the monitoring program, I had planned to get
> > > to that lower level sooner or later but it looks like it will be
> > > sooner. Thanks for the help and information.  I have always used
> > > other peoples programs before, but after a while I finally decided
> > > to learn to do it myself just for the challenge and learning
> > > experience.  I appreciate all the replies. Thanks.
> > 
> > No problem.
> > 
> > Best wishes from Riley.
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -- 
> Jeff, wd4nmq
> wd4nmq@earthlink.net
> http://home.earthlink.net/~wd4nmq
> iLink client node #10438, iLink sysop link node #14746
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Bob Nielsen, N7XY                          n7xy@n7xy.net
Bainbridge Island, WA  
IOTA NA-065, USI WA-028S 

  parent reply	other threads:[~2002-07-17  1:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16 12:19 AX25 socket question TIMOTHY POWELL
2002-07-16 18:17 ` Riley Williams
2002-07-16 20:23   ` jeff
2002-07-16 21:38     ` Riley Williams
2002-07-17  1:07     ` Bob Nielsen [this message]
2002-07-17  0:55   ` Bob Nielsen
  -- strict thread matches above, loose matches on Subject: below --
2002-07-15 12:24 TIMOTHY POWELL
2002-07-15 22:38 ` Tomi Manninen OH2BNS
2002-07-17  5:46 ` Craig Small
2002-07-14 19:01 TIMOTHY POWELL
2002-07-15  0:03 ` Craig Small

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=20020717010752.GB14695@oz.net \
    --to=nielsen@oz.net \
    --cc=linux-hams@vger.kernel.org \
    /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