On Mon, 13 Nov 2017 14:21:52 +0000 Erik Kline <e...@google.com> wrote:
> Should we consider rolling back the patch that caused this? > "accept_dad = 1" is the proper IETF-expected default behaviour. > > Alternatively, if we really want to make all, default, and ifname > useful perhaps we need to investigate a tristate option (for currently > boolean values, at least). -1 could mean no preference, for example. I haven't checked how ugly it would be, yet. But another way to restore the previous behaviour, while keeping the new functionality, would be to keep the global default as 1 and instead set the per-interface accept_dad default value to 0. What do you think? -- Stefano
