1NM-INITRD-GENERATOR(8)       System Administration      NM-INITRD-GENERATOR(8)
2
3
4

NAME

6       nm-initrd-generator - early boot NetworkManager configuration generator
7

SYNOPSIS

9       nm-initrd-generator [OPTIONS...] -- [CMDLINE...]
10

DESCRIPTION

12       nm-initrd-generator scans the command line for options relevant to
13       network configuration and creates configuration files for an early
14       instance of NetworkManager run from the initial ramdisk during early
15       boot.
16

OPTIONS

18       -c | --connections-dir path
19           Output connection directory.
20
21       -i | --initrd-data-dir path
22           Output directory for initrd data (e.g. hostname).
23
24       -d | --sysfs-dir path
25           The sysfs mount point.
26
27       -r | --run-config-dir path
28           Output directory for config files.
29
30       -s | --stdout
31           Dump connections to standard output. Useful for debugging.
32
33       CMDLINE
34           The options that appear on the kernel command line. The following
35           options are recognized:
36               ip
37               rd.route
38               bridge
39               bond
40               team
41               vlan
42               ib.pkey
43               bootdev
44               nameserver
45               rd.peerdns
46               rd.bootif
47               rd.ethtool
48               rd.net.timeout.dhcp
49               rd.net.timeout.carrier
50               rd.znet
51               BOOTIF
52           Please consult the dracut.cmdline(7) manual for the documentation
53           of the precise format of the values supported.
54

DIFFERENCES FROM THE NETWORK-LEGACY DRACUT MODULE

56       nm-initrd-generator generates a set of connections that are then
57       configured by the NetworkManager instance running in the initrd. There
58       are some differences in behavior compared to the network-legacy dracut
59       module:
60
61       •   When an interface is configured with a static address and a
62           gateway, the network-legacy module waits that the gateway responds
63           to arping requests before proceeding, while NetworkManager doesn't.
64
65       •   network-legacy configures interfaces one by one in the order in
66           which they are announced by udev. If multiple interfaces specify a
67           hostname (from command line or from DHCP), the one from the last
68           interface activated wins. With NetworkManager, hostnames from
69           command line have higher precedence over ones from DHCP, and the
70           last that appears in the command line wins.
71
72       •   NetworkManager supports the ib.pkey=PARENT.PKEY argument to set up
73           an Infiniband partition on IPoIB parent device PARENT using the
74           specified partition key PKEY. The partition key must be in
75           hexadecimal notation without leading "0x", for example
76           "ib.pkey=ib0.8004".
77
78       •   NetworkManager supports the rd.ethtool=INTERFACE:AUTONEG:SPEED
79           kernel command line option to set up ethtool NIC configuration
80           parameters AUTONEG and SPEED. The INTERFACE being configured must
81           be specified, and the other parameters are optional and can be left
82           blank. When SPEED is set, duplex mode is automatically set to
83           'full'.  INTERFACE accepts string values, AUTONEG accepts boolean
84           values (true and false / on or off / 0 or 1), and SPEED accepts
85           positive integer values.
86

EXIT STATUS

88       nm-initrd-generator exits with status 0. It ignores unrecognized
89       options and prints an error message if it encounters a malformed
90       option.
91

SEE ALSO

93       dracut.cmdline(7), NetworkManager(8).
94
95
96
97NetworkManager 1.32.12                                  NM-INITRD-GENERATOR(8)
Impressum