mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-02-05 10:00:32 +01:00
This new endpoint type has been recently added to the kernel in v6.18 [1]. It will be used to create new subflows from the associated address to additional addresses announced by the other peer. This will be done if allowed by the MPTCP limits, and if the associated address is not already being used by another subflow from the same MPTCP connection. Note that the fullmesh flag takes precedence over the laminar one. Without any of these two flags, the path-manager will create new subflows to additional addresses announced by the other peer by selecting the source address from the routing tables, which is harder to configure if the announced address is not known in advance. The support of the new flag is easy: simply by declaring a new flag for NM, and adding it in the related helpers and existing checks looking at the different MPTCP endpoint. The documentation now references the new endpoint type. Note that only the new 'define' has been added in the Linux header file: this file has changed a bit since the last sync, now split in two files. Only this new line is needed, so the minimum has been modified here. Link: https://git.kernel.org/torvalds/c/539f6b9de39e [1] Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org> |
||
|---|---|---|
| .. | ||
| tests | ||
| meson.build | ||
| nm-meta-setting-access.c | ||
| nm-meta-setting-access.h | ||
| nm-meta-setting-base-impl.c | ||
| nm-meta-setting-base-impl.h | ||
| nm-meta-setting-base.h | ||
| nm-meta-setting-desc.c | ||
| nm-meta-setting-desc.h | ||
| README.md | ||
| settings-docs.h.in | ||
libnmc-setting
A client library on top of libnm (and libnm-base). Like libnmc-base, this is a helper library that a libnm client could use.
But its purpose is more specific. It's mainly about providing a generic API for handling connection properties. As such, it's only used by nmcli and in practice also specific to nmcli.
Theoretically, the API is supposed to be generic, so we could imagine another client that uses this beside nmcli.
Like libnm-base, this has a similar purpose and application as ../libnm-client-aux-extern/, the difference is that it's even more specific.