From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-hams@vger.kernel.org
Subject: remote TNC
Date: Thu, 26 Dec 2002 00:34:58 +1100 [thread overview]
Message-ID: <20021225133458.GA28240@silly.cloud.net.au> (raw)
Hi all,
Merry Christmas.
Can anyone suggest solutions for using an AX.25 port (TNC, soundmodem
or whatever) remotely eg hooked up to a different computer. Here's two
scenarios:
1. Computer A wants to transmit/receive on RF; RF port is attached to
computer B; computers are on a local Ethernet together.
+------------+ +------------+
| Computer A |----------| Computer B +-- RF port (TNC etc)
+------------+ Ethernet +------------+
Runs application Has RF port
eg XASTIR
Computer A wants to work through B transparently;
it wouldn't have to specifically mention B in its AX.25 packet path,
nor would frames received back by B.
2. Same but computers are connected only via IP, not necessarily on
the same Ethernet:
+------------+ +--------+ +------------+
| Computer A |----------+ Router +-----------| Computer B +-- RF port
+------------+ Ethernet,+--------+ Ethernet, +------------+
PPP etc. PPP etc.
Runs application
eg XASTIR
Again the application on A would like to see a standard Linux
networking interface and think it's connected directly to RF.
On a related note, can somebody give me a good description (either here
or a URL for) for BPQ over Ethernet? Is that part of the answer to #1?
I think AX/IP (RFC 1226) is the protocol behind #2, but does linux (ie
ax25ipd) do this already?
Thanks,
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next reply other threads:[~2002-12-25 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-25 13:34 Hamish Moffatt [this message]
2002-12-25 21:53 ` remote TNC Tomi Manninen
2002-12-25 22:06 ` Tomi Manninen
2002-12-25 22:15 ` Øyvind Hanssen
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=20021225133458.GA28240@silly.cloud.net.au \
--to=hamish@cloud.net.au \
--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.