Closing as Fix Released since the upstream bug was also closed. All
indicates that this works properly at this point.
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: network-manager
Status: New => Fix Released
** Changed in: network-manager
Importance: Unknown => Wishlist
--
dnsmasq with enable-dbus doesn't work properly with NetworkManager
https://bugs.launchpad.net/bugs/192643
You received this bug notification because you are a me
Hello,
Actually it appears that network-manager creates its own dnsmasq fomr the
dnsmasq-base package.
It ignore any and all settings in dnsmasq as the conf file is only set and
included in the dnsmasq package (not the base).
It is called and appear with ONLY command line settings.
It appears
Patch on upstream bugtracker received no attention.
Alexander: is it something we can/should carry on our side ?
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
dnsmasq with enable-dbus doesn't work properly with NetworkManager
https://bugs.launchpad.net/bugs/192643
Y
If you're referring to Gnome bug 551747, yes, I submitted that bug
report and patch, but it appears to have received no attention upstream
yet.
For the reasons I already listed in my previous comment, resolvconf is a
poor solution. I already tried using it here; it still rewrites the disk
too freq
there is an upstream patch pending for this. However, we support
resolvconf. isnt that enough to properly hook in dnsmasq for intrepid?
Switching dnsmasq to dbus that late in the cycle might not be the thing
we want.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
dns
** Changed in: network-manager
Importance: Undecided => Unknown
--
dnsmasq with enable-dbus doesn't work properly with NetworkManager
https://bugs.launchpad.net/bugs/192643
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Just a few comments on prioritizing this wishlist item - I think using
this feature should be the default on any desktop install; using dnsmasq
improves all name resolver lookup response times, and by eliminating
rewrites to /etc/resolv.conf it makes it a lot easier to run a secure
system with a re
** Bug watch added: Email to [EMAIL PROTECTED] #
mailto:[EMAIL PROTECTED]
** Also affects: network-manager via
mailto:[EMAIL PROTECTED]
Importance: Undecided
Status: New
--
dnsmasq with enable-dbus doesn't work properly with NetworkManager
https://bugs.launchpad.net/bugs/192643
Y
This missing feature in NetworkManager was really annoying me so I wrote a
patch for it, which you can find here
http://mail.gnome.org/archives/networkmanager-list/2008-September/msg00042.html
--
dnsmasq with enable-dbus doesn't work properly with NetworkManager
https://bugs.launchpad.net/bugs/1
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Wishlist
--
dnsmasq with enable-dbus doesn't work properly with NetworkManager
https://bugs.launchpad.net/bugs/192643
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
dnsmasq with enable-dbus doesn't work properly with NetworkManager
https://bugs.launchpad.net/bugs/192643
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
dnsmasq provides the DBUS service and methods correctly, it's just that
NetworkManager doesn't do what you think it should do with it (it
probably doesn't call the uk.org.thekelleys.dnsmasq SetServers method
when new DNS servers are received from a new DHCP lease).
In my understanding, this is not
13 matches
Mail list logo
