Well, scratch that hope and consider me mistaken about Goth Queen's workaround. It appears that manually setting a fixed DNS server DOES allow for successful reconnect when the network manager is restarted (whereas before it wouldn't reconnect period), but just like this bug https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241 name resolution (not using the dnscrypt-proxy service, just a fixed DNS address) fails after waking up from suspend for some frustrating, arcane reason. I have downgraded the following packages: (credit to Kostadin Stoilov) sudo apt install network-manager=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm-glib-vpn1=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm-glib4=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm0=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm-util2=1.2.2-0ubuntu0.16.04.4 sudo apt install resolvconf=1.78ubuntu2
and held them in place with 'sudo apt-mark hold' for the time being, as there appears to be a critical flaw in the updated versions of network- manager and possibly resolv-conf and dnsmasq. I suppose we just have to wait until something is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
