mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2025-03-05 21:00:08 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fixed slug

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

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

@ -1,19 +1,19 @@
--- ---
title: Why Meshtastic Uses Managed Flood Routing title: Why Meshtastic Uses Managed Flood Routing
description: "Why Meshtastic Uses Managed Flood Routing" description: "Why Meshtastic Uses Managed Flood Routing"
slug: meshtastic-opposition-to-nextnav-proposed-changes slug: why-meshtastic-uses-managed-flood-routing
authors: [thebentern, GUVWAF] authors: [thebentern, GUVWAF]
tags: [meshtastic] tags: [meshtastic]
date: 2024-08-17T12:00 date: 2024-08-18T12:00
hide_table_of_contents: false hide_table_of_contents: false
image: "/design/web/social-preview-1200x630.png" 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/). 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* simulations ### 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) ![https://github.com/GUVWAF/Meshtasticator](/img/blog/route_plot.png)
{/* truncate */} {/* truncate */}