diff options
author | Thomas Haller <thaller@redhat.com> | 2018-11-13 12:30:27 +0100 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2018-11-13 13:48:10 +0100 |
commit | 17f9801e07df0c544e0416c65cedc28727476e55 (patch) | |
tree | c06b854090c8b522650f20029d98220c5e43c3d6 /man | |
parent | 37e47fbdabd6439c022a5fc3b72176aa6c4e569f (diff) |
man: clarify blocking autoconnect during `nmcli connection down`
Manually disconnecting a profile of course blocks autoconnect of the
same profile. Otherwise, the profile would likely re-activate right
away, which is clearly against the users intention. If the users just
want to re-activate the profile, they should issue `nmcli connection up`
instead, with does a full down and up cycle.
This is more interesting for profiles that have 'connection.multi-connect'
set to 'multiple'. Would you expect that manually deactivating such a
profile blocks autoconnect of the profile on all devices? Maybe
yes, maybe not. Currently that is indeed the case and autoconnect gets
blocked regardless of multi-connect.
Diffstat (limited to 'man')
-rw-r--r-- | man/nmcli.xml | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/man/nmcli.xml b/man/nmcli.xml index b98651a799..68dc2298b0 100644 --- a/man/nmcli.xml +++ b/man/nmcli.xml @@ -831,9 +831,10 @@ <para>Be aware that this command deactivates the specified active connection, but the device on which the connection was active, is still ready to connect and will perform auto-activation by looking for a suitable connection that has - the 'autoconnect' flag set. This includes the just deactivated connection. So - if the connection is set to auto-connect, it will be automatically started on - the disconnected device again.</para> + the 'autoconnect' flag set. Note that the deactivating connection profile is + internally blocked from autoconnecting again. Hence it will not autoconnect + until reboot or until the user performs an action that unblocks autoconnect, + like modifying the profile or explcitly activating it.</para> <para>In most cases you may want to use <command>device disconnect</command> command instead.</para> |