Re: dnsmasq DBUS integration

[Mathieu Trudel-Lapierre <mathieu tl gmail com>]

On Wed, Apr 18, 2012 at 10:04 AM, Howard Chu <hyc symas com> wrote:
> Just refreshing a patch I posted here before...
> http://mail.gnome.org/archives/networkmanager-list/2011-January/msg00029.html
> https://bugzilla.gnome.org/show_bug.cgi?id=551747
>
> I don't see any conflict with libvirt, since that dnsmasq instance is
> running with its own private dnsmasq.conf already.

It won't exactly cover the case of updating resolv.conf properly
(because "properly" depends on context), but we've noticed issues with
the default dnsmasq configuration when it's installed as a standalone
server. Basically, dnsmasq as shipped in Ubuntu as the 'dnsmasq'
package (as opposed to dnsmasq-base which is what NetworkManager
depends on, and ships just the binary and manpage), installs an init
script and a very barebones configuration file. That configuration
file defaults to binding to 0.0.0.0, which breaks launching NM's own
instance of dnsmasq.

That's partly why I suggested on IRC to start dnsmasq on a different
IP address, though that along won't fix the issues.

I think NM should, at least in Debian/Ubuntu, launch on 127.0.1.1, and
system-wide dnsmasq configuration as shipped by the 'dnsmasq' package,
should probably bind to each interface's IP address, rather than
binding to 0.0.0.0 without restrictions.

It's not quite just NM's responsibility there and it's pretty
Debian/Ubuntu specific, but I thought best to share my ideas ;)

Mathieu Trudel-Lapierre <mathieu tl gmail com>
Freenode: cyphermox, Jabber: mathieu tl gmail com
4096R/EE018C93 1967 8F7D 03A1 8F38 732E  FF82 C126 33E1 EE01 8C93