fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2026-01-04 20:20:17 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

man: clarify blocking autoconnect during nmcli connection down

Browse source 
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.
This commit is contained in:
Thomas Haller 2018-11-13 12:30:27 +01:00
parent 37e47fbdab
commit 17f9801e07
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
man/nmcli.xml
View file

@ -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>