mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2025-12-26 08:50:07 +01:00
The matching works fuzzy and is not reliable. That is why we store
which connection should be assumed after restart in the state file
of NetworkManager.
In that case, we don't need to do a full check (with the possibility
of a false-reject). Just check for the minimum required properties:
the type and slave-type.
Yes, if the user modifies the connection while restarting NM, then
we might wrongly assume a connection that no longer would match.
But NM should not read minds, it should do as indicated.
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| config | ||
| test-dcb.c | ||
| test-general-with-expect.c | ||
| test-general.c | ||
| test-ip4-config.c | ||
| test-ip6-config.c | ||
| test-resolvconf-capture.c | ||
| test-secret-agent.py | ||
| test-systemd.c | ||
| test-utils.c | ||
| test-wired-defname.c | ||