On 08/12/11 12:57, Thomas Schweikle wrote: > 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. >
Dnsmasq will cope fine with dynamically-created interfaces, as long as "bind-interfaces" is NOT set in the configuration. Simon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
