Clearly a bug in either how n-m-pptp spawns the vpn process, or how it
goes out to update DNS. Regardless, then this may need to be reassigned
if pptp doesn't provide a way to avoid updating DNS directly.
** Package changed: network-manager (Ubuntu) => network-manager-pptp
(Ubuntu)
** Changed in: network-manager-pptp (Ubuntu)
Status: Confirmed => Triaged
--
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/980579
Title:
It's impossible to ignore VPN provided DNS servers
Status in “network-manager-pptp” package in Ubuntu:
Triaged
Bug description:
I have a desktop Precise installation with a normal dnsmasq installed,
so I disabled the nm-spawned dnsmasq instance from
NetworkManager.conf.
I create a VPN connection in Network Manager without specifying any DNS
servers. When I connect to it, I get:
$ cat /var/run/dnsmasq/resolv.conf
nameserver 150.140.1.4
nameserver 150.140.1.25
nameserver 127.0.0.1
nameserver 194.63.238.4
nameserver 8.8.8.8
I want to ignore the first two entries which are provided by my VPN.
So I go to the VPN connection editor and I declare DNS=127.0.0.1. But
again I get the same /var/run/dnsmasq/resolv.conf, so my DNS server
entry there is completely ignored by network-manager and/or
resolvconf.
How can I tell Network Manager and/or resolvconf to ignore the DNS
servers provided by my VPN connection?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/980579/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
