Mesh Network Communication Without Internet

Evaluate three primary mesh systems: LoRa-based (Meshtastic: 1-10 km range, 100-300 mW power, sub-1 GHz); packet radio (goTenna: 4-6 km line-of-sight, proprietary encryption); Wi-Fi Direct (100-200 meters, high bandwidth, built-in to phones). LoRa excels in rural areas with minimal power draw. goTenna works without additional hardware for smartphone users. Wi-Fi Direct connects multiple devices instantly but limited range. Select based on your community's geography—mountainous terrain favors LoRa, dense urban areas benefit from Wi-Fi Direct mesh apps like FireChat or Bridgefy. Document your choice and ensure at least 3-5 devices per network node for redundancy.

LoRa frequencies vary by region (915 MHz in US/AU, 868 MHz in EU, 433 MHz in Japan)—verify local regulations before purchasing devices.

Purchase Meshtastic-compatible hardware (RAK Wireless WisBlock, Heltec LoRa 32 v3, or LilyGO TTGO): approximately $35-80 per unit. Charge fully via USB-C (2-3 hours). Download the Meshtastic app (iOS/Android). Enable Bluetooth on your phone, open the app, scan for nearby devices, and connect to the first mesh node. Configure basic settings: Set a unique node name (e.g., 'Node-Downtown-01'), select your region (automatically sets correct LoRa frequency), enable position tracking if GPS is available. Adjust transmit power to medium (5-10 mW) for 5-8 km range or low (1-2 mW) to extend battery life to 72+ hours. Set channel encryption with a shared 32-character passphrase for security—all community members must use identical settings to communicate.

Avoid maximum transmit power in enclosed spaces—it causes device overheating and reduces battery life from weeks to days.

Identify 4-8 high-elevation positions within your community: hilltops, tall buildings, water towers, or church steeples gain 3-5 km additional range. Place devices in weatherproof enclosures (IP67 rated PVC boxes, $5-15) with clear antenna orientation—vertical orientation provides omnidirectional coverage. Mount antennas 10-20 meters above ground when possible; every meter of height roughly doubles range. Connect solar panels (5-10 W) and a 5000 mAh battery to each node for continuous operation. Use 6-meter coaxial cable runs to separate the antenna from the device to reduce interference. Label each node with its name and frequency on weatherproof labels. Create a physical map marking all node locations and backup power locations in case of supply disruption.

Rooftop installations require landowner permission and fall-protection equipment—never install alone or during high winds.

Download backup messaging platforms that function over Meshtastic, Wi-Fi Direct, or Bluetooth: Bridgefy (Firebase backend with offline support), FireChat (peer-to-peer, no backend required), or Serval Mesh (mesh-native). For FireChat: Install on all community phones, create a single shared public chat room titled 'EMERGENCY-<YourArea>', and test message relay by standing 500+ meters apart. Configure Bridgefy with a custom relay server if operating in regions with restricted internet. Enable offline mode explicitly in app settings to ensure function without cellular or Wi-Fi. Create written instructions (laminated cards) for each app with: installation steps, how to enable offline mode, default chat room names, and reconnection procedures. Conduct monthly drills where 20% of community members use only mesh-based messaging for 4 hours to identify software gaps before emergencies.

Bridgefy and FireChat store message metadata—review privacy policies; do not share critical operational security details on public channels.

Create written Standard Operating Procedures (SOPs) for your mesh network: define 3-5 communication net times daily (e.g., 8 AM, 12 PM, 6 PM), assign a Net Controller at each time slot, and establish a check-in rotation where each neighborhood ward reports status in 30-second updates. Designate call signs (e.g., 'North-One' for North Ward Node 1) to avoid voice identification vulnerabilities. Establish message priority levels: Level 1 (Medical emergency), Level 2 (Critical infrastructure failure), Level 3 (Resource status), Level 4 (Informational). Require all operators to repeat back critical messages verbatim to prevent miscommunication. Train at least 2-3 primary and 2-3 backup operators per node to ensure 24/7 continuity. Distribute printed protocol cards to all participating households with phonetic alphabet for clarity (Alpha, Bravo, Charlie, etc.).

Without clear protocols, mesh networks become chaotic during stress—enforce discipline strictly during drills.

Conduct monthly range tests: Walk systematically from your home node in cardinal directions (N, S, E, W) at 500-meter intervals, sending test messages every 100 meters until connection fails. Document the actual range achieved (typically 60-80% of theoretical maximum due to terrain). Use a simple test script: 'Test message XYZ node name timestamp'—this ensures message timestamps sync correctly across the network. Test relay capability by having two operators 2-3 km apart communicate through a central node without direct line-of-sight—message delivery should occur within 10-30 seconds depending on network traffic. Test battery drain under load: run messaging for 4 hours and measure voltage drop using a multimeter; normal drain is 10-15% per 4-hour session. Create a test log documenting date, weather, atmospheric conditions, messages sent/received, and latency observed. Failures indicate antenna degradation, interference, or software issues requiring investigation.

Do not test during peak usage times—mesh networks degrade under heavy load and tests may disrupt emergency traffic.

Enable AES-256 encryption on all Meshtastic devices using a 32-character alphanumeric passphrase shared only through secure in-person distribution (never via email or phone). Rotate encryption keys quarterly using a documented key rotation schedule. Implement radio discipline: limit transmissions to critical information, use brief messages, and avoid repeating sensitive details unnecessarily—every transmission is broadcast to entire network. Segregate operational channels: reserve Channel 1 for emergency coordination, Channel 2 for resource status, Channel 3 for neighborhood welfare checks. Establish call-in passwords (e.g., 'Aurora' = all clear, 'Beacon' = alert status) to authenticate legitimate operators during chaos when voice recognition fails. Do not share node locations, operator names, or frequency information publicly—this prevents adversarial jamming. Audit device logs monthly for unauthorized access attempts or unusual activity patterns.

Encrypted mesh networks may attract regulatory scrutiny in some jurisdictions—verify local laws before deploying community-wide systems.

Create a maintenance calendar: check solar panel cleanliness monthly (dust reduces output 20-30%), test all batteries quarterly, inspect weatherproofing seals bi-annually, and replace antenna cables every 2-3 years (UV degradation). Maintain a physical parts inventory at each node location: spare LoRa modules ($50-70), batteries (5000-10000 mAh), coaxial cable (50 feet), enclosure gaskets, and silica gel desiccant packs replaced every 6 months. Document all hardware serial numbers, installation dates, and last service dates in a neighborhood mesh registry. Designate 2-3 trained technicians responsible for repairs with backup training for successors. Store encrypted backups of all device configurations (MAC addresses, encryption keys, channel settings) in secure offline locations—configurations enable rapid node restoration if devices fail. Schedule annual community review meetings where all operators verify device status and discuss operational improvements learned from drills.

LoRa devices degrade without maintenance—replace corroded connectors immediately or connection reliability drops 40-60%.