From 6681f77b757bbc42ce5c8868ee9142b7ebc8c059 Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Tue, 13 Feb 2024 22:23:40 +0100
Subject: New upstream version 1.45.91

---
 docs/api/html/settings-connection.html | 6 ++++++
 1 file changed, 6 insertions(+)

(limited to 'docs/api/html/settings-connection.html')

diff --git a/docs/api/html/settings-connection.html b/docs/api/html/settings-connection.html
index d451fb79..f450a596 100644
--- a/docs/api/html/settings-connection.html
+++ b/docs/api/html/settings-connection.html
@@ -76,6 +76,12 @@ If multiple profiles are ready to autoconnect on the same device, the one with t
 Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.</td>
 </tr>
 <tr>
+<td><pre class="screen">autoconnect-ports</pre></td>
+<td><pre class="screen">NMTernary (int32)</pre></td>
+<td><pre class="screen"></pre></td>
+<td>Whether or not ports of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for controller connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave port connections untouched, 1: activate all the port connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-ports is read to determine the real value. If it is default as well, this fallbacks to 0.</td>
+</tr>
+<tr>
 <td><pre class="screen">autoconnect-priority</pre></td>
 <td><pre class="screen">int32</pre></td>
 <td><pre class="screen">0</pre></td>
-- 
cgit 1.3.0-6-gf8a5