Skip to content

bgpd: fix to show exist/non-exist-map in 'show run' properly #18853

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

Conversation

ton31337
Copy link
Member

Currently, peergroup_filter_check() does not check whether exist-map or non-exist-map is configured along with advertise-map. This check is missing only when the peer is part of peergroup and having the exist/non-exist-map. So the 'show run' does not show the configured exist/non-exist-map as expected.

This new check is needed because, unlike other filter type the adv-map can have exist/non-exist-map additionally and we don't store this in the filter_override but store only the adv-map. So, a specific check is required to account the exist/non-exist-map while printing the adv-map config. Fixing the same by adding a check.

@ton31337
Copy link
Member Author

@Mergifyio rebase

Copy link

mergify bot commented May 22, 2025

rebase

❌ Pull request can't be updated with latest base branch changes

Mergify needs the author permission to update the base branch of the pull request.
@ton31337 needs to authorize modification on its head branch.

Currently, peergroup_filter_check() does not check whether exist-map or
non-exist-map is configured along with advertise-map. This check is
missing only when the peer is part of peergroup and having the
exist/non-exist-map. So the 'show run' does not show the
configured exist/non-exist-map as expected.

This new check is needed because, unlike other filter type the adv-map can have
exist/non-exist-map additionally and we don't store this in the
filter_override but store only the adv-map. So, a specific check is
required to account the exist/non-exist-map while printing the adv-map config.
Fixing the same by adding a check.

Signed-off-by: Krishnasamy <[email protected]>
@ton31337 ton31337 force-pushed the fix/backport_aa012d8d43c2cf703dcfd57927a47da059bf16b3 branch from cebf412 to 214db8e Compare May 22, 2025 05:56
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
Copy link
Member

riw777 commented May 27, 2025

Looks like linter is blocking ... :-(

@ton31337
Copy link
Member Author

we can ignore the linter

@Jafaral Jafaral added this to the 10.4 milestone May 29, 2025
@ton31337 ton31337 removed this from the 10.4 milestone Jun 2, 2025
@riw777 riw777 merged commit e7ac7da into FRRouting:stable/10.3 Jun 3, 2025
12 of 13 checks passed
@ton31337 ton31337 deleted the fix/backport_aa012d8d43c2cf703dcfd57927a47da059bf16b3 branch June 3, 2025 12:19
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.

4 participants