plans: the OSPF Pri column is a number nothing can set, and the election never reads it #1964

Merged
jaylouisw merged 1 commit from plan/1118-0911 into main 2026-11-18 09:17:01 +00:00
Owner

Forward plan only, no code. One page at docs/plans/ospf-elections.md.

show ip ospf neighbor prints a Pri column that is 1 in every lab, because ip ospf priority is refused with the _ipOspf usage line (engine/cli.js:2704). The role beside it - FULL/DR / FULL/BDR - is decided by router ID alone (engine/simulator.js:1506), and the neighbour record hardcodes priority: 1 (:1545) while the console already reads that field as a number (engine/cli.js:4649, three columns wide - fits 0-255 unchanged).

Measured today: r1 1.1.1.1 reads 2.2.2.2 1 FULL/DR, r2 reads 1.1.1.1 1 FULL/BDR; ip ospf priority 200 on r1 changes nothing.

Four S steps: (1) make the setting exist in _ipOspf and publish it per interface; (2) make the election read it - priority first, router ID second, priority 0 never eligible, DROTHER distinguished from -; (3) add Pri to show ip ospf interface so the value can be read back where it was typed; (4) reconcile docs/CLI.md, docs/SIMULATION.md:385 and research/show-ospf-neighbor-state.md.

No step needs Jay's approval and no open issue is closed - the queue is four hardware requests (#130, #803, #808, #810).

Forward plan only, no code. One page at `docs/plans/ospf-elections.md`. `show ip ospf neighbor` prints a `Pri` column that is `1` in every lab, because `ip ospf priority` is refused with the `_ipOspf` usage line (`engine/cli.js:2704`). The role beside it - `FULL/DR` / `FULL/BDR` - is decided by router ID alone (`engine/simulator.js:1506`), and the neighbour record hardcodes `priority: 1` (`:1545`) while the console already reads that field as a number (`engine/cli.js:4649`, three columns wide - fits 0-255 unchanged). Measured today: r1 1.1.1.1 reads `2.2.2.2 1 FULL/DR`, r2 reads `1.1.1.1 1 FULL/BDR`; `ip ospf priority 200` on r1 changes nothing. Four S steps: (1) make the setting exist in `_ipOspf` and publish it per interface; (2) make the election read it - priority first, router ID second, priority 0 never eligible, `DROTHER` distinguished from `-`; (3) add `Pri` to `show ip ospf interface` so the value can be read back where it was typed; (4) reconcile `docs/CLI.md`, `docs/SIMULATION.md:385` and `research/show-ospf-neighbor-state.md`. No step needs Jay's approval and no open issue is closed - the queue is four hardware requests (#130, #803, #808, #810).
plans: the OSPF Pri column is a number nothing can set, and the election never reads it
All checks were successful
CI / Classify the change (pull_request) Successful in 4s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 9s
7d71945d1e
Sign in to join this conversation.
No reviewers
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!1964
No description provided.