mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2024-11-09 23:24:10 -08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Move this block

Browse source
This commit is contained in:
Ben Meadors 2024-08-18 07:35:33 -05:00
parent 8f1ea72b5a
commit 9f72599abe
1 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
blog/2024/August/why-meshtastic-uses-managed-flood-router.mdx
View file

@ -14,6 +14,15 @@ Designing a low-bandwidth wireless mesh network to run on low-power microprocess
{/* truncate */} {/* truncate */}
## Key Advantages to Managed Flood Routing
1. Eliminates route discovery overhead
2. Provides superior adaptation to dynamic network topologies
3. Optimized for broadcast-heavy traffic patterns common in Meshtastic
4. Demonstrates excellent scalability in low-bandwidth environments
5. Minimizes resource utilization on constrained IoT devices
6. Empirically validated through extensive network simulations
Since Flood Routing is not very efficient, we realize that this approach is not perfect. The firmware has a number of measures in place to limit traffic in order not to overwhelm your mesh, but there will be a limit to what the mesh can withstand. In attempts to enhance the efficiency, we have evaluated “smarter” routing protocols at times in the past. However, we have yet to find anything that would consistently outperform the current approach in the use-cases and scenarios Meshtastic is currently being utilized. We’ll go over several reasons for why we believe Managed Flood Routing remains a superior approach for Meshtastic. Since Flood Routing is not very efficient, we realize that this approach is not perfect. The firmware has a number of measures in place to limit traffic in order not to overwhelm your mesh, but there will be a limit to what the mesh can withstand. In attempts to enhance the efficiency, we have evaluated “smarter” routing protocols at times in the past. However, we have yet to find anything that would consistently outperform the current approach in the use-cases and scenarios Meshtastic is currently being utilized. We’ll go over several reasons for why we believe Managed Flood Routing remains a superior approach for Meshtastic.
## Avoids Route Discovery ## Avoids Route Discovery
@ -35,15 +44,6 @@ Finally, Managed Flood Routing minimizes footprint on very resource-constrained
![Route Plot](/img/blog/route_plot.png) ![Route Plot](/img/blog/route_plot.png)
::: :::
## Key Advantages to Managed Flood Routing
1. Eliminates route discovery overhead
2. Provides superior adaptation to dynamic network topologies
3. Optimized for broadcast-heavy traffic patterns common in Meshtastic
4. Demonstrates excellent scalability in low-bandwidth environments
5. Minimizes resource utilization on constrained IoT devices
6. Empirically validated through extensive network simulations
## Considerations and Future Directions ## Considerations and Future Directions
While Managed Flood Routing has proven highly effective for Meshtastic, we acknowledge its limitations: While Managed Flood Routing has proven highly effective for Meshtastic, we acknowledge its limitations: