From 5d9e3721ad196595acd064e0d3ce66edc2613e51 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 11 Jan 2023 13:39:59 +0100 Subject: New upstream version 1.40.10 --- .../dbus-org.freedesktop.NetworkManager.Device.xml | 5 +- docs/api/html/NetworkManager.devhelp2 | 99 +++++++++++----------- ...dbus-org.freedesktop.NetworkManager.Device.html | 6 +- docs/api/html/index.html | 2 +- docs/api/html/ix01.html | 16 ++-- docs/api/html/nm-dbus-types.html | 67 +++++++++++++-- docs/api/version.xml | 2 +- 7 files changed, 130 insertions(+), 67 deletions(-) (limited to 'docs/api') diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml index 0d73ca72..c8ccbd52 100644 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml +++ b/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml @@ -100,6 +100,9 @@ that the user made these changes intentionally outside of NetworkManager). Reapply can make the applied-connection different from the settings-connection, just like updating the settings-connection can make them different. + +Since 1.42, 1.40.10, "preserve-external-ip" flag (0x1) is supported to not +remove externally added IP addresses and routes on the device during reapply. @@ -117,7 +120,7 @@ If non-zero, the current version id of the applied-connection must match. The cu IN u flags: -Flags which would modify the behavior of the Reapply call. There are no flags defined currently and the users should use the value of 0. +Flags which would modify the behavior of the Reapply call. Invalid flags are rejected. diff --git a/docs/api/html/NetworkManager.devhelp2 b/docs/api/html/NetworkManager.devhelp2 index 257f6bde..52186b6b 100644 --- a/docs/api/html/NetworkManager.devhelp2 +++ b/docs/api/html/NetworkManager.devhelp2 @@ -508,6 +508,7 @@ + @@ -811,54 +812,56 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html index b1e492cb..f5026a1f 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html @@ -129,6 +129,10 @@ Reapply can make the applied-connection different from the settings-connection, just like updating the settings-connection can make them different.

+

+Since 1.42, 1.40.10, "preserve-external-ip" flag (0x1) is supported to not +remove externally added IP addresses and routes on the device during reapply. +

@@ -150,7 +154,7 @@ If non-zero, the current version id of the applied-connection must match. The cu diff --git a/docs/api/html/index.html b/docs/api/html/index.html index 6c1324c1..240e61e6 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@

IN u flags:

-Flags which would modify the behavior of the Reapply call. There are no flags defined currently and the users should use the value of 0. +Flags which would modify the behavior of the Reapply call. Invalid flags are rejected.

- for NetworkManager 1.40.8 + for NetworkManager 1.40.10 The latest version of this documentation can be found on-line at https://networkmanager.dev/docs/api/latest/. diff --git a/docs/api/html/ix01.html b/docs/api/html/ix01.html index 15c9933b..d1897057 100644 --- a/docs/api/html/ix01.html +++ b/docs/api/html/ix01.html @@ -1123,9 +1123,9 @@

