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

bgpd: Respect allowas-in value from the source VRF's peer #17800

Conversation

ton31337
Copy link
Member

@ton31337 ton31337 commented Jan 8, 2025

Closes #17797

If the peer which has allowas-in enabled and then reimports the routes to another
local VRF, respect that value.

This was working with < 10.2 releases.

Fixes: d4426b6 ("bgpd: copy source vrf ASN to leaked route and block loops")

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

ton31337 commented Jan 8, 2025

@Mergifyio backport stable/10.2

Copy link

mergify bot commented Jan 8, 2025

backport stable/10.2

✅ Backports have been created

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 4212bac into FRRouting:master Jan 14, 2025
18 checks passed
@ton31337 ton31337 deleted the fix/import_between_vrf_respect_allowas_in branch January 14, 2025 15:24
riw777 added a commit that referenced this pull request Jan 14, 2025
bgpd: Respect allowas-in value from the source VRF's peer (backport #17800)
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.

VPN import excludes routes with system AS
2 participants