networkmanager-config-server wrote:This adds a NetworkManager configuration file to make it behave more like the old "network" service. In particular, it stops NetworkManager from automatically running DHCP on unconfigured ethernet devices, and allows connections with static IP addresses to be brought up even on ethernet devices with no carrier.
The network connection that was ok after installation is a "configured device" (configuration created by installer).
If there is a VM and one attaches (hotplugs) additional interfaces to it, then those are unconfigured devices.
NetworkManager will autoconfigure and start connections on them, if networkmanager-config-server is not installed.
You don't want that, if the defaults are not ok for you. On server they usually are not.
Installation of additional packages, like networkmanager-config-server, should have no effect on connections.
Unless ... what packages were installed before you add the ones listed in "Server with GUI" dnf group?
What if network and firewall are configured and managed by different services than what are implicitly pulled in by "dnf install
lots_of_packages"?
The new services would be on defaults and might be mutually exclusive with original.
Example: Another OpenStack provider has images with no firewall (because OpenStack does the filtering). No firewalld. I did, by mistake, pull firewalld in as dependency. While ssh was still allowed, other traffic was cleanly cut.
You can also do:
That lists the dnf groups that are "part of" Server with GUI environment. You might not need all of them, nor all packages from each group.
A dnf group is just a list, not hard requirement. One can:
Code: Select all
dnf group install foo --exclude=bar
Even if 'bar' is a mandatory package for group 'foo', the other packages (that do not require 'bar') still install without error.