Bug #1638842 has been marked as a duplicate of this one, and also has been marked Won't Fix (before this bug was reported). So if we want the current behavior to be changed, we need to discuss.
Reason of the current behavior is given in Comment 7 of Bug #1638842: “On desktop images we want NM to manage everything, thus the installer creates /etc/NetworkManager/conf.d/10-globally-managed-devices.conf. But on a server, container, or similar environment we do NOT want NM to suddenly take over existing connections from netplan, networkd, or ifupdown -- there it should be restricted to wifi and 3G.” I agree with the idea and I can imagine that even if I cannot think of a case where NM is installed in a container / on a server without wanting it to manage connections, the current behavior works around a real problem that as been encountered and that chroot installation of Ubuntu Desktops might have been forgotten in the process. Now, installing Ubuntu using chroot is convenient and the easiest method is some cases, and as we can see in the comments here, people really do it so this should work as expected. In this setting, the current behavior is confusing. By default, nothing shows that NM is configured not to manage wired and Bluetooth connection. I lost almost a day because of this. It should at least be explicit in the configuration and in the logs. And NM changing its behavior because an empty configuration file exists at /etc/NetworkManager/conf.d/10-globally-managed- devices.conf seems weird to me. I agree that solving the initial problem is probably important, but I think that breaking things so badly for people installing Ubuntu using chroot is wrong and that the installation of Ubuntu should be a process that remains simple and intuitive. Making the Ubuntu installer create /etc/NetworkManager/conf.d/10-globally-managed-devices.conf and make NM work as expected when this file exists looks like a hack to me, and a fragile behavior. A better solution might be to make network-manager manage connections as expected when *-desktop packages are installed. But it is not sufficient as some people don't install these packages in their desktop setup to avoid installing things they don't use. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1658921 Title: NetworkManager does not manage wired connection Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager does not manage my wired eth0 connection, no matter how I set /etc/network/interfaces or /etc/NetworkManager/NetworkManager.conf Using ubuntu 16.04, /etc/network/interfaces only managed lo, and [ifupdown] section of NetworkManager.conf had set managed=false. With these same settings, after upgrading to ubuntu 16.10, eth0 appears as unmanaged in nm-applet. If I modify /etc/network/interfaces and add auto eth0 iface eth0 inet dhcp And set managed=true in NetworkManager.conf [ifupdown] section, eth0 is still unmanaged despite it does get an IP from DHCP server. This is happening in my five computers (two laptops and three desktops). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
