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 of this nature in an LTS release is decidedly unwelcome. The second exposes a bug in dnsmasq which needs to be fixed for any case where an interface is removed and then readded, this includes suspend/resume and some VPN cases. Regards, Zephaniah E. Loss-Cutler-Hull. -- 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/1645698 Title: [SRU] Upgrade network-manager to latest point release Status in OEM Priority Project: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Status in network-manager source package in Yakkety: Fix Released Bug description: [Impact] This SRU would try to have the latest well-tested upstream point release (1.2.6) of 1.2.x land in Xenial, which is the successor of the current 1.2.2 version, fixing quite some bugs that's suitable to land in the stable branch. https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2 [Test Case] After installing the updated version, users should be able to avoid some mem leaks in some cases and have generally improved DNS related experiences. Also, as this is a general point release update, cases described in https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used for smoke testing. [Regression Potential] This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite complete. [Other Info] The first attempt at SRUing this to xenial was for 1.2.4 but it failed verification. This second attempt matches yakkety with 1.2.6. Parallel building was enabled in xenial to keep the diff between xenial and yakkety minimal since they are basically in sync now. Parallel building was enabled in the yakkety package in May 2016 so it's been working fine for a while. needed by: lp #1647283 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
