Current ifupdown does wait for DAD to complete so chances are that this
specific issue has now been resolved for IPv6 at least.
Also note that the event is called net-device-up, not net-device-
connected. All the event means is that the interface has been brought up
and the configuration has been applied. It doesn't do any connectivity
check with the outside world nor should it.
There is another ifupdown bug report covering suggestions on how to
address this bug #848823.
I'm going to close this bug as fix released for the DAD case, for the NFS case,
this is a duplicate of 848823 (even though this bug technically came first, the
latter has more information).
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702802
Title:
event "net-device-up" is triggered too early
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/702802/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
