Linking Isolated Mesh Islands

Linking Isolated Mesh Islands

As independent community mesh networks grow, they sometimes develop in parallel—two neighborhoods, two towns, or two emergency response zones that each have healthy internal mesh coverage but no connection between them. When those communities have reason to communicate or coordinate, linking the islands becomes a priority. This page covers the main technical approaches and when each is appropriate.

Option 1: Long-Range Backbone Link (Yagi-to-Yagi)

A directional point-to-point RF link between two high sites can bridge 15-50 km under the right conditions. Each end requires a high-gain Yagi or panel antenna (12-17 dBi is typical for LoRa backbone links), a clear line-of-sight path with adequate Fresnel zone clearance, and a dedicated MeshCore node in REPEATER mode pointed at the far end. This approach is the lowest-latency and most resilient option when geography cooperates.

Technical requirements: Calculate path loss using a link budget tool before committing to hardware. At 915 MHz with 22 dBm TX power and 15 dBi antennas at both ends, reliable links to roughly 40 km are achievable over flat terrain. Hills, trees, and buildings reduce this significantly. Use the 0.6 Fresnel zone formula to ensure the direct path has adequate clearance above intervening terrain.

When it makes sense: Two networks that share emergency response responsibility—adjacent fire districts, overlapping amateur radio emergency service areas—benefit most from a persistent RF backbone that works without Internet infrastructure.

Option 2: Internet-Based Gateway Federation (Room Server to Room Server)

If both mesh islands already operate room servers with Internet connectivity, federation allows messages to bridge between networks via the existing Internet link. Users on either mesh can reach each other through a federated channel without any RF hardware changes. This is the fastest option to deploy and requires no line-of-sight between the networks.

Technical requirements: Both room servers must run a MeshCore version that supports federation, and operators must exchange server credentials or tokens to establish the trust relationship. Latency is typically under one second over a reliable broadband link.

When it makes sense: Networks that are geographically far apart but organizationally related—a regional amateur radio club with chapters in multiple cities—gain coordination capability without RF infrastructure changes. Federation does not help during Internet outages, making it unsuitable as the sole link for emergency-focused networks.

Option 3: Dual-Radio Bridge Node

A single physical site—ideally at high elevation between the two networks—hosts two LoRa radios, each tuned to a different mesh channel. The bridge node forwards traffic between channels, effectively stitching the two meshes together. This requires a custom firmware build or a lightweight software bridge running on an attached microcontroller or single-board computer.

Technical requirements: The bridge site must have RF visibility into both networks. Channel separation must be sufficient to prevent receiver desensitization (at least 500 kHz between center frequencies on the same band). Power requirements are roughly double those of a single-radio node.

When it makes sense: Two networks that share the same general region but grew independently on different channel plans. The dual-radio bridge allows both communities to keep their existing channel configurations while gaining interconnection.

Choosing an Approach

Emergency-resilient networks should prioritize the RF backbone (Option 1) or dual-radio bridge (Option 3)—both operate without Internet infrastructure. Networks primarily focused on everyday community communication, where Internet availability is assumed, can use federation (Option 2) as a lower-effort starting point, with the understanding that RF resilience can be added later.