From ab0efddcdb48d800e2f938da54cfe3074640792e Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Fri, 26 Aug 2022 20:36:29 +0200 Subject: New upstream version 1.40.0 --- docs/api/html/NetworkManager.conf.html | 2 +- docs/api/html/NetworkManager.devhelp2 | 13 ++++++----- docs/api/html/index.html | 2 +- docs/api/html/nm-dbus-types.html | 23 ++++++++++++++---- docs/api/html/nm-settings-dbus.html | 18 +++++++------- docs/api/html/nm-settings-nmcli.html | 17 +++++++------- docs/api/version.xml | 2 +- docs/libnm/html/NMRemoteConnection.html | 11 +++++---- docs/libnm/html/NMVpnConnection.html | 8 +++---- docs/libnm/html/NMVpnPluginOld.html | 12 +++++----- docs/libnm/html/NMVpnServicePlugin.html | 6 ++--- docs/libnm/html/api-index-full.html | 8 +++---- docs/libnm/html/index.html | 2 +- docs/libnm/html/libnm-nm-dbus-interface.html | 35 +++++++++++++++++++++------- docs/libnm/html/libnm.devhelp2 | 5 ++-- docs/libnm/html/object-tree.html | 8 +++---- docs/libnm/html/usage.html | 2 +- docs/libnm/version.xml | 2 +- 18 files changed, 108 insertions(+), 68 deletions(-) (limited to 'docs') diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index e2bd8c54..34063973 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -818,7 +818,7 @@ ipv6.ip6-privacy=0

connection.mptcp-flags

-

If unspecified, the fallback is either 0 ("disabled") or 0x22 ("enabled-on-global-iface,subflow"), depending on /proc/sys/net/mptcp/enabled.

+

If unspecified, the fallback is 0x22 ("enabled,subflow"). Note that if sysctl /proc/sys/net/mptcp/enabled is disabled, NetworkManager will still not configure endpoints.

connection.dns-over-tls

diff --git a/docs/api/html/NetworkManager.devhelp2 b/docs/api/html/NetworkManager.devhelp2 index 7fd00dea..257f6bde 100644 --- a/docs/api/html/NetworkManager.devhelp2 +++ b/docs/api/html/NetworkManager.devhelp2 @@ -852,12 +852,13 @@ - - - - - - + + + + + + + diff --git a/docs/api/html/index.html b/docs/api/html/index.html index 89e8f738..e753eef1 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@

- for NetworkManager 1.39.90 + for NetworkManager 1.40.0 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 9935f48c..46152667 100644 --- a/docs/api/html/nm-dbus-types.html +++ b/docs/api/html/nm-dbus-types.html @@ -5366,7 +5366,7 @@ -

NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE

+

NM_MPTCP_FLAGS_ENABLED

@@ -5374,14 +5374,14 @@

-

MPTCP handling is enabled or disabled depending on whether a /0 default route (either IPv4 or IPv6) is configured in the main routing table.

+

MPTCP is enabled and endpoints will be configured. This flag is implied if any of the other flags indicate that MPTCP is enabled and therefore in most cases unnecessary. Note that if "/proc/sys/net/mptcp/enabled" sysctl is disabled, MPTCP handling is disabled despite this flag. This can be overruled with the "also-without-sysctl" flag. Note that by default interfaces that don't have a default route are excluded from having MPTCP endpoints configured. This can be overruled with the "also-without-default-route" and this affects endpoints per address family.

  -

NM_MPTCP_FLAGS_ENABLED

+

NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL

@@ -5389,7 +5389,22 @@

-

MPTCP is enabled and endpoints will be configured. This flag is implied if any of the other flags indicate that MPTCP is enabled and therefore in most cases unnecessary.

+

even if MPTCP handling is enabled via the "enabled" flag, it is ignored unless "/proc/sys/net/mptcp/enabled" is on. With this flag, MPTCP endpoints will be configured regardless of the sysctl setting.

+

+ +  + + + +

NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE

+

+ + +

= 0x8

+

+ + +

