[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: wm DAD duplicate address
On Fri, Feb 24, 2017 at 09:40:27AM +0000, Roy Marples wrote:
> On 21/02/2017 12:32, Patrick Welche wrote:
> > On Tue, Feb 21, 2017 at 12:25:00PM +0000, Patrick Welche wrote:
> >> wm2: DAD defended address 0.0.0.0 from 00:15:17:1a:48:1d
> >> wm2: DAD defence failed for 0.0.0.0 from 00:15:17:1a:48:1d
> >> wm2: DAD duplicate address 0.0.0.0 from 00:15:17:1a:48:1d
> > ...
> > Reverse Request who-is 00:15:17:22:6c:e0 tell 00:15:17:22:6c:e0, length 46
> > Request who-has 169.254.95.254 tell 169.254.95.254, length 28
> > etc., and no 0.0.0.0 to be seen anywhere by tcpdump
> So the DAD reporting reports on an address assigned to the interface,
> not the actual address from the ARP message.
> There is code to pick the first address from the interface if none match
> the ARP message, the below patch skips DAD if that happens.
> Does it help?
It does indeed!
Main Index |
Thread Index |