← Complete project index

Wireless & Sensing / Working prototype

Reticulum / RNode Mesh Prototype

Multi-node Reticulum setup with RNode radio interfaces, LAN TCP transport and ESP32/LR1121 experiments for resilient local messaging.

STATUSWorking prototype
AREAWireless & Sensing
STACK6 documented technologies
INTEGRATIONS3 connected / bounded services
01

OVERVIEW

What I built.

Multi-node Reticulum setup with RNode radio interfaces, LAN TCP transport and ESP32/LR1121 experiments for resilient local messaging.

01

Built a local Reticulum lab with multiple RNode/radio paths and a LAN TCP transport.

02

Worked with ESP32-S3/LR1121 hardware, RNode serial interfaces and Reticulum configuration.

03

Tested transport behavior, radio parameters and host/container device mapping.

02

SYSTEM ARCHITECTURE

How the system is divided.

01
Architecture boundary

Reticulum daemon -> RNodeInterface -> serial-attached radio -> LoRa RF link.

02
Architecture boundary

A separate TCPServerInterface provides LAN transport so RF and wired paths can coexist.

03
Architecture boundary

Radio frequency, bandwidth, spreading factor and coding rate are explicit link parameters rather than hidden defaults.

03

NETWORK / DATA FLOW

What talks to what.

04

TECHNOLOGY STACK

The technical surface.

01Reticulum
02RNode
03ESP32-S3
04LR1121
05LoRa
06TCP
05

IMPLEMENTATION

How it works in practice.

  1. 01

    Reticulum daemon -> RNodeInterface -> serial-attached radio -> LoRa RF link.

  2. 02

    A separate TCPServerInterface provides LAN transport so RF and wired paths can coexist.

  3. 03

    Radio frequency, bandwidth, spreading factor and coding rate are explicit link parameters rather than hidden defaults.

06

TESTING & VALIDATION

How I know it works.

TEST 01

Serial/RNode device mapping checks

TEST 02

Radio console verification of frequency/SF/BW/CR

TEST 03

Multi-node lab tests

TEST 04

LAN TCPServerInterface tested separately from RF transport

TEST 05

Container health and /dev/rnode mapping diagnostics

07

EXTERNAL SERVICES & DEPENDENCIES

What sits outside the core.

COREReticulum / RNode Mesh Prototype
08

ENGINEERING EVIDENCE

Artifacts behind the claims.

01Reticulum config
02RNode console output
03Three-node lab state
04Container diagnostics
05Frequency/link parameter experiments
09

BOUNDARIES / CONSTRAINTS

What the project does not pretend to solve.

RF range requires the correct antenna and legal regional parameters

A LAN transport working does not prove the LoRa path

Radio parameters must match at both ends

10

RESULT / CURRENT STATE

What this produced.

A functional multi-node Reticulum test environment for experimenting with resilient local messaging and radio transport.