Interface not up if TimeoutDAD is "too short" about netctl

[joukewitteveen]

By 'Looks like' you mean it says so in the journal? If DAD takes more than 3 seconds (the default) you either have a very complex or slow network, or a misconfiguration in it.

[triplem]

Complex? Definitly not, slow? Well, I do not have a Gb, but usually fast enough. Anyways, even if it is slow, I would not expect that the device is not coming up at all, even though there is already an IPv4 adress assigned.

[joukewitteveen]

You need to provide more info. How do you know DAD is at fault?

[triplem]

hmp,

systemd[1]: Unit netctl@ethernet\x2dstatic.service entered failed state.
systemd[1]: Failed to start A basic static ethernet connection.
systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exited, status=1/FAILURE
network[343]: Failed to bring the network up for profile 'ethernet-static'
network[343]: Duplicate Address Detection is taking too long on interface 'enp0s25'

Basically I guess my problem is not really the TimeoutDAD, but that the device is not brought up correctly, even though the IPv4 adress is already assigned correctly. There should be a way to bring the device up and answer even though it is not configured for another protocol (IPv6 in this case).

The whole device is still configured "down" and I need to delete the IPv4 manually before trying to bring the device up again. Very awkward.

[joukewitteveen]

It sounds like somethin in your network is not configured properly. You can, however, just add SkipDAD=yes to your profile and see if that works for you :-).