Module routes 

Routes remembered between invocations.

The MAC learns a route from inbound traffic and keeps it in the peer registry, which lives exactly as long as the Mac does — and this tool builds a new one for every command. Without somewhere to put them, two manage calls a second apart each flood the mesh to discover the same path.

So each session hands its learned routes to a file, and the next one puts them back before it says anything. A route is a hint, not a promise: a stale one costs a single failed exchange, after which the MAC’s own ack-timeout retry rediscovers the path and overwrites it. That is why the file can be lost, truncated, or edited by hand without breaking anything.

Structs

RouteCache

Every route this tool remembers.

RouteRecord

One remembered route and when it was learned.

Constants

HEADER 🔒

The file’s first line, so a future format can be told apart from this one without guessing.

ROUTE_TTL

How long a remembered route is worth trying.

Functions

describe

How a route reads in a listing: what it does, not how it is encoded.

parse_line 🔒

parse_pairs 🔒

render_pairs 🔒

render_route 🔒

A route as one field of kind and its parameters: