A complete emergency communications playbook using Reticulum and LoRa. Hardware kit list, pre-configuration steps, deployment procedures, and communication protocols for when infrastructure fails.

Emergency Comms Playbook: Reticulum for Disaster Preparedness

This is Part 12 of a 12-part series on building private, resilient communication networks with Reticulum, LoRa, and associated tools.

When infrastructure fails — hurricane, earthquake, wildfire, grid collapse — cell towers go down, internet goes out, and suddenly the communication tools everyone depends on are useless. This guide puts everything from the previous 11 parts into a practical emergency communications kit that you can build now and grab when you need it.

The Scenario

Power is out. Cell towers are down or overloaded. Internet is gone. You need to: - Communicate with family members across town - Coordinate with neighbors - Get information from outside the affected area (if any link exists) - Do all of this without depending on any infrastructure

Reticulum was designed for exactly this.

The Kit

Tier 1: Minimum Viable Comms (~$50)

For each person who needs to communicate:

Item	Cost	Purpose
Flashed RNode (LilyGO LoRa32 v2.1)	$15	Radio modem
USB OTG cable/adapter	$5	Connect RNode to phone
Android phone with Sideband installed	(already owned)	Messaging interface
Small USB battery bank (10,000+ mAh)	$15-20	Power for phone and RNode
Rubber duck antenna (868/915 MHz)	$5	Comes with most boards

This gives each person a handheld encrypted radio communicator with 5-15 km range (depending on terrain).

Tier 2: Extended Range + Relay (~$100-150 additional)

Add a transport node to extend range and provide store-and-forward:

Item	Cost	Purpose
Raspberry Pi 4 or Pi Zero 2 W	$35-50	Transport node computer
Second flashed RNode	$15	Radio interface for the Pi
20W solar panel	$25-35	Power generation
Solar charge controller + 12V battery	$20-30	Power storage
12V to 5V USB converter	$5	Power the Pi and RNode
Elevated antenna (whip or J-pole) + coax	$15-25	Better range from height
Weatherproof enclosure	$10-15	Outdoor protection

Mount this on a roof, pole, or high point. It relays messages between handheld users who can't directly reach each other, and stores messages for people who aren't currently online.

Tier 3: Internet Bridge (~$30 additional if internet exists somewhere)

