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

Try blockquotes

Browse source
This commit is contained in:
Ben Meadors 2024-08-17 08:30:56 -05:00
parent 2b04e22a8b
commit cfc2479565
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -3,7 +3,7 @@ title: Why Meshtastic Uses Managed Flood Routing
description: "Why Meshtastic Uses Managed Flood Routing"
slug: why-meshtastic-uses-managed-flood-routing
authors: [thebentern, GUVWAF]
tags: [meshtastic]
tags: [meshtastic, technical]
date: 2024-08-18T12:00
hide_table_of_contents: false
image: "/design/web/social-preview-1200x630.png"
@ -12,12 +12,12 @@ image: "/design/web/social-preview-1200x630.png"
Designing a low-bandwidth wireless mesh network to run on low-power microprocessors with limited memory is challenging. Arguably the simplest mesh routing protocol is Flood Routing: each radio receiving a packet will rebroadcast this again, up to a certain hop limit. Although Meshtastic is based on this, there are a few subtle, but significant enhancements. Most importantly, before a node rebroadcasts, it waits a short while and listens if anyone else is rebroadcasting already. If so, it won’t rebroadcast again. Therefore, “Managed Flood Routing” would be a better name. For more details on the enhancements, please review our [documentation](https://meshtastic.org/docs/overview/mesh-algo/).
### Many of our decisions are based empirical data from [Meshtasticator](https://github.com/GUVWAF/Meshtasticator) simulations
![https://github.com/GUVWAF/Meshtasticator](/img/blog/route_plot.png)
{/* truncate */}
> ### Many decisions are based on empirical data from [Meshtasticator](https://github.com/GUVWAF/Meshtasticator) simulations
> ![Route Plot](/img/blog/route_plot.png)
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

2
blog/authors.yml
View file

@ -7,7 +7,7 @@ crichton:
github: rcarteraz
thebentern:
name: TheBentern
title: "Meshtastic Device Firmware Development Lead"
title: "Device Firmware Development Lead"
url: https://github.com/thebentern
image_url: https://github.com/thebentern.png
socials: