From 2965dc70bb3cbfa8de2f279761812b84b87600cb Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Sun, 18 Dec 2022 21:31:39 +0100 Subject: New upstream version 1.40.8 --- docs/api/html/index.html | 2 +- docs/api/html/nm-dbus-types.html | 2 +- docs/api/html/nm-settings-dbus.html | 4 ++-- docs/api/html/nm-settings-nmcli.html | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) (limited to 'docs/api/html') diff --git a/docs/api/html/index.html b/docs/api/html/index.html index ad46bacb..6c1324c1 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@

- for NetworkManager 1.40.6 + for NetworkManager 1.40.8 The latest version of this documentation can be found on-line at https://networkmanager.dev/docs/api/latest/. diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html index d940c0f8..0580b439 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.

diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index 854ca8f0..fd1f0892 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -2372,7 +2372,7 @@ mka-cak string   - The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. + The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters. @@ -2386,7 +2386,7 @@ mka-ckn string   - The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. + The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Must be a string of hexadecimal characters with a even length between 2 and 64. diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index 17ef394f..e2f76d6a 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -2787,7 +2787,7 @@ Example: priority 5 from 1:2:3::5/128 table 45

Alias: cak

-

The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement.

+

The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.

Format: string

@@ -2805,7 +2805,7 @@ Example: priority 5 from 1:2:3::5/128 table 45

Alias: ckn

-

The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement.

+

The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Must be a string of hexadecimal characters with a even length between 2 and 64.

Format: string

-- cgit 1.3.0-6-gf8a5