Reticulum / RNS
The networking stack. It handles identities, destinations, paths, interfaces and encrypted transport between systems.
Reticulum 101 • Complete beginner
RETICULUM 101. START HERE.
Never used Reticulum? Perfect. You do not need a radio, Raspberry Pi, tower or giant pile of hardware to understand the basics.
This guide starts with the software on an ordinary computer or compatible device. Once that makes sense, you can add LoRa through an RNode and build outward from there.
Plain English first
WHAT ARE ALL THESE WORDS?
You only need a few ideas to get moving.
LXMF
A messaging protocol built on Reticulum. Apps such as Sideband and MeshChatX use it for person-to-person messaging and delayed delivery workflows.
RNode
A radio interface designed for Reticulum. Supported LoRa development boards can run RNode firmware and connect a Reticulum host to LoRa.
Your first experiment
NO RADIO REQUIRED.
The official Reticulum documentation specifically supports starting over ordinary Ethernet or Wi-Fi and adding radio later.
Install or choose an app
On a computer with Python, the basic RNS installation is pip install rns. If you would rather begin with a graphical application, Sideband or MeshChatX can provide a more visual path into the ecosystem.
Use the local network
Reticulum's default AutoInterface can discover compatible peers on local Ethernet or Wi-Fi. Two devices on the same network are enough for a useful first lab.
Check what is happening
Utilities such as rnstatus, rnpath and rnprobe help you see interfaces, paths and connectivity instead of guessing.
Then add LoRa
READY FOR AN RNODE?
Once the software side makes sense, add radio as another Reticulum interface.
What the setup looks like
Reticulum host → RNode → LoRa → RNode → Reticulum host
The host can be a compatible laptop, desktop, Raspberry Pi or other supported system. The Raspberry Pi is an option, not a requirement.
Supported development boards
The current official hardware documentation includes supported boards such as Heltec LoRa32 V3 and V4. Installing RNode firmware replaces whatever firmware was previously on that board.
What should I actually use?
APPS MAKE RETICULUM FEEL REAL.
RNS is the networking layer. These applications show what people can build on top of it.
Sideband
Graphical Reticulum client with LXMF messaging, LXST voice calls, files, telemetry, mapping and plugins across supported platforms.
MeshChatX
A current all-in-one Reticulum client with LXMF messaging, LXST calls, multiple identities, maps, telemetry, NomadNet browsing, offline documentation and more.
Nomad Network
A terminal-oriented Reticulum/LXMF environment for encrypted messaging, pages, files and information sharing.
Beginner mistakes
KEEP THE FIRST BUILD BORING.
Do this
- Start on local Wi-Fi or Ethernet.
- Learn what an identity, destination and interface are.
- Get one application working before adding more.
- Use official documentation when configuring interfaces.
- Back up identities you care about.
- Add an RNode only after the software side works.
Not this
- Do not assume Reticulum joins Meshtastic or MeshCore over the air.
- Do not flash a board without confirming the exact hardware.
- Do not assume LoRa settings are legal everywhere.
- Do not start with a giant transport network when two devices will teach you more.
- Do not copy old configuration examples without checking current documentation.
You are ready for step two
FROM “WHAT IS RETICULUM?” TO A WORKING LAB.
If you can run Reticulum or a Reticulum application, see a local interface and understand where an RNode fits, you have the foundation. The next step is experimenting, not buying everything at once.