plans: the OSPF Pri column is a number nothing can set, and the election never reads it #1964
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!1964
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plan/1118-0911"
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?
Forward plan only, no code. One page at
docs/plans/ospf-elections.md.show ip ospf neighborprints aPricolumn that is1in every lab, becauseip ospf priorityis refused with the_ipOspfusage 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 hardcodespriority: 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 reads1.1.1.1 1 FULL/BDR;ip ospf priority 200on r1 changes nothing.Four S steps: (1) make the setting exist in
_ipOspfand publish it per interface; (2) make the election read it - priority first, router ID second, priority 0 never eligible,DROTHERdistinguished from-; (3) addPritoshow ip ospf interfaceso the value can be read back where it was typed; (4) reconciledocs/CLI.md,docs/SIMULATION.md:385andresearch/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).