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

zebra: Do not install local route if it matches a connected route #14970

Conversation

ton31337
Copy link
Member

@ton31337 ton31337 commented Dec 8, 2023

No description provided.

C * 10.0.0.2/32 is directly connected, lo, 00:00:03
L>* 10.0.0.2/32 is directly connected, lo, 00:00:10

No need to install it, since we know that prefix anyway.

Signed-off-by: Donatas Abraitis <[email protected]>
@donaldsharp
Copy link
Member

I disagree -> This was discussed and it was decided to have this in. Effectively it will match the actual routing table of linux kernel.

@ton31337
Copy link
Member Author

ton31337 commented Dec 8, 2023

Got it, I missed that discussion then. From the other side, as an example Cisco does not install L routes if they match.

@donaldsharp
Copy link
Member

Let's re have the discussion in Tuesday's meeting

@donaldsharp
Copy link
Member

So I'm going to close this one. During today's tech meeting this was discussed:

a) Having both allows operators to apply policy to either connected or local and allowing them to stay consistent. Having a local that disapears when the connected prefix matches the local prefix would make that inconsistent.
b) The desire is to have the Local route the selected. I'll make this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants