Setting Channel Keys and Network Identity

Your channel configuration defines who can communicate on your mesh. Getting it right from the start saves painful re-configuration later as your network grows.

Understanding Channel Keys

Both Meshtastic and MeshCore use a shared channel key (Pre-Shared Key or PSK) that all nodes on a given channel must share to communicate. The key serves two functions:

• Authentication - Nodes without the key cannot decode messages, preventing outsiders from reading your mesh traffic
• Network segmentation - Multiple community networks can coexist on the same frequency by using different keys

Important: If you use the Meshtastic default key ("AQ==" / all-zeros), your messages are readable by every Meshtastic node in range. For a community network, always set a custom channel key.

Generating a Strong Channel Key

# Generate a random 256-bit key (32 bytes, base64 encoded)
python3 -c "import os, base64; print(base64.b64encode(os.urandom(32)).decode())"

Distributing Channel Keys

Methods for sharing your channel key with new members:

• QR code - Meshtastic generates a channel QR code that encodes the full channel configuration (name, key, modem preset). Share via your website or print at events. The most convenient method.
• Deep link URL - Meshtastic QR codes encode as URLs (meshtastic:///...). Can be posted as a clickable link in your community documentation.
• Manual entry - For MeshCore and technical users, document the key as a base64 string in your private community documentation.

Key distribution security: Your channel key doesn't need to be secret from trusted community members, but don't publish it on your public website. Share it in your community Discord/Signal or at in-person events.

Multi-Channel Strategy

Consider running multiple channels for different purposes:

Network Name and Node Naming Conventions

Establish naming standards early. Consistent naming makes the node list immediately informative:

• Meshtastic long name format: [City/Area]-[Location]-[Type] - e.g., "PDX-WestHills-Repeater" or "SEA-Capitol-Hill-Node"
• Short name (4 chars max): Use initials + number - "WH01", "CH02"
• Repeater nodes: Include "Rpt" or "Rep" in the name to distinguish from client nodes
• Room servers: Include "RS" - "PDX-RS01"