From a39f7050ccd4375800e5b88f827fc06a9051e046 Mon Sep 17 00:00:00 2001 From: Thomas Haller Date: Fri, 9 Jul 2021 16:41:10 +0200 Subject: [PATCH] man/cli: mention `nmcli device up|down` instead of `nmcli device connect|disconnect` --- man/nmcli.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/man/nmcli.xml b/man/nmcli.xml index b014e86b86..c2b867ddb8 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. - In most cases you may want to use device disconnect + In most cases you may want to use device down command instead. The connection is identified by its name, UUID or D-Bus path. If @@ -1405,7 +1405,7 @@ If no compatible connection exists, a new profile with default settings will be created and activated. This differentiates nmcli connection up ifname "$DEVICE" from - nmcli device connect "$DEVICE" + nmcli device up "$DEVICE" If option is not specified, the default timeout will be 90 seconds. @@ -1672,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 connection down or device - disconnect to stop the hotspot. + down to stop the hotspot. Parameters of the hotspot can be influenced by the optional parameters: @@ -2356,7 +2356,7 @@ - nmcli dev disconnect em2 + nmcli dev down em2 disconnects a connection on interface em2 and marks the device as unavailable for auto-connecting. As a result, no connection will automatically