From e536d40eaea5dcdc0743b0a5e8e17faa46608a50 Mon Sep 17 00:00:00 2001
From: Michael Biebl
The permitted values are: yes: register hostname and resolving -for the connection, no: disable LLMNR for the interface, resolve: -do not register hostname but allow resolving of LLMNR host names.
-This feature requires a plugin which supports LLMNR. One such -plugin is dns-systemd-resolved.
+The permitted values are: "yes" (2) register hostname and resolving +for the connection, "no" (0) disable LLMNR for the interface, "resolve" +(1) do not register hostname but allow resolving of LLMNR host names +If unspecified, "default" ultimately depends on the DNS plugin (which +for systemd-resolved currently means "yes").
+This feature requires a plugin which supports LLMNR. Otherwise the +setting has no effect. One such plugin is dns-systemd-resolved.
Flags: Read / Write
Default value: -1
Since: 1.14
@@ -2169,11 +2171,14 @@ plugin is dns-systemd-resolved.“mdns” property “mdns” gint
Whether mDNS is enabled for the connection.
-The permitted values are: yes: register hostname and resolving -for the connection, no: disable mDNS for the interface, resolve: -do not register hostname but allow resolving of mDNS host names.
-This feature requires a plugin which supports mDNS. One such -plugin is dns-systemd-resolved.
+The permitted values are: "yes" (2) register hostname and resolving +for the connection, "no" (0) disable mDNS for the interface, "resolve" +(1) do not register hostname but allow resolving of mDNS host names +and "default" (-1) to allow lookup of a global default in NetworkManager.conf. +If unspecified, "default" ultimately depends on the DNS plugin (which +for systemd-resolved currently means "no").
+This feature requires a plugin which supports mDNS. Otherwise the +setting has no effect. One such plugin is dns-systemd-resolved.
Flags: Read / Write
Default value: -1
Since: 1.12
diff --git a/docs/libnm/html/NMSettingIP6Config.html b/docs/libnm/html/NMSettingIP6Config.html index 2cdd15c6..fc74885c 100644 --- a/docs/libnm/html/NMSettingIP6Config.html +++ b/docs/libnm/html/NMSettingIP6Config.html @@ -79,6 +79,14 @@ nm_setting_ip6_config_get_dhcp_duid () +Since: 1.12
+gint32
+nm_setting_ip6_config_get_ra_timeout (NMSettingIP6Config *setting);
+
+ The configured NM_SETTING_IP6_CONFIG_RA_TIMEOUT value with the
+timeout for router advertisements in seconds.
Since: 1.24, 1.22.8
+#define NM_SETTING_IP6_CONFIG_METHOD_IGNORE "ignore"@@ -615,6 +665,19 @@ setting as another way of avoiding host tracking with IPv6 addresses.
“ra-timeout” property“ra-timeout” gint+
A timeout for waiting Router Advertisements in seconds. If zero (the default), a +globally configured default is used. If still unspecified, the timeout depends on the +sysctl settings of the device.
+Set to 2147483647 (MAXINT32) for infinity.
+Flags: Read / Write
+Allowed values: >= 0
+Default value: 0
+Since: 1.24, 1.22.8
+“token” property“token” gchar *
Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 diff --git a/docs/libnm/html/NMSettingIPConfig.html b/docs/libnm/html/NMSettingIPConfig.html index c7f19f28..32891026 100644 --- a/docs/libnm/html/NMSettingIPConfig.html +++ b/docs/libnm/html/NMSettingIPConfig.html @@ -6472,7 +6472,10 @@ providing a static hostname for the computer. If the
“dhcp-timeout” property“dhcp-timeout” gint-
A timeout for a DHCP transaction in seconds.
+A timeout for a DHCP transaction in seconds. If zero (the default), a +globally configured default is used. If still unspecified, a device specific +timeout is used (usually 45 seconds).
+Set to 2147483647 (MAXINT32) for infinity.
Flags: Read / Write
Allowed values: >= 0
Default value: 0
@@ -6510,10 +6513,11 @@ same connection profile.When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. When multiple -devices have configurations with the same priority, the one with an -active default route will be preferred. Negative values have the special +devices have configurations with the same priority, VPNs will be +considered first, then devices with the best (lowest metric) default +route and then all other devices. Negative values have the special effect of excluding other configurations with a greater priority value; -so in presence of at least a negative priority, only DNS servers from +so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used.
When using a DNS resolver that supports Conditional Forwarding as dns=dnsmasq or
dns=systemd-resolved, each connection is used to query domains in its
diff --git a/docs/libnm/html/api-index-full.html b/docs/libnm/html/api-index-full.html
index a987e0fb..ee7bf244 100644
--- a/docs/libnm/html/api-index-full.html
+++ b/docs/libnm/html/api-index-full.html
@@ -1589,6 +1589,10 @@ nml_dbus_property_o_is_ready, function in
libnm Reference Manual
- for libnm 1.22.6
+ for libnm 1.22.8
The latest version of this documentation can be found on-line at
https://developer.gnome.org/libnm/stable/.
diff --git a/docs/libnm/html/libnm-nm-version.html b/docs/libnm/html/libnm-nm-version.html
index 3178fbde..d596b86e 100644
--- a/docs/libnm/html/libnm-nm-version.html
+++ b/docs/libnm/html/libnm-nm-version.html
@@ -254,6 +254,10 @@
#define
NM_AVAILABLE_IN_1_22_2
# define NM_AVAILABLE_IN_1_22_2 G_UNAVAILABLE(1,22.2)+