OSPF is configurable and computed, and the console cannot report any of it #1371

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

OSPF is configurable — ospf router-id, ospf area, ip ospf cost|area|passive per interface — and
computeOspf() turns those numbers into adjacencies, an SPF tree and installed routes. None of it can be read
back.
The only console answer that mentions OSPF is O in show ip route.

So: set ip ospf cost 25, then try to find out whether the engine used it, which port the adjacency formed on, or
who the neighbour is. There is no command that answers any of those. Same shape as show power inline before
#1295 and the STP election before #1365 — the mechanism exists, the surface does not.

What must be true instead

  1. show ip ospf — the process: router id, areas, interfaces (with the passive count), neighbours, routes
    installed, and whether the engine has settled.
  2. show ip ospf neighbour [<port>] — who, at what address, on which port.
  3. show ip ospf interface [<port>] — area, cost, adjacency, passive, and where the cost came from, because
    cost 10 typed and cost 10 derived from a 100 Mbps wire are the same route and a different story.
  4. A named port that is not contributing is named with the reason, not shown as an empty table.
  5. Every row must come from what the engine computed, so the console and show ip route cannot disagree.
OSPF is configurable — `ospf router-id`, `ospf area`, `ip ospf cost|area|passive` per interface — and `computeOspf()` turns those numbers into adjacencies, an SPF tree and installed routes. **None of it can be read back.** The only console answer that mentions OSPF is `O` in `show ip route`. So: set `ip ospf cost 25`, then try to find out whether the engine used it, which port the adjacency formed on, or who the neighbour is. There is no command that answers any of those. Same shape as `show power inline` before #1295 and the STP election before #1365 — the mechanism exists, the surface does not. ## What must be true instead 1. `show ip ospf` — the process: router id, areas, interfaces (with the passive count), neighbours, routes installed, and whether the engine has settled. 2. `show ip ospf neighbour [<port>]` — who, at what address, on which port. 3. `show ip ospf interface [<port>]` — area, cost, adjacency, passive, **and where the cost came from**, because `cost 10` typed and `cost 10` derived from a 100 Mbps wire are the same route and a different story. 4. A named port that is not contributing is named *with the reason*, not shown as an empty table. 5. Every row must come from what the engine computed, so the console and `show ip route` cannot disagree.
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#1371
No description provided.