The inspector's Routes table shows a healthy route table while every route is unusable #1301

Closed
opened 2026-11-10 00:04:38 +00:00 by jaylouisw · 0 comments
Owner

The console was taught (#1234, #1271) to print four things about a route that the inspector's Routes table
does not: the code the table actually installs (S* for the gateway of last resort), the administrative distance
that decides which route wins, is directly connected, Gi0/0 instead of via -, and — the one that matters —
the sentence saying a row cannot carry a packet.

The panel printed code | dest/len | gw straight out of runtime state. So on a router whose only uplink was
down:

R1#show ip route
C   10.1.2.0       /24  is directly connected, Gi0/0  (down: link down)
S  0.0.0.0        /0  [1/0] via 10.1.2.1  (down: link down)
S  192.168.5.0    /24  [1/0] via 10.1.2.1  (down: link down)

and the panel drew three perfectly healthy rows — C 10.1.2.0/24 -, S 0.0.0.0/0 10.1.2.1, S 192.168.5.0/24 10.1.2.1 — on the one screen an operator has open while the link is broken. The drop that follows says "no ARP
reply from X", which sends them looking for a host instead of at the wire.

Two smaller versions of the same problem: a connected row read via - (which looks like "no next hop" rather
than "directly connected"), and a configured gateway was indistinguishable from a static default even though the
engine treats them as different sources (distance 254 vs 1).

What it must do instead

  • the verdict is computed once, in Device.routesTable(topo), which now annotates every row with
    displayCode, distance, note and unusable — so show ip route and the panel read the same fields
    instead of keeping two opinions;
  • Device.routeDistance() moves the distance table into the engine, where the console's "Gateway of last
    resort" sort and the panel's column both read it;
  • the panel shows the same code (S*), the same distance ([254/0]), is directly connected, Gi0/0, and the
    same sentence, with the row dimmed and the reason in red;
  • the interface-only-static caveat stays a caveat (no next hop: ARP for the destination on that segment), not
    a fault — that route still carries a packet where the far side proxies ARP;
  • routesTable() called without a topology returns checked: false and claims neither health nor fault,
    and the panel says (not checked) — the same principle as #1299: a surface must not report "fine" because
    nobody looked.
The console was taught (#1234, #1271) to print four things about a route that the inspector's Routes table does not: the code the table actually installs (`S*` for the gateway of last resort), the administrative distance that decides which route wins, `is directly connected, Gi0/0` instead of `via -`, and — the one that matters — the sentence saying a row cannot carry a packet. The panel printed `code | dest/len | gw` straight out of runtime state. So on a router whose only uplink was down: ``` R1#show ip route C 10.1.2.0 /24 is directly connected, Gi0/0 (down: link down) S 0.0.0.0 /0 [1/0] via 10.1.2.1 (down: link down) S 192.168.5.0 /24 [1/0] via 10.1.2.1 (down: link down) ``` and the panel drew three perfectly healthy rows — `C 10.1.2.0/24 -`, `S 0.0.0.0/0 10.1.2.1`, `S 192.168.5.0/24 10.1.2.1` — on the one screen an operator has open while the link is broken. The drop that follows says "no ARP reply from X", which sends them looking for a host instead of at the wire. Two smaller versions of the same problem: a connected row read `via -` (which looks like "no next hop" rather than "directly connected"), and a configured gateway was indistinguishable from a static default even though the engine treats them as different sources (distance 254 vs 1). ## What it must do instead * the verdict is computed **once**, in `Device.routesTable(topo)`, which now annotates every row with `displayCode`, `distance`, `note` and `unusable` — so `show ip route` and the panel read the same fields instead of keeping two opinions; * `Device.routeDistance()` moves the distance table into the engine, where the console's "Gateway of last resort" sort and the panel's column both read it; * the panel shows the same code (`S*`), the same distance (`[254/0]`), `is directly connected, Gi0/0`, and the same sentence, with the row dimmed and the reason in red; * the interface-only-static caveat stays a caveat (`no next hop: ARP for the destination on that segment`), not a fault — that route still carries a packet where the far side proxies ARP; * `routesTable()` called **without** a topology returns `checked: false` and claims neither health nor fault, and the panel says `(not checked)` — the same principle as #1299: a surface must not report "fine" because nobody looked.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge#1301
No description provided.