Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: wm DAD duplicate address
On Wed, Feb 22, 2017 at 03:44:31PM +0000, Patrick Welche wrote:
> On Wed, Feb 22, 2017 at 02:26:49PM +0000, Patrick Welche wrote:
> > > Netboot kernel with r1.241 also fails. (server is 1.242)
> >
> > FWIW Netboot NetBSD 7 kernel works (server is 1.242)
>
> Went back to the flex update of Mon Jan 2 16:26:30 2017 +0000 (b9dc6b54b)
> which also failed.
Maybe the result of the bisection isn't too surprising - get rid of DAD
completely and it can't complain.
# git bisect good
d7e49963faf52a2e69a033be25fa87ba5bbb976d is the first bad commit
commit d7e49963faf52a2e69a033be25fa87ba5bbb976d
Author: roy <roy>
Date: Tue Oct 11 13:59:30 2016 +0000
Implement RFC 5227 2.4 Ongoing Conflict Detection and Address Defence.
If ip_dad_count is 0, then the conflict is just logged and the address
is not marked as duplicated.
:040000 040000 8345b05ee8686ed797507b5ce0daa5d90e192905 9292dc9a35b2859474b8c08918deab2147678847 M sys
Home |
Main Index |
Thread Index |
Old Index