The inspector's Routes table reads the same annotated rows as show ip route (#1301) #1302
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1302
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/routes-agreement"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The inspector's Routes table reads the same annotated rows as
show ip route.Fixes #1301.
The defect
The console was taught (#1234, #1271) to print four things about a route that the panel did not: the code the
table actually installs (
S*for the gateway of last resort), the administrative distance that decides whichroute wins,
is directly connected, Gi0/0instead ofvia -, and — the one that mattered — the sentence sayinga row cannot carry a packet.
The panel printed
code | dest/len | gwstraight out of runtime state. On a router whose only uplink was down:…and the panel drew three healthy-looking rows — 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.
After
The verdict is computed once, in
Device.routesTable(topo), which annotates every row withdisplayCode,distance,noteandunusable;show ip routeand the panel read the same fields rather than keeping twoopinions.
Device.routeDistance()moves the distance table into the engine, where the console's "Gateway of lastresort" sort and the panel's column both read it.
S*), the same distance ([254/0]),is directly connected, Gi0/0, and thesame sentence, with the row dimmed and the reason in red (
.route-dead/.route-note);no next hop: ARP for the destination on that segment— andthe row stays usable, because it does carry a packet where the far side proxies ARP;
routesTable()called without a topology returnschecked: false, claims neither health nor fault, and thepanel prints
(not checked)— #1299's lesson: a surface must not report "fine" because nobody looked;server/index.jspasses the topology, so the verdict is computed against live cable state.Evidence
test/routes-agreement.test.js— 19 checks over nine situations: no routes, connected only, static default, aconfigured gateway competing with a static default, interface-only static, OSPF/BGP-learned, link down, peer shut,
local port shut.
code|prefix|distance|note— two rows can legitimately share0.0.0.0/0— so adropped, duplicated or re-worded row fails;
S*vsSwith distances 254 and 1; an unannotated payload saying(not checked); and the distance table asserted through its exported function.With
engine/device.jsreverted, 11 of the 19 fail — the reported case among them, reporting all three routesas usable with no note.
docs/CLI.md: the inspector's table described as the same table.docs/LINK-STATE.md: the panel added to thecallers of the route-liveness rule.
Suite: 166 suites, 6,796 assertions, 0 failed.
show ip route(#1301)