cliroute

Overview ¶

Package cliroute cmd/skywire-cli/commands/route/calc.go c4-vis-cli

Package cliroute cmd/skywire-cli/commands/route/minhops.go c4-vis-cli

Package cliroute cmd/skywire-cli/commands/route/policy.go c4-vis-cli operator tooling for the skylark routing-policy DSL (RFC #2882). `skywire cli route policy test` previews what a script would decide for a synthetic dial; `bench` runs the script 1M times and reports per-call latency.

Package cliroute cmd/skywire-cli/commands/route/route.go c4-vis-cli

Package cliroute cmd/skywire-cli/commands/route/rsn_remote.go c4-vis-cli

Package cliroute cmd/skywire-cli/commands/route/rsn_stats.go c4-vis-cli

Package cliroute cmd/skywire-cli/commands/route/settings.go

Package cliroute cmd/skywire-cli/commands/route/settings_dial.go

`skywire cli route settings dial` — the DIAL-TIME half of the router's runtime knobs: the route-ranking priors, how many candidates a dial asks the finder for, the warm-plan cache shape, the dead-route young-death window, the dial-time tunnel width and the operator's prefer-these-peers list.

It is a subcommand of `route settings` rather than more flags on it because the two sets answer different questions and a caller parsing --json should get one document per question, not a merged one.

Package cliroute cmd/skywire-cli/commands/route/table_stats.go c4-vis-cli

Package cliroute cmd/skywire-cli/commands/route/trace.go c4-vis-cli `skywire cli route trace <pk>` — per-hop latency printout for the route to a destination visor. Equivalent to Unix traceroute, scoped to the skywire route-finder graph.

Why a dedicated command vs. `cli visor ping`:

• `visor ping` is end-to-end. It can't tell an operator WHERE in a 4-hop route the latency is coming from.
• `visor ping tree` is a TUI for an interactive sweep of public visors. Not scripting-friendly, not per-hop.
• `route find` shows the forward path's PK list but no measurements.

trace stitches them: fetch the route from the route-finder (or local DHT), then ping each intermediate visor in that route over dmsg (so the intermediate's own visor RPC isn't required), and report a hop-by-hop table.