Router vs. Repeater Role — Which to Choose

Overview of Device Roles

Meshtastic firmware supports several device roles that control how a node behaves on the mesh. For infrastructure nodes, the two most relevant are ROUTER and REPEATER.

ROUTER Role

• Actively participates in flooding and rebroadcasting all packets it hears.
• Maintains a node position - appears on the map at meshmap.net and in the app node list.
• Can receive and display messages; someone in the field can text the node directly to check status.
• Higher airtime usage because it retransmits more aggressively.
• Prioritises rebroadcasting packets that still have maximum hops remaining.
• Good for: nodes that also serve as monitoring points, nodes with a screen or GPS that need to appear on maps, medium-traffic networks.

REPEATER Role

• Optimised purely for packet relay - rebroadcasts with lower overhead.
• Does not broadcast its own position - will not appear on maps, which reduces network traffic.
• Does not receive messages for "self" - cannot be texted directly.
• Lower power consumption than ROUTER in practice because it generates fewer self-broadcasts.
• Firmware configures the device as a "hop maximiser" - prioritises packets that still have hops remaining.
• Good for: permanent unattended infrastructure, solar deployments, maximising battery life, reducing self-generated traffic.

When to Use Each Role

CLIENT_MUTE Role

CLIENT_MUTE is the opposite of a repeater - it prevents a regular client device (phone, laptop) from rebroadcasting mesh traffic. This is useful for devices that are on the mesh but should not consume airtime acting as relays, such as tablets used only for monitoring.

Setting the Role

In the Meshtastic app: Config → Device Config → Role → select ROUTER or REPEATER.

Via the web client at client.meshtastic.org: connect via USB, navigate to Device Config, and choose the desired role from the drop-down.