summaryrefslogtreecommitdiff
path: root/libnm
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2019-07-09 12:46:53 +0200
committerThomas Haller <thaller@redhat.com>2019-07-25 15:26:49 +0200
commit0aa323fb2887fc4b5decfb5360d7384bf774e6db (patch)
treedfb6902a740fdbc657d0b42ed8a6b745f3e005ce /libnm
parentdcdbe984065ed06753a0ce542c1aaaa9336d8424 (diff)
downloadNetworkManager-0aa323fb2887fc4b5decfb5360d7384bf774e6db.tar.gz
settings: add NM_SETTINGS_UPDATE2_FLAG_NO_REAPPLY to prevent runtime changes when updating connection profile
When modifying a connection profile that happens to be active on a device, then most of the changes don't take effect immediately. Only after a full re-activation or reapply (nmcli device reapply) does the configuration of the active device change (the "applied-connection"). With two execptions: "connection.zone" and "connection.metered" take effect immediately. I think this is historic, but also to facilitate firewall-cmd to modify a profile and change the zone right away. Anyway, I think it should be possible to modify a profile without changes to the runtime. Add a flag to prevent reapplying these properties right away. https://bugzilla.redhat.com/show_bug.cgi?id=1677070
Diffstat (limited to 'libnm')
0 files changed, 0 insertions, 0 deletions