Am Samstag, 6. Juni 2015, 23:12:14 schrieb Guus Sliepen: > The post-up lines are executed for static ipv6 interfaces, but not if > something went wrong while configuring the interface. One issue is that > ifupdown assumes the kernel is performing Duplicate Address Detection in > a timely fashion, and only considers the interface properly up if the > kernel completes DAD. It could be that at boot time this doesn't work. > Try adding "dad-attempts 0" to the iface eth0 stanza, and see if that > makes a difference.
Sorry about the late reply, I had been away on a trip abroad and did not have access to that machine. I've tried your hint setting dad-attempts 0 in /etc/network/interfaces. That did not change anything, however. One thing i forgot to add, though, is, that this machine has its disk encrypted with luks and I am using mandos-client to unlock the disks during early userspace (i.e. mandos-client is run from initrd). mandos-client brings up the network interface in question to receive the password for the luks volume. Having looked at the logs, it seems that the interface is not taken down before early userspace is finished. The system still manages to set up the static addresses right, but the additinal "up" stanza does not get executed. I've also tried the other way of configuring additional addresses as described in the debian wiki, by adding eth a third time, configuring the additional ULA address in the third interface config section. The result was the same, though, the additional address did not get set up at boot time. Regards, Dominik
signature.asc
Description: This is a digitally signed message part.
