Re: [PATCH net v2] ipv6: set all.accept_dad to 0 by default

2017-11-15 Thread Nicolas Dichtel
Le 15/11/2017 à 11:25, David Miller a écrit : > From: Nicolas Dichtel > Date: Wed, 15 Nov 2017 11:17:28 +0100 > >> I saw that you pushed this patch in net-next instead of net. Is it >> intentional? >> I was expecting to see it in net, to fix the 4.14. > > All changes are going into net-next as

Re: [PATCH net v2] ipv6: set all.accept_dad to 0 by default

2017-11-15 Thread David Miller
From: Nicolas Dichtel Date: Wed, 15 Nov 2017 11:17:28 +0100 > I saw that you pushed this patch in net-next instead of net. Is it > intentional? > I was expecting to see it in net, to fix the 4.14. All changes are going into net-next as I prepare to send a pull request to Linus for the merge win

Re: [PATCH net v2] ipv6: set all.accept_dad to 0 by default

2017-11-15 Thread Nicolas Dichtel
Le 14/11/2017 à 14:21, Nicolas Dichtel a écrit : > With commits 35e015e1f577 and a2d3f3e33853, the global 'accept_dad' flag > is also taken into account (default value is 1). If either global or > per-interface flag is non-zero, DAD will be enabled on a given interface. > > This is not backward co

Re: [PATCH net v2] ipv6: set all.accept_dad to 0 by default

2017-11-14 Thread Girish Moodalbail
On 11/14/17 11:10 AM, Stefano Brivio wrote: On Tue, 14 Nov 2017 10:30:33 -0800 Girish Moodalbail wrote: On 11/14/17 5:21 AM, Nicolas Dichtel wrote: With commits 35e015e1f577 and a2d3f3e33853, the global 'accept_dad' flag is also taken into account (default value is 1). If either global or per

Re: [PATCH net v2] ipv6: set all.accept_dad to 0 by default

2017-11-14 Thread Stefano Brivio
On Tue, 14 Nov 2017 10:30:33 -0800 Girish Moodalbail wrote: > On 11/14/17 5:21 AM, Nicolas Dichtel wrote: > > With commits 35e015e1f577 and a2d3f3e33853, the global 'accept_dad' flag > > is also taken into account (default value is 1). If either global or > > per-interface flag is non-zero, DAD w

Re: [PATCH net v2] ipv6: set all.accept_dad to 0 by default

2017-11-14 Thread Girish Moodalbail
On 11/14/17 5:21 AM, Nicolas Dichtel wrote: With commits 35e015e1f577 and a2d3f3e33853, the global 'accept_dad' flag is also taken into account (default value is 1). If either global or per-interface flag is non-zero, DAD will be enabled on a given interface. This is not backward compatible: bef

Re: [PATCH net v2] ipv6: set all.accept_dad to 0 by default

2017-11-14 Thread Stefano Brivio
On Tue, 14 Nov 2017 14:21:32 +0100 Nicolas Dichtel wrote: > With commits 35e015e1f577 and a2d3f3e33853, the global 'accept_dad' flag > is also taken into account (default value is 1). If either global or > per-interface flag is non-zero, DAD will be enabled on a given interface. > > This is not

[PATCH net v2] ipv6: set all.accept_dad to 0 by default

2017-11-14 Thread Nicolas Dichtel
With commits 35e015e1f577 and a2d3f3e33853, the global 'accept_dad' flag is also taken into account (default value is 1). If either global or per-interface flag is non-zero, DAD will be enabled on a given interface. This is not backward compatible: before those patches, the user could disable DAD