thank you for your bug report, could you give some details on your
configuration? do you have systemd-resolved installed? could be the same
as bug #1647066
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of D
Can you please attach your /etc/NetworkManager/NetworkManager.conf ? NM
is not supposed to create /etc/resolv.conf any more, so I suppose
something else is going on. Can you please reproduce the failed state
and then do
cat /etc/resolv.conf
and copy&paste the output, and run
journalctl -u Ne
Martin, here is the contents of /etc/NetworkManager/NetworkManager.conf
(with the version 1.4.2-2ubuntu3) installed:
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
And here is the output of
cat /etc/resolv.conf
# Generated by NetworkManager
search dhcp.inet.fi
nameserve
Sebastien,
could you please give me instructions on how to install systemd-resolved?
I do have a fully working Gnome-shell DE with systemd as pid1 and no upstart
packages installed.
The network is working fine if I use network-manager (1.4.2-2ubuntu3), but not
anymore if I upgrade to the version
Martin,
here is the failed state output of
cat /etc/resolv.conf
# Generated by NetworkManager
search dhcp.inet.fi
nameserver 127.0.1.1
So, nothing changed. And NM still generates the file /etc/resolv.conf.
I also run
journalctl -u NetworkManager.service -u systemd-resolved.service -b >
/t
> dns=dnsmasq
Ah -- please remove that from /etc/NetworkManager/NetworkManager.conf,
this is not currently working (this is known, this needs to be fixed in
a better way).
** Summary changed:
- Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)
+ dns=dnsmasq does not work any more
6 matches
Mail list logo
