mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2025-12-29 16:10:11 +01:00
If IPv4 configuration did not succeed or the device has no IPv4 addresses when NM restarts, it will detect the existing device configuration as 'disabled'. This can happen when a bridge has no slaves and thus cannot perform IPv4 addressing because it has no carrier (since bridge carrier status depends on slave carriers). When NM starts or restarts, it sees the bridge has no IPv4 address and assumes the IPv4 method is 'disabled'. This creates a new connection, which blocks any slave connections from activating if they specify their master via UUID (since the bridge's active connection is generated). Fix this by allowing matches from 'disabled' to 'auto' if the device has no carrier, and there are no other differences between the original and the candidate connections. |
||
|---|---|---|
| .. | ||
| Makefile.am | ||
| test-dcb.c | ||
| test-dhcp-options.c | ||
| test-general.c | ||
| test-ip4-config.c | ||
| test-ip6-config.c | ||
| test-policy-hosts.c | ||
| test-resolvconf-capture.c | ||
| test-secret-agent.py | ||
| test-wifi-ap-utils.c | ||