-
Notifications
You must be signed in to change notification settings - Fork 92
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
Allow setting preferred source address in routes per interface via config file #18
Conversation
5a82e68
to
4dfe00e
Compare
Agreed in principle. Please provide a clean patch series, preferably just a single patch, and preferably against rfc6126bis. |
the patch towards rfc6126bis was raised via mailing list. |
with the current branching model I am getting confused with the PRs. |
4dfe00e
to
775bc48
Compare
The first and last patches are no longer relevant. The second patch (the manpage typo) I've applied. As to the main patch, it has a bug: use_prefsrc should be set to CONFIG_YES, otherwise the MERGE macro won't work. Rather than using an extra boolean in the config, I recommend simply setting the prefix to all-zeroes if it is not set, and checking whether it's all zeroes before passing it to the kernel. This avoids having the same information in two places, which risks having inconsistent data. |
775bc48
to
5a4f40b
Compare
This preferred source address will be added as prefsrc stanza to each exported route via this interface. For this the interface configuration is extended by the parameter pref-src requiring an ipv6 address as argument.
5a4f40b
to
a14239c
Compare
reworked to include review comments. |
On Sun, Mar 31, 2019 at 02:57:15PM -0700, Juliusz Chroboczek wrote:
Sorry for the delay, but I was waiting for @killianlufau to submit #31.
I haven't looked at the code in #31 yet, but I rather like the idea of
attaching source addresses to install filters rather than to the
interface configuration. @christf, I'd like to hear your opinion.
It seems like using filters can be more flexible. So yes, this approach
is interesting. Why didn't we think of that before?
…--
() ascii ribbon campaign - against html e-mail
/\ against proprietary attachments
|
Killian,
In the second patch:
Other than that, it looks good to me. |
this replaces #15 and is directed towards the unicast branch.
With this patch, we can set preferred source address stanzas in routes for each interface using a configuration like this:
interface babel-vpn-1374 type tunnel link-quality true update-interval 300 pref-src aaaa:bbbb:cccc:dddd:eeee::fffff