even if MPTCP handling is enabled via the "enabled" flag, it is ignored per-address family unless NetworkManager configures a default route. With this flag, NetworkManager will also configure MPTCP endpoints if there is no default route. This takes effect per-address family.

  diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index f0aed252..0903c329 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -245,13 +245,15 @@ If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. - The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. + The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. - The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. + Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. - If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. - If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". + When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + + If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. @@ -1805,9 +1807,9 @@   The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". @@ -2099,9 +2101,9 @@   The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index 672f9e43..6968e035 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -217,10 +217,11 @@

Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints.

If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered.

-

The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured.

-

The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags.

-

If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.

-

If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled".

+

The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags.

+

Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless.

+

Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that.

+

When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.

+

If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl.

NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp.

Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).

@@ -2156,8 +2157,8 @@

Alias: gw4

The gateway associated with this configuration. This is only meaningful if "addresses" is also set.

-

The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default.

-

As an alternative to set the gateway, configure a static default route with /0 as prefix length.

+

Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.

+

Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".

Format: string

@@ -2453,8 +2454,8 @@ Example: priority 5 from 192.167.4.0/24 table 45

Alias: gw6

The gateway associated with this configuration. This is only meaningful if "addresses" is also set.

-

The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default.

-

As an alternative to set the gateway, configure a static default route with /0 as prefix length.

+

Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.

+

Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".

Format: string

diff --git a/docs/api/version.xml b/docs/api/version.xml index d3781d71..32b7211c 100644 --- a/docs/api/version.xml +++ b/docs/api/version.xml @@ -1 +1 @@ -1.39.90 +1.40.0 diff --git a/docs/libnm/html/NMRemoteConnection.html b/docs/libnm/html/NMRemoteConnection.html index fbb6a70b..dedf951f 100644 --- a/docs/libnm/html/NMRemoteConnection.html +++ b/docs/libnm/html/NMRemoteConnection.html @@ -803,10 +803,6 @@ nm_remote_connection_get_secrets (const char *setting_name, GCancellable *cancellable, GError **error); -
-

nm_remote_connection_get_secrets has been deprecated since version 1.22 and should not be used in newly-written code.

-

Use nm_remote_connection_get_secrets_async() or GDBusConnection.

-

Request the connection's secrets. Note that this is a blocking D-Bus call, not a simple property accessor.

@@ -845,7 +841,12 @@ not a simple property accessor.

Returns

a GVariant of type NM_VARIANT_TYPE_CONNECTION containing connection -'s secrets, or NULL on error.

+'s secrets, or NULL on error.

+

Warning: NMClient contains a cache of objects on D-Bus. This cache gets updated +with D-Bus signals when iterating the GMainContext. This function performs a +(pseudo) blocking D-Bus call. Aside blocking, the result will not be in sync +and not be ordered with the content of the NMClient cache. +This function used to be deprecated between 1.22 and 1.38 releases.

[transfer full]

diff --git a/docs/libnm/html/NMVpnConnection.html b/docs/libnm/html/NMVpnConnection.html index 6dfe6f8b..1aeca777 100644 --- a/docs/libnm/html/NMVpnConnection.html +++ b/docs/libnm/html/NMVpnConnection.html @@ -44,7 +44,7 @@ -NMVpnConnectionState +NMVpnConnectionState nm_vpn_connection_get_vpn_state () @@ -76,7 +76,7 @@ Read -NMVpnConnectionState +NMVpnConnectionState vpn-state Read @@ -136,7 +136,7 @@

Functions

nm_vpn_connection_get_vpn_state ()

-
NMVpnConnectionState
+
NMVpnConnectionState
 nm_vpn_connection_get_vpn_state (NMVpnConnection *vpn);

 
Gets the current NMVpnConnection state.

 

@@ -219,7 +219,7 @@ string used by the connection, and must not be modified.

 

 

 
The “vpn-state” property

-
  “vpn-state”                NMVpnConnectionState

+
  “vpn-state”                NMVpnConnectionState

 
The VPN state of the active VPN connection.

 
Owner: NMVpnConnection

 
Flags: Read

diff --git a/docs/libnm/html/NMVpnPluginOld.html b/docs/libnm/html/NMVpnPluginOld.html
index 4d623fe2..bf6a322c 100644
--- a/docs/libnm/html/NMVpnPluginOld.html
+++ b/docs/libnm/html/NMVpnPluginOld.html
@@ -53,7 +53,7 @@
 
 
 
