First of all,
If NM 1.4.2-2ubuntu4 needs the package resolvconf in order to function
properly, it should depend on it.
Secondly,
NM 1.4.2-2ubuntu3 works perfectly, like all earlier versions, without the
package resolvconf.
Thirdly,
after installing resolvconf with NM 1.4.2-2ubuntu4, NM still does not work
properly. It is not OK.
And here are some test results.
With NM 1.4.2-2ubuntu3: "systemd-resolve --status"
Global
DNS Servers: 127.0.1.1
DNS Domain: dhcp.inet.fi
DNSSEC NTA: 10.in-addr.arpa
home
internal
intranet
lan
local
private
test
Link 2 (eth0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: allow-downgrade
DNSSEC supported: yes
With NM 1.4.2-2ubuntu4: "systemd-resolve --status"
Global
DNSSEC NTA: 10.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test
Link 2 (eth0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: allow-downgrade
DNSSEC supported: yes
DNS Servers: 193.210.18.18
193.210.19.19
DNS Domain: dhcp.inet.fi
--
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/1647133
Title:
dns=dnsmasq does not work any more
Status in network-manager package in Ubuntu:
Triaged
Bug description:
Network-manager will make my network connection immediately lost after
updating to the newest version 1.4.2-2ubuntu4.
However, downgrading to the previous version 1.4.2-2ubuntu3 the network
connection is back again and fine. If, with this version, I remove the file
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as
network-manager creates a new resolv.conf file.
The newest version 1.4.2-2ubuntu4 also creates the very same kind of
file, but no network.
I have the latest (Gnome-shell DE) updates installed and of course all
packages that network-manager depends on. But not the ones it only recommends
or suggests.
Should I have resolvconf installed? I think not, as isc-dhcp-client only
suggests it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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
