mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-05-21 02:38:16 +02: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-auth-subject.c | ||
| nm-auth-subject.h | ||
| nm-common-macros.h | ||
| nm-libnm-core-utils.c | ||
| nm-libnm-core-utils.h | ||
| README.md | ||
libnm-core-aux-intern
libnm-core-aux-intern is a static library that:
- uses parts of
libnm-core-impl, that are public API oflibnm(i.e.libnm-core-public). - that is statically linked into
libnm-core-impl(and thuslibnmand NetworkManager core. - that can also be statically linked into other users of
libnm.
Basically, it is a static library with utility functions that extends
libnm-core-impl (the part that is public API of libnm),
but it is also used by libnm-core-impl itself.
That means:
- you can use it everywhere where you either statically link
with
libnm-core-impl, or dynamically link withlibnm. - you can even use it inside of
libnm-core-implitself. This is the difference betweenlibnm-core-aux-internandlibnm-core-aux-extern.
Note that libnm-core-aux-intern only uses public API of libnm.
This directory should not be added to the include search path. Instead,
users should fully qualify the include like #include "libnm-core-aux-intern/nm-auth-subject.h".