This bug was fixed in the package network-manager -
0.9.2.0+git201201101813.0b30200-0ubuntu1
---------------
network-manager (0.9.2.0+git201201101813.0b30200-0ubuntu1) precise; urgency=low
* New upstream snapshot.
* debian/libnm-util2.symbols: add new symbols:
- nm_setting_vpn_get_num_data_items@Base
- nm_setting_vpn_get_num_secrets@Base
* debian/patches/dnsmasq-vpn-dns-filtering.patch: filter nameservers before
adding to dnsmasq to avoid using DNS servers which are unavailable due to
a VPN taking the default route, or to be considered insecure when a VPN
is connected. (LP: #898224)
* debian/NetworkManager.conf: enable the use of DNSMasq as a resolver by
default, NetworkManager will configure it based on DHCP responses and
interface settings. See the 'foundations-p-dns-resolving' blueprint.
* debian/control: move dnsmasq-base from a Recommends to a Depends.
-- Mathieu Trudel-Lapierre <mathieu...@ubuntu.com> Thu, 12 Jan 2012 11:01:32
+0100
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/898224
Title:
Wrong dnsmasq configuration when VPN is set as default gateway
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/898224/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
