Meshtastic vs. MeshCore on Austin Mesh

• TL;DR; ELI5
• Mesh networking in 30 seconds
• Default roles & behavior
• Hop Limits
• Telemetry & airtime
• Radio presets, throughput & interference
• When to use each
• Comparison table

TL;DR; ELI5

ELI5

Think of passing a secret across a playground using hushed voices or whispers. With Meshtastic, every single person passes your whisper along, so the chain moves and grows even if people are moving around. They also keep track of how many people have shared your secret, and once it’s been shared 7 times, they stop. With MeshCore, only certain people (called repeaters) pass the whisper, but they can pass it to up to 64 times instead of only 7.

By default, with MeshCore those helpers also talk faster and there are fewer side conversations that cause your secret to be delayed. On Meshtastic, everyone talks slower and are having side conversations, causing your secret to slow down or get lost.

TL;DR;

Meshtastic is best when people/radios are moving (e.g. music festival, hiking, bike rides) because every node rebroadcasts messages, so the network “self-heals”.

MeshCore is best when there are repeaters in static positions(e.g. city wide mesh with rooftops/hills).

Comparison Highlight

• Repeat/hop limits: Meshtastic default 3 (max 7); MeshCore up to 64.
• Who rebroadcasts: Meshtastic “clients” help rebroadcast; MeshCore only repeaters rebroadcast.
• Telemetry (e.g. node info, battery, temperature): MeshCore pushes rarely(if at all), and allows manual requests. Meshtastic pushes less than it used to(v2.7.15 Nov of 25, but still significantly more often than MeshCore.^[19].
• Responsiveness: MeshCore feels considerably faster by default; Meshtastic requires manual tuning for similar results.

Default roles & behavior

A role is a preset behavior applied to a radio/node.

• Meshtastic: Default role is CLIENT. Clients rebroadcast, allowing ad-hoc/moving groups to connect without static infrastructure.^[4]
• MeshCore: Companions(what your phone connects to to send messages) do not rebroadcast packets. Only Repeaters rebroadcast, concentrating airtime to well-placed infrastructure nodes.^[5][6][7]

Routing strategies

• Channels
• Both technologies use pure flood routing for messages sent in channels.
• Direct Messages
• Both technologies(as of Meshtastic v2.6) use a form of “learned” routing.
• Meshtastic: “Managed flood”. Flood to discover, then “next hop” routing for subsequent DMs. Next Hop routing is notably complex because it had to be backwards compatible and handle mobile nodes and asymmetric links^[1][2]
• MeshCore: Flood then defined path. The first message floods to learn a path; later messages use that learned path; if the path fails after a few(4) retries, it uses flood as fallback and can automatically re-learn a new path. Paths can be manually observed and configured, allowing for network tuning.^[3]

Hop Limits

• Meshtastic: Default Max Hops = 3 (configurable to max 7). In November of 2025 Meshtastic introduced “Zero-Cost Hops” through specific configurations.^[8][20]
• MeshCore: Max hop limit = 64. MeshCore has 3 different hash sizes(1b, 2b, 3b) which impact the number of hops available. 1-byte(e.g. a1) allows 64, 2-byte(e.g. a1b2) allows 32, and 3-byte(e.g. a1b2c3) allows 21. Longer hashes allow more specific paths once there are enough nodes that there are duplicate hashes on the network.^[9]

Here in Austin we have low hill/valley terrain often requiring many repeats(we regularly see 10+). Seven hops can be a hard ceiling for Meshtastic across the whole metro, while MeshCore’s higher limit gives more headroom.

Telemetry & airtime

• On very large meshes, background telemetry can consume valuable airtime, and it should only be enabled when necessary. As of Meshtastic firmware v2.7.15, some device telemetry broadcasts are disabled by default. As network device count increases, frequency of these broadcasts lowers to reduce congestion. ^[10][19]
• MeshCore defaults to no telemetry except repeaters which announce themselves every 24h. Environmental telemetry may be requested on demand.^[7][16]

For Austin Mesh (where the goal is region wide text communication) MeshCore leaves far more airtime for actual messages. Updates to Meshtastic have aimed to close the gap, but require most, or all, devices on the network to update first. Due to many “zombie” nodes which are no longer maintained, the Meshtastic network mostly remains unstable(July, 2027).

Radio presets, throughput, and interference

Both systems use LoRa (Chirp Spread Spectrum), where bandwidth, spreading factor (SF), and coding rate (CR) are used to balance range, speed, airtime.^[11]

• Meshtastic defaults: The standard preset is “LongFast”, which (in US) uses 250 kHz bandwidth and a conservative SF/CR mix. It’s robust, but airtime per message is relatively high, especially over multiple hops.^[12][13]
  NOTE: You can switch Meshtastic to faster presets (e.g., MediumFast/ShortFast) or even custom narrow bandwidths.^[14]
• MeshCore US default: narrow bandwidth (62.5 kHz) with moderate SF/CR to slot that tends to sit between noisy parts of the band.^[15][17]

Since September of 2025, the narrower MeshCore default have produced noticeably more responsive and reliable delivery (sub-second for nearby peers and ~5s for 9 hop routes vs 10-20s for Meshtastic). Your experience will vary by terrain, antenna quality, and infrastructure density, but the airtime math generally favors higher data rates + less background traffic.

When to use each

• Choose Meshtastic if you want a “bring-a-radio, it just works” experience for roaming groups, mapping, and rich telemetry modules, with minimal setup and no guaranteed infrastructure.
• Choose MeshCore if your aim is a resilient, city or region scale messaging network with fixed repeaters(Shameless plug for our DIY Solar Repeater Parts List).

Quick comparison

Footnotes

1. Meshtastic uses Managed Flood Routing for broadcast messages to avoid heavy route maintenance on low-bandwidth radios. Meshtastic blog: “Why Meshtastic Uses Managed Flood Routing.” link ↩ ↩
2. Meshtastic v2.6 adds next-hop routing for Direct Messages (DMs): flood to discover, then optimized relays. Docs (“Mesh Algorithm”) & 2.6 preview post. Docs: link · Blog: link ↩ ↩
3. MeshCore flood-then-direct routing: flood to learn → embed path → fallback to flood if direct fails. (Concept pages & explainer.) Deep dive: link · Packet handling: link · Explainer: link ↩ ↩
4. Device roles — default role is CLIENT; CLIENT “rebroadcasts packets when no other node has done so.” Meshtastic Device Configuration. link ↩
5. “Repeaters route; edge nodes don’t pollute the airwaves.” MeshCore Philosophy. link ↩
6. Companion Radio Protocol (USB/BLE) connects apps to radios; it is an edge/client firmware, not a repeater. MeshCore Wiki. link ↩
7. Repeater/Room Server CLI (e.g., set repeat on, set flood.max {hops}, set advert.interval {minutes}, set flood.advert.interval {hours}). MeshCore Wiki. link ↩ ↩
8. Max Hops defaults to 3 and “can’t be greater than 7.” Meshtastic LoRa Configuration. link ↩
9. MeshCore internal max hop limit = 64. MeshCore Wiki (FAQ). link ↩
10. Regular broadcast intervals (defaults) and auto-backoff as meshes grow. Meshtastic “Mesh Algorithm” overview. link · Telemetry module reference: link ↩
11. LoRa = Chirp Spread Spectrum (CSS); SF/BW/CR drive data rate vs. range/airtime. Semtech AN1200.22 “LoRa Modulation Basics.” link ↩
12. Meshtastic modem presets (LongFast, MediumFast, ShortFast, etc.). Protobuf enum docs. link ↩
13. Comparative preset table (BW, SF, approximate kbps) and why LongFast isn’t ideal for dense meshes. Meshtastic blog. link ↩
14. Special bandwidth values supported in Meshtastic custom modem settings (e.g., 31.25 kHz, 62.5 kHz). Meshtastic LoRa Configuration. link ↩
15. MeshCore docs note that narrower BW + lower SF can fit between ISM-band interference and yield better SNR/airtime. MeshCore FAQ. link ↩
16. MeshCore communities commonly configure long flood-advert intervals (e.g., ~12 h) to conserve airtime; tooling and issues reflect this direction. CLI reference (adverts): link · Issue: link · FAQ note: link ↩
17. Example community settings (US/CAN): 910.525 MHz, 62.5 kHz BW, SF7/CR5. Ottawa Mesh. link ↩
18. Meshtastic docs caution against over-using infrastructure roles and hop counts on dense meshes; a network of CLIENTs with a small number of well-placed ROUTER/REPEATERs is usually best. Configuration Tips. link ↩
19. Meshtastic v2.7.15 disables some telemetry broadcasts over LoRa by default. Nodes must opt-in to broadcast telemetry. Meshtastic Firmware Release. link ↩ ↩
20. Meshtastic zero-cost hops blog post

Questions or edits? Open a PR on austinmesh.org’s repo or ping the Austin Mesh chat.