diff options
| author | Beniamino Galvani <bgalvani@redhat.com> | 2021-05-07 13:57:04 +0200 |
|---|---|---|
| committer | Beniamino Galvani <bgalvani@redhat.com> | 2021-07-27 16:36:48 +0200 |
| commit | df2fe157142f92847d4f14103775e3cf704cb3ca (patch) | |
| tree | 3065ffb6a73339f78f86142b19087360dc6cb5d2 /man/NetworkManager.conf.xml | |
| parent | b1644fa826bafe95dfe338e56541c59468ba763c (diff) | |
| download | NetworkManager-df2fe157142f92847d4f14103775e3cf704cb3ca.tar.gz | |
core: add 'keep-configuration' device configuration option
Add a new 'keep-configuration' device option, set to 'yes' by
default. When set to 'no', on startup NetworkManager ignores that the
interface is pre-configured and doesn't try to keep its
configuration. Instead, it activates one of the persistent
connections.
Diffstat (limited to 'man/NetworkManager.conf.xml')
| -rw-r--r-- | man/NetworkManager.conf.xml | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index 3ef5d3dc5a..819c051e20 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -1150,6 +1150,44 @@ managed=1 </para> </listitem> </varlistentry> + <varlistentry id="keep-configuration"> + <term><varname>keep-configuration</varname></term> + <listitem> + <para> + 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. + </para> + <para> + 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. + </para> + <para> + It is possible to disable this behavior by setting + <literal>keep-configuration</literal> to + <literal>no</literal>. 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). + </para> + <para> + Note that when NetworkManager gets restarted, it stores + the previous state in + <filename>/run/NetworkManager</filename>; in particular + it saves the UUID of the connection that was previously + active so that it can be activated again after the + restart. Therefore, + <literal>keep-configuration</literal> does not have + any effect on service restart. + </para> + </listitem> + </varlistentry> <varlistentry> <term><varname>wifi.scan-rand-mac-address</varname></term> <listitem> |