Reticulum: a network that isn't tied to one kind of radio
What problem does it solve? Reticulum is a networking system designed to move information across different types of communication links. Unlike a project tied to one particular radio board, it can use several kinds of interfaces—including supported LoRa devices, local networks and certain packet radio equipment.
An everyday way to think about it
Imagine a town where some streets are paved, some are gravel and some are trails. People still need a method to move between destinations. Reticulum is designed to operate across a mix of different communication paths, provided the interfaces between them are configured and can move the required information.
That analogy is only a starting point: Reticulum includes its own identities, routing and cryptographic design.
Three layers worth separating
- Physical link: the radio, cable, Wi-Fi or other medium that actually moves information.
- Reticulum interface: the software configuration describing how Reticulum accesses that link.
- Application: a program that lets a person send messages or use another service. Sideband and the LXMF messaging ecosystem are examples.
A Raspberry Pi and LoRa radio don't automatically become a working Reticulum network by being plugged together. The device, firmware, interface and application must support the arrangement.
What's different from Meshtastic or MeshCore?
Reticulum isn't simply another firmware image that turns every LoRa board into a compatible Meshtastic node. It is a separate protocol stack with its own networking model.
What might appeal to you: bridging different forms of links, building independent networks, experimenting with routing and creating applications.
What makes it challenging: more concepts may need to be understood at first—interfaces, software installation, address/identity concepts and how different links interact.
A sensible beginner sequence
- Start with radio fundamentals and network types.
- Read the Reticulum manual and understand the term interface before purchasing hardware.
- Try a local experiment using two computers or devices and an interface supported by the manual.
- Only then investigate which LoRa hardware and RNode firmware are supported for your experiment.
- Document what worked, what didn't and what you learned.
Reticulum's networking design uses encryption. U.S. amateur rules generally prohibit messages encoded for the purpose of obscuring their meaning (47 CFR § 97.113(a)(4)). Do not assume default Reticulum transmissions are suitable for amateur bands. Evaluate encryption, identification, device, mode and service rules before transmitting. Unlicensed-band operation has its own applicable equipment and technical rules as well.
Questions worth asking
Is Internet required? Not inherently. Reticulum can use local/non-Internet interfaces, but it can also carry traffic over IP networks when configured to do so.
Can it run over any LoRa radio? No. Confirm supported hardware and firmware; a supported LoRa link is more than just a radio chip.
Is it “better” than MeshCore? That's not a useful general comparison. Their goals and architectures differ. Your intended application and skills are the better basis for a decision.
Primary sources
Questions, corrections or project ideas: Northern Michigan Mesh Forum.