From bfe522304da217296e2a61040f58e35ec5d6f3f2 Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Mon, 16 Aug 2021 09:51:46 +0200
Subject: New upstream version 1.30.6

---
 man/nmcli.xml | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 61 insertions(+)

(limited to 'man/nmcli.xml')

diff --git a/man/nmcli.xml b/man/nmcli.xml
index b0665efd..bc72c311 100644
--- a/man/nmcli.xml
+++ b/man/nmcli.xml
@@ -356,6 +356,7 @@
         <arg choice='plain'><command>hostname</command></arg>
         <arg choice='plain'><command>permissions</command></arg>
         <arg choice='plain'><command>logging</command></arg>
+        <arg choice='plain'><command>reload</command></arg>
       </group>
       <arg rep='repeat'><replaceable>ARGUMENTS</replaceable></arg>
     </cmdsynopsis>
@@ -419,6 +420,66 @@
           for available level and domain values.</para>
         </listitem>
       </varlistentry>
+
+      <varlistentry>
+        <term>
+          <command>reload</command>
+          <arg rep='repeat'><replaceable>flags</replaceable></arg>
+        </term>
+
+        <listitem>
+          <para>
+            Reload NetworkManager's configuration and perform certain
+            updates, like flushing caches or rewriting external state to
+            disk. This is similar to sending SIGHUP to NetworkManager
+            but it allows for more fine-grained control over what to
+            reload through the flags argument. It also allows non-root
+            access via PolicyKit and contrary to signals it is
+            synchronous. Available flags are:
+          </para>
+          <variablelist>
+            <varlistentry>
+              <term><option>conf</option></term>
+              <listitem><para>
+                Reload the NetworkManager.conf configuration from
+                disk. Note that this does not include connections, which
+                can be reloaded through <command>nmcli connection
+                reload</command> instead.
+              </para></listitem>
+            </varlistentry>
+
+            <varlistentry>
+              <term><option>dns-rc</option></term>
+              <listitem><para>
+                Update DNS configuration, which usually involves writing
+                /etc/resolv.conf anew. This is equivalent to sending the
+                SIGUSR1 signal to the NetworkManager process.
+              </para></listitem>
+            </varlistentry>
+
+            <varlistentry>
+              <term><option>dns-full</option></term>
+              <listitem><para>
+                Restart the DNS plugin. This is for example useful when
+                using dnsmasq plugin, which uses additional
+                configuration in
+                <filename>/etc/NetworkManager/dnsmasq.d</filename>. If
+                you edit those files, you can restart the DNS
+                plugin. This action shortly interrupts name resolution.
+              </para></listitem>
+            </varlistentry>
+          </variablelist>
+          <para>
+            With no flags, everything that is supported is reloaded,
+            which is identical to sending a SIGHUP. See
+            <citerefentry>
+              <refentrytitle>NetworkManager</refentrytitle>
+              <manvolnum>8</manvolnum>
+            </citerefentry>
+            for more details about signals.
+          </para>
+        </listitem>
+      </varlistentry>
     </variablelist>
   </refsect1>
 
-- 
cgit 1.3.0-6-gf8a5


From 88c227d90a6b7b388c5c85d72802a0ca8f05ed5c Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Thu, 13 Jan 2022 22:30:39 +0100
Subject: New upstream version 1.34.0

---
 man/nmcli.xml | 39 ++++++++++++++++++++++++++++++++-------
 1 file changed, 32 insertions(+), 7 deletions(-)

(limited to 'man/nmcli.xml')

diff --git a/man/nmcli.xml b/man/nmcli.xml
index bc72c311..c2b867dd 100644
--- a/man/nmcli.xml
+++ b/man/nmcli.xml
@@ -902,7 +902,7 @@
           until reboot or until the user performs an action that unblocks autoconnect,
           like modifying the profile or explicitly activating it.</para>
 
