fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2026-01-02 14:40:13 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/src/libnmc-setting
History
Íñigo Huguet 90640673d6 nm-settings-nmcli: show proper valid values of ip-tunnel properties 
Show all valid properties for ip-tunnel.mode, not only 2 examples.

Show constants as values suitable for user input in nmcli. That means
showing, for example, "ipip (1)" instead of "IP_TUNNEL_MODE_IPIP (1)".

(cherry picked from commit 140abc81ec)
2023-10-03 14:54:20 +02:00
..
tests libnm-client: Add public nm_conn_wireguard_import() func 2022-07-21 14:53:26 +02:00
meson.build build: pass both filenames to "tools/check-compare-generated.sh" script 2022-10-31 09:11:30 +01:00
nm-meta-setting-access.c all: use nm_g_array_{index,first,last,index_p}() instead of g_array_index() 2022-09-15 12:39:07 +02:00
nm-meta-setting-access.h format: reformat source tree with clang-format 13.0 2021-11-29 09:31:09 +00:00
nm-meta-setting-base-impl.c all: add "link" setting 2023-03-02 16:51:16 +01:00
nm-meta-setting-base-impl.h all: add "link" setting 2023-03-02 16:51:16 +01:00
nm-meta-setting-base.h build: move "clients/common/" to "src/libnmc-{base,setting}/" 2021-03-02 08:38:25 +01:00
nm-meta-setting-desc.c cli: fix signature of dcb_check_feature_enabled() 2023-05-23 09:25:51 +02:00
nm-meta-setting-desc.h nmcli: add get_env_flags() accessor to NMMetaEnvironment for checking offline mode 2022-08-31 19:20:11 +02:00
README.md all: add some README.md files describing the purpose of our sources 2021-08-19 17:51:11 +02:00
settings-docs.h.in nm-settings-nmcli: show proper valid values of ip-tunnel properties 2023-10-03 14:54:20 +02:00

README.md

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.