Am 17.07.2017 um 13:28 schrieb Wouter Verhelst: > On Mon, Jul 17, 2017 at 01:15:42PM +0200, Michael Biebl wrote: >>> I suppose that "ifup -a" returns before everything's set up properly >>> then; that would explain it. >> >> I'm reassigning this to ifupdown then. Assuming you use "auto" >> interfaces this is supposed to work. > > Apparently I wasn't (sorry, missed that bit in your previous email). > After fixing that, it works. > > Thanks for the help, closing the bug now (because there isn't one, after > all). > > Might be good to have ifupdown deal with interfaces in a way so that > even with allow-hotplug (which the installer uses by default) at least > some network is up and functional when "network-online.target" is > reached; but other than that, we should be fine.
Supporting allow-hotplug interfaces for network-online.target is something we discussed quite a while ago (unfortunately I can't find the archive anymore). I don't think we ever filed a bug report for this though, so we could just reopen this one? A long time ago I created a PoC for ifupdown-wait-online [1]. It was rather simple though. I simply blocked until at least one interface was configured. One would probably want something more sophisticated. Michael [1] https://people.debian.org/~biebl/ifupdown-wait-online.tar.gz -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
