nm-initrd-generator generates a set of connections that are then configured by the NetworkManager
instance running in the initrd. There are some differences in behavior compared to the network-legacy
dracut module:
• When an interface is configured with a static address and a gateway, the network-legacy module waits
that the gateway responds to arping requests before proceeding, while NetworkManager doesn't.
• network-legacy configures interfaces one by one in the order in which they are announced by udev. If
multiple interfaces specify a hostname (from command line or from DHCP), the one from the last
interface activated wins. With NetworkManager, hostnames from command line have higher precedence
over ones from DHCP, and the last that appears in the command line wins.
• NetworkManager supports the ib.pkey=PARENT.PKEY argument to set up an Infiniband partition on IPoIB
parent device PARENT using the specified partition key PKEY. The partition key must be in hexadecimal
notation without leading "0x", for example "ib.pkey=ib0.8004".
• NetworkManager supports the rd.ethtool=INTERFACE:AUTONEG:SPEED kernel command line option to set up
ethtool NIC configuration parameters AUTONEG and SPEED. The INTERFACE being configured must be
specified, and the other parameters are optional and can be left blank. When SPEED is set, duplex
mode is automatically set to 'full'. INTERFACE accepts string values, AUTONEG accepts boolean values
(true and false / on or off / 0 or 1), and SPEED accepts positive integer values.
• NetworkManager supports the rd.net.dns-backend=VALUE kernel command line option to configure the DNS
processing mode. See the description of the "dns" key in the "main section" paragraph of
NetworkManager.conf(5). For example: rd.net.dns-backend=systemd-resolved, rd.net.dns-backend=dnsconfd
• NetworkManager supports the rd.net.dns=SERVER kernel command line option to configure a global (non
interface-specific) DNS server. The option can be specified multiple time to add more than one
server. Each server can be specified as a plain IP or as an URI according to the description in the
"global-dns-domains sections" paragraph of NetworkManager.conf(5). For example:
rd.net.dns=2001:db8::1, rd.net.dns=dns+tls://192.0.2.0,
rd.net.dns=dns+tls://[2001:db8::2]:5353#example.org. In addition, it supports configuring the
"resolve-mode" key in the global DNS configuration via the rd.net.dns-resolve-mode command line
option.
• NetworkManager supports the rd.net.dhcp.dscp={CS0|CS4|CS6} kernel command line option to set a
specific DSCP (TOS) value in the IP header of DHCP messages.