-NMVpnServiceState
+NMVpnServiceState
 
 
 nm_vpn_plugin_old_get_state ()
@@ -158,7 +158,7 @@
 Read / Write / Construct Only
 
 
-NMVpnServiceState
+NMVpnServiceState
 state
 Read / Write
 
@@ -274,7 +274,7 @@ nm_vpn_plugin_old_get_connection (
 

 
nm_vpn_plugin_old_get_state ()

-
NMVpnServiceState
+
NMVpnServiceState
 nm_vpn_plugin_old_get_state (NMVpnPluginOld *plugin);

 

 
nm_vpn_plugin_old_get_state has been deprecated since version 1.2 and should not be used in newly-written code.

@@ -286,7 +286,7 @@ nm_vpn_plugin_old_get_state (
nm_vpn_plugin_old_set_state ()

 
void
 nm_vpn_plugin_old_set_state (NMVpnPluginOld *plugin,
-                             NMVpnServiceState state);

+                             NMVpnServiceState state);

 

 
nm_vpn_plugin_old_set_state has been deprecated since version 1.2 and should not be used in newly-written code.

 
Replaced by NMVpnServicePlugin.

@@ -352,7 +352,7 @@ nm_vpn_plugin_old_set_login_banner (
nm_vpn_plugin_old_failure ()

 
void
 nm_vpn_plugin_old_failure (NMVpnPluginOld *plugin,
-                           NMVpnPluginFailure reason);

+                           NMVpnPluginFailure reason);

nm_vpn_plugin_old_failure has been deprecated since version 1.2 and should not be used in newly-written code.

Replaced by NMVpnServicePlugin.

@@ -535,7 +535,7 @@ to flags,

The “state” property

-
  “state”                    NMVpnServiceState
+
  “state”                    NMVpnServiceState

The state of the plugin.

NMVpnPluginOld:state has been deprecated since version 1.2 and should not be used in newly-written code.

diff --git a/docs/libnm/html/NMVpnServicePlugin.html b/docs/libnm/html/NMVpnServicePlugin.html index cd038c2e..965727a3 100644 --- a/docs/libnm/html/NMVpnServicePlugin.html +++ b/docs/libnm/html/NMVpnServicePlugin.html @@ -150,7 +150,7 @@ Read / Write / Construct Only -NMVpnServiceState +NMVpnServiceState state Read / Write @@ -324,7 +324,7 @@ nm_vpn_service_plugin_set_login_banner

nm_vpn_service_plugin_failure ()

void
 nm_vpn_service_plugin_failure (NMVpnServicePlugin *plugin,
-                               NMVpnPluginFailure reason);
+ NMVpnPluginFailure reason);
@@ -515,7 +515,7 @@ to flags,

The “state” property

-
  “state”                    NMVpnServiceState
+
  “state”                    NMVpnServiceState

The state of the plugin.

Owner: NMVpnServicePlugin

Flags: Read / Write

diff --git a/docs/libnm/html/api-index-full.html b/docs/libnm/html/api-index-full.html index a1c2086d..7a730e98 100644 --- a/docs/libnm/html/api-index-full.html +++ b/docs/libnm/html/api-index-full.html @@ -3761,11 +3761,11 @@ NMUtilsPredicateStr, user_function in NMSettingOvs
-NMVpnConnectionState, enum in nm-vpn-dbus-interface +NMVpnConnectionState, enum in nm-vpn-dbus-interface
-NMVpnConnectionStateReason, enum in nm-vpn-dbus-interface +NMVpnConnectionStateReason, enum in nm-vpn-dbus-interface
@@ -3817,7 +3817,7 @@ NMVpnConnectionStateReason, enum in nm-vpn-dbus-interface
-NMVpnPluginFailure, enum in nm-vpn-dbus-interface +NMVpnPluginFailure, enum in nm-vpn-dbus-interface
@@ -3929,7 +3929,7 @@ NMVpnPluginFailure, enum in nm-vpn-dbus-interface
-NMVpnServiceState, enum in nm-vpn-dbus-interface +NMVpnServiceState, enum in nm-vpn-dbus-interface
diff --git a/docs/libnm/html/index.html b/docs/libnm/html/index.html index 73821288..f9ea840b 100644 --- a/docs/libnm/html/index.html +++ b/docs/libnm/html/index.html @@ -15,7 +15,7 @@

