I can possibly try 19.10 later, however at the moment I only have my LTS
laptop to test with.
Just to ensure we've covered any variations, here is a redacted version
of my connection file, in case I have missed anything.
[connection]
id=Vxxx
uuid=----
type=vpn
Thanks Joe.
There has to be another factor coming into play, as my setup contains
"use only for resources on its network".
$ nmcli connection show my-vpn | grep -e ipv4.never-default -e
ipv4.dns-priority
ipv4.dns-priority: -30
ipv4.never-default: yes
Ar
Did you ensure that the connection was set for "use only for resources
on the connection"? (I believe this may be ipv4.never-default=yes
setting in nmcli... and only bring it up because you do not mention it.)
I also think the negative DNS priority might be historical, no longer
needed. (I just no
** Tags added: regression-update
--
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/1851407
Title:
NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
Status in network-m
Joe, I still can't reproduce your issue.
Can you please verify against what I'm trying:
1. Setup a VPN that provides DNS via DHCP
2. Connect to that VPN and verify DNS by:
$ systemd-resolve --status
(...)
Link 4 (tun0)
(...)
DNS Servers: X.X.X.X
(...)
3. Disconnect VPN and edit connection:
$ nmcli
I had the exact same issue, upon upgrading I got the same issues as
jhohertz, I followed the above instructions and the issue was fixed.
--
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.l
1) Add an openvpn connection, which emits DHCP DNS servers, and is flagged "use
only for resources on this connection"
2) Add a negative dns_priority to the connection via CLI or editing the
connection
Prior to the change, this worked fine, you could connect, and the
indicated DNS server would b
Joe, thanks for reporting the bug.
I am unable to reproduce the issue in my test env.
Can you please provide a step-by-step procedure to reproduce it on a
clean 18.04 installation?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://
9 matches
Mail list logo
