From e74c568b07b50b97873fb4ee1d776dedefbd54d6 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Fri, 1 Oct 2021 23:05:04 +0200 Subject: New upstream version 1.32.12 --- docs/api/html/NetworkManager.conf.html | 236 ++++++++++++++++++++++++++++++--- 1 file changed, 216 insertions(+), 20 deletions(-) (limited to 'docs/api/html/NetworkManager.conf.html') diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index 3655be21..e8efb5e7 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -7,7 +7,7 @@ - + @@ -17,7 +17,7 @@ Home Up Prev -Next +Next
@@ -72,6 +72,12 @@ Certain settings from the configuration can be reloaded at runtime either by sending SIGHUP signal or via D-Bus' Reload call.

+

+ NetworkManager does not require any configuration in NetworkManager.conf. Depending + on your use case, you may remove all files to restore the default configuration (factory reset). But + note that your distribution or other packages may drop configuration snippets for NetworkManager, such + that they are part of the factory default. +

File Format

@@ -91,7 +97,7 @@ below.

- Minimal system settings configuration file looks like this: + A simple configuration file looks like this: 

 [main]
@@ -326,7 +332,9 @@ no-auto-default=*
 
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.

+        will be managed by dnssec-trigger daemon. This option is
+        deprecated. Note that dnssec-trigger ships a NetworkManager dispatcher
+        script so this DNS plugin is not necessary.

 
none: NetworkManager will not
         modify resolv.conf. This implies
         rc-manager unmanaged

@@ -456,6 +464,47 @@ no-auto-default=*
             index).
           

 
+
+
firewall-backend

+

+            The firewall backend for configuring masquerading
+            with shared mode.
+            Set to either iptables, nftables
+            or none.
+            iptables and nftables
+            require iptables and nft
+            application, respectively.
+            none means to skip firewall configuration if
+            the users wish to manage firewall themselves.
+            If unspecified, it will be auto detected.
+          

+
+
+
iwd-config-path

+
+

+            If the value is "auto" (the default), IWD is queried for its
+            current state directory when it appears on D-Bus -- the
+            directory where IWD keeps its network configuration files --
+            usually /var/lib/iwd.  NetworkManager will then attempt to
+            write copies of new or modified Wi-Fi connection profiles,
+            converted into the IWD format, into this directory thus making
+            IWD connection properties editable.  NM will overwrite existing
+            files without preserving their contents.
+          

+

+            The path can also be overriden by pointing to a specific
+            existing and writable directory.  On the other hand setting
+            this to an empty string or any other value disables the
+            profile conversion mechanism.
+          

+

+            This mechanism allows editing connection profile settings such
+            as the 802.1x configuration using NetworkManager clients.
+            Without it such changes have no effect in IWD.
+          

+
+
@@ -489,21 +538,30 @@ no-auto-default=*

unmanaged-devices

-

Set devices that should be ignored by - NetworkManager. -

-

See the section called “Device List Format” for the syntax on how to - specify a device. -

+

Set devices that should be ignored by NetworkManager. +

- Example: + A device unmanaged due to this option is strictly + unmanaged and cannot be overruled by using the API like + nmcli device set $IFNAME managed yes. + Also, a device that is unmanaged for other reasons, like + an udev rule, cannot be made managed with this option (e.g. by + using an except: specifier). + These two points make it different from the device*.managed + option which for that reason may be a better choice. +

+

See the section called “Device List Format” for the syntax on how to + specify a device.

+

+ Example: + 

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

-

+

@@ -772,6 +830,10 @@ ipv6.ip6-privacy=0 and 100 for other profiles.

+

ipv4.required-timeout

+ + +

ipv4.route-metric

@@ -815,6 +877,10 @@ ipv6.ip6-privacy=0

+

ipv6.required-timeout

+ + +

ipv6.route-metric

@@ -1005,19 +1071,32 @@ managed=1

carrier-wait-timeout

-

+ +

Specify the timeout for waiting for carrier in milliseconds. + The default is 5000 milliseconds. + This setting exists because certain drivers/hardware can take + a long time to detect whether the cable is plugged in. +

+

When the device loses carrier, NetworkManager does not react immediately. Instead, it waits for this timeout before considering - the link lost. Also, on startup, NetworkManager considers the + the link lost. +

