Thomas Haller 5d112092bc cloud-setup/azure: fix detecting the gateway address ... The code never set "iface_get_config->cidr_addr", despite setting "cidr_prefix" and "has_cidr". As a result, cloud-setup would think that the subnet is "0.0.0.0/$PLEN", and calculate the gateway as "0.0.0.1". As a result it would add a default route to table 30400 via 0.0.0.1, which is obviously wrong. How to detect the right gateway? Let's try obtain the subnet also via the meta data. That seems mostly correct, except that we only access subnet at index 0. What if there are multiple ones? I don't know. https://bugzilla.redhat.com/show_bug.cgi?id=1912236 (cherry picked from commit c2629f72b0)		2021-10-14 13:02:00 -03:00
..
cli	all: add a new ipv{4,6}.required-timeout property	2021-09-06 10:56:12 +02:00
cloud-setup	cloud-setup/azure: fix detecting the gateway address	2021-10-14 13:02:00 -03: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