From 9959fdb2e8ddd06f2161798ca0a39c77d67c652d Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 4 May 2022 15:35:24 +0200 Subject: New upstream version 1.37.92 --- ...bus-org.freedesktop.NetworkManager.Settings.xml | 73 ++++++++++++++-------- 1 file changed, 47 insertions(+), 26 deletions(-) (limited to 'docs/api/dbus-org.freedesktop.NetworkManager.Settings.xml') diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Settings.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Settings.xml index 68275f4e..3dfc50e1 100644 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Settings.xml +++ b/docs/api/dbus-org.freedesktop.NetworkManager.Settings.xml @@ -5,7 +5,7 @@ org.freedesktop.NetworkManager.Settings org.freedesktop.NetworkManager.Settings - org.freedesktop.NetworkManager.Settings Connection Settings Profile Manager + org.freedesktop.NetworkManager.Settings Connection Settings Profile Manager. Methods ListConnections (OUT ao connections); @@ -142,24 +142,43 @@ AddConnection2 (IN a{sa{sv}} settings, OUT o path, OUT a{sv} result); - "0x1" (to-disk), - "0x2" (in-memory), - "0x20" (block-autoconnect). - Unknown flags cause the call to fail. - args: optional arguments dictionary, for extentibility. Currently, no - arguments are accepted. Specifying unknown keys causes the call - to fail. - path: Object path of the new connection that was just added. - result: output argument, currently no additional results are returned. - Add a new connection profile. - Either the flags 0x1 (to-disk) or 0x2 (in-memory) must be specified. - The effect is whether to behave like AddConnection or AddConnectionUnsaved. - If 0x20 (block-autoconnect) is specified, autoconnect for the new profile - is blocked from the beginning. Otherwise, the profile might automatically - connect if a suitable device is around. - AddConnection2 is a extensible alternative to AddConnection, and AddConnectionUnsaved. + Add a new connection profile. + AddConnection2 is an alternative to + AddConnection and + AddConnectionUnsaved. The new variant can do everything that the older variants could, and more. - Since: 1.20 + Its behavior is extensible via extra flags and args arguments. + The flags argument accepts the combination of following values, + logically or-ed together: + + + 0x1 (to-disk): + The connection is persisted to disk. + + + 0x2 (in-memory): + The change is only made in memory (without touching an eventual + profile on disk). If neither 0x1 nor 0x2 is set, the change is made in memory + only, if the connection is already in memory only. + + + 0x20 (block-autoconnect): + Blocks auto-connect on the new profile + + + The args argument accepts the following keys: + + + plugin: + The settings plugin the newly added connection will + use, such as "keyfile" or "ifcfg-rh". + Since 1.38 + + + Either the flags 0x1 (to-disk) or 0x2 (in-memory) must be specified. + The effect is whether to behave like + AddConnection or + AddConnectionUnsaved. @@ -168,21 +187,22 @@ AddConnection2 (IN a{sa{sv}} settings, IN u flags: - optional flags argument. Currently, the following flags are supported: + Flags. Unknown flags cause the call to fail. IN a{sv} args: - + Optional arguments dictionary, for extentibility. Specifying unknown keys causes the call to fail. OUT o path: - + Object path of the new connection that was just added. OUT a{sv} result: - + Output argument, currently no additional results are returned. +Since 1.20 The LoadConnections() method @@ -192,13 +212,14 @@ LoadConnections (IN as filenames, OUT b status, OUT as failures); - Note that before 1.20, NetworkManager had a bug and this status value was wrong. It is better to assume success if the method does not return with a D-Bus error. On top of that, you can look at failures to know whether any of the requested files failed. - failures: Paths of connection files that could not be loaded. - Loads or reloads the indicated connections from disk. You should call this + Loads or reloads the indicated connections from disk. You should call this after making changes directly to an on-disk connection file to make sure that NetworkManager sees the changes. As with AddConnection(), this operation does not necessarily start the network connection. + Note that before 1.20, NetworkManager had a bug and this status value was wrong. + It is better to assume success if the method does not return with a D-Bus error. + On top of that, you can look at failures to know whether any of the requested files failed. @@ -211,7 +232,7 @@ LoadConnections (IN as filenames, OUT as failures: - + Paths of connection files that could not be loaded. -- cgit 1.3.0-6-gf8a5