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: Validate only affected RPKI prefixes instead of a full RIB #17586

Conversation

ton31337
Copy link
Member

@ton31337 ton31337 commented Dec 4, 2024

Closes #17533

bgpd/bgp_rpki.c Outdated Show resolved Hide resolved
Before this fix, if rpki_sync_socket_rtr socket returns EAGAIN, then ALL routes
in the RIB are revalidated which takes lots of CPU and some unnecessary traffic,
e.g. if using BMP servers. With a full feed it would waste 50-80Mbps.

Instead we should try to drain an existing pipe (another end), and revalidate
only affected prefixes.

Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
@ton31337 ton31337 force-pushed the fix/revalidate_only_affected_routes branch from c8f7984 to b0800bf Compare December 6, 2024 21:32
@ton31337 ton31337 requested a review from riw777 December 17, 2024 16:43
@Jafaral Jafaral merged commit 956143a into FRRouting:master Dec 19, 2024
11 checks passed
@ton31337 ton31337 deleted the fix/revalidate_only_affected_routes branch December 20, 2024 05:02
@pguibert6WIND
Copy link
Member

https://github.com/Mergifyio backport stable/10.2 stable/10.1 stable/10.0

Copy link

mergify bot commented Dec 20, 2024

backport stable/10.2 stable/10.1 stable/10.0

✅ Backports have been created

@nikhilgv
Copy link

Hey @ton31337, will this fix be backported to versions 8.5.5 and 9.1.1?

@ton31337
Copy link
Member Author

Nope, not planned.

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.

Using RTR with BMP triggers a RIB-DUMP upon RTR Refresh
5 participants