+

+ Also, on startup, NetworkManager considers the device as busy for this time, as long as the device has no carrier. This delays startup-complete signal and NetworkManager-wait-online. Configuring this too high means to block NetworkManager-wait-online - longer then necessary. Configuring it too low, means that NetworkManager - will declare startup-complete, although carrier is about to come - and auto-activation to kick in. - The default is 5000 milliseconds. -

+ longer than necessary when booting with cable unplugged. Configuring + it too low, means that NetworkManager will declare startup-complete too + soon, although carrier is about to come and auto-activation to kick in. + Note that if a profile only has static IP configuration or Layer 3 configuration + disabled, then it can already autoconnect without carrier on the device. + Once such a profile reaches full activated state, startup-complete + is considered as reached even if the device has no carrier yet. +

+

ignore-carrier

@@ -1056,6 +1135,63 @@ managed=1 +

keep-configuration

+ +

+ On startup, NetworkManager tries to not interfere with + interfaces that are already configured. It does so by + generating a in-memory connection based on the interface + current configuration. +

+

+ If this generated connection matches one of the existing + persistent connections, the persistent connection gets + activated. If there is no match, the generated + connection gets activated as "external", which means + that the connection is considered as active, but + NetworkManager doesn't actually touch the interface. +

+

+ It is possible to disable this behavior by setting + keep-configuration to + no. In this way, on startup + NetworkManager always tries to activate the most + suitable persistent connection (the one with highest + autoconnect-priority or, in case of a tie, the one + activated most recently). +

+

+ Note that when NetworkManager gets restarted, it stores + the previous state in + /run/NetworkManager; in particular + it saves the UUID of the connection that was previously + active so that it can be activated again after the + restart. Therefore, + keep-configuration does not have + any effect on service restart. +

+ + + +

allowed-connections

+ +

+ A list of connections that can be activated on the + device. See the section called “Connection List Format” for the + syntax to specify a connection. If this option is not + specified, all connections can be potentially activated + on the device, provided that the connection type and + other settings match. +

+

+ A notable use case for this is to filter which + connections can be activated based on how they were + created; see the origin keyword in + the section called “Connection List Format”. +

+ + +

wifi.scan-rand-mac-address

Configures MAC address randomization of a Wi-Fi device during @@ -1092,7 +1228,7 @@ managed=1 If wifi.backend is iwd, setting this to false forces IWD's autoconnect mechanism to be disabled for this device and connections will only be initiated by NetworkManager whether - commaned by a client or automatically. Leaving it true (default) + commanded by a client or automatically. Leaving it true (default) stops NetworkManager from automatically initiating connections and allows IWD to use its network ranking and scanning logic to decide the best networks to autoconnect to next. Connections' autoconnect-priority, @@ -1573,6 +1709,66 @@ interface-name:vboxnet*,except:interface-name:vboxnet2

+
+
+

Connection List Format

+

+ Connections can be specified using the following format: +

+

+

+
++++ + + + + + + + + + + + + + + + + + + + + + + + + + + +

*

Matches every connection.

uuid:UUID

Match the connection by UUID, for example + "uuid:83037490-1d17-4986-a397-01f1db3a7fc2"

id=ID

Match the connection by name.

origin:ORIGIN

Match the connection by origin, stored in the + org.freedesktop.NetworkManager.origin tag of the user setting. For example, use + "except:origin:nm-initrd-generator" to forbid activation of connections created by the + initrd generator.

except:SPEC

 +

Negative match of a connection. A negative match has higher priority then the positive + matches above.

+

If there is a list consisting only of negative matches, the behavior is the same as if there is also + match-all. That means, if none of all the negative matches is satisfied, the overall result is still a + positive match.

+

SPEC[,;]SPEC

 +

Multiple specs can be concatenated with commas or semicolons. The order does not matter as + matches are either inclusive or negative (except:), with negative matches having higher + priority.

+

Backslash is supported to escape the separators ';' and ',', and to express special characters such as + newline ('\n'), tabulator ('\t'), whitespace ('\s') and backslash ('\\'). Whitespace is not a separator but + will be trimmed between two specs (unless escaped as '\s').

+
+

+

+

See Also

-- cgit 1.3.0-6-gf8a5