On Sat, Jun 14, 2014 at 4:30 PM, Vincent Bernat <ber...@debian.org> wrote: [...] > So, NetworkManager checks if somebody is listening to the right DBus > address. With Debian and systemd, since dnsmasq is DBus enabled, it will > be started at this point. Otherwise, the patch also tries to run dnsmasq > itself. > > Then, there is another patch to use a "private" DBus name to avoid using > dnsmasq from the system I suppose. The relevant entry is here: >
Exactly. The issue is that it's not just incompatible with systemd, but more or less with just about any other dnsmasq instance that could be started either with just installing the dnsmasq package (regardless of it actually being properly configured and in use), in some ways incompatible with the libvirtd / qemu instances of dnsmasq... In general, it's just not necessarily meant for running multiple instances of dnsmasq that speak to each other. > network-manager (0.9.6.0-0ubuntu4) quantal; urgency=low > > * debian/patches/dns-dnsmasq-interface-and-dbus-path.patch: set the address > dnsmasq (and bind) plugins should listen on for DNS resolution to > 127.0.1.1, > as opposed to 127.0.0.1 to avoid conflicts with other instances that might > need to run on the system with that address. > Also set the dnsmasq DBus service name to our own custom name: > org.freedesktop.NetworkManager.dnsmasq, which will also avoid conflicting > with other dnsmasq instances which might have --enable-dbus enabled. > (LP: #1034946) > > -- Mathieu Trudel-Lapierre <mathieu...@ubuntu.com> Tue, 21 Aug 2012 > 11:45:46 -0400 > > Maybe Mathieu (in copy) can tell us if this has been forwarded upstream. > It hasn't yet -- upstreaming the dnsmasq patches I wrote is still a work in progress: I've started to prepare clean patches in a pristine git tree, but I can't put time in fast enough to keep up with master. You'll likely also want to have the patch to configure dnsmasq via DBus rather than restarting it all the time, and that's the one that needs to most work, I wanted to update it to use the SetServersEx instead of SetServers DBus method; which would avoid a minor regression. So, to quickly get the patches you could use the ones from trusty or utopic, they should apply cleanly to the version in unstable. Regards, Mathieu Trudel-Lapierre <mathieu...@ubuntu.com> Freenode: cyphermox, Jabber: mathieu...@gmail.com 4096R/EE018C93 1967 8F7D 03A1 8F38 732E FF82 C126 33E1 EE01 8C93 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org