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

better/proper duplicate route handling #116

Open
KanjiMonster opened this issue Jul 19, 2024 · 0 comments
Open

better/proper duplicate route handling #116

KanjiMonster opened this issue Jul 19, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@KanjiMonster
Copy link
Contributor

Currently, BISDN Linux does not handle duplicate routes very well. This is partially due to libnl not properly treating multiple routes with identical metric as a single route that changes its interface, and partially due to baseboxd not being prepared for multiple routes at all.

To better support this, we basically need to fix various places.

  1. baseboxd needs to learn to handle multiple routes with different priorities for the same destination, and keep the route with the highest priority (lowest metric) enabled. This may require keeping track of routes within baseboxd to properly update the ASIC configuration.
  2. libnl needs to learn treat multiple routes for the same destination as multiple routes, IF they are multiple routes in the kernel. This is non trivial, and may not even be achievable, depending on how detailed the information is that is shared by the kernel via netlink.
@KanjiMonster KanjiMonster added bug Something isn't working enhancement New feature or request labels Jul 19, 2024
@KanjiMonster KanjiMonster removed the enhancement New feature or request label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant