Skip to main content
Pitch In Subscribe

Multi-Repeater Network Coordination

When multiple MeshCore repeaters serve the same community, coordination between operators ensures the network behaves predictably and provides maximum benefit to users.

ChannelRadio Preset Consistency (and the Channel-Key ConsistencyMyth)

AllA repeaterscommon misconception is that every repeater on a community network must share a "channel key." It does not. In MeshCore, repeaters forward packets based on routing/path information and do not decrypt message payloads — they relay encrypted traffic for any channel without needing that channel's key. Channel keys are a client-side concern: only clients holding a channel's key can read that channel's group messages. So a repeater never "silently drops traffic it cannot decrypt." What every repeater (and client) must share to interoperate is the same publicradio channelpreset key./ frequency — if the radio parameters don't match, the repeater literally cannot hear the packets. When deploying a new repeater, obtaincoordinate the communityradio channelpreset, keyfrequency, fromand repeater naming/placement with the network coordinator before commissioning. An incorrectly keyed repeater will be visible on the network but will silently drop all traffic it cannot decrypt.

Verify channela keynew consistencyrepeater is relaying by attemptingsending a test message from a client node so that it routes through the new repeater. A successful delivery confirms the repeater is hearing and forwarding correctly (correct preset, placement, and RF range). It does not test channel-key alignment.alignment — that is verified between client nodes (whether two clients can read each other's group messages), not at the repeater. A failed route-through test points to a radio-config/preset mismatch or insufficient RF range, not a missing channel key.

Coverage Overlap Planning

Adjacent repeaters should overlaphave theirsome coverage areasoverlap byfor 20-30%.redundancy Thisand continuity. The exact amount depends on terrain, antenna height, and node density — there is no universal percentage. Validate overlap empirically with drive/walk tests confirming each area is reachable via at least two repeaters. Overlap provides:

  • Redundancy - if one repeater goes offline, adjacent repeaters still serve the overlap area
  • ReliableContinuity handoffof coverage for moving nodes - when a mobile nodesnode travelingleaves one repeater's range, its cached path will fail and MeshCore re-runs path discovery to find a route through the coveragenext areain-range maintainrepeater. connectivityThis asis theynot movea seamless cellular-style handoff — there is no association handed between repeaters; any in-range repeater rangessimply relays. Expect a brief delivery gap while a new path is discovered. Overlap reduces, but does not eliminate, this gap.
  • Route diversity - multiple path options between distant network segments improve end-to-end reliability

Insufficient overlap creates coverage holes where users are out of range of all repeaters. ExcessiveAt overlapthe (underother 1kmextreme, spacingdeploying inmany urbanrepeaters areas)very createsclose unnecessarytogether traffic— covering the same footprint with no new coverage — adds channel airtime contention and flood amplification without coverageproportional benefit. Note that close spacing is not inherently wasteful: in dense urban terrain with heavy building attenuation, sub-kilometer spacing can be necessary and appropriate (the density guidance suggests roughly one repeater per ~1 km² / ~500 m radius). Avoid overlap only where it is genuinely redundant.

Frequency and Preset Coordination

All community repeaters must use the same presetradio parameters (the USA/Canada recommended)preset is recommended in this region). Verify with:

statusget radio

The statusget radio output shows the current preset, frequency, bandwidth, spreading factor, and othercoding rate (get freq and get tx report frequency and TX power individually). MeshCore presets are an app-side selection; the serial CLI reports the raw radio parameters.parameters rather than a named preset. Confirm these values match the communitycommunity-standard standardUSA/Canada preset before committing a new repeater to service.

Network Documentation

Maintain a community document with:

  • Repeater name, operator callsign/contact
  • Physical location (approximate - GPS coordinates if the operator consents to publishing)
  • Power system type (mains, solar) and expected uptime
  • Installation date and last maintenance date
  • Known coverage limitations or issues

This documentation is invaluable when diagnosing network problems or planning expansion. Store it in a shared document that all operators can access and update.

Repeater Retirement and Replacement

When a repeater is permanently taken offline, notify the community so they can update routing expectations and coverage maps. Removing a node that other nodes' cached routes depend on will cause temporary routing failures until routes are rediscovered. This is normal behavior; MeshCore re-discovers routes when existing paths fail.

Back to top