New upstream version 1.34.0 upstream/1.34.0

1 files changed, 41 insertions, 8 deletions

diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html
index 2fab4fd2..f9307059 100644
--- a/docs/api/html/nm-settings-dbus.html
+++ b/docs/api/html/nm-settings-dbus.html
@@ -122,14 +122,14 @@
 <a name="nm-settings-dbus.property.connection.autoconnect"></a>autoconnect</td>
 <td align="left">boolean</td>
 <td align="left">TRUE</td>
-<td>Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.</td>
+<td>Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.</td>
 </tr>
 <tr>
 <td align="left">
 <a name="nm-settings-dbus.property.connection.autoconnect-priority"></a>autoconnect-priority</td>
 <td align="left">int32</td>
 <td align="left">0</td>
-<td>The autoconnect priority. If the connection is set to autoconnect, connections with higher priority will be preferred. Defaults to 0. The higher number means higher priority.</td>
+<td>The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.</td>
 </tr>
 <tr>
 <td align="left">
@@ -147,6 +147,13 @@
 </tr>
 <tr>
 <td align="left">
+<a name="nm-settings-dbus.property.connection.dns-over-tls"></a>dns-over-tls</td>
+<td align="left">int32</td>
+<td align="left">-1</td>
+<td>Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</td>
+</tr>
+<tr>
+<td align="left">
 <a name="nm-settings-dbus.property.connection.gateway-ping-timeout"></a>gateway-ping-timeout</td>
 <td align="left">uint32</td>
 <td align="left">0</td>
@@ -1155,8 +1162,8 @@
 <td align="left">
 <a name="nm-settings-dbus.property.dcb.app-fcoe-mode"></a>app-fcoe-mode</td>
 <td align="left">string</td>
-<td align="left">"fabric"</td>
-<td>The FCoE controller mode; either "fabric" (default) or "vn2vn".</td>
+<td align="left"> </td>
+<td>The FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".</td>
 </tr>
 <tr>
 <td align="left">
@@ -3600,7 +3607,7 @@
 <a name="nm-settings-dbus.property.802-3-ethernet.s390-options"></a>s390-options</td>
 <td align="left">dict of string to string</td>
 <td align="left">{}</td>
-<td>Dictionary of key/value pairs of s390-specific device options.  Both keys and values must be strings.  Allowed keys include "portno", "layer2", "portname", "protocol", among others.  Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).</td>
+<td>Dictionary of key/value pairs of s390-specific device options.  Both keys and values must be strings.  Allowed keys include "portno", "layer2", "portname", "protocol", among others.  Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]). Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.</td>
 </tr>
 <tr>
 <td align="left">
@@ -4097,7 +4104,33 @@
 </div>
 <hr>
 <div class="refsect2">
-<a name="id-1.2.8.4.51"></a><h3>hostname setting</h3>
+<a name="id-1.2.8.4.51"></a><h3>bond-port setting</h3>
+<p>Bond Port Settings.</p>
+<div class="informaltable"><table class="informaltable" border="1">
+<colgroup>
+<col>
+<col>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>Key Name</th>
+<th>Value Type</th>
+<th>Default Value</th>
+<th>Value Description</th>
+</tr></thead>
+<tbody><tr>
+<td align="left">
+<a name="nm-settings-dbus.property.bond-port.queue-id"></a>queue-id</td>
+<td align="left">uint32</td>
+<td align="left">0</td>
+<td>The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.</td>
+</tr></tbody>
+</table></div>
+</div>
+<hr>
+<div class="refsect2">
+<a name="id-1.2.8.4.52"></a><h3>hostname setting</h3>
 <p>Hostname settings.</p>
 <div class="informaltable"><table class="informaltable" border="1">
 <colgroup>
@@ -4146,7 +4179,7 @@
 </div>
 <hr>
 <div class="refsect2">
-<a name="id-1.2.8.4.52"></a><h3>ovs-external-ids setting</h3>
+<a name="id-1.2.8.4.53"></a><h3>ovs-external-ids setting</h3>
 <p>OVS External IDs Settings.</p>
 <div class="informaltable"><table class="informaltable" border="1">
 <colgroup>
@@ -4172,7 +4205,7 @@
 </div>
 <hr>
 <div class="refsect2">
-<a name="id-1.2.8.4.53"></a><h3>veth setting</h3>
+<a name="id-1.2.8.4.54"></a><h3>veth setting</h3>
 <p>Veth Settings.</p>
 <div class="informaltable"><table class="informaltable" border="1">
 <colgroup>