New upstream version 1.29.90 upstream/1.29.90

1 files changed, 63 insertions, 14 deletions

diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html
index 6c8f1f8e..05250d17 100644
--- a/docs/api/html/NetworkManager.conf.html
+++ b/docs/api/html/NetworkManager.conf.html
@@ -268,18 +268,24 @@ no-auto-default=*
             this option. An hostname empty or equal to 'localhost', 'localhost6',
             'localhost.localdomain' or 'localhost6.localdomain' is considered invalid.
           </p>
-<p><code class="literal">default</code>: NetworkManager will update the hostname
-          with the one provided via DHCP on the main connection (the one with a default
-          route). If not present, the hostname will be updated to the last one set
-          outside NetworkManager. If it is not valid, NetworkManager will try to recover
-          the hostname from the reverse lookup of the IP address of the main connection.
-          If this fails too, the hostname will be set to 'localhost.localdomain'.
+<p><code class="literal">default</code>: 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
+          '<code class="literal">false</code>'. Connections are considered in order of
+          increasing value of the <code class="literal">hostname.priority</code>
+          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 'localhost.localdomain'.
           </p>
-<p><code class="literal">dhcp</code>: NetworkManager will update the transient hostname
-          only with information coming from DHCP. No fallback nor reverse lookup will be
-          performed, but when the dhcp connection providing the hostname is deactivated,
-          the hostname is reset to the last hostname set outside NetworkManager or
-          'localhost' if none valid is there.
+<p><code class="literal">dhcp</code>: this is similar to
+          '<code class="literal">default</code>', 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
+          '<code class="literal">hostname.from-dns-lookup</code>' to
+          '<code class="literal">false</code>' globally for all connections in
+          NetworkManager.conf.
           </p>
 <p><code class="literal">none</code>: NetworkManager will not manage the transient
           hostname and will never set it.
@@ -617,6 +623,18 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth
 <p>Specify default values for connections.
     </p>
 <p>
+      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 <code class="literal">connection.mud-url</code>).
+      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 <code class="literal">NetworkManager.conf</code>.
+    </p>
+<p>
       Example:
 </p>
 <pre class="programlisting">
@@ -626,13 +644,13 @@ ipv6.ip6-privacy=0
 <p>
     </p>
 <div class="refsect2">
-<a name="id-1.2.3.11.4"></a><h3>Supported Properties</h3>
+<a name="id-1.2.3.11.5"></a><h3>Supported Properties</h3>
 <p>
       Not all properties can be overwritten, only the following
       properties are supported to have their default values configured
       (see <span class="citerefentry"><span class="refentrytitle">nm-settings</span>(5)</span> for details).
-      A default value is only consulted if the corresponding per-connection value
-      explicitly allows for that.
+    </p>
+<p>
       
       
       </p>
@@ -700,6 +718,22 @@ ipv6.ip6-privacy=0
 <td></td>
 </tr>
 <tr>
+<td><p><span class="term"><code class="varname">hostname.from-dhcp</code></span></p></td>
+<td></td>
+</tr>
+<tr>
+<td><p><span class="term"><code class="varname">hostname.from-dns-lookup</code></span></p></td>
+<td></td>
+</tr>
+<tr>
+<td><p><span class="term"><code class="varname">hostname.only-from-default</code></span></p></td>
+<td></td>
+</tr>
+<tr>
+<td><p><span class="term"><code class="varname">hostname.priority</code></span></p></td>
+<td></td>
+</tr>
+<tr>
 <td><p><span class="term"><code class="varname">infiniband.mtu</code></span></p></td>
 <td><p>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.</p></td>
 </tr>
@@ -1053,6 +1087,21 @@ managed=1
             </p></td>
 </tr>
 <tr>
+<td><p><span class="term"><code class="varname">wifi.iwd.autoconnect</code></span></p></td>
+<td><p>
+              If <code class="literal">wifi.backend</code> is <code class="literal">iwd</code>, setting this to
+              <code class="literal">false</code> 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 <code class="literal">true</code> (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' <code class="literal">autoconnect-priority</code>,
+              <code class="literal">autoconnect-retries</code> settings will be ignored.  Other settings
+              like <code class="literal">permissions</code> or <code class="literal">multi-connect</code> may interfere
+              with IWD connection attempts.
+            </p></td>
+</tr>
+<tr>
 <td><p><a name="sriov-num-vfs"></a><span class="term"><code class="varname">sriov-num-vfs</code></span></p></td>
 <td><p>
               Specify the number of virtual functions (VF) to enable