The network does not have to use one kind of link
Reticulum is a cryptography-based networking stack. It provides identities, routing, encrypted links, and data transport over different underlying media. It can use Ethernet/Wi-Fi and IP connections, serial interfaces, and LoRa hardware. IP is optional: an IP network can carry Reticulum, but Reticulum does not require IP for every path. Reticulum overview
This makes it useful for exploring a network with several types of connection. A local radio segment could connect through a computer to another segment over an available network link. The design does not remove the capacity or availability limits of those links.
Four names to learn
| Name | Role |
|---|---|
| Reticulum / RNS | The networking stack and its reference implementation |
| RNode | A radio interface using supported hardware and firmware, often over LoRa |
| LXMF | A messaging protocol above Reticulum, including delayed-delivery patterns |
| Sideband, Nomad Network, CrossTalk | Applications with different interfaces and capabilities |
Reticulum's own getting-started guide links its tools, applications, and LXMF. An RNode is an interface to the network; it is not itself equivalent to a full messaging application.
Begin without buying hardware
A sensible first lab is two computers or supported app devices on an existing LAN. Establish messages, learn identities and delivery status, and then test with one participant disconnected. Add radio only after the software workflow makes sense. Sideband is available for Android, Linux, and macOS; platform support differs among other applications. Reticulum getting started
For LoRa, select a board listed by the RNode firmware tooling. Existing supported LoRa boards may be reusable after reflashing. Exact board revision and transceiver matter, and reflashing usually replaces the software currently on the device. Supported communications hardware
How this differs from the local Meshtastic mesh
A stock Meshtastic node does not natively interpret Reticulum packets. MeshCore is another protocol again. Shared LoRa chips do not create automatic compatibility. A bridge or tunnel is an additional application with its own configuration, trust boundaries, overhead, and failure modes.
Reticulum is therefore attractive for a networking experiment, while Meshtastic or MeshCore may be the easier way to join neighbors who already use those systems. That is a recommendation about the starting task, not a ranking of protocol quality.
Encryption is part of the architecture
Reticulum uses cryptographic identities and encrypted communication. It can run over technically compatible radio interfaces, but technical support for an amateur-radio TNC does not authorize encrypted traffic on amateur frequencies. Apply the rules of the actual radio service to every outgoing path. Reticulum design · 47 CFR 97.113
The household implication is straightforward: use compliant unlicensed radio links for the encrypted LoRa experiment. Do not route opaque encrypted traffic onto the club's amateur packet network merely because software exposes that option.
What satellite support actually exists
Our initial research had not verified a maintained 9704 interface. Further investigation found CrossTalk documentation for an optional RockBLOCK 9704 interface. It carries encrypted Reticulum packets over Iridium IMT and uses Ground Control's Python driver. This is a documented implementation path, not a feature we installed or tested in the lab. CrossTalk guide
MeshSat separately documents Reticulum interoperability and a 9704 path, with important distinctions between its Bridge, Android application, and physical-node tests. The next article explains that evidence and where a remote provider or Hub participates.
A useful experiment for the club
Create two identities on an ordinary local network and exchange messages. Add a supported RNode pair and repeat the test without the LAN path. Record what fails when each path disappears. Only then evaluate a paid satellite route with an explicit destination allowlist and traffic budget. This keeps a learning exercise observable and prevents background network traffic from becoming an unexpected airtime bill.