Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ospfd: Prune duplicate next-hop when installing into zebra route table. #17906

Merged

Conversation

aceelindem
Copy link
Collaborator

 ospfd: Prune duplicate next-hops when installing into zebra

Duplicate next-hops are maintained for OSPF inter-area and AS
external routes in the OSPF routing table as long as they
correspond to LSAs for different adverting routers. The
intra-area route computation will not result in duplicate
next-hops.

tests: OSPF topotest for next-hop pruning

OSPF topotest to test OSPF next-hop pruning on installation
into zebra routing table.

Signed-off-by: Acee Lindem <[email protected]>

@frrbot frrbot bot added ospf tests Topotests, make check, etc labels Jan 22, 2025
@aceelindem aceelindem force-pushed the aceelindem/ospf-prune-dup-next-hops branch from 4795c87 to 8be264c Compare January 23, 2025 00:21
@ton31337
Copy link
Member

Does this PR close #17869?

@aceelindem
Copy link
Collaborator Author

Does this PR close #17869?

Yes - we discussed it in the Tuesday huddle and both Don and Mark thought it would be good to not send the duplicates to zebra. One question is whether the change warrants a separate topotest? I found that there was already a multicast test with duplicates.

@donaldsharp
Copy link
Member

if there is already a test w/ duplicates then just add a extension to that test to see that the duplicates are not sent down?

OSPF topotest to test OSPF next-hop pruning on installation
into zebra routing table. Also fix multicast_pim_dr_nondr_test
topotest which had a duplicate OSPF route in the results.

Signed-off-by: Acee Lindem <[email protected]>

X
Duplicate next-hops are maintained for OSPF inter-area and AS
external routes in the OSPF routing table as long as they
correspond to LSAs for different adverting routers. The
intra-area route computation will not result in duplicate
next-hops.

Signed-off-by: Acee Lindem <[email protected]>
@aceelindem aceelindem force-pushed the aceelindem/ospf-prune-dup-next-hops branch from 8be264c to 1c55cf2 Compare January 23, 2025 15:14
@riw777 riw777 added the bugfix label Jan 28, 2025
Copy link
Member

@riw777 riw777 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@riw777 riw777 merged commit 3bdb561 into FRRouting:master Jan 28, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants