Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Pidoux <f6bvp@free.fr>
To: John Ronan <jronan@tssg.org>
Cc: Linux-Hams <linux-hams@vger.kernel.org>
Subject: Re: ax25 route question.
Date: Sat, 15 Nov 2008 14:52:40 +0100	[thread overview]
Message-ID: <491ED428.5080509@free.fr> (raw)
In-Reply-To: <E2CCEDF0-B717-4266-AAA3-06AC1B1E3B9C@tssg.org>

Hi John,

I did not see any reply to your question.
Personnally I don't know if the example you gave is correct and would work.
But you may have perfomed some tests already ?
I would say that, as far as AX25 routing is concerned, there are a number of possibilities, using higher level routing 
facilities, such as node, flexnet or FPAC (based on ROSE network protocol).
I am more familiar with ROSE/FPAC that uses a very efficient routing algorithm and white pages at the cost of only three 
more bytes per AX25 frames.
You could find some documentation about FPAC here

http://ftp.f6fbb.org/fpac/doc/FPAC-HOWTO.html#toc1
http://rose.fpac.free.fr/MINI-HOWTO/


73 de Bernard, f6bvp
http://f6bvp.org



John Ronan wrote :
> Could someone give an example of how ax25 routes are supposed to work? 
> I've been trying to figure this out.
> 
> My understanding (which could be wrong) was that If I did
> 
> axparms -route add myport calla digia
> 
> that if I did
> axcall calla
> 
> that the outgoing connect would be directed through digia
> 
> Is my understanding incorrect?
> 
> Regards
> de John
> EI7IG
> 
> -- 
> John Ronan <jronan@tssg.org>, +353-51-302938
> Telecommunications Software &  Systems Group,  http://www.tssg.org
> 
> 
> 



      reply	other threads:[~2008-11-15 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 18:25 ax25 route question John Ronan
2008-11-15 13:52 ` Pidoux [this message]

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=491ED428.5080509@free.fr \
    --to=f6bvp@free.fr \
    --cc=jronan@tssg.org \
    --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