Task #5360
closed
Investigate usage of prefix inheritance flags in NLSR
90%
Description
Currently, NLSR appears to use the Capture instead of the default Child Inherit flags for inserted routes. It is not immediately clear what the design intention was for this; we should ensure that this is a sensible default.
Updated by Alexander Lane 3 months ago
This change was implemented due to #1841; the goal was to prevent issues with router prefixes inheriting nexthops for very broad routes on local nodes which could interfere with shortest path behavior. However, I'm unclear if this is a common occurrence in actual deployment.
Updated by Alexander Lane 3 months ago
- Status changed from New to In Progress
- Assignee set to Alexander Lane
- % Done changed from 0 to 40
The main blocker with implementing this change is due to the fact that there's currently not much in the way of robust existing mechanisms to distinguish between explicitly advertised prefixes and ones from the NLSR application. The code is designed around treating these as homogeneous, which means that we ultimately need to do some refactoring to properly track this.
Updated by Alexander Lane about 2 months ago
- Status changed from In Progress to Code review
Updated by Alexander Lane 10 days ago
- Status changed from Code review to Closed
- % Done changed from 40 to 90
This should be reopened if any locations this did not apply to are found.