Public bug reported:
A DHCPv6 server may respond with multiple addresses, and is not an
unusual case as you may wish to provide both a ULA and a global prefix
to a common suffix. Recent versions of OpenWRT behave in this manner for
DHCPv6.
Network Manager is handling this *almost* correctly.
1.10.6-2ubuntu1.2 has cause a regression in functionality.
Anyone using a "split" VPN, where there is no default route, AND wish to
have DNS services supplied by the server to be honoured, via use of the
ipv4.dns-priority parameter, will have this broken. This is a bit of a
sore point considering
Public bug reported:
NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a
VPN connection which sets it's dns-priority to a negative value, which
should cause the DNS server supplied by the DNS connection to be placed
first, instead now refuses to place the DNS server into the
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
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
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
6 matches
Mail list logo
