Definition
The hop limit is a Meshtastic LoRa configuration value that controls how far a packet travels across the mesh before it is dropped. Each packet carries a hop count; when a node relays it, the count decrements by one, and once it reaches zero, receiving nodes stop rebroadcasting. The default is 3 and the maximum is 7. This simple mechanism is what keeps a flood-routed mesh from drowning itself in endlessly circulating traffic.
Why the limit exists
Meshtastic uses managed flooding: there is no central router, so every node that hears a new packet may rebroadcast it. Without a hop limit, packets would loop indefinitely and saturate the shared LoRa airtime. Capping hops bounds the rebroadcast radius, conserves the duty-cycle budget on congested channels, and keeps latency predictable. Raising the limit extends reach but multiplies channel utilization — on a busy mesh, a high hop limit can actively degrade reliability for everyone.
Tuning guidance
For most deployments the default 3 covers several kilometers of node-to-node relaying and is the right starting point. Increase it only when you have confirmed dead zones and a sparse network where extra relays genuinely help. Because the setting is part of the LoRa config protobuf, it can be changed locally or via remote admin. Hop limit works hand-in-hand with the channel configuration that defines which nodes can decrypt and forward a given message. For background on flood-style relaying, see our broader mesh-routing material.
In Simple Terms
The hop limit is a Meshtastic LoRa configuration value that controls how far a packet travels across the mesh before it is dropped. Each packet…