RF Comms
Mesh
Small messages over local radio links, using a network built by its users.
What a mesh does
A mesh can pass a message through participating radios when the recipient is not directly reachable. It still needs useful radio paths; buying a device does not create regional coverage. Meshtastic and MeshCore are separate LoRa-based messaging systems with different firmware and routing designs.
A Meshtastic node does not natively relay MeshCore messages, and neither is automatically a Reticulum node. Choose the system the people near you use, then coordinate settings.
Meshtastic and MeshCore compared
| Consideration | Meshtastic | MeshCore |
|---|---|---|
| Approach | Managed rebroadcasting for broadcasts; current versions also learn routes for direct messages. | Discovery and learned paths, with dedicated repeaters providing infrastructure. |
| Strengths | Messaging, position, and telemetry projects; mobile apps and integrations. | Focused messaging and deliberate repeater placement suit a planned network. |
| Trade-offs | Busy networks and frequent telemetry consume airtime; role and channel choices matter. | Companion radios do not relay like repeaters; range expansion needs repeater infrastructure. |
| Privacy | Private channels and direct-message protections; default public channel keys are published. | Private messaging and channels; public channels and shared keys still need care. |
| Starting equipment | Supported radio, Meshtastic firmware and app, agreed region/preset/channel. | Supported radio with companion firmware and app, agreed network settings. |
| Compatibility | Cannot directly message MeshCore radios. | Cannot directly message Meshtastic radios. |
Privacy choices
The default public channel is not private. Meshtastic’s published default key lets others read those channel messages. Use a private key for a private group, share it carefully, and check current direct-message protections.
Position broadcasts, node names, gateways, and MQTT bridges can expose information even when content is protected. Review what your node shares and whether a bridge forwards it to the Internet. Both systems depend on endpoint security and careful key handling.
A Central Illinois Meshtastic goal
I want to help connect Central Illinois on Meshtastic. This is a goal for local testing, not a claim that continuous regional coverage exists. Find nearby users, match their region and radio preset, and prove a short path before adding sites.
Start with two compatible radios and antennas. Set the US region and agreed settings, exchange messages both ways, and record locations and obstacles. Place infrastructure based on those tests rather than advertised maximum range.
Emergency and self-managed uses
Low bandwidth messaging can support check-ins and simple status reports when mobile service is unavailable. It is not a replacement for a dependable way to call emergency services. Test contacts, power, and a check-in plan before an outage.
A self-managed server can log permitted telemetry or run a local integration. An MQTT bridge can connect radio information to IP tools, but the radio path and Internet bridge are different dependencies. Review what leaves your network and avoid flooding the channel with server updates.