-
Notifications
You must be signed in to change notification settings - Fork 24
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
Implement IPv4 Route Policy to prefer babel routes #965
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Installed it on w38b-core an also my test router noki-core, so far without any issues. Seems to work exactly the same as before.
@Noki can you confirm the route policy and routing tables are filled accordingly to the scheme?
|
Yes, from my understanding that is the case. Looks good to me. Looking forward for a first babel-default route for IPv4 ;-) |
I'd propose to depoloy that change to a few high traffic nodes like
in order to check for sideeffects we might have overseen yet at our stub sites. |
Deployed to:
|
492b13f
to
49a102d
Compare
If you look at the babel neighbours, we see that there is no ipv4 neighbours but ipv4 routes. Is that intended? |
@PolynomialDivision you might have spotted the routes from the f2a nodes etc. setup by patrick. They were in there before... |
49a102d
to
a5ccbba
Compare
a5ccbba
to
c0dec88
Compare
@spolack what about announcing the default ipv4 via babeld? |
Implement following changes which are preparing the migration towards using babel also for IPv4 - #964
Add new Routing Tables to avoid babel routes compete with olsrd, which could lead to routing loops. We have to ensure that the routes get installed only in the appropriate tables, never in the default/main.
Setup routing policy in following order:
Ensure that olsrd and babeld install IPv4 routes only in the appropriate tables. Unfortunately babeld is not able to install routes in different policies, therefore routes are installed in "intermediate" table
babel-src
, from which they are leaked conditionally intobabel-ff
andbabel-default
using bird2. In addition it has to be ensured that the babel-src table is also used to lookup IPv6 targets.With these changes in place we have ensured that babeld and olsrd routes never compete and babel is prefered whenever a route is there, but if not it is routed using olsr.