Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Managed Flood #26

Open
harelber opened this issue Feb 6, 2025 · 1 comment
Open

Managed Flood #26

harelber opened this issue Feb 6, 2025 · 1 comment

Comments

@harelber
Copy link

harelber commented Feb 6, 2025

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.

@GUVWAF
Copy link
Member

GUVWAF commented Feb 6, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants