RF Comms
RNS / Reticulum Network Stack
Carry messages across different networks, including links you build yourself.
What it is
Reticulum is a networking stack: software that handles addressing, routing, and protected communication between applications. It can use an existing IP connection or a suitable radio interface, and a network can join different link types. LoRa is one possible radio link; Reticulum is not a radio frequency or a particular device.
LXMF provides messaging over Reticulum. Sideband and MeshChatX are clients you can use for those messages. Keep using your regular LAN or Tailscale for IP services such as Nextcloud; a low bandwidth radio is not a broadband connection.
Get started now
- On an Android phone, install Sideband from the developer’s official releases and follow its Android instructions. The project lists Android and desktop platforms; do not assume an iPhone build is available.
- On your computer, install MeshChatX from its official project. Follow the current instructions for your operating system rather than an old forum command.
- Start on an existing network. Try both devices on the same LAN with compatible local discovery enabled. For a wider network, configure a reachable Reticulum peer from an operator you trust. Installing the app alone does not guarantee a route to distant contacts.
- Exchange addresses and test both directions. Back up identity keys and confirm recipients through another channel.
- Add radio after messaging works. Use RNode-compatible hardware and matching settings. Test without the Internet path to confirm what really works offline.
Privacy and emergency use
Reticulum supports encrypted communication, but encryption does not make an operator unobservable. Radio transmissions, traffic timing, compromised endpoints, and identities you share can still reveal information. Keep software current and verify who you are talking to.
For outages, the useful feature is another tested path. A radio link still needs power, compatible equipment, and a reachable route. Internet peers stop helping when their connections fail. Practice with local contacts and backup power, and keep other ways to request emergency help.
Link types and what they require
| Link / interface | What it does | What you need |
|---|---|---|
| LAN / AutoInterface | Finds nearby peers on local Ethernet or Wi-Fi. | Devices on a compatible local network, with discovery allowed. |
| TCP / Backbone | Carries Reticulum over an IP connection. | A reachable peer address and port, using the Internet or another IP path. |
| UDP | Carries packets over IP without a persistent TCP connection. | Matching endpoint settings and suitable firewall rules. |
| LoRa / RNode | A low power radio path for small messages. | Supported LoRa hardware with RNode firmware, antennas, and matching settings. |
| Packet radio / KISS or AX.25 KISS | Connects through a radio modem or terminal node controller. | A compatible modem/TNC, radio, antenna, and authority to use that band and mode. |
| Serial | Uses a cable or serial modem. | Compatible ports and matching speed/settings. |
| I2P | Carries Reticulum through I2P. | An I2P router and underlying connectivity; not an offline radio link. |
| Pipe | An external program supplies the link. | A suitable transport program connected through standard input/output. |
Connecting Central Illinois
I want to help connect Central Illinois using Reticulum. The local starting frequency proposed here for compatible LoRa / RNode devices is 914.875 MHz. This is a project coordination setting, not a universal LoRa or Reticulum default and not proof of coverage.
Frequency alone is not enough: coordinate bandwidth, spreading factor, coding rate, and interface access settings. Use hardware and operating settings permitted for your location. Meshtastic and MeshCore use different protocols; matching their frequency does not make them compatible with Reticulum.
Start with a known pair of nodes, record test locations and obstacles, and add relay sites where a real gap exists. If you are nearby, use the Contact page to compare setups.
How it fits the home server
An always-on server can run a Reticulum node and, when deliberately configured, provide transport between its interfaces. A suitable LXMF propagation service can support delayed delivery. A compatible RNode can give the host a radio interface.
Use this for messages and lightweight status. Keep photos, software downloads, and backups on faster networks. Test routing, power loss, and recovery before promising availability.