From: "Paul R. Tagliamonte" <paultag@gmail.com>
To: linux-hams@vger.kernel.org
Subject: Re: AX.25 Linux Packet Forwarding
Date: Mon, 28 Mar 2022 10:13:04 -0400 [thread overview]
Message-ID: <CAO6P2QR1kYnT9ag_bB1yiTU3jJNkwNvcE9Yo-jGfrWcczriATQ@mail.gmail.com> (raw)
In-Reply-To: <CAO6P2QRhPXpOw6EYkeFv+QsGGZfTce98uTgTd-oYQ7L0sE5TbA@mail.gmail.com>
Thank you Dennis and David!
I was able to get the right parts moving after picking up the phrase
"Digipeating" - I have it all working, thank you very much for your
help!
Paul K3XEC
On Sun, Mar 27, 2022 at 8:18 PM Paul R. Tagliamonte <paultag@gmail.com> wrote:
>
> Hello, Linux HAMs,
>
> I'm just getting into AX.25, and I've not been able to find the right
> set of keywords to search for. I've only started learning about this
> two days ago, so pointing me to the right docs would be very welcome
> and helpful in this case.
>
> I've got a base station and a Kenwood handheld that I've got working
> with AX.25. I have a BBS I can hit via my base station, but not my
> handheld.
>
> I'd like to set up my Linux box attached to my base station to forward
> AX.25 traffic on-frequency as a relay.
>
> HT: "K3XEC-1" (Kenwood)
> Base Station: "MYRELAY" (Yaesu)
> Remote Station: "MYBBS"
>
> Assuming MYRELAY and MYBBS are valid callsigns / stations -- I'm going
> to use these so that we don't get confused by the same callsign but
> different SSIDs.
>
> I'd like to be able to (from my Laptop and Kenwood) do (as K3XEC-1):
>
> $ axcall MYBBS via MYRELAY
>
> which would result in MYRELAY sending traffic K3XEC-2>MYBBS, and
> relaying traffic back to K3XEC-2 (or something) back via
> MYRELAY>K3XEC-1 (or however it should be properly translated - still
> not comfortable with the AX.25 framing yet or if there's a convention
> there), and have my base-station relay traffic to and from.
>
> Is there something like "net.ipv4.ip_forward" but for AX.25 that would
> allow me to do this? Or a daemon or something? I'd love to allow
> anyone else nearby to use my base station, so filtering by callsign is
> not required here either.
>
> I /think/ I subscribed, but please do keep me on CC in the event I fudged up.
>
> Paul K3XEC
>
> --
> :wq
--
:wq
prev parent reply other threads:[~2022-03-28 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 0:18 AX.25 Linux Packet Forwarding Paul R. Tagliamonte
2022-03-28 0:25 ` Dennis Boone
2022-03-28 3:22 ` David Ranch
2022-03-28 14:13 ` Paul R. Tagliamonte [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=CAO6P2QR1kYnT9ag_bB1yiTU3jJNkwNvcE9Yo-jGfrWcczriATQ@mail.gmail.com \
--to=paultag@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).