From 05e4a733f2141995181a551854d5df929f084adf Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Wed, 9 Aug 2023 21:55:35 +0200
Subject: New upstream version 1.44.0

---
 docs/api/html/NetworkManager.conf.html | 45 +++++++++++++++++++++++++---------
 1 file changed, 33 insertions(+), 12 deletions(-)

(limited to 'docs/api/html/NetworkManager.conf.html')

diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html
index b4134352..abd47cea 100644
--- a/docs/api/html/NetworkManager.conf.html
+++ b/docs/api/html/NetworkManager.conf.html
@@ -344,7 +344,7 @@ no-auto-default=*
         setting below), the name server there will be localhost only.
         NetworkManager also writes a file <code class="filename">/run/NetworkManager/no-stub-resolv.conf</code>
         that contains the original name servers pushed to the DNS plugin.</p>
-<p>When using <code class="literal">dnsmasq</code> and <code class="literal">systemd-resolved</code>
+<p>When using <code class="literal">dnsmasq</code> and <code class="literal">systemd-resolved</code>,
         per-connection added dns servers will always be queried using
         the device the connection has been activated on.</p>
 </td>
@@ -407,16 +407,15 @@ no-auto-default=*
 <tr>
 <td><p><span class="term"><code class="varname">systemd-resolved</code></span></p></td>
 <td>
-<p>Send the connection DNS configuration to
+<p>Additionally, send the connection DNS configuration to
         <code class="literal">systemd-resolved</code>. Defaults to "<code class="literal">true</code>".
         </p>
-<p>Note that this setting is complementary to the
-        <code class="varname">dns</code> setting. You can keep this enabled while using
-        <code class="varname">dns</code> set to another DNS plugin alongside
-        <code class="literal">systemd-resolved</code>, or <code class="varname">dns</code> set to
-        <code class="literal">systemd-resolved</code> to configure the system resolver to use
-        <code class="literal">systemd-resolved</code>.</p>
-<p>If systemd-resolved is enabled, the connectivity check resolves the
+<p>Note that this setting has no effect if the main <code class="varname">dns</code>
+        plugin is already <code class="literal">systemd-resolved</code>. It is complementary to the
+        <code class="varname">dns</code> setting to configure systemd-resolved alongside the
+        main plugin.</p>
+<p>If systemd-resolved is enabled, either via this setting or the main
+        DNS plugin, the connectivity check resolves the
         hostname per-device.</p>
 </td>
 </tr>
@@ -504,6 +503,15 @@ no-auto-default=*
           </p>
 </td>
 </tr>
+<tr>
+<td><p><span class="term"><code class="varname">migrate-ifcfg-rh</code></span></p></td>
+<td><p>Whether NetworkManager tries to automatically convert
+        any connection profile stored in ifcfg-rh format to the keyfile format.
+        Support for ifcfg-rh is deprecated and will be eventually removed. If
+        enabled, the migration is performed at every startup of the daemon.
+        The default value is <code class="literal">false</code>.
+        </p></td>
+</tr>
 </tbody>
 </table></div>
 </div>
@@ -535,6 +543,19 @@ no-auto-default=*
             </p></td>
 </tr>
 <tr>
+<td><p><span class="term"><code class="varname">rename</code></span></p></td>
+<td><p>
+                NetworkManager automatically chooses a filename when storing
+                a new profile to disk. That name depends on the profile's name
+                (connection.id). When updating a profile's name, the file is
+                not renamed to not break scripts that rely on the filename
+                for the profile.
+                By setting this option to "true", NetworkManager renames
+                the keyfile on update of the profile, to follow the profile's
+                name. This defaults to "false".
+            </p></td>
+</tr>
+<tr>
 <td><p><span class="term"><code class="varname">unmanaged-devices</code></span></p></td>
 <td>
 <p>Set devices that should be ignored by NetworkManager.
@@ -1647,9 +1668,9 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16
 <tr>
 <td><p><span class="term"><code class="varname">ifcfg-rh</code></span></p></td>
 <td><p>
-            This plugin is used on the Fedora and Red Hat Enterprise
-            Linux distributions to read and write configuration from
-            the standard
+            This plugin is now deprecated; it can be used on the
+            Fedora and Red Hat Enterprise Linux distributions to read
+            and write configuration from the standard
             <code class="filename">/etc/sysconfig/network-scripts/ifcfg-*</code>
             files. It currently supports reading Ethernet, Wi-Fi,
             InfiniBand, VLAN, Bond, Bridge, and Team connections.
-- 
cgit 1.3.0-6-gf8a5