Under active development. Breaking changes expected. APIs, installers, and UI may shift between releases.
Five uplinks. One router. No reconfig.
The agent watches every uplink you have plugged in, picks the best one, and fails over automatically when it dies. Swap sites and the right path comes up on its own.
Uplink Matrix
Everything you plug in is a path.
The uplink router picks by priority. You can override the defaults per site through the Hardware tab or the ados gs network CLI.
| Uplink | Role | Priority | Typical use | Behavior |
|---|---|---|---|---|
| WiFi AP | Always on | N/A | Serves laptop and phone clients locally. | Local only, not a cloud path. |
| Ethernet | Best cloud path | 1 | Bench, lab, fixed-site deployments. | Chosen first when link is up. |
| WiFi client | Join existing network | 2 | Home WiFi, venue hotspot, office lab. | Used when Ethernet is down. |
| 4G LTE | Cellular fallback | 3 | Remote sites with no WiFi or Ethernet. | Used when both wired paths are down. |
| USB tether | Laptop-only | 4 | Bench debug, indoor lab. | Lowest priority, laptop-side only. |
Failover
Three strikes, then switch.
The uplink router runs a short health check on the chosen path. Three consecutive failures trigger failover. Three consecutive successes on a lower-priority path switch back.
The health check is a cheap HTTPS probe against an Altnautica endpoint every 15 seconds on the active uplink. Three failures in a row moves the active uplink to the next priority. On lower-priority paths, the check runs every 60 seconds. Three successes flip the active back. This pattern avoids flapping on a marginal link.
Priority lists beat round-robin for a field station because the operator usually knows that Ethernet is cheaper than WiFi which is cheaper than cellular. The agent honors that intent and does not try to optimize bandwidth by striping across paths.
Shipped
Production, not promise.
Every feature on this page is code-complete on main and shipping in the current release. The cloud observer path is opt-in and available to any paired node.
Share Uplink
Give the whole field team internet.
Turn on share-uplink and the ground node becomes a NAT gateway for its own WiFi AP clients. One node, one 4G modem, every laptop and phone on the site gets online.
The share-uplink feature writes an iptables MASQUERADE rule from the AP subnet to the active cloud uplink. AP clients get internet. The rule is persisted so it survives reboots, and it is removed cleanly when the feature is turned off. Data-cap throttling applies to the shared path as well.
This is a convenience feature. Turn it on for a small team at a remote site. Turn it off when you are on a metered plan and want only the video stream on the cellular path.
Plug in the path. The router picks it up.
Uplink configuration, failover tuning, and cloud relay setup are covered in public docs.
Networking docs