aprstastic 0.0.1a16

A Meshtastic-APRS Gateway

aprstastic

---

[!WARNING] Legal operation of this software requires an amateur radio license and a valid call sign.

[!NOTE] Code contributions are welcomed and appreciated. See CONTRIBUTING.md for details.

New!

:fire: 2-minute YouTube demo

:fire: Basic position beacons now supported (lat, lon, timestamp)

:fire: Over-the-air discovery and registration now supported. See image below.

:fire: Registrations are now (optionally) beaconed to MESHID-01 to facilitate a global roaming profile.

:fire: Design doc and future plans: DESIGN.md

Introduction

Here is a proof of concept of a Meshtastic to APRS gateway for Meshtastic users with amateur radio licenses. It runs on stock Meshtastic (915MHz, not HAM band or mode), but uses a pre-registered association between Meshtastic device MAC addresses and amateur radio callsign+SSID to keep things properly attributed and compliant with FCC regulations. To this end, operation requires at least two meshtastic devices: one to serve as the gateway, and the others are the clients. The following image demonstrates how operators can register with the gateway:

In this scenario, once registered, private message to the gateway will be forwarded to APRS with the "from" call sign KK7CMT-8. Likewise, APRS messages addressed to KK7CMT-8 will be routed to operators Meshtastic device via a Meshtastic direct message.

These interactions are demonstrated in the following YouTube video https://www.youtube.com/watch?v=qUvpZUwl-cY

Each gateway mimics an iGate, and can support multiple Meshtastic users, as long as their call signs and devices are pre-registered.

Installation, Configuration, and Running

pip install aprstastic

python -m aprstastic

The first time aprstastic runs, it will create a sample aprstastic.yaml file. Edit the sample, then run it again.

nano ~/.config/aprstastic/aprstastic.yaml
python -m aprstastic

Addressing APRS messages

How does the gateway know the addressee ("to" address) of APRS packets when all Meshtastic messages are addressed to the gateway device?

To address this, we adopt the "CALLSIGN: " convention. Messages should start with the addressee's call sign, followed by a colon. If this is omitted, then the call sign of the addressee is taken to be that of the previous message (i.e., to respond to the previously received message).

As an example, from Meshtastic you could interact with the Winlink gateway (WLNK-1) as follows:

WLNK-1: ?

The reply from Winlink would be:

NOCALL-1: SP, SMS, L, R#, K#, Y#, F#, P, G, A, I, PR, B (? + cmd for more)

You could then simply enter:

L

and it would assume a reply to WLNK-1, producing the following response:

NOCALL-1: 10/11/2024 23:52:30 No messages.

Compliance

aprstastic only allows messages to transit if they are found in the client device-to-callsign mapping, and are thus attributable to a licensed operator. Random messages published on channels like LongFast, or from other devices do not qualify. All messages are unencrypted before they leave Meshtastic, so all APRS traffic is clear text.

Future Plans

The clear weakness of this gateway is the need to register devices in order for the call sign mapping to work. If every node administrator needs to manage this list, then the system will not scale (and maybe this is fine to control traffic). However, one compelling possibility is to create a central registry where, call signs can be registered to nodes, and the gateways could then subscribe to this list. This would allow a degree of roaming without much need for coordination. To support this, all dynamic registrations (!register command) are optionally beaconed to APRS-IS, to facilitate discovery. Such beacons are expected to be rare -- at most once per device.

For more details, and other upcoming features, see DESIGN.md

License

aprstastic is distributed under the terms of the MIT license.