[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

Ryan, The problem is not that a recent change in resolvconf caused a regression. The problem with resolvconf is that the upgrade to network-manager exposed an existing bug in resolvconf. This happens because the new version of network-manager now tells resolvconf that it must only use a

[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

After two and a half weeks, can we please get a build of resolvconf with http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b applied pushed out? We don't even need the full new release of resolvconf, we just need the documented bug

[Desktop-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

So, this managed to break at least my VPN setup quite well. See #1672491 with the details, but the short version is that 'specify egress interface for each dnsmasq upstream server' breaks things in two cases. The first could be argued to be a bug on the VPN client side, though a behavior change

[Desktop-packages] [Bug 1672491] Re: New NetworkManager breaks VPN DNS.

Alright, this is due to a change to 1.2.4: commit 2f12f485607590d6415cf5fb81ad4db5b04615cd Author: Beniamino Galvani Date: Wed May 11 18:43:41 2016 +0200 dns: specify egress interface for each dnsmasq upstream server Currently we don't specify to dnsmasq

[Desktop-packages] [Bug 1672491] [NEW] New NetworkManager breaks VPN DNS.

Public bug reported: Alright, this is going to be a frustrating bug for everyone involved I expect, but here goes. On Ubuntu 16.04, using a non-released VPN client (making this _much_ harder for anyone to reproduce), upgrading the network-manager packages from 1.2.2-0ubuntu0.16.04.3 to