From 2e5fa45ddfbb5cffa1e78221f1cea706e2f298af Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 31 Jul 2019 10:51:42 +0200 Subject: New upstream version 1.19.90 --- docs/libnm/html/libnm-nm-dbus-interface.html | 114 +++++++++++++++++++++++---- 1 file changed, 98 insertions(+), 16 deletions(-) (limited to 'docs/libnm/html/libnm-nm-dbus-interface.html') diff --git a/docs/libnm/html/libnm-nm-dbus-interface.html b/docs/libnm/html/libnm-nm-dbus-interface.html index 17617b95..541a5a56 100644 --- a/docs/libnm/html/libnm-nm-dbus-interface.html +++ b/docs/libnm/html/libnm-nm-dbus-interface.html @@ -470,6 +470,10 @@ enum +NMSettingsAddConnection2Flags + + +enum NMSettingsUpdate2Flags @@ -507,6 +511,7 @@ ├── NMDeviceWifiCapabilities ├── NMSecretAgentCapabilities ├── NMSecretAgentGetSecretsFlags + ├── NMSettingsAddConnection2Flags ├── NMSettingsConnectionFlags ╰── NMSettingsUpdate2Flags @@ -1439,6 +1444,13 @@ GSM/UMTS, or LTE network access protocols

  + +

NM_WIFI_DEVICE_CAP_MESH

+ +

device supports acting as a mesh point

+ +  + @@ -1654,6 +1666,13 @@ supported

  + +

NM_802_11_MODE_MESH

+ +

the device is a 802.11s mesh point.

+ +  + @@ -3330,6 +3349,55 @@ VPN plugin authentication dialogs.

+

enum NMSettingsAddConnection2Flags

+

Numeric flags for the "flags" argument of AddConnection2() D-Bus API.

+
+

Members

+
+++++ + + + + + + + + + + + + + + + + + + + + + + +

NM_SETTINGS_ADD_CONNECTION2_FLAG_NONE

 +

an alias for numeric zero, no flags set.

+		 

NM_SETTINGS_ADD_CONNECTION2_FLAG_TO_DISK

 +

to persist the connection to disk.

+		 

NM_SETTINGS_ADD_CONNECTION2_FLAG_IN_MEMORY

 +

to make the connection in-memory only.

+		 

NM_SETTINGS_ADD_CONNECTION2_FLAG_BLOCK_AUTOCONNECT

 +

usually, when the connection + has autoconnect enabled and gets added, it becomes eligible to autoconnect + right away. Setting this flag, disables autoconnect until the connection + is manually activated.

+		 
+
+

Since: 1.20

+
+
+

enum NMSettingsUpdate2Flags

Members

@@ -3357,25 +3425,24 @@ VPN plugin authentication dialogs.

NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY

-

to make the connection in-memory only. - If the connection was previously persistent, the corresponding file on disk - is not deleted but merely the connection is decoupled from the file - on disk. If you later delete an in-memory connection, the connection - on disk will be deleted as well.

+

makes the profile in-memory. + Note that such profiles are stored in keyfile format under /run. + If the file is already in-memory, the file in /run is updated in-place. + Otherwise, the previous storage for the profile is left unchanged + on disk, and the in-memory copy shadows it. + Note that the original filename of the previous persistent storage (if any) + is remembered. That means, when later persisting the profile again to disk, + the file on disk will be overwritten again. + Likewise, when finally deleting the profile, both the storage from /run + and persistent storage are deleted (or if the persistent storage does not + allow deletion, and nmmeta file is written to mark the UUID as deleted).

 

NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED

-

this is like NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY -, - but if the connection has a corresponding file on disk, the association between - the connection and the file is forgotten but the file is not modified. - The difference to NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY is if you later - save the connection again to disk, a new file name will be chosen without - overwriting the remaining file on disk. Also, if you delete the connection - later, the file on disk will not be deleted.

+

this is almost the same as

  @@ -3384,8 +3451,9 @@ VPN plugin authentication dialogs.

this is like NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY , - but if the connection has a corresponding file on disk, the file on - disk will be deleted.

+ but if the connection has a corresponding file on persistent storage, the file + will be deleted right away. If the profile is later again persisted to disk, + a new, unused filename will be chosen.

  @@ -3393,7 +3461,8 @@ VPN plugin authentication dialogs.

NM_SETTINGS_UPDATE2_FLAG_VOLATILE

This can be specified with either - NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED or NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY. + NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED + or NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY. After making the connection in-memory only, the connection is marked as volatile. That means, if the connection is currently not active it will be deleted right away. Otherwise, it is marked to for deletion @@ -3413,6 +3482,19 @@ VPN plugin authentication dialogs.

  + +

NM_SETTINGS_UPDATE2_FLAG_NO_REAPPLY

+ +

when a profile gets modified that is + currently active, then these changes don't take effect for the active + device unless the profile gets reactivated or the configuration reapplied. + There are two exceptions: by default "connection.zone" and "connection.metered" + properties take effect immediately. Specify this flag to prevent these + properties to take effect, so that the change is restricted to modify + the profile. Since: 1.20.

+ +  +
-- cgit 1.3.0-6-gf8a5 From 5c79b900b59a5ad162ecc836e424468207ff031e Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Tue, 6 Aug 2019 22:46:20 +0200 Subject: New upstream version 1.20.0 --- docs/libnm/html/libnm-nm-dbus-interface.html | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) (limited to 'docs/libnm/html/libnm-nm-dbus-interface.html') diff --git a/docs/libnm/html/libnm-nm-dbus-interface.html b/docs/libnm/html/libnm-nm-dbus-interface.html index 541a5a56..2e649502 100644 --- a/docs/libnm/html/libnm-nm-dbus-interface.html +++ b/docs/libnm/html/libnm-nm-dbus-interface.html @@ -1447,7 +1447,7 @@ GSM/UMTS, or LTE network access protocols

NM_WIFI_DEVICE_CAP_MESH

-

device supports acting as a mesh point

+

device supports acting as a mesh point. Since: 1.20.

  @@ -1669,7 +1669,7 @@ supported

NM_802_11_MODE_MESH

-

the device is a 802.11s mesh point.

+

the device is a 802.11s mesh point. Since: 1.20.

  @@ -2510,8 +2510,7 @@ GPRS, EDGE, UMTS, HSDPA, HSUPA, or HSPA+ packet switched data capability

indicates that the per-connection setting is unspecified. In this case, it will fallback to the default - value, which is NM_CONNECTION_MULTI_CONNECT_SINGLE -.

+ value, which is NM_CONNECTION_MULTI_CONNECT_SINGLE.

  @@ -3442,15 +3441,20 @@ VPN plugin authentication dialogs.

NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED

-

this is almost the same as

+

this is almost the same + as NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, with one difference: when later deleting + the profile, the original profile will not be deleted. Instead a nmmeta + file is written to /run to indicate that the profile is gone. + Note that if such a nmmeta tombstone file exists and hides a file in persistant + storage, then when re-adding the profile with the same UUID, then the original + storage is taken over again.

 

NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY

-

this is like NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY -, +

this is like NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, but if the connection has a corresponding file on persistent storage, the file will be deleted right away. If the profile is later again persisted to disk, a new, unused filename will be chosen.

-- cgit 1.3.0-6-gf8a5