658aef0fa1
We have encountered multiple incidents where users face connectivity issues after booting, particularly due to hardware like switches that do not pass traffic for a few seconds after startup. And services such as NFS fail to mount because they try to initiate before the network is fully reachable. Therefore, we are supporting `connection.ip-ping-addresses` and `connection.ip-ping-timeout` to allow administrators to configure the network to verify connectivity to a specific target(such as a service like NFS) instead of relying on gateway reachability, which may not always be relevant in certain network configurations. Resolves: https://issues.redhat.com/browse/RHEL-21160 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2034 https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/1797 |
||
|---|---|---|
| .. | ||
| meson.build | ||
| nm-core-internal.h | ||
| nm-keyfile-internal.h | ||
| nm-keyfile-utils.h | ||
| nm-meta-setting-base-impl.h | ||
| nm-meta-setting-base.h | ||
| README.md | ||
libnm-core-intern
This contains header files only, which are also part of
the internal API of libnm-core-impl.
libnm-core-impl is a static library that (among others) implements
libnm-core-public (which is a part of the public API of libnm).
This library gets statically linked into libnm and NetworkManager.
Hence, those components can also access internal (but not private) API of
libnm-core-impl, and this API is in libnm-core-intern.
These headers can thus be included by anybody who statically links with
libnm-core-impl (including libnm-core-impl itself).
The directory should not be added to the include search path, instead
users should explicitly #include "libnm-core-intern/nm-core-internal.h")
There is no source code here and no static library to link against.