mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-06-03 12:38:24 +02:00
17f9801e07
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. |
||
|---|---|---|
| .. | ||
| common.ent.in | ||
| meson.build | ||
| NetworkManager.conf.xml | ||
| NetworkManager.xml | ||
| nm-initrd-generator.xml | ||
| nm-online.xml | ||
| nm-openvswitch.xml | ||
| nm-settings-ifcfg-rh.xsl | ||
| nm-settings-keyfile.xsl | ||
| nm-settings.xsl | ||
| nmcli-examples.xml | ||
| nmcli.xml | ||
| nmtui.1.in | ||
| nmtui.xml | ||