Using Tailscale as the IP Underlay for Reticulum
Reticulum does not need Tailscale, but its TCP interfaces can use a Tailscale path just like any other private IP network.
TOPIC
LoRa & Reticulum
Lessons, explainers, experiments, and implementation notes.
A Practical Reticulum TCP Bridge over Tailscale on Port 4242
The configuration is small, but binding address and access policy decide whether the bridge is private or accidentally broader than intended.
What Happens to Reticulum When the Tailscale Path Drops and Returns
The useful property is not that the IP path never fails; it is that the transport can recover without redefining the whole Reticulum network.
Combining an RNode LoRa Link and a Tailscale TCP Link in One Reticulum System
The interesting architecture is not choosing radio or IP; it is letting Reticulum use different interfaces for different reachability conditions.
Why I Mapped the Host Device to /dev/rnode
Raw host tty names leak host enumeration details into Reticulum configuration and make migration harder.
Reticulum Radio Parameters Must Match Exactly
Two healthy RNodes can be mutually deaf when frequency, bandwidth, spreading factor or coding rate differ.
enable_transport Changes the Node’s Responsibility
Turning on Reticulum transport was more than a logging preference because it changed how the host participates in forwarding.
A LAN TCP Server and a LoRa Interface Solve Different Reachability Problems
The same Reticulum instance needed to bridge local IP-connected peers and radio-connected peers without pretending TCP and LoRa were the same medium.
SF, Bandwidth and Coding Rate Are a Three-Way Trade
Changing one LoRa parameter to chase range can quietly change airtime, sensitivity and compatibility elsewhere.
433 MHz and 867.2 MHz Belonged to Different Experiments
The lab used both 433-class LR1121/E22 work and an 867.2 MHz RNode profile, which could easily be mixed in memory.
Sync Word Mismatch Can Look Like a Dead Receiver
A receiver can detect energy or even preamble-like activity while rejecting the packet format expected by the application.
Preamble Detected but No Header Was Better Than “Nothing Happened”
A scan could fail to decode a packet yet still reveal that one PHY was closer to the transmitter than all the others.
Scanning 32 PHY Profiles Was a Diagnostic, Not a Network Design
Auto-scanning many SF/BW combinations helped discover compatibility clues but could not replace an agreed production PHY.
A LoRa Range Test Without the Right Antenna Is Not a Range Test
Early experiments were tempting to interpret as radio-range evidence even when the nodes did not yet have confirmed band-appropriate antennas.
A 2.4 GHz Antenna Is Not a Generic Antenna for 433 or 868 MHz
Having only a 2.4 GHz antenna available created pressure to use it for sub-GHz experiments just to continue testing.
Ten Kilometres Starts with a Link Budget, Not Maximum TX Power
The desire for multi-kilometre range could easily turn into a single-variable question about how many dBm the radio can transmit.
More TX Power Can Make the Experiment Worse
A high-power remote module made it tempting to run both nodes at maximum output during bench debugging.
A Stable /dev/serial/by-id Path Is Part of Radio Reliability
A working RNode can disappear after reboot if the host binds to a transient tty name that changes when USB devices reorder.
“Stub Is Already Running” Was Evidence About the Flash Path
Flashing through the bridge looked ambiguous because the USB side and target side were different MCUs.
Changing Distance Did Not Turn an Unknown Mode into a Known Mode
Repeated no-response behavior at different physical setups did not prove a pure propagation problem because the remote device mode/profile was still uncertain.
Local E22 Control Passing Did Not Prove the Remote Link
The local module read and configured correctly, creating a strong temptation to declare the radio side healthy.
The Exact CF CF C0 05 01 17 Command Was a Compatibility Probe
Generic transparent traffic could fail for many reasons, so the investigation needed one manufacturer-documented transaction with a predictable reply.
AUX Activity Proved Transmission Work, Not Remote Reception
The E22 AUX pin changed around transmissions, but the remote EWM still returned no bytes.
Mode 2 Initiator and Mode 0 Target Was a Topology Contract
Different EBYTE operating modes made it possible for both devices to be powered and configured yet unable to execute the intended over-air management transaction.
No Reply Was an Inconclusive Result, Not Proof of RF Failure
Silence from the EWM looked like a hardware failure but the observation did not isolate which half of the wireless path was wrong.
Wired RS485 Was the Recovery Path for Unknown Remote State
Over-air configuration cannot recover a remote module whose stored mode/profile is unknown if that unknown state prevents the OTA command itself.
The Reticulum Container Needed to Observe Its Own Interface
A long-running rnsd process could appear healthy while its RNode device disappeared or the interface failed.
Radio Configuration Belongs in Versioned Infrastructure
Frequency, bandwidth, SF, coding rate and device mapping were being changed during experiments and could easily become undocumented shell history.
A PHY Scan Should Produce Evidence, Not Just Console Noise
Long automatic scans produced hundreds of lines that were hard to compare across runs.
Scaling from a Lab Pair to a Reticulum Mesh Changes the Acceptance Test
A successful point-to-point packet is necessary but insufficient evidence for a useful multi-node transport network.
The ESP32-C6 Bridge Was a Transport Tool, Not the Radio Node
The USB-visible ESP32-C6 bridge made it easy to confuse the bridge MCU with the ESP32-S3/LR1121 radio target behind it.
ModemManager Can Break a Perfectly Good RNode Session
Linux services can probe new serial devices and interfere with a host-controlled radio before Reticulum starts.
Three Powered Radios Are Not Yet a Network
Having multiple radio boards powered and visible created a false sense that a multi-node Reticulum network already existed.
Containerizing Reticulum Did Not Remove the Hardware Boundary
Docker made RNS reproducible, but the radio still existed as a physical character device outside the container.