Reticulum for beginners
Guide · updated June 2026
Reticulum is a way to build private, server-less networks over almost anything — LoRa, the internet, packet radio. New to it? Start here. No prior knowledge assumed.
What Reticulum actually is
The thing to get straight first: Reticulum isn’t an app — it’s a networking stack. It’s an alternative to the plumbing of the internet (TCP/IP), built for a world with no fixed infrastructure: no servers you depend on, no DNS, no company handing out addresses.
A few things make it special:
- It runs over anything. LoRa radio, packet radio, serial cables, WiFi, plain internet, even I2P — and it bridges them, so a single message can hop from LoRa to the internet and back without anyone setting that up.
- You own your address. There’s no registration. Your device generates its own cryptographic identity, and the address derived from it is reachable across the whole network within seconds.
- It’s encrypted by default. You can’t even make an unencrypted link. Packets carry no “from” address either, so who sent something stays private.
- It loves bad links. Slow, lossy, high-latency connections where normal networking gives up are exactly where Reticulum is happiest.
If you know Meshtastic or MeshCore… those are LoRa messaging apps with a network baked in. Reticulum is the network itself — a stack you could run over LoRa and the internet and ham packet at the same time. If they’re walkie-talkies, Reticulum is the phone system you could build them on.
Five words that unlock it
Learn these five and the rest of Reticulum makes sense.
| Term | In plain words |
|---|---|
| Identity | A public/private key pair that is you. No sign-up, no account — your device just makes one. |
| Destination / address | Your reachable address, derived from your identity. You generate it yourself; it’s announced to the network and reachable in seconds. Packets never reveal the sender. |
| Interface | A connection to one medium — your local WiFi, an internet hub, an RNode for LoRa. You list these in a config file; Reticulum bridges across all of them. |
| Transport node | A node set to relay for others, extending the network’s reach. Routing needs no central planning — nodes figure out paths on their own. |
| LXMF | The messaging layer — think “email for Reticulum.” It delivers directly when it can, or holds and forwards messages when the other person is offline. |
Path A — just use Sideband
No terminal, no config. The fastest way to feel what Reticulum is.
-
Install Sideband
Sideband is a friendly messenger for Reticulum — Android (app store or APK) and desktop (Linux, macOS, Windows).
-
Open it — you’re already on the network
On first run it creates your identity and address and connects over the internet automatically. Zero setup; you’re reachable.
-
Message someone
Share your address (or a QR code), add a contact, and send. It’s end-to-end encrypted, and it can carry files, location and even real-time voice calls.
-
Optional: go on the air
Pair an RNode (below) over USB or Bluetooth and Sideband will also talk over LoRa — no internet needed at all.
Path B — run the stack yourself
Want to actually build a network? It’s one Python package.
pip install rns # the Reticulum stack (add --break-system-packages if pip refuses) rnsd # run the daemon — creates ~/.reticulum/config on first run rnstatus # see your interfaces and connections
- Out of the box, the default
AutoInterfacefinds other Reticulum peers on your local WiFi / Ethernet — you can already reach them. - To join the wider network, add a
TCPClientInterfacepointing at a public hub (find a current one in the community directory at directory.rns.recipes). Everything then bridges into one network. - Want a messenger plus an off-grid “web”?
pip install nomadnet— Nomad Network is a terminal client for LXMF messaging and self-hosted pages.
Handy tools that come with it: rnstatus (status), rnpath (look up a route), rnprobe (test reachability), rncp (copy files), rnx (run a command on a remote node).
RNode — Reticulum over LoRa
An RNode is a cheap LoRa board running open RNode firmware. It turns the same kind of hardware you’d flash Meshtastic onto — Heltec, T-Beam, RAK, LilyGo — or a purpose-built RNode, into a Reticulum radio interface.
Flash it with the RNode Configuration Utility (rnodeconf) or the web flasher, plug it in, add it as an interface in your config, and you’ve got a real network with no internet anywhere in the path. RNodes can also bridge classic ham packet radio. This is what makes Reticulum a genuine off-grid option, not just an internet overlay.
Reticulum vs Meshtastic & MeshCore
If you already run Meshtastic or MeshCore, here’s the honest pitch — and the catch:
- It’s the whole network, not one app. Message, share files, host pages, make voice calls — all on the same stack.
- One network across mediums. LoRa, the internet and packet radio, bridged together — even mixed on a single route.
- Private and self-owned by design. Encryption you can’t turn off, addresses you generate yourself, and routing with no central coordinator — which is a big part of why it scales.
- The catch: it’s a toolkit, so there’s more to learn than flashing Meshtastic and chatting. Think of it as the next rung up — more power, a bit more setup.
Where it’s at
Reticulum is at v1.3.5 (June 2026) and moving quickly. Recent additions include real-time voice calls and slick web & desktop clients like MeshChat. It’s grown into a community-driven project with a busy app ecosystem, and it’s drawing real attention as a resilient, sovereign alternative for off-grid comms. A few recent reads:
Building a network that can’t be switched off?
Trade setups and ask the dumb questions (we all did) in #reticulum.