Device Roles

Nearly all Meshtastic devices on the mesh should be set to either Client-Mute or Client/Client-Base role.

It is critical to the effectiveness of the mesh that devices not be used in ROUTER mode unless it is truly able to function as a router. Routers are used to shuttle traffic around from region to region/area to area on our mesh. A poorly-placed or constructed Router can severely degrade mesh effectiveness in the area around it and potentially even further away.

A ROUTER MUST FIT THE FOLLOWING CRITERIA
:

  • Documented build/location project thread on the Discord for community vetting
  • 90 ft above ground level minimum antenna height, full 360 degree coverage
  • Must have at least 5 other Routers or Router Late nodes with DIRECT bi-directional communication.
  • Node owner must be communicative with the overall group, and potentially willing to share admin capability to facilitate /participate in routing tweaks & experiments

OTHER NOTES ABOUT ROUTERS AND MSP MESH:

  • Please understand — We’re not mad, not trying to be mean, and not trying to be control freaks. Meshtastic’s performance on a mesh this large is very sensitive to the role of Routers. A lot of people work very hard to locate, plan, build, and maintain the community’s Routers.
  • ROUTER LATE and CLIENT BASE and CLIENT are all extremely helpful to your local area of the mesh, and will not cause the problems that using Router mode will cause. All of these device types repeat mesh traffic whenever applicable.
  • If a node is marked by the community as a mis-roled Router continues to operate in Router mode after attempts to contact the owner via the mesh public chat and/or Discord, the node will be placed into the “ignore” lists of the existing Router network in an attempt to mitigate the damage to the greater mesh. This will severely limit the reach of the mis-roled Router node.
  • Again – We’re not just making rules for the sake of making rules – we are just working to make sure the mesh functions as well is it can for everyone. We fully realize that nobody is intentionally setting up Routers with the intent to damage mesh performance, but our experience over the years has been that the issue doesn’t fix itself very often and action must be taken.
  • Education is essential to making the mesh function as well as it can. We’re all learning this together!

If you think you may have a node or location that is suitable to participate in MSP Mesh infrastructure, check a generated coverage map and have fellow MSP Meshers review your findings before converting to a Router/Repeater.

Also DO NOT use “Repeater” mode if:

Feel free to check out Meshtastic.org’s roles documentation as well as theirĀ configuration tips.