Securely changing a distant node’s configuration—and knowing which failures still require a site visit.
Remote administration sends normal configuration requests through the mesh to an authorized distant node. It can save a site visit when an interval, channel option or module setting needs adjustment. It cannot fix a flat battery, failed radio, damaged antenna, unreachable modem configuration, crashed bootloader or a mistake that removes the only path back.
Current authorization model
For firmware 2.5 and later, the remote node stores the public key of each node allowed to administer it. Up to three administrator keys can be configured. Admin messages are then sent securely through the mesh. Firmware 2.4 and earlier used a secondary channel named admin with a shared PSK; current firmware retains that legacy mechanism only for managing pre-2.5 nodes when explicitly enabled.
The official Remote Node Administration guide should be checked for client-specific steps. Android and Apple clients support remote configuration workflows. The CLI uses --dest '!nodeid' with supported --get and --set operations. The Web client can configure an admin key locally but, according to current documentation, does not send remote administration commands.
Managed Mode is separate
Remote Admin works without Managed Mode. Managed Mode prevents ordinary connected clients from writing radio configuration; only authorized remote administration can change it. Before enabling Managed Mode, prove remote access end to end and retain a tested physical recovery path. Otherwise an operator can lock out local users without gaining reliable remote control.
What can usually be done
- Read supported radio and module settings.
- Change intervals, roles and many configuration values.
- Add or adjust channels with care.
- Prepare a controlled configuration change before a planned visit.
- Confirm selected settings after an update.
What it cannot do
| Failure | Why remote admin may fail |
|---|---|
| No power | The radio cannot receive an admin packet |
| Broken RF path | No control channel exists without connectivity |
| Wrong region, preset or frequency slot | The administrator can no longer reach the node’s radio settings |
| Bad firmware or boot failure | Configuration messages require running firmware |
| Hardware damage | Software cannot repair antenna, connector, battery or board |
| Lost administrator identity | The remote node trusts configured public keys, not a replacement key |
Safe change procedure
- Back up configuration and record firmware, node ID and administrator keys.
- Test remote reads before attempting a write.
- Change one low-risk setting and read it back.
- Never change every path-affecting setting in one operation.
- For modem/channel migrations, keep an on-site or independently reachable recovery node.
- Schedule high-risk changes when physical access is possible.
- Record the change, result and rollback plan.
Key stewardship
Use dedicated administrator nodes rather than personal devices that are frequently reflashed. Authorize more than one steward only when governance is clear. Store recovery information securely, remove access when responsibility changes and do not publish public keys, private keys and channel material together as an informal “backup.” The private key never belongs in a public site record.
Remote administration is not remote maintenance
Administration changes software settings. Maintenance includes cleaning solar panels, tightening connectors, replacing batteries, checking water ingress, updating firmware safely and repairing hardware. Even a remotely configurable node needs a named owner, site access plan, spare parts and retirement procedure.
Before relying on this feature, read Recovering an inaccessible remote node and Firmware updates and configuration backups. The best remote administration design assumes that one day remote administration will not work.