The inspector's Routes table shows a healthy route table while every route is unusable #1301
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1301
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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 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 distancethat decides which route wins,
is directly connected, Gi0/0instead ofvia -, and — the one that matters —the sentence saying a row cannot carry a packet.
The panel printed
code | dest/len | gwstraight out of runtime state. So on a router whose only uplink wasdown:
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 ARPreply 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" ratherthan "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
Device.routesTable(topo), which now annotates every row withdisplayCode,distance,noteandunusable— soshow ip routeand the panel read the same fieldsinstead of keeping two opinions;
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;
no next hop: ARP for the destination on that segment), nota fault — that route still carries a packet where the far side proxies ARP;
routesTable()called without a topology returnschecked: falseand claims neither health nor fault,and the panel says
(not checked)— the same principle as #1299: a surface must not report "fine" becausenobody looked.
show ip route(#1301) #1302