LPWAN Meshes: The Verdict - Making the Choice

Over the past few weeks, I’ve pulled apart four different LPWAN mesh technologies. Now it’s time to bring those findings together and look at which tool fits which job on the property or in the community.

There is no “perfect” protocol. What we have is a set of tools with different trade-offs. I’ve evaluated all four across five parameters to help cut through the marketing noise and get to the technical reality.

The Five Key Parameters

In my experience with field deployments, these five areas are where the differences really show:

1. Range & Coverage — How far does it reach, and how well do multiple hops actually work?
2. Security — Is the cryptography baked in or bolted on as an afterthought?
3. Ease of Use — Can you get it running in an afternoon, or do you need a week with a serial console?
4. Scalability — Does the network fall over when you add the tenth node?
5. Resilience — How does it handle node failure, flat batteries, or moving targets?

Range & Coverage

Meshtastic: ★★☆☆☆

Leverages LoRa’s raw range well enough for point-to-point, but its rudimentary flood routing often makes multi-hop communication unreliable. In varied terrain, you might get 2-5 km, but don’t count on the mesh to reliably extend that through many hops.

MeshCore: ★★★★★

By using a structured approach—separating quiet “Companion” devices from dedicated “Repeaters”—MeshCore manages the airwaves much better. This allows for cleaner multi-hop links and better overall coverage in managed deployments.

Reticulum: ★★★★☆

Range on LoRa is comparable to the others, but Reticulum wins on its transport independence. Because it doesn’t care if the link is radio, WiFi, or a wired cable, you can bridge massive gaps using whatever backhaul is available while keeping the mesh intact.

ClusterDuck Protocol: ★★★☆☆

Hierarchical design (Duck/Mama/Papa) is solid for getting data from the field to a gateway. It’s not built for maximum range but for a reliable path from a disaster zone to a coordinator.

Security

Meshtastic: ★☆☆☆☆

Security feels like an afterthought. It uses pre-shared keys, lacks proper authentication, and is prone to spoofing. Fine for casual chat, but fundamentally inadequate for anything sensitive.

MeshCore: ★★★☆☆

Offers a good toolkit—AES-256, ChaCha20, and node authentication—but you have to know how to use them. It’s built for structured setups where you have the technical grit to configure things properly.

Reticulum: ★★★★★

The benchmark. Cryptography (Curve25519, Ed25519) is fundamental to the protocol. Every link is encrypted and authenticated by default. It’s the only one in this list I’d trust with critical communication.

ClusterDuck Protocol: ★★☆☆☆

Basic encryption meant to stop casual eavesdropping. It prioritises getting messages through in a crisis over cryptographic robustness.

Ease of Use

Meshtastic: ★★★★☆

The clear winner for accessibility. If you can use a mobile app, you can use Meshtastic. Just be aware that this ease of use masks some pretty significant flaws in routing and security.

MeshCore: ★★☆☆☆

A steeper climb. You’ll be editing configuration files and thinking about network topology. It’s for people building infrastructure, not those looking for a plug-and-play toy.

Reticulum: ★★★☆☆

Middle of the road. If you’re comfortable with a command line and basic networking, you’ll be fine. The quality of the documentation is excellent, but it doesn’t hold your hand.

ClusterDuck Protocol: ★★★☆☆

Designed for quick deployment in emergencies. While the concept is simple, the project’s maturity and hardware support have been patchy in the past, which can make the initial setup more of a chore than it should be.

Scalability

Meshtastic: ★☆☆☆☆

Flood routing is the enemy of scale. As the node count grows, the airwaves get congested with everyone shouting at once. It’s strictly for small, casual groups.

MeshCore: ★★★★☆

Built specifically to solve the scaling issues of flooding meshes. By managing who repeats what, it can handle hundreds of nodes without the network eating itself.

Reticulum: ★★★★★

Scales well through intelligent, path-aware routing. It doesn’t flood the network; it finds the best way through. Because it can bridge different mediums, it handles larger, more complex networks gracefully.

ClusterDuck Protocol: ★★★☆☆

The hierarchical “Duck” model handles medium-sized groups (50-100 nodes) well by funnelling data toward gateways rather than letting everyone repeat everything.

Resilience

Meshtastic: ★★★☆☆

Self-heals well enough in simple scenarios, but the unreliable routing means it can be temperamental when conditions get tough or nodes move frequently.

MeshCore: ★★★★★

Extremely resilient in managed environments. Fine-grained control over power and routing means you can build a network that stays up even when individual nodes go dark.

Reticulum: ★★★★★

Outstanding. If a radio link fails, it can hop to WiFi. If the internet goes down, it sticks to radio. This transport-agnostic failover is exactly what you want for remote safety.

ClusterDuck Protocol: ★★★★☆

Built for chaos. It handles node failures and rapid deployment better than most because that is its primary mission.

The Comparison Matrix

Recommendations: The Right Tool for the Job

For Rural Resilience and Safety

Choose Reticulum. If you need a network you can bet your life on in the back paddock or during a bushfire, this is it. The security is top-tier and the ability to bridge different radios and internet links provides the redundancy needed when things go wrong.

For Structured Community Infrastructure

Choose MeshCore. When you’re building a managed network over a town or district and need it to scale without congestion, MeshCore is the superior path. I’m currently part of a group exploring how to run MeshCore over a Reticulum “backbone”—combining MeshCore’s structured LoRa routing with Reticulum’s cryptographic transport.

For Emergency Response

Choose CDP. If you need to drop a network into a disaster zone and have it working in minutes with non-expert users, the ClusterDuck Protocol remains a relevant tool, despite its slower development pace.

For Casual Experimentation

Choose Meshtastic. It’s a fun way to learn the basics of LoRa, but I’ve moved away from it for any serious work. Its security and routing are too rudimentary for anything critical.

What I’m Using Now

My setup on the property isn’t a single-protocol monoculture. I use a hybrid approach that picks the best tool for each specific requirement:

• Reticulum: My primary LoRa mesh platform. It handles all secure messaging, remote safety comms, and any data I consider critical.
• LoRaWAN: I still use this for high-density, industry-standard sensor deployments (like soil moisture probes across large areas). It’s far more efficient for thousands of small data packets than any mesh.
• MeshCore: Currently being used in experiments as a structured layer over a Reticulum backbone.
• WiFi & WiFi-HaLow: I use standard WiFi for high-bandwidth needs and am actively exploring WiFi-HaLow (802.11ah) for medium-range links that need more throughput than LoRa can provide.

Final Thoughts

We’ve moved past the era of “just getting a packet through.” We now have the tools to build secure, resilient, and private networks that don’t depend on corporate clouds or fragile infrastructure.

For me, Reticulum is where I’ve landed for the serious work, but the exploration of MeshCore and the emerging WiFi-HaLow standards shows that the field is still moving fast. The key is to build for resilience—use the tool that gives you the most sovereignty over your own communications.

Now, get some dirt under your fingernails and start building.

• Lpwan
• Mesh Networks
• Meshtastic
• Meshcore
• Reticulum
• Clusterduck Protocol
• Comparison
• Agricultural