From: Cathryn Mataga <cathryn@junglevision.com>
To: Thomas Osterried <thomas@x-berg.in-berlin.de>
Cc: linux-hams@vger.kernel.org
Subject: Re: ax25ipd.c routing
Date: Mon, 07 Dec 2009 21:11:36 -0800 [thread overview]
Message-ID: <4B1DE008.1080306@junglevision.com> (raw)
In-Reply-To: <20091207235111.GS19524@x-berg.in-berlin.de>
http://www.mataga.net/mataga/ax25ipdke6i.diff
Here's a link to the change I made to ax25ipd. This is a diff
versus the rc2 version. It hasn't been tested that much,
but it does work for me.
It's pretty basic. It reads ip addresses and callsigns
using code taken from the test version. But then it stores the
matching route/Callsign in a btree, and uses this btree to
retrieve the correct ip during sending. It does fix the issue
shown in the logs I created earlier.
It doesn't deal with the route IP's changing. Currently, I just
print a message when this happens. It only addresses the issue
of user callsigns.
next prev parent reply other threads:[~2009-12-08 5:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1752195AbZK3HxQ/20091130075316Z+372@vger.kernel.org>
2009-11-30 20:38 ` nr0 doesn't show up (netrom) Cathryn Mataga
2009-11-30 21:13 ` Cathryn Mataga
2009-11-30 21:48 ` Cathryn Mataga
2009-12-01 6:05 ` Cathryn Mataga
2009-12-07 10:30 ` ax25ipd.c routing Cathryn Mataga
2009-12-07 16:25 ` Thomas Osterried
2009-12-07 20:02 ` Cathryn Mataga
2009-12-07 20:26 ` Thomas Osterried
2009-12-07 23:30 ` Ray Wells
[not found] ` <4B1D84C4.8000206@exemail.com.au>
[not found] ` <20091207235111.GS19524@x-berg.in-berlin.de>
2009-12-08 1:45 ` Cathryn Mataga
2009-12-08 5:11 ` Cathryn Mataga [this message]
2009-12-08 22:15 ` Cathryn Mataga
2009-12-15 23:14 ` [PATCH] ax25ipd Cathryn Mataga
2009-12-25 11:35 ` [PATCH] call.c Cathryn Mataga
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=4B1DE008.1080306@junglevision.com \
--to=cathryn@junglevision.com \
--cc=linux-hams@vger.kernel.org \
--cc=thomas@x-berg.in-berlin.de \
/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.