From cfb80376641fa49137b9996130352697e7f8b436 Mon Sep 17 00:00:00 2001 From: Sebastien Bacher Date: Wed, 25 Aug 2021 15:23:22 +0200 Subject: New upstream version 1.32.10 --- man/NetworkManager.conf.xml | 112 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 112 insertions(+) (limited to 'man/NetworkManager.conf.xml') diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index df85e641..7eaa4cb2 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -868,6 +868,9 @@ ipv6.ip6-privacy=0 If unspecified or zero, use 50 for VPN profiles and 100 for other profiles. + + ipv4.required-timeout + ipv4.route-metric @@ -910,6 +913,9 @@ ipv6.ip6-privacy=0 "/proc/sys/net/ipv6/conf/default/use_tempaddr" as last fallback. + + ipv6.required-timeout + ipv6.route-metric @@ -1144,6 +1150,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 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 + . + + + wifi.scan-rand-mac-address @@ -1641,6 +1704,55 @@ 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'). + + + + + -- cgit 1.3.0-6-gf8a5