-          <para>In most cases you may want to use <command>device disconnect</command>
+          <para>In most cases you may want to use <command>device down</command>
           command instead.</para>
 
           <para>The connection is identified by its name, UUID or D-Bus path. If
@@ -910,7 +910,7 @@
           <option>uuid</option>, <option>path</option> or
           <option>apath</option> can be used.</para>
 
-          <para> See <command>connection show</command> above for the description of
+          <para>See <command>connection show</command> above for the description of
           the <replaceable>ID</replaceable>-specifying keywords.</para>
 
           <para>If <option>--wait</option> option is not specified, the default timeout
@@ -1323,9 +1323,11 @@
         <arg choice='plain'><command>status</command></arg>
         <arg choice='plain'><command>show</command></arg>
         <arg choice='plain'><command>set</command></arg>
+        <arg choice='plain'><command>up</command></arg>
         <arg choice='plain'><command>connect</command></arg>
         <arg choice='plain'><command>reapply</command></arg>
         <arg choice='plain'><command>modify</command></arg>
+        <arg choice='plain'><command>down</command></arg>
         <arg choice='plain'><command>disconnect</command></arg>
         <arg choice='plain'><command>delete</command></arg>
         <arg choice='plain'><command>monitor</command></arg>
@@ -1391,7 +1393,7 @@
 
       <varlistentry>
         <term>
-          <command>connect</command>
+          <command>up</command>
           <arg choice='plain'><replaceable>ifname</replaceable></arg>
         </term>
 
@@ -1403,13 +1405,25 @@
           <para>If no compatible connection exists, a new profile with default
           settings will be created and activated. This differentiates
           <command>nmcli connection up ifname "$DEVICE"</command> from
-          <command>nmcli device connect "$DEVICE"</command></para>
+          <command>nmcli device up "$DEVICE"</command></para>
 
           <para>If <option>--wait</option> option is not specified, the default timeout will be 90
           seconds.</para>
         </listitem>
       </varlistentry>
 
+      <varlistentry>
+        <term>
+          <command>connect</command>
+          <arg choice='plain'><replaceable>ifname</replaceable></arg>
+        </term>
+
+        <listitem>
+          <para>Alias for command <command>up</command>. Before version 1.34.0 <command>up</command>
+                was not supported.</para>
+        </listitem>
+      </varlistentry>
+
       <varlistentry>
         <term>
           <command>reapply</command>
@@ -1448,7 +1462,7 @@
 
       <varlistentry>
         <term>
-          <command>disconnect</command>
+          <command>down</command>
           <arg choice='plain' rep='repeat'><replaceable>ifname</replaceable></arg>
         </term>
 
@@ -1462,6 +1476,17 @@
         </listitem>
       </varlistentry>
 
+      <varlistentry>
+        <term>
+          <command>disconnect</command>
+          <arg choice='plain' rep='repeat'><replaceable>ifname</replaceable></arg>
+        </term>
+
+        <listitem>
+          <para>Alias for command <command>down</command>. Before version 1.34.0 <command>down</command>
+                was not supported.</para>
+        </listitem>
+      </varlistentry>
 
       <varlistentry>
         <term>
@@ -1647,7 +1672,7 @@
           according to Wi-Fi device capabilities and activates it on the device. The
           hotspot is secured with WPA if device/driver supports that, otherwise WEP is
           used. Use <command>connection down</command> or <command>device
-          disconnect</command> to stop the hotspot.</para>
+          down</command> to stop the hotspot.</para>
 
           <para>Parameters of the hotspot can be influenced by the optional
           parameters:</para>
@@ -2331,7 +2356,7 @@
       </varlistentry>
 
       <varlistentry>
-        <term><userinput>nmcli dev disconnect em2</userinput></term>
+        <term><userinput>nmcli dev down em2</userinput></term>
         <listitem>
           <para>disconnects a connection on interface em2 and marks the device as
           unavailable for auto-connecting. As a result, no connection will automatically
-- 
cgit 1.3.0-6-gf8a5