Thomas Haller 2b96e9314c cloud-setup: preserve IPv4 addresses/routes/rules from profile ... nm-cloud-setup automatically detects routes, addresses and rules and configures them on the device using the emphermal Reapply() API. That is, it does not modify the existing profile (on disk), but changes the runtime configuration only. As such, it used to wipe otherwise statically configured IP addresses, routes and rules. That seems unnecessary. Let's keep the configuration from the (persistent) configuration. There is of course the problem that nm-cloud-setup doesn't really understand the existing IP configuration, and it can only hope that it can be meaningfully combined with what nm-cloud-setup wants to configure. This should cover most simple cases, for more complex setups, the user probably should disable nm-cloud-setup and configure the network explicitly to their liking. https://bugzilla.redhat.com/show_bug.cgi?id=1971527 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/893 (cherry picked from commit 4201ee5119) (cherry picked from commit 9541b0bea4)		2021-10-05 09:35:48 +02:00
..
cli	all: add a new ipv{4,6}.required-timeout property	2021-09-06 10:56:12 +02:00
cloud-setup	cloud-setup: preserve IPv4 addresses/routes/rules from profile	2021-10-05 09:35:48 +02:00
common	all: add a new ipv{4,6}.required-timeout property	2021-09-06 10:56:12 +02:00
tests	all: add a new ipv{4,6}.required-timeout property	2021-09-06 10:56:12 +02:00
tui	libnmt-newt: fix leak in nmt_newt_button_build_component()	2021-06-04 21:21:52 +02:00
meson.build	all: add "libnm/nm-default-client.h" as replacement for "nm-default.h"	2021-02-09 12:38:17 +01:00
nm-online.c	all: add "libnm/nm-default-client.h" as replacement for "nm-default.h"	2021-02-09 12:38:17 +01:00