网络

Fedora 36 no longer includes NetworkManager support for legacy network configuration (ifcfg) files by default in new installations.

Long ago, networking in Fedora was configured using network service, which was a set of shell scripts that sourced snippets of configuration from /etc/sysconfig/network-scripts/ifcfg-* ("ifcfg files"). The ifcfg files compatible with the legacy network service were kept when NetworkManager was introduced.

As the NetworkManager feature set was expanding beyond what the legacy network service could support, the ifcfg files written by NetworkManager could no longer be guaranteed to be compatible. NetworkManager eventually gained support for connection types completely unknown to the legacy network service and ended up using a more streamlined configuration file format for those, known as a "keyfile".

NetworkManager对各种配置文件的使用实际上是可以配置和通过插件扩展的。在Fedora 33之前，NetworkManager默认配置为启用ifcfg文件和密钥文件，在可能的情况下，前者具有优先权。优先级在Fedora 33中发生了变化，改为优先使用密钥文件。当创建网络连接配置文件时，优先级会有影响。一旦连接配置文件存在，NetworkManager就无法将其转换为不同的配置后端，这影响了在旧系统上创建的旧配置文件。

For the time being, the ifcfg plugin is still available for installation, albeit in a subpackage that is not automatically included in new installations. The appropriate RPM tags will ensure the subpackage with the ifcfg plugin will be installed on upgrades. A migration tool will be provided for users who’d like to remove the legacy package from their systems after upgrade.

System integrators and administrators might use tools that drop in ifcfg files during automated installations (e.g. via kickstart or a configration management tool). They will need to update their tools - either convert the ifcfg files to keyfiles, or include the ifcfg subpackage.