From: Cathryn Mataga <cathryn@junglevision.com>
To: Linux Hams Mailing list <linux-hams@vger.kernel.org>
Subject: ax25ipd.c routing
Date: Mon, 07 Dec 2009 02:30:27 -0800 [thread overview]
Message-ID: <4B1CD943.6030808@junglevision.com> (raw)
In-Reply-To: <4B14B22E.6010901@junglevision.com>
How does this work with multiple connections?
Suppose I have two incoming connections
My call is K1BBS.
route K1PAR 1.0.0.0
route K2PAR 2.0.0.0 d
Then suppose K1USR at K1PAR does a connect to K1BBS.
What seems to happen is I see packets come in from K1USR to K1BBS.
But then when packets go back out, they go back to K2PAR, even though
he's at K1PAR. At least that's what I think is happening.
Shouldn't ax25d.c keep a record of which IP callsigns came from, so that
way when it needs to send a packet back they go to the right place?
I'm not 100% sure of this, but it seems like the lookup only checks
the route commands. I only see one call to route_add in config.c.
Shouldn't it 'route_add' every time a callsign comes in axip?
Or the only way to make this work is to run a separate
ax25ipd for every connection.
next prev parent reply other threads:[~2009-12-07 10:30 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 ` Cathryn Mataga [this message]
2009-12-07 16:25 ` ax25ipd.c routing 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
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=4B1CD943.6030808@junglevision.com \
--to=cathryn@junglevision.com \
--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 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.