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: Allow using maximum-prefix for EVPN #15735

Merged

Conversation

ton31337
Copy link
Member

@ton31337 ton31337 commented Apr 13, 2024

Closes #15720

Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
@frrbot frrbot bot added bgp tests Topotests, make check, etc labels Apr 13, 2024
@ton31337
Copy link
Member Author

@Mergifyio backport stable/10.0 stable/9.1 stable/9.0

Copy link

mergify bot commented Apr 15, 2024

backport stable/10.0 stable/9.1 stable/9.0

✅ Backports have been created

@donaldsharp
Copy link
Member

I hate to be this way but how is this a bug fix? Adding new functionality, while probably going to work, worries me a bit

@ton31337
Copy link
Member Author

Neither a bug, nor a feature, IMO, but we can skip it from being backported, not a big deal :)

@donaldsharp donaldsharp merged commit 54cfb13 into FRRouting:master Apr 15, 2024
13 checks passed
@ton31337 ton31337 deleted the feature/maximum-prefix_evpn branch April 15, 2024 18:52
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.

Missing maximum-prefix feature for address-family l2vpn evpn
2 participants