Not amateur radio
Channels and encryption
Named channels with shared keys, and what is and is not hidden from nodes that relay.
Not amateur radio
Named channels with shared keys, and what is and is not hidden from nodes that relay.
A channel is a named, encrypted group. Everyone who uses a channel with the same name and key forms one logical mesh. A node can hold up to eight channels, and only nodes set up with the same name and key can read a custom channel. Channels sit on top of the radio settings, which must also match for nodes to hear each other at all (see LoRa for mesh networks).
Channel 0, the default, has a blank name and a well-known key that is published. The Meshtastic documentation is blunt about it: anything sent on a channel that uses the default key can be read by anyone.
Only the application message is encrypted. The 16-byte routing header is sent in the clear, because relaying nodes need it, including nodes that cannot decrypt the packet.
That is why every node in range receives and may relay your packets whether or not it holds your key. A node's rebroadcast setting decides whether it relays packets it cannot decrypt.
Anyone listening can also read the header, which carries the sender and destination node numbers. The documentation is direct that this is not as strong as Wi-Fi WPA3, HTTPS or Signal, which add protections that do not fit in LoRa packets. It also describes optional integrity features on newer firmware, such as an authenticated mode for channels and signed broadcasts, since plain channel encryption does not detect a message that was changed in transit.
On amateur frequencies, the documentation says encryption is not permitted, and nodes in licensed mode send unencrypted; see Meshtastic and the rules.