NMCheckpointCreateFlags, enum NMCheckpointCreateFlags
-
NMClientPermission, enum NMClientPermission +
NMClientPermission, enum NMClientPermission
-
NMClientPermissionResult, enum NMClientPermissionResult +
NMClientPermissionResult, enum NMClientPermissionResult
NMConnectionMultiConnect, enum NMConnectionMultiConnect
@@ -1133,10 +1133,12 @@
NMDeviceCapabilities, enum NMDeviceCapabilities
-
NMDeviceInterfaceFlags, enum NMDeviceInterfaceFlags +
NMDeviceInterfaceFlags, enum NMDeviceInterfaceFlags
NMDeviceModemCapabilities, enum NMDeviceModemCapabilities
+
NMDeviceReapplyFlags, enum NMDeviceReapplyFlags +
NMDeviceState, enum NMDeviceState
NMDeviceStateReason, enum NMDeviceStateReason @@ -1147,13 +1149,13 @@
NMIPTunnelMode, enum NMIPTunnelMode
-
NMManagerReloadFlags, enum NMManagerReloadFlags +
NMManagerReloadFlags, enum NMManagerReloadFlags
NMMetered, enum NMMetered
-
NMMptcpFlags, enum NMMptcpFlags +
NMMptcpFlags, enum NMMptcpFlags
-
NMRadioFlags, enum NMRadioFlags +
NMRadioFlags, enum NMRadioFlags
NMRollbackResult, enum NMRollbackResult
@@ -1169,7 +1171,7 @@
NMState, enum NMState
-
NMTernary, enum NMTernary +
NMTernary, enum NMTernary
NMVpnConnectionState, enum NMVpnConnectionState
diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html index 0580b439..892a1924 100644 --- a/docs/api/html/nm-dbus-types.html +++ b/docs/api/html/nm-dbus-types.html @@ -3071,7 +3071,7 @@

enum NMMetered

-

The NMMetered enum has two different purposes: one is to configure "connection.metered" setting of a connection profile in NMSettingConnection, and the other is to express the actual metered state of the NMDevice at a given moment.

+

The NMMetered enum has two different purposes: one is to configure "connection.metered" setting of a connection profile in NMSettingConnection, and the other is to express the actual metered state of the NMDevice at a given moment.

For the connection profile only NM_METERED_UNKNOWN, NM_METERED_NO and NM_METERED_YES are allowed.

The device's metered state at runtime is determined by the profile which is currently active. If the profile explicitly specifies NM_METERED_NO or NM_METERED_YES, then the device's metered state is as such. If the connection profile leaves it undecided at NM_METERED_UNKNOWN (the default), then NetworkManager tries to guess the metered state, for example based on the device type or on DHCP options (like Android devices exposing a "ANDROID_METERED" DHCP vendor option). This then leads to either NM_METERED_GUESS_NO or NM_METERED_GUESS_YES.

Most applications probably should treat the runtime state NM_METERED_GUESS_YES like NM_METERED_YES, and all other states as not metered.

@@ -4619,12 +4619,63 @@
+

enum NMDeviceReapplyFlags

+

Flags for the Reapply() D-Bus call of a device and nm_device_reapply_async().

+

Since: 1.42, 1.40.10

+

On 1.40.10+, no GFlags type is created.

+

+
+

Values

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

NM_DEVICE_REAPPLY_FLAGS_NONE

+

+		 +

= 0

+

+		 +

no flag set.

+

+		 
+

NM_DEVICE_REAPPLY_FLAGS_PRESERVE_EXTERNAL_IP

+

+		 +

= 0x1

+

+		 +

during reapply, preserve external IP addresses and routes.

+

+		 
+
+
+
+

enum NMTernary

An boolean value that can be overridden by a default.

Since: 1.14

-

Values

+

Values

@@ -4689,7 +4740,7 @@

Since: 1.22

-

Values

+

Values

@@ -4784,7 +4835,7 @@

Since: 1.22

-

Values

+

Values

@@ -4893,7 +4944,7 @@

NMClientPermission values indicate various permissions that NetworkManager clients can obtain to perform certain tasks on behalf of the current user.

-

Values

+

Values

@@ -5182,7 +5233,7 @@

NMClientPermissionResult values indicate what authorizations and permissions the user requires to obtain a given NMClientPermission

-

Values

+

Values

@@ -5262,7 +5313,7 @@

Since: 1.38

-

Values

+

Values

@@ -5326,7 +5377,7 @@

Since: 1.40

-

Values

+

Values

diff --git a/docs/api/version.xml b/docs/api/version.xml index 19d25d0a..5faa4fff 100644 --- a/docs/api/version.xml +++ b/docs/api/version.xml @@ -1 +1 @@ -1.40.8 +1.40.10 -- cgit 1.3.0-6-gf8a5