New upstream version 1.16.0 upstream/1.16.0

1 files changed, 85 insertions, 12 deletions

diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html
index 4fbf45e6..0069f1e4 100644
--- a/docs/api/html/NetworkManager.conf.html
+++ b/docs/api/html/NetworkManager.conf.html
@@ -146,7 +146,8 @@ plugins-=remove-me
 </tr>
 <tr>
 <td><p><span class="term"><code class="varname">monitor-connection-files</code></span></p></td>
-<td><p>Whether the configured settings plugin(s)
+<td>
+<p>Whether the configured settings plugin(s)
         should set up file monitors and immediately pick up changes
         made to connection files while NetworkManager is running. This
         is disabled by default; NetworkManager will only read
@@ -159,7 +160,19 @@ plugins-=remove-me
         In some situations, NetworkManager might first delete and add the
         connection anew, instead of updating the existing one. Also, NetworkManager
         might pick up incomplete settings while the user is still editing the files.
-        </p></td>
+        </p>
+<p>
+        Note that neither this setting nor restarting the NetworkManager daemon
+        is the advised way to reload connection profiles from disk. Instead, after
+        modifying the files reload them with <span class="command"><strong>nmcli connection reload</strong></span>
+        or <span class="command"><strong>nmcli connection load "$FILENAME"</strong></span>. Even better,
+        instead of modifying files directly, use NetworkManager tools like
+        <span class="command"><strong>nmcli</strong></span>, <span class="command"><strong>nmtui</strong></span> or the GUI.
+        </p>
+<p>
+        This setting is deprecated and will have no effect in the future.
+        </p>
+</td>
 </tr>
 <tr>
 <td><p><span class="term"><code class="varname">auth-polkit</code></span></p></td>
@@ -200,7 +213,7 @@ plugins-=remove-me
 <p>When the default wired connection is deleted or saved
         to a new persistent connection by a plugin, the device is
         added to a list in the file
-        <code class="filename">/run/NetworkManager/no-auto-default.state</code>
+        <code class="filename">/var/lib/NetworkManager/no-auto-default.state</code>
         to prevent creating the default connection for that device
         again.</p>
 <p>See <a class="xref" href="NetworkManager.conf.html#device-spec" title="Device List Format">the section called “Device List Format”</a> for the syntax how to
@@ -254,7 +267,7 @@ no-auto-default=*
             environments where network setup is more or less static or it is
             desirable to save process time but still handle some dynamic
             configurations.  When this option is <code class="literal">true</code>,
-            network configuration for WiFi, WWAN, Bluetooth, ADSL, and PPPoE
+            network configuration for Wi-Fi, WWAN, Bluetooth, ADSL, and PPPoE
             interfaces cannot be preserved due to their use of external
             services, and these devices will be deconfigured when NetworkManager
             quits even though other interface's configuration may be preserved.
@@ -297,8 +310,8 @@ no-auto-default=*
 <tr>
 <td><p><span class="term"><code class="varname">dns</code></span></p></td>
 <td>
-<p>Set the DNS (<code class="filename">resolv.conf</code>) processing mode.
-        If the key is unspecified, <code class="literal">default</code> is used,
+<p>Set the DNS processing mode.</p>
+<p>If the key is unspecified, <code class="literal">default</code> is used,
         unless <code class="filename">/etc/resolv.conf</code> is a symlink to
         <code class="filename">/run/systemd/resolve/stub-resolv.conf</code>,
         <code class="filename">/run/systemd/resolve/resolv.conf</code>,
@@ -322,15 +335,22 @@ no-auto-default=*
         after some time. This behavior can be modified passing the
         'all-servers' or 'strict-order' options to dnsmasq (see the
         manual page for more details).</p>
+<p><code class="literal">systemd-resolved</code>: NetworkManager will
+        push the DNS configuration to systemd-resolved</p>
 <p><code class="literal">unbound</code>: NetworkManager will talk
         to unbound and dnssec-triggerd, providing a "split DNS"
         configuration with DNSSEC support. <code class="filename">/etc/resolv.conf</code>
         will be managed by dnssec-trigger daemon.</p>
-<p><code class="literal">systemd-resolved</code>: NetworkManager will
-        push the DNS configuration to systemd-resolved</p>
 <p><code class="literal">none</code>: NetworkManager will not
         modify resolv.conf. This implies
         <code class="literal">rc-manager</code> <code class="literal">unmanaged</code></p>
+<p>Note that the plugins <code class="literal">dnsmasq</code>, <code class="literal">systemd-resolved</code>
+        and <code class="literal">unbound</code> are caching local nameservers.
+        Hence, when NetworkManager writes <code class="filename">/var/run/NetworkManager/resolv.conf</code>
+        and <code class="filename">/etc/resolv.conf</code> (according to <code class="literal">rc-manager</code>
+        setting below), the name server there will be localhost only.
+        NetworkManager also writes a file <code class="filename">/var/run/NetworkManager/no-stub-resolv.conf</code>
+        that contains the original name servers pushed to the DNS plugin.</p>
 </td>
 </tr>
 <tr>
