After a new install of Kubuntu 16.10, I'm unable to convince Network Manager to manage my wired network interfaces. I've already confirmed that I can use the wired interfaces by configuing them manually in /etc/network/interfaces and using ifup/ifdown. In preparation for Network Manager, I have removed any mention of the wired interfaces from /etc/network/interfaces:
# cat /etc/network/interfaces
auto lo
iface lo inet loopback
After messing around with it (e.g. setting managed=true), I've restored NetworkManager.conf to its original state:
# cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq
[ifupdown]
managed=false
After each change, I always restart Network Manager using systemctl restart network-manager, but there is never any change. Nothing I do will convince Network Manager to touch those two wired interfaces. For example, using nmcli to explicitly instruct NM to manage one of them has no effect:
# nmcli d
DEVICE TYPE STATE CONNECTION
wlx0002723c09df wifi connected JRT-AIR
enp0s31f6 ethernet unmanaged --
enp11s0 ethernet unmanaged --
lo loopback unmanaged --
# nmcli d set enp11s0 managed yes
# nmcli d
DEVICE TYPE STATE CONNECTION
wlx0002723c09df wifi connected JRT-AIR
enp0s31f6 ethernet unmanaged --
enp11s0 ethernet unmanaged --
lo loopback unmanaged --
# nmcli d show enp11s0 | grep STATE
GENERAL.STATE: 10 (unmanaged)
All the documentation and help information I've found says that I need to edit either /etc/network/interfaces or /etc/NetworkManager/NetworkManager.conf (e.g. setting managed=true in NM.conf), but none of these edits has had any effect. Both ethernet interfaces are always listed as "unmanaged" in nmcli, and NM refuses to create any connections using them. Can anyone suggest what I might be missing here?
As an additional note, when booting a live USB on this machine, Network Manager happily manages these wired interfaces as expected. Comparing the config files between the live USB system and the installed one, I see no differences relating to network configuration.
Edit: On further investigation, this only happens when the root filesystem is ZFS. I installed to an EXT4 partition, and everything worked correctly. Then, I copied the files from that working installation into a ZFS filesystem and made that copy bootable, and the ZFS copy showed the error, despite having all identical files to the working EXT4 copy.
