This bug basically requires adapting the dbus changes (and possibly
another patch) to dnsmasq. Enabling dbus itself isn't huge, but if the
binding code needs to be backported too, it's likely to be non-trivial.
As for NM, it's a matter of cherry-picking the patches, which should
apply pretty cleanly on top of the package for precise.
It's still on my list; so let's aim at getting this checked off before
the end of the week.
** Also affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dnsmasq (Ubuntu)
Status: New => Fix Released
** Changed in: dnsmasq (Ubuntu Quantal)
Status: New => Fix Released
** Changed in: dnsmasq (Ubuntu Precise)
Status: New => In Progress
** Changed in: dnsmasq (Ubuntu Precise)
Importance: Undecided => High
** Changed in: dnsmasq (Ubuntu Precise)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1004775
Title:
NetworkManager restarts dnsmasq and adds host route on every IPv6
route lookup
Status in “dnsmasq” package in Ubuntu:
Fix Released
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “dnsmasq” source package in Precise:
In Progress
Status in “network-manager” source package in Precise:
In Progress
Status in “dnsmasq” source package in Quantal:
Fix Released
Status in “network-manager” source package in Quantal:
Fix Released
Bug description:
NetworkManager stops and starts dnsmasq very frequently (every few
minutes). During the brief window that dnsmasq is restarting,
hostname resolution doesn't work. dnsmasq is getting restarted
frequently enough that I see brief hostname resolution errors in
Chrome several times a day during normal web browsing.
This is on Precise with network-manager 0.9.4.0-0ubuntu4 and dnsmasq-
base 2.59-4.
The frequent restarts seem to be triggered by IPv6 route
advertisements on my network. (See log snippet below.) When
NetworkManager gets a route advertisement, it reconfigures everything.
In the case of dnsmasq, this means stopping dnsmasq, writing a new
config file, and starting dnsmasq. NetworkManager should restart
dnsmasq only if it its configuration changes.
I'm attaching a snippet from /var/log/daemon.log on my system that
demonstrates a restart. This is with debug logging configured in
/etc/NetworkManager/NetworkManager.conf.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1004775/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
