[Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked

2020-01-11 Thread Launchpad Bug Tracker
[Expired for network-manager-openvpn (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager-openvpn (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https:

[Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked

2019-11-12 Thread Dariusz Gadomski
Can you connect to that VPN with the same settings, but from a virtual machine with a freshly installed system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851793 Title: NetworkManager OpenVPN No

[Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked

2019-11-12 Thread Uros Platise
How to test on LTS/production machine? (it's not really experimental machine) ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851793 Title: NetworkManager OpenVPN No longer sets up DNS if "Use this

[Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked

2019-11-12 Thread Dariusz Gadomski
The behavior described in this bug seems to be consistent with what is the default in Eoan (19.10). Uros, are you able to check if 19.10 network-manager is also affected with this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https

[Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked

2019-11-08 Thread Dariusz Gadomski
I examined the differences between bionic and upstream NetworkManager source around systemd-resolved interactions. I did not see any significant differences to blame for this. I have just tested it on a build from nm-1-10 branch of upstream NetworkManager and the behavior seems to be identical: th

[Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked

2019-11-08 Thread Uros Platise
Great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851793 Title: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked To manage not

[Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked

2019-11-08 Thread Dariusz Gadomski
I've checked that and what I see is: the DNS setting is visible in nmcli output, but it's not propagated to systemd-resolved (no DNS entry for the VPN connection in systemd-resolved --status). Looking into that. -- You received this bug notification because you are a member of Ubuntu Bugs, whi

[Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked

2019-11-08 Thread Uros Platise
Thanks for hint, the network related packages that were upgraded are actually these (not the openvpn): 2019-11-04 21:43:52 upgrade gir1.2-networkmanager-1.0:amd64 1.10.6-2ubuntu1.1 1.10.6-2ubuntu1.2 2019-11-04 21:43:52 upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.6-2ubuntu1.2 2019-11-04

[Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked

2019-11-08 Thread Sebastien Bacher
Thank you for your bug report. Do you remember what package got updated when the issue started? (you can also check in /var/log/dpkg.log) When you say 'DNS is not configured', could you give details on what you is wrong/note working exactly? Is name resolution failing? Or is it using another DNS s