mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2025-12-26 03:00:13 +01:00
4201ee5119
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 |
||
|---|---|---|
| .. | ||
| tests | ||
| 90-nm-cloud-setup.sh | ||
| main.c | ||
| meson.build | ||
| nm-cloud-setup-utils.c | ||
| nm-cloud-setup-utils.h | ||
| nm-cloud-setup.service.in | ||
| nm-cloud-setup.timer | ||
| nm-http-client.c | ||
| nm-http-client.h | ||
| nmcs-provider-azure.c | ||
| nmcs-provider-azure.h | ||
| nmcs-provider-ec2.c | ||
| nmcs-provider-ec2.h | ||
| nmcs-provider-gcp.c | ||
| nmcs-provider-gcp.h | ||
| nmcs-provider.c | ||
| nmcs-provider.h | ||