Deploying Mesh Networks in Disaster Scenarios

Overview

Deploying a LoRa mesh network during an active disaster differs significantly from a planned exercise. Speed, improvisation, and integration with an active ICS structure are paramount. This page walks through the complete deployment sequence from pre-event staging through live operations.

Pre-Event Staging

The most effective disaster mesh deployments begin well before the event. Pre-staging includes:

Fixed relay nodes at key sites: EOC, hospitals, Red Cross shelters, CERT caches, and strategic high-elevation points (water towers, fire stations) should have permanently installed relay nodes maintained on standby power.
Go kit pre-positioning: Portable node kits stored at ARES/RACES deployment caches, pre-configured with the operational channel and node names.
Firmware and configuration freeze: Two weeks before a forecast event (hurricane, wildfire season), freeze firmware versions and push final channel configurations. Do not update during an active event.
Battery maintenance: Charge all battery systems to 100%. LiFePO4 cells should be stored at approximately 50% if not in active standby; bring to 100% 24-48 hours before expected deployment.

Rapid Deployment Sequence

Receive activation order from COML or ARES EC. Confirm assigned tactical node name, channel plan, and check-in frequency and interval.
Travel to assigned position with go kit. Log departure time in ICS 214.
Conduct site survey: Identify best antenna elevation point. Note any obstructions (buildings, terrain, foliage).
Deploy antenna: Elevate to maximum practical height. Secure coax and weatherproof connections.
Power up node: Allow 2-5 minutes for GPS cold fix. Confirm node name and channel in Meshtastic app.
Test connectivity: Send a check-in message to EOC-MAIN. Confirm receipt acknowledgment (green checkmark in Meshtastic).
Report to COML: Via voice radio or mesh message — node name, location (GPS coordinates or address), battery level, estimated endurance, node count visible.
Begin ICS 214 log: Record activation time, location, initial node count, and all subsequent events.

Antenna Elevation Strategies

In disaster environments, traditional antenna mounting points may be unavailable or unsafe. Practical options:

Vehicle rooftop: Magnetic mount antenna on a metal vehicle roof is fast to deploy and provides 2-4 meters of elevation above grade. Most effective in flat terrain or when working in a parking lot staging area.
Temporary mast: A 3-6 meter telescoping fiberglass push-up mast (e.g., MFJ-1910 or equivalent) with a ground stake can be deployed in under 5 minutes by one person. Provides significant elevation advantage.
Existing structure attachment: In urban rubble environments, attaching a whip antenna to any surviving elevated structure (fence post, utility pole stub, intact second-floor window frame) can provide 3-6 meters of elevation with minimal equipment.
Balloon lift: For extended fixed relay in flat terrain, a helium balloon can lift a lightweight node and antenna to 10-30 meters. Requires tether management and calm wind conditions.

Frequency Coordination with Served Agency

Confirm that your LoRa channel center frequency does not conflict with LoRaWAN sensors already deployed by the served agency (e.g., flood sensors on 915.2 MHz). The Meshtastic default US channel preset should be checked against the agency sensor inventory. Document the agreed channel in ICS 205.

Mesh Topology for Disaster Environments

Topology	Description	When to Use
Star (hub-and-spoke)	All field nodes communicate directly to a central elevated relay. No inter-node routing.	Open flat terrain; EOC has excellent elevation; small node count (fewer than 10).
Mesh (peer-to-peer)	Every node routes for every other node. Messages hop through multiple nodes to reach destination.	Urban rubble; blocked line-of-sight; large geographic area; many nodes.
Chain (linear relay)	Nodes placed in a line to extend range along a corridor (road, valley, ridge).	Evacuation corridor monitoring; search teams moving along a defined route.

Key insight: In rubble environments, more hops equals more coverage. A message that travels through 3 intermediate nodes to reach a buried receiver can succeed where a direct link cannot, because the signal is re-transmitted at full power at each hop. Meshtastic supports up to 7 hops by default (configurable). Do not reduce max hop count below 3 in disaster deployments.

Interface with ICS Structure

The mesh network is a resource managed by the Communications Unit within the Logistics Section. All operational changes (channel reassignment, node redeployment, shutdown) require authorization from the COML. Field mesh operators report to the COML, not directly to Operations. When Operations Section needs to reach a field team via mesh, the request flows: Operations Chief to COML to mesh operator to field node. This chain maintains ICS unity of command and ensures communications changes are coordinated.