mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-03-04 06:00:33 +01:00
2e4b73c7fe
nm-cloud-setup automatically configures the network. That may conflict with what the user wants. In case the user configures some specific setup, they are encouraged to disable nm-cloud-setup (and its automatism). Still, what we do by default matters, and should play as well with user's expectations. Configuring policy routing and a higher priority table (30400+) that hijacks the traffic can cause problems. If the system only has one IPv4 address and one interface, then there is no point in configuring policy routing at all. Detect that, and skip the change in that case. Note that of course we need to handle the case where previously multiple IP addresses were configured and an update gives only one address. In that case we need to clear the previously configured rules/routes. The patch achieves this. (cherry picked from commit |
||
|---|---|---|
| .. | ||
| 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 | ||