- for libnm 1.39.90 + for libnm 1.40.0 The latest version of this documentation can be found on-line at https://networkmanager.dev/docs/libnm/latest/. diff --git a/docs/libnm/html/libnm-nm-dbus-interface.html b/docs/libnm/html/libnm-nm-dbus-interface.html index 1585ca83..36eb69f8 100644 --- a/docs/libnm/html/libnm-nm-dbus-interface.html +++ b/docs/libnm/html/libnm-nm-dbus-interface.html @@ -4116,20 +4116,39 @@ is detected in the system.

  -

NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE

+

NM_MPTCP_FLAGS_ENABLED

-

MPTCP handling is enabled -or disabled depending on whether a /0 default route (either IPv4 or IPv6) is -configured in the main routing table.

+

MPTCP is enabled and endpoints will be configured. +This flag is implied if any of the other flags indicate that +MPTCP is enabled and therefore in most cases unnecessary. +Note that if "/proc/sys/net/mptcp/enabled" sysctl is disabled, MPTCP +handling is disabled despite this flag. This can be overruled with the +"also-without-sysctl" flag. +Note that by default interfaces that don't have a default route are +excluded from having MPTCP endpoints configured. This can be overruled +with the "also-without-default-route" and this affects endpoints +per address family.

  -

NM_MPTCP_FLAGS_ENABLED

+

NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL

-

MPTCP is enabled and endpoints will be configured. -This flag is implied if any of the other flags indicate that -MPTCP is enabled and therefore in most cases unnecessary.

+

even if MPTCP handling is enabled +via the "enabled" flag, it is ignored unless "/proc/sys/net/mptcp/enabled" +is on. With this flag, MPTCP endpoints will be configured regardless +of the sysctl setting.

+ +  + + +

NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE

+ +

even if MPTCP handling is enabled +via the "enabled" flag, it is ignored per-address family unless NetworkManager +configures a default route. With this flag, NetworkManager will also configure +MPTCP endpoints if there is no default route. This takes effect per-address +family.

  diff --git a/docs/libnm/html/libnm.devhelp2 b/docs/libnm/html/libnm.devhelp2 index b245c127..18e1826c 100644 --- a/docs/libnm/html/libnm.devhelp2 +++ b/docs/libnm/html/libnm.devhelp2 @@ -589,7 +589,7 @@ - + @@ -3529,8 +3529,9 @@ - + + diff --git a/docs/libnm/html/object-tree.html b/docs/libnm/html/object-tree.html index 04306fd0..ebc3205c 100644 --- a/docs/libnm/html/object-tree.html +++ b/docs/libnm/html/object-tree.html @@ -214,10 +214,10 @@ ├── NMTernary ├── NMUtilsSecurityType ├── NMVlanPriorityMap - ├── NMVpnConnectionState - ├── NMVpnConnectionStateReason - ├── NMVpnPluginFailure - ├── NMVpnServiceState + ├── NMVpnConnectionState + ├── NMVpnConnectionStateReason + ├── NMVpnPluginFailure + ├── NMVpnServiceState ├── NMWepKeyType ╰── NMWimaxNspNetworkType GBoxed diff --git a/docs/libnm/html/usage.html b/docs/libnm/html/usage.html index cc2062d0..5b5fb9ab 100644 --- a/docs/libnm/html/usage.html +++ b/docs/libnm/html/usage.html @@ -96,7 +96,7 @@ 

$ cc $(pkg-config --libs --cflags libnm) -o hello-nm hello-nm.c
   $ ./hello-nm
-  NetworkManager version: 1.39.90
+  NetworkManager version: 1.40.0
 
   $

diff --git a/docs/libnm/version.xml b/docs/libnm/version.xml index d3781d71..32b7211c 100644 --- a/docs/libnm/version.xml +++ b/docs/libnm/version.xml @@ -1 +1 @@ -1.39.90 +1.40.0 -- cgit 1.3.0-6-gf8a5