diff options
| author | Andrew Zaborowski <andrew.zaborowski@intel.com> | 2020-10-30 13:27:41 +0100 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2020-11-19 10:12:04 +0100 |
| commit | dc0e31fb7014d8a97aca96bf97a8f86f8236300c (patch) | |
| tree | 92f54b86ec14ad0ca844d2ec439935a5baef7910 /man | |
| parent | 43fd93d8f485d710215717bce8928520e3744f7a (diff) | |
iwd: Add the wifi.iwd.autoconnect setting
If this setting it true (or missing) we skip most of the D-Bus
Disconnect() calls whoe purpose was to keep IWD's internal autoconnect
mechanism always disabled. We use the IWD's Station.State property
updates, and secrets requets through our IWD agent, to find out when IWD
is trying to connect and create "assumed" activations on the NM side to
mirror the IWD state. This is quite complicated due to the many
possible combinations of NMDevice's state and IWD's state. A lot of
them are "impossible" but we try to be careful to consider all the
different possibilities.
NM has a nice API for "assuming connections" but it's designed for
slightly different use cases than what we have here and for now we
created normal "managed"-type activations when assuming an IWD automatic
connection.
Diffstat (limited to 'man')
| -rw-r--r-- | man/NetworkManager.conf.xml | 19 |
1 files changed, 18 insertions, 1 deletions
diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index a235cf2553..1af436bbab 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -1090,8 +1090,25 @@ managed=1 </para> </listitem> </varlistentry> + <varlistentry> + <term><varname>wifi.iwd.autoconnect</varname></term> + <listitem> + <para> + If <literal>wifi.backend</literal> is <literal>iwd</literal>, setting this to + <literal>false</literal> 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 <literal>true</literal> (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' <literal>autoconnect-priority</literal>, + <literal>autoconnect-retries</literal> settings will be ignored. Other settings + like <literal>permissions</literal> or <literal>multi-connect</literal> may interfere + with IWD connection attempts. + </para> + </listitem> + </varlistentry> <varlistentry id="sriov-num-vfs"> - , <term><varname>sriov-num-vfs</varname></term> + <term><varname>sriov-num-vfs</varname></term> <listitem> <para> Specify the number of virtual functions (VF) to enable |