On 14/10/2019 11:35, rudolf wrote:
Looking at the patch you've attached I guess the culprit is probably
that due to the direct connect, the wm0 address is tentative at the
moment of the arping (the link goes up and down several times before
the arping) and thus not being defended?
Well, the culprit is the link going up and down.
dhcpcd ARPing is basically a DaD probe.
The NetBSD host is also performing DaD each time the link comes up and
it correctly spots dhcpcd ARPing for it and marks it's address as
duplicated.