Thomas, i'd argue that any service not using ifup/ifdown, and not manually calling the /etc/network/if-up.d scripts after bringing interfaces up is the bug then. NetworkManager has a plugin specifically to do this, and vmware/virtualbox should too if they're going to manage interfaces. Of course, it also means that they need to start before runlevel 2, so they'll need upstart jobs.
Still, I don't think this is dnsmasq's problem. As Simon says, just make sure dnsmasq is not binding to specific interfaces. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/876458 Title: dnsmasq started before all interfaces are up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/876458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
