I agree that the /usr/lib/NetworkManager/conf.d/10-globally-managed- devices.conf should be deleted from Ubuntu's network-manager package.
Especially, as it is being overwritten in any normal Ubuntu Desktop installation, using the following netplan YAML: ``` network: version: 2 renderer: NetworkManager ``` If we use a global "renderer: NetworkManager" stanza (as is the default on Ubuntu Desktop, where NM is part of the default installation) netplan will create an empty file in /run/NetworkManager/conf.d/10-globally- managed-devices.conf, to override that file anyway. But we should be aware that it could introduce a change of default behavior on Ubuntu server where network-manager is being installed additionally. But netplan generates /run/NetworkManager/conf.d/netplan.conf to specifically ignore devices that are not supposed to be handled by NM, so we should be fine there, too. I've recently updated the allow- and deny-list logic in netplan to be more generic and instruct NetworkManager to ignore/manage devices based on specific udev rules. With this PR I'm also changing the 10-globally- managed-devices.conf logic to override Ubuntu's default anytime a NetworkManager interface is being defined in netplan YAML (not just if it's defined as the global renderer). https://github.com/canonical/netplan/pull/276 ** Changed in: netplan.io (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) ** Changed in: netplan.io (Ubuntu) Status: Triaged => In Progress -- 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/1951653 Title: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' Status in netplan.io package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Confirmed Bug description: I have tried to tell netplan to let my ethernet device be managed by NetworkManager, so that I can then configure a pppoe connection on top of this device. This fails with: # nmcli c up netplan-wan Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged). # I don't know why it mentions 'lo' in that message, but the wan interface is unmanaged (as are all devices on the system, but this one is supposed to be managed): # nmcli d status | grep wan wan ethernet unmanaged -- # After much searching, I've figured out that this comes from /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf: keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Even though I've told netplan to use the NM renderer for this device, the configuration emitted by netplan is insufficient to override this. Using the workaround from https://askubuntu.com/questions/71159/network-manager-says-device-not- managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed- devices.conf) doesn't work, but if I set NetworkManager as the toplevel renderer in /etc/netplan, /run/NetworkManager/conf.d/10-globally-managed-devices.conf is emitted, which evidently DOES work. But I only have one device that I want rendered by NM, so I shouldn't have to declare NM at the top level of the yaml with a lot of duplication in order to get this result. I would argue that the 10-globally-managed-devices.conf should not be there at all. But if it is going to be, then netplan needs to consistently override it whenever there is any use of the NetworkManager backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+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