Outbound paths start the suggested routes, for each site and fixed device

The user names the ways out of their node, one or more hops long, in order.
Each site of this computer (Home, Foulab) has its own list, one site is
active, and a fixed device keeps its own list.

- Explore > Outbound paths: the sites with the active mark, the fixed
  devices, and a staged editor for each list. Each path shows how well its
  first hop hears us (out) and how well we hear it (in). Measure sends one
  trace out along a path and back, after the cooldown.
- The path composer has an outbound mode, and puts the active paths first
  while the insertion slot is at our node (trace target, trace path, the
  TX sweep route).
- MeshTopology.outbound_scenarios: one route through each path. It scores
  from the link after the path, lets the user's order win a near tie, and
  skips a path whose first hop was silent for outbound_silent_hours. These
  routes lead Explore paths, the node page's Routes tab, and the trace auto
  route, ahead of a device route that starts on another hop.
- A first link out of our node is scored from what the far end measured,
  when a trace gave such readings.
- The site suggestion: when the radio hears the first hop of another site
  three times, the main menu asks to use that site and says what it heard.
  "Never suggest" sets the new suggest_site preference off.
- CLI: meshterm outbound [show|sites|use|set|remove|fix|unfix], plain and
  --json.

Refs: #35

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Jean-Pierre MartineauandClaude Opus 5.5 committed 2026-11-07 14:21:46 -05:00
1 parent c50656c586
commit ec64076d44
19 files changed
+2468 -55

No files matched your search

+43
View File
@@ -1622,6 +1622,49 @@ $ meshterm trace-path --path "a1,d4" --json | jq -r '.edges | min_by(.snr_db) |
a1 -> d4 2.0 dB
```
#### `meshterm outbound`
Show and change the outbound paths: the ways out of your node that the trace features
start their routes on. A path is a spec, the same as `--path` (`3d63,f2c2`), from your
node outward. Each site of this computer has its own paths, and one site is active. A
fixed device keeps its own paths, and the active site does not apply to it.
| Command | What it does |
| --- | --- |
| `outbound` or `outbound show` | The paths that apply to the connected device now, and where they come from. |
| `outbound sites` | Each site, whether it is active, and its paths. |
| `outbound use SITE` | Make a site active. `outbound use --none` makes no site active. |
| `outbound set SITE PATH…` | Make a site, or replace its paths, in your order. When no site is active, the new site becomes active. |
| `outbound remove SITE --yes` | Delete a site and its paths. |
| `outbound fix [PATH…]` | Give the connected device its own paths. With no path, it starts with the paths of the active site. |
| `outbound unfix --yes` | The connected device follows the active site again. |
```console
$ meshterm outbound set Home 3d63c6429436 27d4,f2c2
✓ site Home: 2 outbound path(s)
$ meshterm outbound sites
SITE ACTIVE PATHS
Home yes 3d63c6429436 27d4,f2c2
Foulab no a100
$ meshterm outbound
SOURCE site
NAME Home
RANK PATH HOPS
1 3d63c6429436 3d63c6429436
2 27d4,f2c2 27d4 → f2c2
```
`sites`, `use`, `set`, and `remove` do not open the device. `show`, `fix`, and `unfix`
open it, because the fixed devices are known by their public key. `show` returns `5` when
no list applies. `sites` returns `5` when there is no site. A path with a node two times,
or a hop that is not whole bytes of hex, is a usage error (`2`).
**`--json`** gives `show` as one object, `{"source": …, "name": …, "paths": [{"rank": …,
"path": …, "hops": […]}]}`. `source` is `site`, `device`, or `null`. `sites` is an array of
`{"site", "active", "paths"}`. Each change prints the object that it wrote, for example
`{"active": "Foulab"}`.
#### `meshterm tx-optimize`
Sweep the transmit power of a remote node against a target. Then select the lowest level