[Touch-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'

This bug was fixed in the package netplan.io - 0.105-0ubuntu1 --- netplan.io (0.105-0ubuntu1) kinetic; urgency=medium * New upstream release: 0.105 - Add support for VXLAN tunnels (#288), LP: #1764716 - Add support for VRF devices (#285), LP: #1773522 - Add support for

[Touch-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'

** Changed in: netplan.io (Ubuntu) Status: In Progress => Fix Committed -- 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

[Touch-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'

network-manager's default /usr/lib/NetworkManager/conf.d/10-globally- managed-devices.conf file also produces other issues, see LP: #1615044 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu.

[Touch-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'

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:

[Touch-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu.

[Touch-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'

We want to implement an explicit allow- and denylist for NM to handle certain device (or not). NM’s own matching engine is not powerful enough to handle all of netplan’s matching needs, but it can also be implemented with udev matching rules, using ENV{NM_UNMANAGED}="1" We also want to discuss

[Touch-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'

Yes, indeed. NetworkManager tries to control all interfaces that are available by default and netplan implemented some quirks in the past to avoid this. But we should review those quirks and rather implement a per-interface/netdef deny- or accept-list. ** Tags added: fr-1888 ** Changed in: