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: Fix ip protocol route-map issue. #17474

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sougata-github-nvidia
Copy link

@sougata-github-nvidia sougata-github-nvidia commented Nov 21, 2024

"ip/ipv6 protocol any route-map " cli is setting wrong route type (ZEBRA_ROUTE_MAX), It should set route type ZEBRA_ROUTE_ALL.

After executing the above CLI, routes are not scheduled for processing with routemap.
Reason: CLI set route-type=ZEBRA_ROUTE_MAX but Zebra checks ZEBRA_ROUTE_ALL in rib_update_route_node().
FRR restart solves the issue, and filter works as expected, because restart route install flow is different and its checks are proper.
After this code change all the api's are in synced, and right FLAG is used.
CLI, rib_update_route_node() , zebra_route_map_check ()

Ticket: #4101560

"ip/ipv6 protocol any route-map <route map>" cli is setting
wrong route type (ZEBRA_ROUTE_MAX), It should set route type
ZEBRA_ROUTE_ALL.

Ticket: #4101560

Signed-off-by: Sougata Barik <sougatab@nvidia.com>
@ton31337
Copy link
Member

Do we need a topotest to check such a foobar?

@donaldsharp
Copy link
Member

I'm not sure matters a whole bunch for this case

@sougata-github-nvidia
Copy link
Author

Do we need a topotest to check such a foobar?

Yes, I am adding topotest also

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.

3 participants