Re: dnsmasq DBUS integration

Mathieu Trudel-Lapierre wrote:
On Wed, Apr 18, 2012 at 10:04 AM, Howard Chu<hyc symas com>  wrote:
Just refreshing a patch I posted here before...

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, 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, and
system-wide dnsmasq configuration as shipped by the 'dnsmasq' package,
should probably bind to each interface's IP address, rather than
binding to 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 ;)

Hm. The default dnsmasq.conf on my Ubuntu laptop had everything commented out, thus provided no services at all. That seems like the most sensible shipping default - if you've gone to the trouble of installing it, you can certainly take the trouble to configure it.

  -- Howard Chu
  CTO, Symas Corp. 
  Director, Highland Sun
  Chief Architect, OpenLDAP

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]