What if messages could traverse your mesh infrastructure in a single hop?
What if you could bridge two cities 600 miles apart via LoRa and still have hops to spare?
What if a faster preset requires twice as many hops to reach your friends, but you don't have hops to spare?
That’s exactly what Zero-Cost Hops unlocks for your mesh.
Since the last guide on choosing the right role, a new role - ROUTER_LATE - has been added. What exactly does this role do, when should it be used, and how does it fit into the overall picture of how a Meshtastic network operates?
Meshtastic has a large number of device roles, each designed for a different purpose. While the default CLIENT is a good start for simpler meshes without complex obstacles to work around, for larger meshes with more complex routing needs it's important to select the right role to ensure that the overall mesh is robust, does not get overloaded, and ensures the reliable transit of packets to where they need to go.