You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Just to make sure, based on the managed flood routing, no routing table calculation for each node/client, right?
The node resubmits a message based on the frequency it intercepts the message in a predefined window.
The text was updated successfully, but these errors were encountered:
Indeed, it uses no routing tables, which requires control packets or metadata to derive and distribute across the mesh, which is costly using a low-bandwidth technology like LoRa. Instead, it uses the signal quality of a received packet to determine a rebroadcast delay, thereby giving priority to nodes on the edges and thus enhancing the coverage (limiting the amount of hops needed). Nodes in CLIENT mode only rebroadcast when they did not hear anyone else do so.
See also: https://meshtastic.org/docs/overview/mesh-algo/#layer-3-managed-flooding-for-multi-hop-messaging
Hi,
Just to make sure, based on the managed flood routing, no routing table calculation for each node/client, right?
The node resubmits a message based on the frequency it intercepts the message in a predefined window.
The text was updated successfully, but these errors were encountered: