My systemd is newer (237-3ubuntu10.24), instead network manager is
locked at 1.10.6 (1.10.6-2ubuntu1.1). I've upgraded network-manager as
suggested to 1.10.14-0ubuntu2 and rebooted.
I've shut down both my Wifi and LAN since I'm at the office, and hooked
up my phone with USB tethering to use an external connection and use the
VPN to my office.
First test: it works. I get my DNS from the VPN:
Link 61 (tun2)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 172.27.0.42
172.27.0.33
DNS Domain: ~.
Following the test case in #1754671: when I enable the split connection, this
is the full result of systemd-resolve --status, where I do not see any DNS
coming from the VPN:
Global
DNS Domain: mycompany.com
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test
Link 48 (tun1)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 43 (tun0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 42 (enp0s20f0u2)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.42.129
DNS Domain: ~.
Link 11 (br-b2c3b7f9b208)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 10 (br-775248335fa8)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 9 (br-6671ba352ece)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 8 (br-642ed19f0ac7)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 7 (br-5699f03e12bc)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 6 (br-1f97d7363f0e)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 5 (docker0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 4 (br-dbf7ef8f9ab9)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 3 (wlp2s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 2 (enx106530b07160)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1829838
Title:
1.10.14-0ubuntu2 breaks DNS propagation from VPN
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I have an OpenVPN connection, and I use the update-systemd-resolved to
correctly fetch the DNS from the VPN. The issue arose updating my
Ubuntu 18.04: the script is no longer invoked, and even invoking it
manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
that case systemd-resolve --status shows the new DNS on the interface
correctly.
As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1211110/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
