Yes, that's right, but there are interfaces not started from /etc/network/interfaces or Network Manager: * VMware Workstation / Player installs interfaces starting VMware daemons * VirtualBox installs interfaces * KVM may install an additional bridge * some VPN software installs tun/tap interfaces or virtual interfaces up on an existing interface
As far as I could find: * VMware is started after dnsmasq, leading to a situation dhcp via dnsmasq works, but DNS doesn't * VirtualBox creates interfaces and bridges on the fly --- sometimes dhcp works, sometimes it doesn't; DNS did not work always * KVM interfaces are started concurently with dnsmasq, because kvm is started after "network" is up. Sometimes you'll get full functionality, sometimes you do not. If KVM starts its own dnsmasq both daemons challenge with each other about whom answers dhcp --- sometimes the VM is assigned the one address, sometimes the other. DNS may work or may not. * VPN: sometimes dnsmasq binds dhcp to VPN, sometimes it doesn't. Either way: it leads into trouble. To make dnsmasq work with dhcp, dns (and, if configured tftp) you'll have to restart the daemon each time a new interface it shall bind to is started. -- 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
