desktop-packages team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/192643

Title:
  dnsmasq with enable-dbus doesn't work properly with NetworkManager

Status in NetworkManager:
  Fix Released
Status in “dnsmasq” package in Ubuntu:
  Invalid
Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: dnsmasq

  Ubuntu 7.10, Intel Pentium M,
  dnsmasq 2.39-1
  network-manager 0.6.5-0ubuntu16.7.10.0
  dbus 1.1.1-3ubuntu4

  I  followed the instructions in /usr/share/doc/dnsmasq/DBus-interface.gz and put the line
   enable-dbus
  into /etc/dnsmasq.conf

  This made dnsmasq show up in the output from the dbus-monitor utility,
  but it didn't give the expected behaviour of /etc/resolv.conf, in
  cooperation with NetworkManager, which is to have /etc/resolv.conf
  contain just 127.0.0.1, regard less of the DHCP lease, and when be
  unaffected by VPNC connections going up and down.

  The behaviour is as before dnsmasq was installed, which is to show the
  DNS information from DHCP when getting a DHCP lease, and the DNS
  information from the VPNC remote end, when a VPNC connection is up,

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/192643/+subscriptions