-
Notifications
You must be signed in to change notification settings - Fork 0
Supernodes
mathisono edited this page Jun 8, 2026
·
4 revisions
By default, Crow only shared traffic within the local AREDN network, and not to other AREDN networks. If you want to share traffic with other AREDN meshes you must install Crow on your local supernode.
Crow should be installed on a Supernode just as you would normally install it (see the here for details). It will automatically recognizes it has been installed on a Supernode and reconfigure itself appropriately; there are no extra configuration steps.
- When installed on a supernode, any Meshtastic or MeshCore configuration will be ignored. A supernode instance cannot act as a bridge.
- A supernode cannot act as a text store (see Text Stores.
- You can send messages just like a normal Crow instance; but probably best not to do that.
Crow on a supernode will relay messages from your local AREDN mesh to other Crow instances on other meshes. However, this is only active if those Meshes also have a Crow Supernode instance.
- Home
- Change Log
- Configuration
- Configuring Channels
- Backend Selection and Test Deployment
- Command Reference
- APRS Bridge
- LoRa Gateway Tags
- Meshtastic API Backend
- Memory Use
- Strict Gatekeeper
- Winlink
- USB Storage
APRS.mdBackend-Selection-and-Deployment.mdChange-Log.mdCommand-Reference.mdConfiguration.mdConfiguring-Channels.mdHome.mdLoRa-Gateway-Tags.mdMeshtastic-API.mdMemory-Use.mdStrict-Gatekeeper.mdUSB-Storage.mdWinlink.md_Sidebar.md
- Keep every
.mdwiki page linked here. - Keep
Home.mdand_Sidebar.mdin sync. - When a wiki page is removed, remove it from both the Home page inventory and this sidebar.