MeshCore Network Design

Planning a MeshCore Community Network

Deploying a MeshCore network for a community requires planning beyond simply placing repeaters - you need to think about coverage, redundancy, operator coordination, and long-term maintenance.

Phase 1: Define Coverage Goals

Before placing a single node, answer these questions:

Phase 2: Identify Candidate Sites

For each site, evaluate:

  1. Elevation - Higher is almost always better. Use topographic maps or USGS terrain data to identify hilltops, water towers, or tall buildings that have commanding views of the target area.
  2. Power availability - Mains power is most reliable; solar works at most outdoor sites; battery-only is acceptable for temporary or low-priority nodes.
  3. Accessibility - You will need to access this site for installation and maintenance. A perfect hilltop that requires technical climbing is impractical for most operators - and it is a real safety and liability hazard, not just an inconvenience. High sites that require climbing carry genuine fall and legal risk: use professionals for tower work, get written permission, and never climb without proper fall-protection gear and authorization.
  4. Permission - Property owner permission is required. Start with sites where you have existing relationships: your own roof, a cooperating business, a friendly landowner.

Phase 3: Coverage Analysis

Before installing, verify coverage using tools:

Phase 4: Deployment Sequence

  1. Deploy the backbone first - Install your 2-3 highest-coverage repeaters before deploying fill nodes. The backbone provides the largest coverage gain per node installed.
  2. Test between backbone nodes - Verify each backbone node can reach at least TWO other backbone nodes by independent paths, so the loss of any single node does not partition the network. Avoid daisy-chain topologies for emergency-grade networks - a chain that looks tested can still split in two when one node drops.
  3. Add fill nodes for dead zones - Use coverage testing to identify gaps; deploy targeted fill repeaters.
  4. Recruit community members - Once basic coverage exists, recruit nearby property owners to host additional nodes. Their rooftops fill gaps and add redundancy.

Documentation and Handoff

Create documentation before deploying each node:

Store this documentation somewhere accessible to all network operators - not just one person's laptop.

MeshCore vs Meshtastic: Choosing for Your Community

If you're building a community mesh from scratch, choosing between MeshCore and Meshtastic is one of the first decisions. This page provides a framework for that decision.

The Most Important Factor: Community

The single most important factor is what your local community already uses. A technically inferior protocol with 50 active nodes in your area is better than the technically superior protocol with zero. Check what's already deployed in your area before committing.

Choosing MeshCore When

Choosing Meshtastic When

Running Both

Some communities operate parallel Meshtastic and MeshCore networks. This is common in areas where early adopters chose different protocols. The networks operate on the same frequency band but use different packet formats and cannot interoperate. A single operator can run both by using two LoRa boards - one flashed as MeshCore, one as Meshtastic.

Running parallel networks adds complexity but ensures coverage for all community members regardless of which protocol they chose. If your community has both, coordinate channel settings and coverage to complement rather than duplicate each other.

Summary Comparison Table

FactorMeshCoreMeshtastic
RoutingPath-based (path discovery/acknowledgment)Flooding
Scales toLarger networks (path-based routing scales better than flooding)Smaller networks; flooding degrades as traffic grows. Exact node counts depend on traffic, airtime, and topology - load-test your own deployment.
DM encryptionCurve25519 ECDH + AES-128 (no forward secrecy)PSK pre-v2.5; Curve25519 ECDH since v2.5 (no forward secrecy)
App ecosystemSmallerLarger (Android, iOS, Web, Python)
Beginner friendlinessModerateVery high
Hardware supportMulti-band (firmware default 869.525 MHz EU; US builds ~910/915 MHz); runs many of the same LoRa boards as MeshtasticBroad (many boards/frequencies)
Room serversFirst-class firmware role (alongside Repeater and Sensor)No direct equivalent role; nearest analogs are the Store & Forward module, channels, and MQTT bridging
Community sizeSmaller, more technicalMuch larger

Repeater Density and Coverage Calculations

How many repeaters do you need, and where should they go? This page provides practical calculation methods for MeshCore network coverage planning.

The maximum range between two MeshCore nodes depends on the link budget:

Compliance note: Under 47 CFR 15.247, conducted output power in the 902-928 MHz band is capped at 1 W (+30 dBm), referenced to an antenna of 6 dBi or less. Antennas above 6 dBi require a dB-for-dB reduction in conducted power, yielding a derived EIRP ceiling of 36 dBm (4 W). There is no point-to-point antenna-gain exemption at 915 MHz - that applies only to the 2.4 and 5.8 GHz bands. The +22 dBm above is the SX1262's hardware ceiling, well within these limits; see the Antennas & RF / FCC compliance pages before increasing power or antenna gain.

Terrain Effects on Range

Free-space calculations assume line of sight. The figures below are best-case line-of-sight estimates assuming default SF/BW and ~5 dBi omni antennas. Treat them as approximate upper bounds, not planning targets - actual ranges vary widely with spreading factor, bandwidth, antenna height, power, and clutter. For emergency-grade coverage, derate heavily and confirm with field tests. Real-world path loss modifiers:

EnvironmentTypical Range (equal-height nodes)Range (one node elevated 30m)
Flat open terrain3-8 km10-20 km
Suburban (low buildings)1-3 km5-10 km
Dense urban (high-rise)0.3-1 km2-5 km
Forest/jungle0.5-2 km2-5 km
Mountainous (valley-to-peak)Variable20-50 km (ridge-to-ridge)

The 20-50 km ridge-to-ridge figure is achievable only with full line of sight, adequate Fresnel-zone clearance, and typically directional antennas - not the omni setup assumed elsewhere on this page. These are approximate field-reported results, not guaranteed coverage.

Coverage Area Calculation

For a given expected range R, a single omnidirectional repeater covers approximately:

Coverage area = pi * R^2

At R = 3 km: ~28 km^2 (~11 sq miles)
At R = 5 km: ~78 km^2 (~30 sq miles)
At R = 10 km: ~314 km^2 (~121 sq miles)

These are theoretical maximums. As a planning rule of thumb, actual coverage is typically only 50-70% of the theoretical circle due to terrain, buildings, and RF absorption - and real coverage is usually governed by client antenna height (handheld, low) rather than the repeater's radius.

Repeater Density Guidelines

The figures below are rough starting points for a first pass only, derived from the (unsourced, optimistic) range table above - not sourced guidelines. They assume near-best-case line of sight and ignore that most clients are handheld and low to the ground, so they tend to under-build coverage. Deploy conservatively and infill from measured RSSI/SNR data. For a network where most clients are within 1 hop of a repeater:

These are starting points biased optimistic. After initial deployment, use the actual RSSI/SNR data from your node database to identify coverage holes and place additional repeaters strategically.

Path Hop Analysis

In MeshCore, messages travel via discovered paths. The path length (hop count) determines:

Target: most clients should reach their typical destination (a room server, gateway, or key peer) within 3 hops. 5+ hops indicates a coverage gap that a new repeater could address. This 3-hop target is a reliability guideline, not a protocol limit - MeshCore supports up to 64 hops in firmware. Increasing the hop limit lets packets travel farther but does not improve per-hop reliability, so deep paths remain unreliable for time-critical traffic.