This works without problems, and without using `ipv4.dns-priority`, on
Ubuntu 20.04.
--
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/1768203
Title:
Connecting to a VPN clears D
The patch from #19 (which is now in Ubuntu) is not enough - there are
still problems with network-manager-sstp, which calls pptp with "nm-
sstp-service-*".
If there's no better workaround, can the userpeerdns and
000resolveconf scripts at least bail on all "nm-*-service-*"?
--
You received t
This helps, but there's still a problem - resolved tries to resolve the
VPN-local addresses with both VPN and global DNS. Some of those
addresses are available on both sites, and I prefer the internal one
when the VPN is active.
--
You received this bug notification because you are a member of De
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ apt-cache policy network-manager
network-manager:
Installed: 1.10.6-2ubuntu1
Candidate: 1.10.6-2ubuntu1
Version table:
*** 1.10.6-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic
~jonathanharker could you check if `nmcli connection show 'CONNECTION
NAME' | grep DNS` shows the nameservers you expect? You can list
connection names with `nmcli connection`. This way we'll make sure if
the problem happens between NM and the VPN or NM and resolved (for me it
was the latter, and t
There is a fix posted on the upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=779087 - I've attached a
ported patch.
** Bug watch added: GNOME Bug Tracker #779087
https://bugzilla.gnome.org/show_bug.cgi?id=779087
** Patch added: "Port of patch from Patch from
https://bugzilla.gnome.org
6 matches
Mail list logo