@@ -370,6 +390,22 @@ no-auto-default=*
 </td>
 </tr>
 <tr>
+<td><p><span class="term"><code class="varname">systemd-resolved</code></span></p></td>
+<td>
+<p>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
+        hostname per-device.</p>
+</td>
+</tr>
+<tr>
 <td><p><span class="term"><code class="varname">debug</code></span></p></td>
 <td>
 <p>Comma separated list of options to aid
@@ -595,6 +631,8 @@ ipv6.ip6-privacy=0
       (see <a class="link" href="nm-settings.html" title="nm-settings"><span class="citerefentry"><span class="refentrytitle">nm-settings</span>(5)</span></a> for details).
       A default value is only consulted if the corresponding per-connection value
       explicitly allows for that.
+      
+      
       </p>
 <div class="variablelist"><table border="0" class="variablelist">
 <colgroup>
@@ -677,6 +715,11 @@ ipv6.ip6-privacy=0
            the interface type is used.</p></td>
 </tr>
 <tr>
+<td><p><span class="term"><code class="varname">ipv4.dns-priority</code></span></p></td>
+<td><p>If unspecified or zero, use 50 for VPN profiles
+           and 100 for other profiles.</p></td>
+</tr>
+<tr>
 <td><p><span class="term"><code class="varname">ipv4.route-metric</code></span></p></td>
 <td></td>
 </tr>
@@ -697,6 +740,11 @@ ipv6.ip6-privacy=0
            the interface type is used.</p></td>
 </tr>
 <tr>
+<td><p><span class="term"><code class="varname">ipv6.dns-priority</code></span></p></td>
+<td><p>If unspecified or zero, use 50 for VPN profiles
+           and 100 for other profiles.</p></td>
+</tr>
+<tr>
 <td><p><span class="term"><code class="varname">ipv6.ip6-privacy</code></span></p></td>
 <td><p>If <code class="literal">ipv6.ip6-privacy</code> is unset, use the content of
             "/proc/sys/net/ipv6/conf/default/use_tempaddr" as last fallback.
@@ -758,9 +806,15 @@ ipv6.ip6-privacy=0
 <td><p><span class="term"><code class="varname">wifi.wake-on-wlan</code></span></p></td>
 <td></td>
 </tr>
+<tr>
+<td><p><span class="term"><code class="varname">wireguard.mtu</code></span></p></td>
+<td></td>
+</tr>
 </tbody>
 </table></div>
 <p>
+      
+      
     </p>
 </div>
 <hr>
@@ -997,6 +1051,20 @@ managed=1
     checking functionality.  This allows NetworkManager to detect
     whether or not the system can actually access the internet or
     whether it is behind a captive portal.</p>
+<p>Connectivity checking serves two purposes. For one, it exposes
+    a connectivity state on D-Bus, which other applications may use. For example,
+    Gnome's portal helper uses this as signal to show a captive portal login
+    page.
+    The other use is that default-route of devices without global connectivity
+    get a penalty of +20000 to the route-metric. This has the purpose to give a
+    better default-route to devices that have global connectivity. For example,
+    when being connected to WWAN and to a Wi-Fi network which is behind a captive
+    portal, WWAN still gets preferred until login.</p>
+<p>Note that your distribution might set <code class="literal">/proc/sys/net/ipv4/conf/*/rp_filter</code> to
+    strict filtering. That works badly with per-device connectivity checking,
+    which uses SO_BINDDEVICE to send requests on all devices. A strict rp_filter
+    setting will reject any response and the connectivity check on all but the
+    best route will fail.</p>
 <p>
       </p>
 <div class="variablelist"><table border="0" class="variablelist">
@@ -1026,10 +1094,15 @@ managed=1
 </tr>
 <tr>
 <td><p><span class="term"><code class="varname">response</code></span></p></td>
-<td><p>If set controls what body content
+<td><p>If set, controls what body content
           NetworkManager checks for when requesting the URI for
-          connectivity checking.  If missing, defaults to
-          "NetworkManager is online" </p></td>
+          connectivity checking.  Note that this only compares
+          that the HTTP response starts with the specifid text,
+          it does not compare the exact string. This behavior
+          might change in the future, so avoid relying on it.
+          If missing, the response defaults to "NetworkManager is online".
+          If set to empty, the HTTP server is expected to answer with
+          status code 204 or send no data.</p></td>
 </tr>
 </tbody>
 </table></div>
@@ -1058,7 +1131,7 @@ managed=1
 <tr>
 <td><p><span class="term"><code class="varname">options</code></span></p></td>
 <td><p>
-             A list of of options to be passed to the hostname resolver.
+             A list of options to be passed to the hostname resolver.
            </p></td>
 </tr>
 </tbody>