NetworkManager.conf - NetworkManager configuration file
2. SYNOPSIS ▲
where <SYSCONFDIR> depends on your distribution or build.
3. DESCRIPTION ▲
NetworkManager.conf is a configuration file for NetworkManager. It is used to set up various aspects of NetworkManager's behavior. The location of the file may be changed through use of the "--config=" argument for NetworkManager (8). It is not necessary to restart NetworkManager when making changes, as the configuration file is watched for changes and reloaded automatically when necessary.
4. FILE FORMAT ▲
The configuration file format is so-called key file (sort of ini-style format). It consists of sections (groups) of key-value pairs. Lines beginning with a '#' and blank lines are considered comments. Sections are started by a header line containing the section enclosed in '[' and ']', and ended implicitly by the start of the next section or the end of the file. Each key-value pair must be contained in a section.
Minimal system settings configuration file looks like this:
Description of sections and available keys follows:
4.1. [main] ▲
This section is the only mandatory section of the configuration file.
List plugin names separated by ','. Plugins are used to read/write system-wide connection. When more plugins are specified, the connections are read from all listed plugins. When writing connections, the plugins will be asked to save the connection in the order listed here. If the first plugin cannot write out that connection type, or can't write out any connections, the next plugin is tried. If none of the plugins can save the connection, the error is returned to the user.
plugin is the generic plugin that supports all the connection types and capabilities that NetworkManager has. It writes files out in a .ini-style format in /etc/NetworkManager/system-connections. For security, it will ignore files that are readable or writeable by any user or group other than root since private keys and passphrases may be stored in plaintext inside the file.
plugin is used on the Fedora and Red Hat Enterprise Linux distributions to read and write configuration from the standard /etc/sysconfig/network-scripts/ifcfg-* files. It currently supports reading wired, WiFi, and 802.1x connections, but does not yet support reading or writing mobile broadband, PPPoE, or VPN connections. To allow reading and writing of these add keyfile plugin to your configuration as well.
plugin is used on the Debian and Ubuntu distributions, and reads connections from /etc/network/interfaces. Since it cannot write connections out (that support isn't planned), it is usually paired with the keyfile plugin to enable saving and editing of new connections. The ifupdown plugin supports basic wired and WiFi connections, including WPA-PSK.
plugin is only provided for simple backward compatibility with SUSE and OpenSUSE configuration. Most setups should be using the keyfile plugin instead. The ifcfg-suse plugin supports reading wired and WiFi connections, but does not support saving any connection types.
dhcp=dhclient | dhcpcd
This key sets up what DHCP client NetworkManager will use. Presently dhclient and dhcpcd are supported. The client configured here should be available on your system too. If this key is missing, available DHCP clients are looked for in this order: dhclient, dhcpcd.
4.2. [keyfile] ▲
This section contains keyfile-specific options and thus only has effect when using keyfile plugin.
Set a persistent hostname when using the keyfile plugin.
Set devices that should be ignored by NetworkManager when using the keyfile plugin. Devices are specified in the following format: "mac:<hwaddr>", where <hwaddr> is MAC address of the device to be ignored, in lowercase. Multiple entries are separated by a semicolon. Example:
4.3. [ifupdown] ▲
This section contains ifupdown-specific options and thus only has effect when using ifupdown plugin.
managed=false | true
Controls whether interfaces listed in the 'interfaces' file are managed by NetworkManager. If set to true, then interfaces listed in /etc/network/interfaces are managed by NetworkManager. If set to false, then any interface listed in /etc/network/interfaces will be ignored by NetworkManager. Remember that NetworkManager controls the default route, so because the interface is ignored, NetworkManager may assign the default route to some other interface. When the option is missing, false value is taken as default.
4.4. [logging] ▲
This section controls NetworkManager's logging. Any settings here are overridden by the --log-level and --log-domains command-line options.
One of [ERR, WARN, INFO, DEBUG]. The ERR level logs only critical errors. WARN logs warnings that may reflect operation. INFO logs various informational messages that are useful for tracking state and operations. DEBUG enables verbose logging for debugging purposes. Subsequent levels also log all messages from earlier levels; thus setting the log level to INFO also logs error and warning messages.
The following log domains are available: [NONE, HW, RKILL, ETHER, WIFI, BT, MB, DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6, AUTOIP4, DNS, VPN, SHARING, SUPPLICANT, USER_SET, SYS_SET, SUSPEND, CORE, DEVICE, OLPC]. When "NONE" is given by itself, logging is disabled. MB = Mobile Broadband, USER_SET = user settings operations and communication, SYS_SET = system settings service operations, OLPC = OLPC Mesh device operations, CORE = core daemon operations, DEVICE = activation and general interface operations.
5. SEE ALSO ▲
R NetworkManager (8),
R nm-tool (1).