If any internet connection exists within your area (a working Starlink, a neighbor's DSL, a library with power):

Item	Cost	Purpose
Ethernet cable or WiFi access	—	Connect the Pi to internet
TCP interface configuration	Free	Bridge local mesh to global network

This lets your local LoRa mesh reach the outside world. Someone 10 km away with a handheld RNode can send a message to someone in another state through your bridge.

Pre-Configuration: Do This Now

The worst time to learn a new system is during an emergency. Set everything up and test it before you need it.

1. Flash All RNodes

Follow Part 5. Flash every board you have. Label them with their frequency and LoRa parameters.

Critical: All RNodes in your group must use identical LoRa parameters.

Pick a standard and write it down:

Frequency:        867.2 MHz (or 915.0 MHz for Americas)
Bandwidth:        125 kHz
Spreading Factor: 8
Coding Rate:      5
TX Power:         7 dBm

Print this on a card and include it in each kit.

2. Install Sideband on All Phones

Follow Part 4. Install Sideband on every Android phone in your household/group. Configure the RNode connection settings with your standard LoRa parameters.

Test it. Have two people walk to opposite ends of your neighborhood and exchange messages. Note the maximum range.

3. Exchange LXMF Addresses

Everyone in your group needs everyone else's LXMF address. Write them down on paper (yes, paper — your phone might be dead when you need them).

Create a contact card for each person:

Name: Alice
LXMF: 8dd57a738226809646089335a6b03695

Laminate these and keep them with the kit.

4. Pre-Configure the Transport Node

Follow Part 8. Set up the Raspberry Pi with: - Reticulum with transport enabled - RNode interface configured with your standard parameters - AutoInterface for local WiFi - NomadNet in daemon mode (for message propagation) - A pre-written NomadNet page with emergency info, contact list, and instructions

The Pi's Reticulum config:

[reticulum]
  enable_transport = yes
  share_instance = yes

[interfaces]
  [[Default Interface]]
    type = AutoInterface
    enabled = yes
    mode = gateway

  [[RNode LoRa Interface]]
    type = RNodeInterface
    enabled = yes
    port = /dev/serial/by-id/YOUR_RNODE_SERIAL_ID
    frequency = 867200000
    bandwidth = 125000
    txpower = 7
    spreadingfactor = 8
    codingrate = 5
    mode = access_point
    airtime_limit_long = 1.5
    airtime_limit_short = 33

Test the full system: Pi running as transport node, two phones with RNodes communicating through it.

5. Build the Handheld Units

Follow Part 7 if you want proper cased units. At minimum, put each RNode in a small ziplock bag with its USB cable and a label.

6. Prepare the Power System

For the transport node: - Charge the 12V battery fully - Test the solar panel charges the battery - Verify the Pi and RNode run from the battery through the USB converter - Calculate runtime: a Pi 4 + RNode draws ~3-4W. A 12V 7Ah battery gives ~20 hours. Solar extends this indefinitely in daylight.

For handhelds: - Charge all USB battery banks - A 10,000 mAh bank will run a phone + RNode for 1-2 days of intermittent use

Deployment Procedure

When disaster strikes:

Immediate (First 30 minutes)

Power up your handheld RNode and connect it to your phone
Open Sideband and announce yourself
Send a status message to your group: "I'm OK at [location]" or "Need help at [location]"
Listen for announces from other group members

Short-term (First few hours)

Deploy the transport node at the highest accessible point — rooftop, second floor, hilltop
Connect the antenna and point it vertically for omnidirectional coverage
Power it from the battery/solar system
Verify it's relaying — other users should see improved connectivity and be able to reach each other through the relay

Extended (Days to weeks)

If internet becomes available anywhere, connect the transport node to bridge your mesh to the outside world (Part 9)
Update the NomadNet page on the transport node with situation reports, resource locations, meeting points
Recruit more nodes — anyone with a LoRa board and a phone can join the network. Flash new RNodes as needed.

Communication Protocols

Establish these with your group before an emergency:

Check-in schedule: Everyone announces and sends a status message at agreed times (e.g., 8 AM, 12 PM, 6 PM)
Message format: Keep messages short. LoRa is slow. "OK @ home, have water, need meds" is better than a paragraph.
Emergency prefix: Start urgent messages with "URGENT:" so they stand out
Relay protocol: If you receive a message for someone you can reach but the sender can't, relay it manually

Range Planning

Map out your area and plan transport node placement:

Flat terrain: One transport node on a rooftop covers a 5-15 km radius
Hilly terrain: Place nodes on ridgelines or hilltops for maximum coverage
Urban: Expect 1-3 km between nodes due to building attenuation
Multiple nodes: Chain transport nodes to cover larger areas. Each hop adds a few seconds of latency but extends range indefinitely.

What Reticulum Gives You That Other Systems Don't

Feature	Reticulum	Cell phone	FRS/GMRS radio	Ham radio
Works without infrastructure	Yes	No	Yes	Mostly
Encrypted	Always	Varies	No	No (illegal to encrypt on ham)
Store-and-forward	Yes	No	No	No
Multi-hop relay	Yes	No	No	Manual only
Digital messaging	Yes	Yes	No	Limited
No license required	Yes (ISM band)	No (needs carrier)	FRS: no, GMRS: yes	Yes (license required)
Cost per user	~$20-50	$0 (if working)	$25-50	$100+

Kit Checklist

Print this and tape it to the inside of your kit container:

□ RNode (flashed, tested) x1 per person
□ USB OTG cable x1 per person
□ USB battery bank (charged) x1 per person
□ Antenna x1 per RNode
□ Contact card with all LXMF addresses
□ LoRa parameter card
□ Raspberry Pi transport node (pre-configured)
□ RNode for transport node
□ 12V battery (charged)
□ Solar panel + charge controller
□ 12V to 5V USB converter
□ Elevated antenna + coax for transport node
□ Weatherproof enclosure
□ Ethernet cable (for internet bridge if available)
□ This guide (printed)

Final Thoughts

The best emergency communication system is one you've already tested. Don't just build the kit — use it. Run a monthly test with your family or group. Take the handheld units on hikes. Let the kids send messages to each other across the neighborhood. The more familiar everyone is with the system, the more useful it will be when it matters.

Reticulum isn't trying to replace your phone. It's the communication system that works when your phone doesn't.

Previous: [Part 11 — Reticulum over I2P and Tor]

This concludes the 12-part Reticulum guide series. For more information, visit the official Reticulum documentation and the Reticulum GitHub discussions.