MeshCore network topology
How clients and repeaters work together in MeshCore: route discovery, learned paths, and coverage shaped by repeater placement.
What is network topology?
Network topology describes how nodes connect in a network. In LoRa deployments, topology directly affects range, reliability, and latency.
In MeshCore, topology is repeater-based: clients send and receive messages but do not act as a general repeater layer. Forwarding is handled by repeaters (and room servers with repeat enabled).
This page explains how that model works in practice and why repeater placement has the biggest impact on network quality.
Practical MeshCore roles
MeshCore is best described by operational roles based on configuration and placement, not by broad generic node taxonomies.
Client node
User node for direct and room messaging. Clients do not repeat traffic.
Repeater node
Stationary node that forwards traffic and bridges distance between clients.
Room server with repeat
Always-on node configuration that can support room traffic with repeat behavior where needed.
Backbone repeater
Strategic repeater used to connect local subnets or nearby regions.
Mobile client
Portable client moving through the network and relying on local repeater coverage.
Topology patterns in the field
MeshCore structure emerges from repeater placement, terrain, buildings, and antenna performance.
1. Dense area with multiple repeaters
Urban areas often create overlapping repeater paths, improving delivery resilience.
2. Linear corridor
Along roads or spread-out settlements, repeaters often form a chain extending coverage.
3. Regional bridge via high site
A well-placed repeater can connect multiple local clusters into one practical network.
4. Growth through added repeaters
Adding repeaters often opens alternate routes and reduces single-path dependency.
Become part of the network
Place a repeater and strengthen MeshCore topology in your region
Start with MeshCore →How routing forms
MeshCore combines discovery traffic with more targeted forwarding through repeaters.
Flood for initial reachability
When no route is known, the network can use flood routing through repeaters to reach the destination.
Path learning after delivery
After successful delivery, path information can be learned so follow-up traffic is forwarded more directly via known repeaters.
Repeater placement drives quality
Real-world performance depends on repeater location, antenna, elevation, and configuration, not on every node acting as a router.
Benefits of this topology model
Resilient paths
Multiple repeater routes improve successful delivery chances.
Regional scalability
Coverage grows with added repeaters without turning every client into a router.
Better stability
Fixed repeaters in strong locations provide more predictable performance.
Clear role split
Clients communicate; repeaters handle forwarding.
Extended reach
Multi-hop through repeaters enables communication beyond direct radio range.
More efficient airtime
Learned follow-up routing reduces unnecessary broad forwarding where possible.
Frequently asked questions
What is the minimum number of nodes for a working network?
Two nodes are enough for direct testing. For useful regional coverage, strategic repeater placement matters more than an arbitrary minimum number of clients.
What is the maximum hop count in MeshCore?
MeshCore documentation references an internal upper bound of 64 hops. Practical behavior is tuned at repeater level (such as flood.max) and airtime targets.
Can I visualize my local topology?
Yes, by combining operational checks, community mapping, and field tests you can build a practical view of reachability and usable paths.
What happens with very high node density?
Channel pressure increases with simultaneous traffic. Good repeater placement, configuration discipline, and message hygiene keep performance usable.
Is a hub-like pattern possible in MeshCore?
Yes. In practice, strong repeaters on good locations often become key links between local subnets.
Strengthen MeshCore topology
A MeshCore network gets stronger through thoughtful repeater placement and correct role configuration.