MeshCore Network Expansion Strategies
When to Add a Repeater vs. When to Move One
When to Add a Repeater vs. When to Move One
Every mesh network operator eventually faces two related but distinct decisions: should you spend money on new hardware, or should you reallocate what you already have? This page gives you a structured framework for making that call.
Signs You Need a New Repeater
Adding hardware is justified when a gap in coverage is genuine and cannot be resolved by repositioning existing nodes. Look for these indicators:
- Coverage gap identified via traceroute: Users in a specific area cannot reach the room server within three hops. Three hops is the practical reliability threshold for MeshCore; beyond that, delivery rates drop sharply and latency increases. If a pocket of users consistently shows four or more hops or message failures, that location needs a node.
- New neighborhood with active users: A cluster of users has joined from an area that was previously uninhabited or where no one had a radio. Coverage there is zero - there is no node to reposition.
- Edge-of-coverage user: A new member joins from a location that can hear the mesh but with marginal signal. Rather than asking them to upgrade antenna hardware, a well-placed intermediate repeater improves reliability for all nearby users simultaneously.
Signs You Should Move an Existing Repeater
Repositioning is often higher-impact per dollar than buying new hardware. Consider moving a repeater when:
- Low-traffic repeater competing for airtime: A node that forwards very few messages per hour - check logs or room server statistics - may be co-located with a better-positioned node. Redundant coverage in the same area wastes airtime that could instead serve a gap elsewhere.
- Changed environment: A building constructed after your original deployment may now block the path your repeater was designed to bridge. Treat your network map as a living document; re-audit coverage whenever significant physical changes occur nearby.
- Better site identified: A rooftop access agreement, a new community partner with a tower, or simply a higher hill - if a superior site becomes available, the math usually favors moving over adding.
Cost-Benefit Framework
Before committing to either action, estimate the impact. A new repeater at $60-$220 is worthwhile if it adds more than 10-15 active users to reliable coverage. Repositioning an existing repeater costs only your time (a few hours) and the risk of temporarily losing coverage during the move - usually 30-90 minutes. If repositioning achieves 80% of the benefit of a new node, move first and buy later.
One practical heuristic: if the candidate site for repositioning serves both the existing coverage area AND the gap, move the node. If the candidate site would leave the existing area uncovered, buy a second node to fill the gap and keep the original in place.
Documentation Practice
Record every deployment decision in a simple network log: node ID, site, date placed, reason for placement, date and reason for any relocation. This history becomes invaluable when diagnosing problems or onboarding new network operators who were not present for the original decisions.
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 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.