As far as I know it is not the default on servers, at least not on servers I use (debian based). Also quote from NetworkManagers website:
Server-like behavior
By default NetworkManager automatically creates a new in-memory connection for every Ethernet device that doesn’t have another candidate connection on disk. These new connections have name “Wired connection 1”, “Wired connection 2” and so on; they have DHCPv4 and IPv6 autoconfiguration enabled.
This behavior is usually not desirable on servers, where all interfaces should be configured explicitly. To disable the creation of such automatic connections, add
no-auto-default=*
to the[main]
configuration section.Also, NetworkManager requires carrier on an interface before a connection can be activated on it. If there are services that need to bind to the interface address at boot, they might fail if the interface has no carrier. The solution is to disable carrier detection with configuration option
ignore-carrier=*
in the[main]
section.Note that on Fedora and RHEL there is a
NetworkManager-config-server
package that install a configuration snippet with the two options described above.
It doesn’t mean you can’t use it, only that I wouldn’t as I know how to configure netplan with networkd properly On a desktop machine, it helps to detect wifi connections and connect to it when you click on a button on GUI.
update:
In my original post I accidentally wrote “netplan with NetworkManager”. I meant of course “netplan with networkd”.