Meshtastic device roles
Every Meshtastic node has a role that decides how it takes part in the mesh: whether it forwards other nodes’ traffic, prioritises its own messages, or stays quiet. The roles below are summarised from the official documentation at meshtastic.org.
Roles you will see around Castlegar
Client
A regular messaging device, connected to a phone app or used on its own. It rebroadcasts packets when no other node has done so first — the everyday role for personal nodes. Most of the nodes mapped so far run it: Splatt0001, Splat, Meshtastic 467c, Huginn and Muninn.
Client Base
A personal base station. It always rebroadcasts packets from or to the nodes it has favorited, and handles all other packets like a plain Client. The intended use is a well-placed attic or roof node that relays for your weaker, indoor or handheld nodes. Eye over Genelle is the only Client Base mapped so far.
Router
Infrastructure that always rebroadcasts packets once and is visible in the nodes list. Best positioned in a strategic high place to extend the mesh for everyone — but because too many routers slow the whole network down, the project recommends reserving this role for deliberately placed infrastructure. VE7BVV is the only Router mapped so far.
Other roles
| Role | What it does |
|---|---|
| Client Mute | Does not forward packets from other devices at all — lowest power use and least network load. |
| Client Hidden | Broadcasts only when needed, for stealth or power savings; it does not appear in other nodes’ lists. |
| Tracker | Prioritises broadcasting GPS position packets — for tracking people or assets. |
| Lost and Found | Regularly broadcasts its location to help recover a lost device. |
| Sensor | Prioritises telemetry broadcasts such as environmental readings. |
| TAK / TAK Tracker | Optimised for Team Awareness Kit (ATAK) integration in coordinated operations. |
| Repeater | Infrastructure that always rebroadcasts packets once, with minimal overhead. It is not shown in the nodes list. |
| Router Late | Like Router, but rebroadcasts only after everything else has had a chance, adding coverage for local clusters and dead spots. |
Choosing a role
The official guidance is simple: keep personal nodes on Client, Client Mute or Client Base, and use Router or Repeater roles only for deliberately placed infrastructure, because too many routers slow the whole mesh down. A Client Base on a roof, favouriting your indoor nodes, is the recommended way to extend your own reach.