mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2024-11-13 17:14:25 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Evaluating
Some checks failed
CI / quality (push) Has been cancelled
Details
CI / build (push) Has been cancelled
Details

Browse source
This commit is contained in:
Ben Meadors 2024-11-10 19:18:12 -06:00
parent 16b4eb5524
commit e6dde6a723
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
blog/2024/November/2024-11-10-choosing-a-device-role.md
View file

@ -37,7 +37,7 @@ The `REPEATER` role behaves very similar to `ROUTER` in terms of becoming a pref
#### What is a strategic location anyway?
When considering strategic locations for these two roles, consider a tower on mountain peak rather than a tall building. By electing a device to become a Router or Repeater, you are making an implicit choice for the entire mesh to prefer that node for rebroadcasts for any direct neighbors. This strategic placement becomes crucial for ensuring that packets can be delivered to the widest possible audience. Using line of sight viewshed survey tools to determine the optimal location is recommended, but selection can best be determined by collecting some real world data on the mesh first.
When evaluating strategic locations for these two roles, consider a tower on mountain peak rather than a tall building. By electing a device to become a Router or Repeater, you are making an implicit choice for the entire mesh to prefer that node for rebroadcasts for any direct neighbors. This strategic placement becomes crucial for ensuring that packets can be delivered to the widest possible audience. Using line of sight viewshed survey tools to determine the optimal location is recommended, but selection can best be determined by collecting some real world data on the mesh first.
![Router](/img/blog/router_not_router.png)