NetworkManager.conf is the configuration file for NetworkManager. It is used
to set up various aspects of NetworkManager's behavior. The
location of the main file and configuration directories may be changed
@@ -74,7 +74,7 @@
-
File Format
+
File Format
The configuration file format is so-called key file (sort of
ini-style format). It consists of sections (groups) of
@@ -111,7 +111,7 @@ plugins-=remove-me
-
+
main section
@@ -183,7 +183,7 @@ plugins-=remove-me
clients to be installed. The internal
option uses a built-in DHCP client which is not currently as
featureful as the external clients.
-
If this key is missing, it defaults to dhclient.
+
If this key is missing, it defaults to internal.
It the chosen plugin is not available, clients are looked for
in this order: dhclient, dhcpcd,
internal.
@@ -267,6 +267,34 @@ no-auto-default=*
+
hostname-mode
+
+
+ Set the management mode of the hostname. This parameter will
+ affect only the transient hostname. If a valid static hostname is set,
+ NetworkManager will skip the update of the hostname despite the value of
+ this option. An hostname empty or equal to 'localhost', 'localhost6',
+ 'localhost.localdomain' or 'localhost6.localdomain' is considered invalid.
+
+
default: NetworkManager will update the hostname
+ with the one provided via DHCP on the main connection (the one with a default
+ route). If not present, the hostname will be updated to the last one set
+ outside NetworkManager. If it is not valid, NetworkManager will try to recover
+ the hostname from the reverse lookup of the IP address of the main connection.
+ If this fails too, the hostname will be set to 'localhost.localdomain'.
+
+
dhcp: NetworkManager will update the transient hostname
+ only with information coming from DHCP. No fallback nor reverse lookup will be
+ performed, but when the dhcp connection providing the hostname is deactivated,
+ the hostname is reset to the last hostname set outside NetworkManager or
+ 'localhost' if none valid is there.
+
+
none: NetworkManager will not manage the transient
+ hostname and will never set it.
+
+
+
+
dns
Set the DNS (resolv.conf) processing mode.
@@ -286,7 +314,7 @@ no-auto-default=*
resolv.conf to point to the local
nameserver. It is possible to pass custom options to the
dnsmasq instance by adding them to files in the
- "${prefix}/etc/NetworkManager/dnsmasq.d/"
+ "/etc/NetworkManager/dnsmasq.d/"
directory. Note that when multiple upstream servers are
available, dnsmasq will initially contact them in parallel and
then use the fastest to respond, probing again other servers
@@ -312,15 +340,17 @@ no-auto-default=*
options, and this version of NetworkManager was build with a default of
"symlink".
Regardless of this setting, NetworkManager will
- always write resolv.conf to its runtime state directory.
-
symlink: NetworkManager will symlink
- /etc/resolv.conf to its private
- resolv.conf file in the runtime state directory. If
- /etc/resolv.conf
- already is a symlink pointing to a different location, the file
- will not be modified. This allows the user to disable managing
- by pointing the link /etc/resolv.conf to
- somewhere else.
+ always write resolv.conf to its runtime state directory
+ /var/run/NetworkManager/resolv.conf.
+
symlink: If /etc/resolv.conf is
+ a regular file, NetworkManager will replace the file on update. If
+ /etc/resolv.conf is instead a symlink, NetworkManager
+ will leave it alone. Unless the symlink points to the internal file
+ /var/run/NetworkManager/resolv.conf,
+ in which case the symlink will be updated to emit an inotify notification.
+ This allows the user to conveniently instruct NetworkManager not
+ to manage /etc/resolv.conf by replacing it with
+ a symlink.
file: NetworkManager will write
/etc/resolv.conf as file. If it finds
a symlink, it will follow the symlink and update the target
@@ -370,7 +400,7 @@ no-auto-default=*
-
+
keyfile section
This section contains keyfile-plugin-specific options, and
is normally only used when you are not using any other
@@ -393,7 +423,7 @@ no-auto-default=*
path
The location where keyfiles are read and stored.
- This defaults to "${prefix}/etc/NetworkManager/conf.d".
+ This defaults to "/etc/NetworkManager/system-connections".
This section controls NetworkManager's logging. Any
settings here are overridden by the --log-level
@@ -511,7 +541,7 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth
"debug" uses syslog and logs to standard error.
If NetworkManager is started in debug mode (--debug)
this option is ignored and "debug" is always used.
- Otherwise, the default is "journal".
+ Otherwise, the default is "syslog".
@@ -520,7 +550,7 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth
auditd, the audit daemon. If false, audit
records will be sent only to the NetworkManager logging
system. If set to true, they will be also
- sent to auditd. The default value is true.
+ sent to auditd. The default value is false.
Not all properties can be overwritten, only the following
properties are supported to have their default values configured
@@ -730,7 +760,7 @@ ipv6.ip6-privacy=1
-
+
device section
Contains per-device persistent configuration.
@@ -745,7 +775,7 @@ unmanaged=1
-
Supported Properties
+
Supported Properties
The following properties can be configured per-device.
@@ -811,6 +841,14 @@ unmanaged=1
for details.
+
+
sriov-num-vfs
+
+ Specify the number of virtual functions (VF) to enable
+ for a PCI physical device that supports single-root I/O
+ virtualization (SR-IOV).
+
+
@@ -818,7 +856,7 @@ unmanaged=1
-
Sections
+
Sections
The [device] section works the same as the [connection] section.
That is, multiple sections that all start with the prefix "device" can be specified.
@@ -830,7 +868,7 @@ unmanaged=1
-
+
connectivity section
This section controls NetworkManager's optional connectivity
checking functionality. This allows NetworkManager to detect
@@ -876,7 +914,7 @@ unmanaged=1
-
+
global-dns section
This section specifies global DNS settings that override
connection-specific configuration.
@@ -906,7 +944,7 @@ unmanaged=1
-
+
global-dns-domain sections
Sections with a name starting with the "global-dns-domain-"
prefix allow to define global DNS configuration for specific
@@ -942,7 +980,7 @@ unmanaged=1
-
+
.config sections
This is a special section that contains options which apply
to the configuration file that contains the option.
@@ -1045,7 +1083,7 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16
@@ -1188,6 +1226,13 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16
Globbing is not supported.
+
driver:DRIVER
+
Match the device driver as reported by "nmcli -f GENERAL.DRIVER,GENERAL.DRIVER-VERSION device show".
+ "DRIVER" must match the driver name exactly and does not support globbing.
+ Optionally, a driver version may be specified separated by '/'. Globbing is supported for the version.
+
+
+
except:SPEC
Negative match of a device. SPEC must be explicitly qualified with
a prefix such as interface-name:. A negative match has higher priority then the positive
@@ -1225,7 +1270,7 @@ interface-name:vboxnet*,except:interface-name:vboxnet2