mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2025-12-27 05:50:08 +01:00
NML3Cfg already handles IPv4 ACD. IPv4LL is just a small additional layer on top of that, so it makes sense that it also is handled by NML3Cfg. Also, the overall goal is that multiple NMDevice and NMVpnConnection instances can cooperate independently. So if multiple "users" enable IPv4LL on an interface, then we should only run it once. This is achieved by NML3IPv4LL's API where users register what they want, and NML3IPv4LL figures out what that means as a whole. Also, we thus will no longer need to use sd_ipv4ll/n-ipv4ll, because we implement it ourself. |
||
|---|---|---|
| .. | ||
| config | ||
| meson.build | ||
| test-core-with-expect.c | ||
| test-core.c | ||
| test-dcb.c | ||
| test-ip4-config.c | ||
| test-ip6-config.c | ||
| test-l3cfg.c | ||
| test-secret-agent.py | ||
| test-systemd.c | ||
| test-utils.c | ||
| test-wired-defname.c | ||