'\" t

.\"     Title: NetworkManager.conf

.\"    Author: 

.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>

.\"      Date: 12/23/2020

.\"    Manual: Configuration

.\"    Source: NetworkManager 1.29.7

.\"  Language: English

.\"

.TH "NETWORKMANAGER\&.CONF" "5" "" "NetworkManager 1\&.29\&.7" "Configuration"

.\" -----------------------------------------------------------------

.\" * Define some portability stuff

.\" -----------------------------------------------------------------

.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.\" http://bugs.debian.org/507673

.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html

.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.ie \n(.g .ds Aq \(aq

.el       .ds Aq '

.\" -----------------------------------------------------------------

.\" * set default formatting

.\" -----------------------------------------------------------------

.\" disable hyphenation

.nh

.\" disable justification (adjust text to left margin only)

.ad l

.\" -----------------------------------------------------------------

.\" * MAIN CONTENT STARTS HERE *

.\" -----------------------------------------------------------------

.SH "NAME"

NetworkManager.conf \- NetworkManager configuration file

.SH "SYNOPSIS"

.PP

/etc/NetworkManager/NetworkManager\&.conf,

/etc/NetworkManager/conf\&.d/\fIname\fR\&.conf,

/run/NetworkManager/conf\&.d/\fIname\fR\&.conf,

/usr/lib/NetworkManager/conf\&.d/\fIname\fR\&.conf,

/var/lib/NetworkManager/NetworkManager\-intern\&.conf

.SH "DESCRIPTION"

.PP

NetworkManager\&.conf

is the configuration file for NetworkManager\&. It is used to set up various aspects of NetworkManager\*(Aqs behavior\&. The location of the main file and configuration directories may be changed through use of the

\fB\-\-config\fR,

\fB\-\-config\-dir\fR,

\fB\-\-system\-config\-dir\fR, and

\fB\-\-intern\-config\fR

argument for NetworkManager, respectively\&.

.PP

If a default

NetworkManager\&.conf

is provided by your distribution\*(Aqs packages, you should not modify it, since your changes may get overwritten by package updates\&. Instead, you can add additional

\&.conf

files to the

/etc/NetworkManager/conf\&.d

directory\&. These will be read in order, with later files overriding earlier ones\&. Packages might install further configuration snippets to

/usr/lib/NetworkManager/conf\&.d\&. This directory is parsed first, even before

NetworkManager\&.conf\&. Scripts can also put per\-boot configuration into

/run/NetworkManager/conf\&.d\&. This directory is parsed second, also before

NetworkManager\&.conf\&. The loading of a file

/run/NetworkManager/conf\&.d/\fIname\fR\&.conf

can be prevented by adding a file

/etc/NetworkManager/conf\&.d/\fIname\fR\&.conf\&. Likewise, a file

/usr/lib/NetworkManager/conf\&.d/\fIname\fR\&.conf

can be shadowed by putting a file of the same name to either

/etc/NetworkManager/conf\&.d

or

/run/NetworkManager/conf\&.d\&.

.PP

NetworkManager can overwrite certain user configuration options via D\-Bus or other internal operations\&. In this case it writes those changes to

/var/lib/NetworkManager/NetworkManager\-intern\&.conf\&. This file is not intended to be modified by the user, but it is read last and can shadow user configuration from

NetworkManager\&.conf\&.

.PP

Certain settings from the configuration can be reloaded at runtime either by sending SIGHUP signal or via D\-Bus\*(Aq Reload call\&.

.SH "FILE FORMAT"

.PP

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 \*(Aq#\*(Aq and blank lines are considered comments\&. Sections are started by a header line containing the section enclosed in \*(Aq[\*(Aq and \*(Aq]\*(Aq, 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\&.

.PP

For keys that take a list of devices as their value, you can specify devices by their MAC addresses or interface names, or "*" to specify all devices\&. See

the section called \(lqDevice List Format\(rq

below\&.

.PP

Minimal system settings configuration file looks like this:

.sp

.if n \{\

.RS 4

.\}

.nf

[main]

plugins=keyfile

.fi

.if n \{\

.RE

.\}

.PP

As an extension to the normal keyfile format, you can also append a value to a previously\-set list\-valued key by doing:

.sp

.if n \{\

.RS 4

.\}

.nf

plugins+=another\-plugin

plugins\-=remove\-me

.fi

.if n \{\

.RE

.\}

.sp

.SH "MAIN SECTION"

.PP

\fIplugins\fR

.RS 4

Lists system settings plugin names separated by \*(Aq,\*(Aq\&. These plugins are used to read and write system\-wide connection profiles\&. When multiple 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\*(Aqt write out any connections) the next plugin is tried, etc\&. If none of the plugins can save the connection, an error is returned to the user\&.

.sp

The default value and the number of available plugins is distro\-specific\&. See

the section called \(lqPLUGINS\(rq

below for the available plugins\&. Note that NetworkManager\*(Aqs native

keyfile

plugin is always appended to the end of this list (if it doesn\*(Aqt already appear earlier in the list)\&.

.RE

.PP

\fImonitor\-connection\-files\fR

.RS 4

This setting is deprecated and has no effect\&. Profiles from disk are never automatically reloaded\&. Use for example

nmcli connection (re)load

for that\&.

.RE

.PP

\fIauth\-polkit\fR

.RS 4

Whether the system uses PolicyKit for authorization\&. If

true, non\-root requests are authorized using PolicyKit\&. Requests from root (user ID zero) are always granted without asking PolicyKit\&. If

false, all requests will be allowed and PolicyKit is not used\&. If set to

root\-only

PolicyKit is not used and all requests except root are denied\&. The default value is

true\&.

.RE

.PP

\fIdhcp\fR

.RS 4

This key sets up what DHCP client NetworkManager will use\&. Allowed values are

dhclient,

dhcpcd, and

internal\&. The

dhclient

and

dhcpcd

options require the indicated clients to be installed\&. The

internal

option uses a built\-in DHCP client which is not currently as featureful as the external clients\&.

.sp

If this key is missing, it defaults to

internal\&. If the chosen plugin is not available, clients are looked for in this order:

dhclient,

dhcpcd,

internal\&.

.RE

.PP

\fIno\-auto\-default\fR

.RS 4

Specify devices for which NetworkManager shouldn\*(Aqt create default wired connection (Auto eth0)\&. By default, NetworkManager creates a temporary wired connection for any Ethernet device that is managed and doesn\*(Aqt have a connection configured\&. List a device in this option to inhibit creating the default connection for the device\&. May have the special value

*

to apply to all devices\&.

.sp

When the default wired connection is deleted or saved to a new persistent connection by a plugin, the device is added to a list in the file

/var/lib/NetworkManager/no\-auto\-default\&.state

to prevent creating the default connection for that device again\&.

.sp

See

the section called \(lqDevice List Format\(rq

for the syntax how to specify a device\&.

.sp

Example:

.sp

.if n \{\

.RS 4

.\}

.nf

no\-auto\-default=00:22:68:5c:5d:c4,00:1e:65:ff:aa:ee

no\-auto\-default=eth0,eth1

no\-auto\-default=*

.fi

.if n \{\

.RE

.\}

.sp

.RE

.PP

\fIignore\-carrier\fR

.RS 4

This setting is deprecated for the per\-device setting

ignore\-carrier

which overwrites this setting if specified (See

\fIignore\-carrier\fR)\&. Otherwise, it is a list of matches to specify for which device carrier should be ignored\&. See

the section called \(lqDevice List Format\(rq

for the syntax how to specify a device\&. Note that master types like bond, bridge, and team ignore carrier by default\&. You can however revert that default using the "except:" specifier (or better, use the per\-device setting instead of the deprecated setting)\&.

.RE

.PP

\fIassume\-ipv6ll\-only\fR

.RS 4

Specify devices for which NetworkManager will try to generate a connection based on initial configuration when the device only has an IPv6 link\-local address\&.

.sp

See

the section called \(lqDevice List Format\(rq

for the syntax how to specify a device\&.

.RE

.PP

\fIconfigure\-and\-quit\fR

.RS 4

When set to \*(Aqtrue\*(Aq, NetworkManager quits after performing initial network configuration but spawns small helpers to preserve DHCP leases and IPv6 addresses\&. This is useful in environments where network setup is more or less static or it is desirable to save process time but still handle some dynamic configurations\&. When this option is

true, network configuration for Wi\-Fi, WWAN, Bluetooth, ADSL, and PPPoE interfaces cannot be preserved due to their use of external services, and these devices will be deconfigured when NetworkManager quits even though other interface\*(Aqs configuration may be preserved\&. Also, to preserve DHCP addresses the \*(Aqdhcp\*(Aq option must be set to \*(Aqinternal\*(Aq\&. The default value of the \*(Aqconfigure\-and\-quit\*(Aq option is \*(Aqfalse\*(Aq, meaning that NetworkManager will continue running after initial network configuration and continue responding to system and hardware events, D\-Bus requests, and user commands\&.

.RE

.PP

\fIhostname\-mode\fR

.RS 4

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 \*(Aqlocalhost\*(Aq, \*(Aqlocalhost6\*(Aq, \*(Aqlocalhost\&.localdomain\*(Aq or \*(Aqlocalhost6\&.localdomain\*(Aq is considered invalid\&.

.sp

default: NetworkManager will update the hostname with the one provided via DHCP or reverse DNS lookup of the IP address on the connection with the default route or on any connection with the property hostname\&.only\-from\-default set to \*(Aqfalse\*(Aq\&. Connections are considered in order of increasing value of the

hostname\&.priority

property\&. In case multiple connections have the same priority, connections activated earlier are considered first\&. If no hostname can be determined in such way, the hostname will be updated to the last one set outside NetworkManager or to \*(Aqlocalhost\&.localdomain\*(Aq\&.

.sp

dhcp: this is similar to \*(Aqdefault\*(Aq, with the difference that after trying to get the DHCP hostname, reverse DNS lookup is not done\&. Note that selecting this option is equivalent to setting the property \*(Aqhostname\&.from\-dns\-lookup\*(Aq to \*(Aqfalse\*(Aq globally for all connections in NetworkManager\&.conf\&.

.sp

none: NetworkManager will not manage the transient hostname and will never set it\&.

.RE

.PP

\fIdns\fR

.RS 4

Set the DNS processing mode\&.

.sp

If the key is unspecified,

default

is used, unless

/etc/resolv\&.conf

is a symlink to

/run/systemd/resolve/stub\-resolv\&.conf,

/run/systemd/resolve/resolv\&.conf,

/lib/systemd/resolv\&.conf

or

/usr/lib/systemd/resolv\&.conf\&. In that case,

systemd\-resolved

is chosen automatically\&.

.sp

default: NetworkManager will update

/etc/resolv\&.conf

to reflect the nameservers provided by currently active connections\&. The

rc\-manager

setting (below) controls how this is done\&.

.sp

dnsmasq: NetworkManager will run dnsmasq as a local caching nameserver, using "Conditional Forwarding" if you are connected to a VPN, and then update

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 "/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 after some time\&. This behavior can be modified passing the \*(Aqall\-servers\*(Aq or \*(Aqstrict\-order\*(Aq options to dnsmasq (see the manual page for more details)\&.

.sp

systemd\-resolved: NetworkManager will push the DNS configuration to systemd\-resolved

.sp

unbound: NetworkManager will talk to unbound and dnssec\-triggerd, using "Conditional Forwarding" with DNSSEC support\&.

/etc/resolv\&.conf

will be managed by dnssec\-trigger daemon\&.

.sp

none: NetworkManager will not modify resolv\&.conf\&. This implies

rc\-manager\ \&unmanaged

.sp

Note that the plugins

dnsmasq,

systemd\-resolved

and

unbound

are caching local nameservers\&. Hence, when NetworkManager writes

/run/NetworkManager/resolv\&.conf

and

/etc/resolv\&.conf

(according to

rc\-manager

setting below), the name server there will be localhost only\&. NetworkManager also writes a file

/run/NetworkManager/no\-stub\-resolv\&.conf

that contains the original name servers pushed to the DNS plugin\&.

.sp

When using

dnsmasq

and

systemd\-resolved

per\-connection added dns servers will always be queried using the device the connection has been activated on\&.

.RE

.PP

\fIrc\-manager\fR

.RS 4

Set the

resolv\&.conf

management mode\&. This option is about how NetworkManager writes to

/etc/resolv\&.conf, if at all\&. The default value depends on NetworkManager build options, and this version of NetworkManager was build with a default of "auto"\&. Regardless of this setting, NetworkManager will always write its version of resolv\&.conf to its runtime state directory as

/run/NetworkManager/resolv\&.conf\&.

.sp

If you configure

dns=none

or make

/etc/resolv\&.conf

immutable with

chattr +i, NetworkManager will ignore this setting and always choose

unmanaged

(below)\&.

.sp

auto: if systemd\-resolved plugin is configured via the

dns

setting or if it gets detected as main DNS plugin, NetworkManager will update systemd\-resolved without touching

/etc/resolv\&.conf\&. Alternatively, if

resolvconf

or

netconfig

are enabled at compile time and the respective binary is found, NetworkManager will automatically use it\&. Note that if you install or uninstall these binaries, you need to reload the

rc\-manager

setting with SIGHUP or

systemctl reload NetworkManager\&. As last fallback it uses the

symlink

option (see next)\&.

.sp

symlink: If

/etc/resolv\&.conf

is a regular file or does not exist, NetworkManager will write the file directly\&. If

/etc/resolv\&.conf

is instead a symlink, NetworkManager will leave it alone\&. Unless the symlink points to the internal file

/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\&.

.sp

file: NetworkManager will write

/etc/resolv\&.conf

as regular file\&. If it finds a symlink to an existing target, it will follow the symlink and update the target instead\&. In no case will an existing symlink be replaced by a file\&. Note that older versions of NetworkManager behaved differently and would replace dangling symlinks with a plain file\&.

.sp

resolvconf: NetworkManager will run resolvconf to update the DNS configuration\&.

.sp

netconfig: NetworkManager will run netconfig to update the DNS configuration\&.

.sp

unmanaged: don\*(Aqt touch

/etc/resolv\&.conf\&.

.sp

none: deprecated alias for

symlink\&.

.RE

.PP

\fIsystemd\-resolved\fR

.RS 4

Send the connection DNS configuration to

systemd\-resolved\&. Defaults to "true"\&.

.sp

Note that this setting is complementary to the

\fIdns\fR

setting\&. You can keep this enabled while using

\fIdns\fR

set to another DNS plugin alongside

systemd\-resolved, or

\fIdns\fR

set to

systemd\-resolved

to configure the system resolver to use

systemd\-resolved\&.

.sp

If systemd\-resolved is enabled, the connectivity check resolves the hostname per\-device\&.

.RE

.PP

\fIdebug\fR

.RS 4

Comma separated list of options to aid debugging\&. This value will be combined with the environment variable

NM_DEBUG\&. Currently, the following values are supported:

.sp

RLIMIT_CORE: set ulimit \-c unlimited to write out core dumps\&. Beware, that a core dump can contain sensitive information such as passwords or configuration settings\&.

.sp

fatal\-warnings: set g_log_set_always_fatal() to core dump on warning messages from glib\&. This is equivalent to the \-\-g\-fatal\-warnings command line option\&.

.RE

.PP

\fIautoconnect\-retries\-default\fR

.RS 4

The number of times a connection activation should be automatically tried before switching to another one\&. This value applies only to connections that can auto\-connect and have a

connection\&.autoconnect\-retries

property set to \-1\&. If not specified, connections will be tried 4 times\&. Setting this value to 1 means to try activation once, without retry\&.

.RE

.PP

\fIslaves\-order\fR

.RS 4

This key specifies in which order slave connections are auto\-activated on boot or when the master activates them\&. Allowed values are

name

(order connection by interface name, the default), or

index

(order slaves by their kernel index)\&.

.RE

.SH "KEYFILE SECTION"

.PP

This section contains keyfile\-plugin\-specific options, and is normally only used when you are not using any other distro\-specific plugin\&.

.PP

.PP

\fIhostname\fR

.RS 4

This key is deprecated and has no effect since the hostname is now stored in

/etc/hostname

or other system configuration files according to build options\&.

.RE

.PP

\fIpath\fR

.RS 4

The location where keyfiles are read and stored\&. This defaults to "/etc/NetworkManager/system\-connections"\&.

.RE

.PP

\fIunmanaged\-devices\fR

.RS 4

Set devices that should be ignored by NetworkManager\&.

.sp

See

the section called \(lqDevice List Format\(rq

for the syntax on how to specify a device\&.

.sp

Example:

.sp

.if n \{\

.RS 4

.\}

.nf

unmanaged\-devices=interface\-name:em4

unmanaged\-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface\-name:eth2

.fi

.if n \{\

.RE

.\}

.sp

.RE

.SH "IFUPDOWN SECTION"

.PP

This section contains ifupdown\-specific options and thus only has effect when using the

ifupdown

plugin\&.

.PP

.PP

\fImanaged\fR

.RS 4

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\&.

.sp

The default value is

false\&.

.RE

.SH "LOGGING SECTION"

.PP

This section controls NetworkManager\*(Aqs logging\&. Any settings here are overridden by the

\fB\-\-log\-level\fR

and

\fB\-\-log\-domains\fR

command\-line options\&.

.PP

.PP

\fIlevel\fR

.RS 4

The default logging verbosity level\&. One of

OFF,

ERR,

WARN,

INFO,

DEBUG,

TRACE\&. 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\&. TRACE enables even more verbose logging then DEBUG level\&. Subsequent levels also log all messages from earlier levels; thus setting the log level to INFO also logs error and warning messages\&.

.RE

.PP

\fIdomains\fR

.RS 4

The following log domains are available: PLATFORM, RFKILL, ETHER, WIFI, BT, MB, DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6, AUTOIP4, DNS, VPN, SHARING, SUPPLICANT, AGENTS, SETTINGS, SUSPEND, CORE, DEVICE, OLPC, WIMAX, INFINIBAND, FIREWALL, ADSL, BOND, VLAN, BRIDGE, DBUS_PROPS, TEAM, CONCHECK, DCB, DISPATCH, AUDIT, SYSTEMD, VPN_PLUGIN, PROXY\&.

.sp

In addition, these special domains can be used: NONE, ALL, DEFAULT, DHCP, IP\&.

.sp

You can specify per\-domain log level overrides by adding a colon and a log level to any domain\&. E\&.g\&., "WIFI:DEBUG,WIFI_SCAN:OFF"\&.

.RE

.PP

.RS 4

.PP

Domain descriptions:

.RS 4

PLATFORM    : OS (platform) operations

.RE

.RS 4

RFKILL      : RFKill subsystem operations

.RE

.RS 4

ETHER       : Ethernet device operations

.RE

.RS 4

WIFI        : Wi\-Fi device operations

.RE

.RS 4

BT          : Bluetooth operations

.RE

.RS 4

MB          : Mobile broadband operations

.RE

.RS 4

DHCP4       : DHCP for IPv4

.RE

.RS 4

DHCP6       : DHCP for IPv6

.RE

.RS 4

PPP         : Point\-to\-point protocol operations

.RE

.RS 4

WIFI_SCAN   : Wi\-Fi scanning operations

.RE

.RS 4

IP4         : IPv4\-related operations

.RE

.RS 4

IP6         : IPv6\-related operations

.RE

.RS 4

AUTOIP4     : AutoIP operations

.RE

.RS 4

DNS         : Domain Name System related operations

.RE

.RS 4

VPN         : Virtual Private Network connections and operations

.RE

.RS 4

SHARING     : Connection sharing\&. With TRACE level log queries for dnsmasq instance

.RE

.RS 4

SUPPLICANT  : WPA supplicant related operations

.RE

.RS 4

AGENTS      : Secret agents operations and communication

.RE

.RS 4

SETTINGS    : Settings/config service operations

.RE

.RS 4

SUSPEND     : Suspend/resume

.RE

.RS 4

CORE        : Core daemon and policy operations

.RE

.RS 4

DEVICE      : Activation and general interface operations

.RE

.RS 4

OLPC        : OLPC Mesh device operations

.RE

.RS 4

WIMAX       : WiMAX device operations

.RE

.RS 4

INFINIBAND  : InfiniBand device operations

.RE

.RS 4

FIREWALL    : FirewallD related operations

.RE

.RS 4

ADSL        : ADSL device operations

.RE

.RS 4

BOND        : Bonding operations

.RE

.RS 4

VLAN        : VLAN operations

.RE

.RS 4

BRIDGE      : Bridging operations

.RE

.RS 4

DBUS_PROPS  : D\-Bus property changes

.RE

.RS 4

TEAM        : Teaming operations

.RE

.RS 4

CONCHECK    : Connectivity check

.RE

.RS 4

DCB         : Data Center Bridging (DCB) operations

.RE

.RS 4

DISPATCH    : Dispatcher scripts

.RE

.RS 4

AUDIT       : Audit records

.RE

.RS 4

SYSTEMD     : Messages from internal libsystemd

.RE

.RS 4

VPN_PLUGIN  : logging messages from VPN plugins

.RE

.RS 4

PROXY       : logging messages for proxy handling

.RE

.RS 4

.RE

.RS 4

NONE        : when given by itself logging is disabled

.RE

.RS 4

ALL         : all log domains

.RE

.RS 4

DEFAULT     : default log domains

.RE

.RS 4

DHCP        : shortcut for "DHCP4,DHCP6"

.RE

.RS 4

IP          : shortcut for "IP4,IP6"

.RE

.RS 4

.RE

.RS 4

HW          : deprecated alias for "PLATFORM"

.RE

.PP

In general, the logfile should not contain passwords or private data\&. However, you are always advised to check the file before posting it online or attaching to a bug report\&.

VPN_PLUGIN

is special as it might reveal private information of the VPN plugins with verbose levels\&. Therefore this domain will be excluded when setting

ALL

or

DEFAULT

to more verbose levels then

INFO\&.

.RE

.PP

\fIbackend\fR

.RS 4

The logging backend\&. Supported values are "syslog" and "journal"\&. When NetworkManager is started with "\-\-debug" in addition all messages will be printed to stderr\&. If unspecified, the default is "syslog"\&.

.RE

.PP

\fIaudit\fR

.RS 4

Whether the audit records are delivered to 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

false\&.

.RE

.SH "CONNECTION SECTION"

.PP

Specify default values for connections\&.

.PP

Such default values are only consulted if the corresponding per\-connection property explicitly allows for that\&. That means, all these properties correspond to a property of the connection profile (for example

connection\&.mud\-url)\&. Only if the per\-profile property is set to a special value that indicates to use the default, the default value from NetworkManager\&.conf is consulted\&. It depends on the property, which is the special value that indicates fallback to the default, but it usually is something like empty, unset values or special numeric values like 0 or \-1\&. That means the effectively used value can first always be configured for each profile, and these default values only matter if the per\-profile values explicitly indicates to use the default from

NetworkManager\&.conf\&.

.PP

Example:

.sp

.if n \{\

.RS 4

.\}

.nf

[connection]

ipv6\&.ip6\-privacy=0

.fi

.if n \{\

.RE

.\}

.sp

.SS "Supported Properties"

.PP

Not all properties can be overwritten, only the following properties are supported to have their default values configured (see

\fBnm-settings\fR(5)

for details)\&.

.PP

.PP

\fI802\-1x\&.auth\-timeout\fR

.RS 4

.RE

.PP

\fIcdma\&.mtu\fR

.RS 4

.RE

.PP

\fIconnection\&.auth\-retries\fR

.RS 4

If left unspecified, the default value is 3 tries before failing the connection\&.

.RE

.PP

\fIconnection\&.autoconnect\-slaves\fR

.RS 4

.RE

.PP

\fIconnection\&.mud\-url\fR

.RS 4

If unspecified, MUD URL defaults to

"none"\&.

.RE

.PP

\fIconnection\&.lldp\fR

.RS 4

.RE

.PP

\fIconnection\&.llmnr\fR

.RS 4

If unspecified, the ultimate default values depends on the DNS plugin\&. With systemd\-resolved the default currently is "yes" (2) and for all other plugins "no" (0)\&.

.RE

.PP

\fIconnection\&.mdns\fR

.RS 4

If unspecified, the ultimate default values depends on the DNS plugin\&. With systemd\-resolved the default currently is "no" (0) and for all other plugins also "no" (0)\&.

.RE

.PP

\fIconnection\&.stable\-id\fR

.RS 4

.RE

.PP

\fIethernet\&.cloned\-mac\-address\fR

.RS 4

If left unspecified, it defaults to "preserve"\&.

.RE

.PP

\fIethernet\&.generate\-mac\-address\-mask\fR

.RS 4

.RE

.PP

\fIethernet\&.mtu\fR

.RS 4

If configured explicitly to 0, the MTU is not reconfigured during device activation unless it is required due to IPv6 constraints\&. If left unspecified, a DHCP/IPv6 SLAAC provided value is used or the MTU is not reconfigured during activation\&.

.RE

.PP

\fIethernet\&.wake\-on\-lan\fR

.RS 4

.RE

.PP

\fIgsm\&.mtu\fR

.RS 4

.RE

.PP

\fIhostname\&.from\-dhcp\fR

.RS 4

.RE

.PP

\fIhostname\&.from\-dns\-lookup\fR

.RS 4

.RE

.PP

\fIhostname\&.only\-from\-default\fR

.RS 4

.RE

.PP

\fIhostname\&.priority\fR

.RS 4

.RE

.PP

\fIinfiniband\&.mtu\fR

.RS 4

If configured explicitly to 0, the MTU is not reconfigured during device activation unless it is required due to IPv6 constraints\&. If left unspecified, a DHCP/IPv6 SLAAC provided value is used or the MTU is left unspecified on activation\&.

.RE

.PP

\fIip\-tunnel\&.mtu\fR

.RS 4

If configured explicitly to 0, the MTU is not reconfigured during device activation unless it is required due to IPv6 constraints\&. If left unspecified, a DHCP/IPv6 SLAAC provided value is used or a default of 1500\&.

.RE

.PP

\fIipv4\&.dad\-timeout\fR

.RS 4

.RE

.PP

\fIipv4\&.dhcp\-client\-id\fR

.RS 4

.RE

.PP

\fIipv4\&.dhcp\-iaid\fR

.RS 4

If left unspecified, it defaults to "ifname"\&.

.RE

.PP

\fIipv4\&.dhcp\-hostname\-flags\fR

.RS 4

If left unspecified, the value 3 (fqdn\-encoded,fqdn\-serv\-update) is used\&.

.RE

.PP

\fIipv4\&.dhcp\-timeout\fR

.RS 4

If left unspecified, the default value for the interface type is used\&.

.RE

.PP

\fIipv4\&.dhcp\-vendor\-class\-identifier\fR

.RS 4

If left unspecified, the default is to not send the DHCP option to the server\&.

.RE

.PP

\fIipv4\&.dns\-priority\fR

.RS 4

If unspecified or zero, use 50 for VPN profiles and 100 for other profiles\&.

.RE

.PP

\fIipv4\&.route\-metric\fR

.RS 4

.RE

.PP

\fIipv4\&.route\-table\fR

.RS 4

If left unspecified, routes are only added to the main table\&. Note that this is different from explicitly selecting the main table 254, because of how NetworkManager removes extraneous routes from the tables\&.

.RE

.PP

\fIipv6\&.ra\-timeout\fR

.RS 4

If left unspecified, the default value depends on the sysctl solicitation settings\&.

.RE

.PP

\fIipv6\&.dhcp\-duid\fR

.RS 4

If left unspecified, it defaults to "lease"\&.

.RE

.PP

\fIipv6\&.dhcp\-iaid\fR

.RS 4

If left unspecified, it defaults to "ifname"\&.

.RE

.PP

\fIipv6\&.dhcp\-hostname\-flags\fR

.RS 4

If left unspecified, the value 1 (fqdn\-serv\-update) is used\&.

.RE

.PP

\fIipv6\&.dhcp\-timeout\fR

.RS 4

If left unspecified, the default value for the interface type is used\&.

.RE

.PP

\fIipv6\&.dns\-priority\fR

.RS 4

If unspecified or zero, use 50 for VPN profiles and 100 for other profiles\&.

.RE

.PP

\fIipv6\&.ip6\-privacy\fR

.RS 4

If

ipv6\&.ip6\-privacy

is unset, use the content of "/proc/sys/net/ipv6/conf/default/use_tempaddr" as last fallback\&.

.RE

.PP

\fIipv6\&.route\-metric\fR

.RS 4

.RE

.PP

\fIipv6\&.route\-table\fR

.RS 4

If left unspecified, routes are only added to the main table\&. Note that this is different from explicitly selecting the main table 254, because of how NetworkManager removes extraneous routes from the tables\&.

.RE

.PP

\fIsriov\&.autoprobe\-drivers\fR

.RS 4

If left unspecified, drivers are autoprobed when the SR\-IOV VF gets created\&.

.RE

.PP

\fIvpn\&.timeout\fR

.RS 4

If left unspecified, default value of 60 seconds is used\&.

.RE

.PP

\fIwifi\&.ap\-isolation\fR

.RS 4

If left unspecified, AP isolation is disabled\&.

.RE

.PP

\fIwifi\&.cloned\-mac\-address\fR

.RS 4

If left unspecified, it defaults to "preserve"\&.

.RE

.PP

\fIwifi\&.generate\-mac\-address\-mask\fR

.RS 4

.RE

.PP

\fIwifi\&.mac\-address\-randomization\fR

.RS 4

If left unspecified, MAC address randomization is disabled\&. This setting is deprecated for

wifi\&.cloned\-mac\-address\&.

.RE

.PP

\fIwifi\&.mtu\fR

.RS 4

If configured explicitly to 0, the MTU is not reconfigured during device activation unless it is required due to IPv6 constraints\&. If left unspecified, a DHCP/IPv6 SLAAC provided value is used or a default of 1500\&.

.RE

.PP