From 34bb501be08aa2b313d88e67d6e0a7e0a3f9cfa6 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Sun, 5 May 2024 00:07:30 +0200 Subject: New upstream version 1.47.90 --- docs/api/html/NetworkManager.conf.html | 46 ++++++- docs/api/html/NetworkManager.devhelp2 | 10 ++ docs/api/html/index.html | 2 +- docs/api/html/ix01.html | 198 +++++++++++++++------------- docs/api/html/nm-dbus-types.html | 152 ++++++++++++++++++++- docs/api/html/nm-settings-dbus.html | 72 +++++++++- docs/api/html/nm-settings-ifcfg-rh.html | 23 ++++ docs/api/html/nm-settings-keyfile.html | 16 +++ docs/api/html/nm-settings-nmcli.html | 137 ++++++++++++++----- docs/api/html/settings-802-11-wireless.html | 6 + docs/api/html/settings-802-1x.html | 6 + docs/api/html/settings-802-3-ethernet.html | 6 + docs/api/html/settings-connection.html | 14 +- docs/api/html/settings-ipv4.html | 6 + docs/api/html/settings-ipv6.html | 26 +++- 15 files changed, 576 insertions(+), 144 deletions(-) (limited to 'docs/api/html') diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index aee3ac66..b98b28ac 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -769,6 +769,11 @@ domains=ALL and these default values only matter if the per-profile values explicitly indicates to use the default from NetworkManager.conf.

+

+ Note that while nmcli supports various aliases and convenience features for configuring + properties, the settings in this section do not. For example, enum values usually only + can be configured via their numeric magic number. +

Example:

@@ -779,7 +784,7 @@ ipv6.ip6-privacy=0

-

Supported Properties

+

Supported Properties

Not all properties can be overwritten, only the following properties are supported to have their default values configured @@ -813,6 +818,10 @@ ipv6.ip6-privacy=0 +

connection.down-on-poweroff

+

Whether the connection will be brought down before the system is powered off.

+ +

connection.mud-url

If unspecified, MUD URL defaults to "none".

@@ -826,7 +835,13 @@ ipv6.ip6-privacy=0

connection.mdns

-

If unspecified, the ultimate default values depends on the DNS plugin. With systemd-resolved the default currently is "no" (0) and for all other plugins also "no" (0).

+

+ Currently only the systemd-resolve DNS plugin supports this setting. + If the setting is unspecified both in the profile and in the global + default here, then the default is determined by systemd-resolved. + See MulticastDNS= in + resolved.conf(5). +

connection.mptcp-flags

@@ -905,6 +920,10 @@ ipv6.ip6-privacy=0

If left unspecified, the value 3 (fqdn-encoded,fqdn-serv-update) is used.

+

ipv4.dhcp-send-release

+

Whether the DHCP client will send RELEASE message when bringing the connection down.

+ +

ipv4.dhcp-timeout

If left unspecified, the default value for the interface type is used.

@@ -960,6 +979,10 @@ ipv6.ip6-privacy=0

If left unspecified, the value 1 (fqdn-serv-update) is used.

+

ipv6.dhcp-send-release

+

Whether the DHCP client will send RELEASE message when bringing the connection down.

+ +

ipv6.dhcp-timeout

If left unspecified, the default value for the interface type is used.

@@ -971,8 +994,23 @@ ipv6.ip6-privacy=0

ipv6.ip6-privacy

-

If ipv6.ip6-privacy is unset, use the content of - "/proc/sys/net/ipv6/conf/default/use_tempaddr" as last fallback. +

If ipv6.ip6-privacy is unset, fall back to the original + value of "/proc/sys/net/ipv6/conf/<iface>/use_tempaddr" from before NetworkManager + started. +

+ + +

ipv6.temp-valid-lifetime

+

If ipv6.temp-valid-lifetime is unset, fall back to the + original value of "/proc/sys/net/ipv6/conf/<iface>/temp_valid_lft" from before + NetworkManager started. +

+ + +

ipv6.temp-preferred-lifetime

+

If ipv6.temp-preferred-lifetime is unset, fall back to + the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_prefered_lft" from + before NetworkManager started.

diff --git a/docs/api/html/NetworkManager.devhelp2 b/docs/api/html/NetworkManager.devhelp2 index 6e0036ab..2102feb9 100644 --- a/docs/api/html/NetworkManager.devhelp2 +++ b/docs/api/html/NetworkManager.devhelp2 @@ -747,6 +747,15 @@ + + + + + + + + + @@ -803,6 +812,7 @@ + diff --git a/docs/api/html/index.html b/docs/api/html/index.html index f43e0514..6f397e91 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@

- for NetworkManager 1.46.0 + for NetworkManager 1.47.90 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 6dc24c5d..7443e3f6 100644 --- a/docs/api/html/ix01.html +++ b/docs/api/html/ix01.html @@ -780,9 +780,11 @@

dhcp-send-hostname, ipv4, ipv6
-
dhcp-timeout, ipv4, ipv6 +
dhcp-send-release, ipv4, ipv6
-
dhcp-vendor-class-identifier, ipv4 +
dhcp-timeout, ipv4, ipv6 +
+
dhcp-vendor-class-identifier, ipv4
org.freedesktop.NetworkManager.DHCP4Config, org.freedesktop.NetworkManager.DHCP4Config
@@ -792,22 +794,24 @@
org.freedesktop.NetworkManager.DHCP6Config:Options, The "Options" property
-
dns, ipv4, ipv6 +
dns, ipv4, ipv6
-
dns-data, ipv4, ipv6 +
dns-data, ipv4, ipv6
-
dns-options, ipv4, ipv6 +
dns-options, ipv4, ipv6
dns-over-tls, connection
-
dns-priority, ipv4, ipv6 +
dns-priority, ipv4, ipv6
-
dns-search, ipv4, ipv6 +
dns-search, ipv4, ipv6
domain-match, 802-1x
domain-suffix-match, 802-1x
+
down-on-poweroff, connection +
driver, match
duplex, 802-3-ethernet @@ -859,9 +863,9 @@

G

-
gateway, ipv4, ipv6 +
gateway, ipv4, ipv6
-
gateway-ping-timeout, connection +
gateway-ping-timeout, connection
generate-mac-address-mask, 802-3-ethernet, 802-11-wireless
@@ -895,13 +899,13 @@

I

-
id, connection, vlan, vxlan +
id, connection, vlan, vxlan
identity, 802-1x
-
ignore-auto-dns, ipv4, ipv6 +
ignore-auto-dns, ipv4, ipv6
-
ignore-auto-routes, ipv4, ipv6 +
ignore-auto-routes, ipv4, ipv6
ingress-priority-map, vlan
@@ -911,13 +915,13 @@
input-key, ip-tunnel
-
interface-name, connection, bond, bridge, match, team, vlan +
interface-name, connection, bond, bridge, match, team, vlan
ip4-auto-default-route, wireguard
ip6-auto-default-route, wireguard
-
ip6-privacy, ipv6 +
ip6-privacy, ipv6
@@ -957,15 +961,15 @@
limit, vxlan
-
link-local, ipv4 +
link-local, ipv4
link-watchers, team, team-port
listen-port, wireguard
-
lldp, connection +
lldp, connection
-
llmnr, connection +
llmnr, connection
local, ip-tunnel, vxlan
@@ -978,7 +982,9 @@
mac-address-blacklist, 802-3-ethernet, 802-11-wireless
-
mac-address-randomization, 802-11-wireless +
mac-address-denylist, 802-3-ethernet, 802-11-wireless +
+
mac-address-randomization, 802-11-wireless
org.freedesktop.NetworkManager, org.freedesktop.NetworkManager
@@ -1080,11 +1086,11 @@
org.freedesktop.NetworkManager:WwanHardwareEnabled, The "WwanHardwareEnabled" property
-
master, connection +
master, connection
max-age, bridge
-
may-fail, ipv4, ipv6 +
may-fail, ipv4, ipv6
mcast-rejoin-count, team
@@ -1092,11 +1098,11 @@
mcast-snooping-enable, ovs-bridge
-
mdns, connection +
mdns, connection
-
metered, connection +
metered, connection
-
method, ipv4, ipv6, proxy +
method, ipv4, ipv6, proxy
mka-cak, macsec
@@ -1108,15 +1114,15 @@
mppe-stateful, ppp
-
mptcp-flags, connection +
mptcp-flags, connection
mru, ppp
mtu, cdma, gsm, infiniband, ipv6, ip-tunnel, ppp, 802-3-ethernet, wireguard, 802-11-wireless, loopback
-
mud-url, connection +
mud-url, connection
-
multi-connect, connection +
multi-connect, connection
multi-queue, tun
@@ -1163,7 +1169,7 @@
network-name, wimax
-
never-default, ipv4, ipv6 +
never-default, ipv4, ipv6
NM80211ApFlags, enum NM80211ApFlags
@@ -1270,7 +1276,9 @@
only-from-default, hostname
-
optional, 802-1x +
openssl-ciphers, 802-1x +
+
optional, 802-1x
options, bond
@@ -1285,7 +1293,7 @@
p-key, infiniband
-
pac-file, 802-1x +
pac-file, 802-1x
pac-script, proxy
@@ -1301,13 +1309,13 @@
parity, serial
-
password, 802-1x, adsl, cdma, gsm, pppoe +
password, 802-1x, adsl, cdma, gsm, pppoe
-
password-flags, 802-1x, adsl, cdma, gsm, pppoe +
password-flags, 802-1x, adsl, cdma, gsm, pppoe
-
password-raw, 802-1x +
password-raw, 802-1x
-
password-raw-flags, 802-1x +
password-raw-flags, 802-1x
path, match
@@ -1321,67 +1329,67 @@
peers, wireguard
-
permissions, connection +
permissions, connection
persistent, vpn
-
phase1-auth-flags, 802-1x +
phase1-auth-flags, 802-1x
-
phase1-fast-provisioning, 802-1x +
phase1-fast-provisioning, 802-1x
-
phase1-peaplabel, 802-1x +
phase1-peaplabel, 802-1x
-
phase1-peapver, 802-1x +
phase1-peapver, 802-1x
-
phase2-altsubject-matches, 802-1x +
phase2-altsubject-matches, 802-1x
-
phase2-auth, 802-1x +
phase2-auth, 802-1x
-
phase2-autheap, 802-1x +
phase2-autheap, 802-1x
-
phase2-ca-cert, 802-1x +
phase2-ca-cert, 802-1x
-
phase2-ca-cert-password, 802-1x +
phase2-ca-cert-password, 802-1x
-
phase2-ca-cert-password-flags, 802-1x +
phase2-ca-cert-password-flags, 802-1x
-
phase2-ca-path, 802-1x +
phase2-ca-path, 802-1x
-
phase2-client-cert, 802-1x +
phase2-client-cert, 802-1x
-
phase2-client-cert-password, 802-1x +
phase2-client-cert-password, 802-1x
-
phase2-client-cert-password-flags, 802-1x +
phase2-client-cert-password-flags, 802-1x
-
phase2-domain-match, 802-1x +
phase2-domain-match, 802-1x
-
phase2-domain-suffix-match, 802-1x +
phase2-domain-suffix-match, 802-1x
-
phase2-private-key, 802-1x +
phase2-private-key, 802-1x
-
phase2-private-key-password, 802-1x +
phase2-private-key-password, 802-1x
-
phase2-private-key-password-flags, 802-1x +
phase2-private-key-password-flags, 802-1x
-
phase2-subject-match, 802-1x +
phase2-subject-match, 802-1x
pi, tun
-
pin, 802-1x, gsm +
pin, 802-1x, gsm
-
pin-flags, 802-1x, gsm +
pin-flags, 802-1x, gsm
pmf, 802-11-wireless-security
port, macsec, 802-3-ethernet
-
port-type, connection +
port-type, connection
port1, hsr
port2, hsr
-
powersave, 802-11-wireless +
powersave, 802-11-wireless
org.freedesktop.NetworkManager.PPP, org.freedesktop.NetworkManager.PPP
@@ -1415,13 +1423,13 @@
priority-traffic-class, dcb
-
private-key, 802-1x, wireguard +
private-key, 802-1x, wireguard
private-key-flags, wireguard
-
private-key-password, 802-1x +
private-key-password, 802-1x
-
private-key-password-flags, 802-1x +
private-key-password-flags, 802-1x
promiscuous, macvlan
@@ -1451,11 +1459,11 @@

R

-
ra-timeout, ipv6 +
ra-timeout, ipv6
-
rate, 802-11-wireless +
rate, 802-11-wireless
-
read-only, connection +
read-only, connection
refuse-chap, ppp
@@ -1469,23 +1477,23 @@
remote, ip-tunnel, vxlan
-
replace-local-rule, ipv4, ipv6 +
replace-local-rule, ipv4, ipv6
require-mppe, ppp
require-mppe-128, ppp
-
required-timeout, ipv4, ipv6 +
required-timeout, ipv4, ipv6
-
route-data, ipv4, ipv6 +
route-data, ipv4, ipv6
-
route-metric, ipv4, ipv6 +
route-metric, ipv4, ipv6
-
route-table, ipv4, ipv6 +
route-table, ipv4, ipv6
-
routes, ipv4, ipv6 +
routes, ipv4, ipv6
-
routing-rules, ipv4, ipv6 +
routing-rules, ipv4, ipv6
rsc, vxlan
@@ -1516,19 +1524,19 @@

S

-
s390-nettype, 802-3-ethernet +
s390-nettype, 802-3-ethernet
-
s390-options, 802-3-ethernet +
s390-options, 802-3-ethernet
-
s390-subchannels, 802-3-ethernet +
s390-subchannels, 802-3-ethernet
-
secondaries, connection +
secondaries, connection
secrets, vpn
-
security, 802-11-wireless +
security, 802-11-wireless
-
seen-bssids, 802-11-wireless +
seen-bssids, 802-11-wireless
send-delay, serial
@@ -1544,17 +1552,17 @@
sim-operator-id, gsm
-
slave-type, connection +
slave-type, connection
source-port-max, vxlan
source-port-min, vxlan
-
speed, 802-3-ethernet +
speed, 802-3-ethernet
ssid, 802-11-olpc-mesh, 802-11-wireless
-
stable-id, connection +
stable-id, connection
sticky, team-port
@@ -1564,9 +1572,9 @@
stp-enable, ovs-bridge
-
subject-match, 802-1x +
subject-match, 802-1x
-
system-ca-certs, 802-1x +
system-ca-certs, 802-1x
@@ -1579,13 +1587,17 @@
tap, macvlan
+
temp-preferred-lifetime, ipv6 +
+
temp-valid-lifetime, ipv6 +
tfilters, tc
timeout, vpn
-
timestamp, connection +
timestamp, connection
-
token, ipv6 +
token, ipv6
tos, ip-tunnel, vxlan
@@ -1597,11 +1609,11 @@
ttl, ip-tunnel, vxlan
-
tx-power, 802-11-wireless +
tx-power, 802-11-wireless
tx-queue-length, link
-
type, connection, bluetooth, ovs-interface +
type, connection, bluetooth, ovs-interface
@@ -1612,7 +1624,7 @@
username, adsl, cdma, gsm, pppoe
-
uuid, connection +
uuid, connection
@@ -1690,15 +1702,15 @@

W

-
wait-activation-delay, connection +
wait-activation-delay, connection
-
wait-device-timeout, connection +
wait-device-timeout, connection
-
wake-on-lan, 802-3-ethernet +
wake-on-lan, 802-3-ethernet
-
wake-on-lan-password, 802-3-ethernet +
wake-on-lan-password, 802-3-ethernet
-
wake-on-wlan, 802-11-wireless +
wake-on-wlan, 802-11-wireless
wep-key-flags, 802-11-wireless-security
@@ -1744,7 +1756,7 @@

Z

-
zone, connection +
zone, connection
diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html index 96afcda9..eba72972 100644 --- a/docs/api/html/nm-dbus-types.html +++ b/docs/api/html/nm-dbus-types.html @@ -3144,6 +3144,141 @@   + + +

NM_DEVICE_STATE_REASON_UNMANAGED_BY_DEFAULT

+

+ + +

= 69

+

+ + +

The device is unmanaged because the device type is unmanaged by default. Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_EXTERNAL_DOWN

+

+ + +

= 70

+

+ + +

The device is unmanaged because it is an external device and is unconfigured (down or without addresses). Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_LINK_NOT_INIT

+

+ + +

= 71

+

+ + +

The device is unmanaged because the link is not initialized by udev. Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_QUITTING

+

+ + +

= 72

+

+ + +

The device is unmanaged because NetworkManager is quitting. Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_SLEEPING

+

+ + +

= 73

+

+ + +

The device is unmanaged because networking is disabled or the system is suspended. Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_USER_CONF

+

+ + +

= 74

+

+ + +

The device is unmanaged by user decision in NetworkManager.conf ('unmanaged' in a [device*] section). Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_USER_EXPLICIT

+

+ + +

= 75

+

+ + +

The device is unmanaged by explicit user decision (e.g. 'nmcli device set $DEV managed no'). Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_USER_SETTINGS

+

+ + +

= 76

+

+ + +

The device is unmanaged by user decision via settings plugin ('unmanaged-devices' for keyfile or 'NM_CONTROLLED=no' for ifcfg-rh). Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_USER_UDEV

+

+ + +

= 77

+

+ + +

The device is unmanaged via udev rule. Since: 1.48

+

+ +  + @@ -3151,7 +3286,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.

@@ -4144,6 +4279,21 @@   + + +

NM_CHECKPOINT_CREATE_FLAG_TRACK_INTERNAL_GLOBAL_DNS

+

+ + +

= 0x20

+

+ + +

during rollback, by default changes to global DNS via D-BUS interface are preserved. With this flag, the rollback reverts the global DNS changes made via D-Bus interface. Global DNS defined in [global-dns] section of NetworkManager.conf is not impacted by this flag. Since: 1.48.

+

+ +  +
diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index 52539c2e..96992290 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -160,7 +160,9 @@ Depending on "connection.multi-connect", a profile can (auto)connect only once a autoconnect-slaves NMSettingConnectionAutoconnectSlaves (int32)   -Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0. +Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0. + +Deprecated 1.46. Use "autoconnect-ports" instead, this is just an alias. @@ -182,6 +184,13 @@ This feature requires a plugin which supports DNSOverTls. Otherwise, the setting +down-on-poweroff +int32 +-1 +Whether the connection will be brought down before the system is powered off. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as 0 (no). + + + gateway-ping-timeout uint32 0 @@ -239,9 +248,9 @@ Deprecated 1.46. Use "controller" instead, this is just an alias. -1 Whether mDNS is enabled for the connection. -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"). +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. -This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. +This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. Currently the only supported DNS plugin is systemd-resolved. For systemd-resolved, the default is configurable via MulticastDNS= setting in resolved.conf. @@ -556,6 +565,13 @@ Certificate data is specified using a "scheme"; two are currently supported: blo +openssl-ciphers +string +  +Define openssl_ciphers for wpa_supplicant. Openssl sometimes moves ciphers among SECLEVELs, thus compiled-in default value in wpa_supplicant (as modified by some linux distributions) sometimes prevents to connect to old servers that do not support new protocols. + + + optional boolean FALSE @@ -1822,6 +1838,13 @@ This property is currently not implemented for DHCPv6. +dhcp-send-release +NMTernary (int32) +  +Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE. + + + dhcp-timeout int32 0 @@ -2179,6 +2202,13 @@ This property is currently not implemented for DHCPv6. +dhcp-send-release +NMTernary (int32) +  +Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE. + + + dhcp-timeout int32 0 @@ -2281,9 +2311,7 @@ Note that the gateway usually conflicts with routing that NetworkManager configu   Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). -Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". - -If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". +If set to "-1" (unknown) for a connection, the value is taken from the global "ipv6.ip6-privacy" setting. If the global setting is unspecified or also set to "-1", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/use_tempaddr" from before NetworkManager started. Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses. @@ -2396,6 +2424,24 @@ Array of IPv6 route structures. Each IPv6 route structure is composed of an IPv +temp-preferred-lifetime +int32 +0 +The preferred lifetime of autogenerated temporary addresses, in seconds. + +If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-preferred-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_prefered_lft" from before NetworkManager started. + + + +temp-valid-lifetime +int32 +0 +The valid lifetime of autogenerated temporary addresses, in seconds. + +If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-valid-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_valid_lft" from before NetworkManager started. + + + token string   @@ -4230,6 +4276,13 @@ If the value contains more than one additional MAC addresses, one of them is cho +mac-address-denylist +array of string +  +If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55). + + + mtu uint32 0 @@ -4495,6 +4548,13 @@ Note that marking the network as hidden may be a privacy issue for you (in infra +mac-address-denylist +array of string +  +A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55"). + + + mac-address-randomization uint32 0 diff --git a/docs/api/html/nm-settings-ifcfg-rh.html b/docs/api/html/nm-settings-ifcfg-rh.html index 890e4643..cdeeabf6 100644 --- a/docs/api/html/nm-settings-ifcfg-rh.html +++ b/docs/api/html/nm-settings-ifcfg-rh.html @@ -354,6 +354,13 @@ Example: BSSID=00:1E:BD:64:83:21 It denies usage of the connection for any device whose address is listed. +mac-address-denylist +HWADDR_BLACKLIST(+) + +  +It denies usage of the connection for any device whose address is listed. + + seen-bssids (none)   @@ -913,6 +920,13 @@ Example: IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12   whether the 802.1X authentication is optional + +openssl-ciphers +IEEE_8021X_OPENSSL_CIPHERS(+) + +  +Cipher string for tls setup of wpa_supplicant. + @@ -982,6 +996,15 @@ Example: IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12   It denies usage of the connection for any device whose address is listed. +Example: HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55" + + +mac-address-denylist +HWADDR_BLACKLIST(+) + +  +It denies usage of the connection for any device whose address is listed. + Example: HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55" diff --git a/docs/api/html/nm-settings-keyfile.html b/docs/api/html/nm-settings-keyfile.html index 6779fa4c..d998d502 100644 --- a/docs/api/html/nm-settings-keyfile.html +++ b/docs/api/html/nm-settings-keyfile.html @@ -241,6 +241,14 @@ Example: ssid=Quick Net Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78 + +mac-address-denylist +  +list of MACs (separated with semicolons) +MAC address denylist. + +Example: mac-address-denylist= 00:22:68:12:79:A6;00:22:68:12:79:78 + @@ -280,6 +288,14 @@ Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79 Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78 + +mac-address-denylist +  +list of MACs (separated with semicolons) +MAC address denylist. + +Example: mac-address-denylist= 00:22:68:12:79:A6;00:22:68:12:79:78 + diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index 9d266d92..d91c80e3 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -141,6 +141,7 @@

connection.autoconnect-slaves

Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.

+

Deprecated 1.46. Use "autoconnect-ports" instead, this is just an alias.

Format: choice (NMSettingConnectionAutoconnectSlaves)

@@ -170,6 +171,16 @@ +

connection.down-on-poweroff

+ +

Whether the connection will be brought down before the system is powered off. The default value is "default" (-1). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as "no" (0).

+

+ Format: ternary

+

+ Valid values: true/yes/on, false/no/off, default/unknown

+ + +

connection.gateway-ping-timeout

If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.

@@ -238,8 +249,8 @@

connection.mdns

Whether mDNS is enabled for the connection.

-

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.

+

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.

+

This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. Currently the only supported DNS plugin is systemd-resolved. For systemd-resolved, the default is configurable via MulticastDNS= setting in resolved.conf.

Format: choice (NMSettingConnectionMdns)

@@ -376,7 +387,7 @@

The connection.uuid is the real identifier of a profile. It cannot change and it must be unique. It is therefore often best to refer to a profile by UUID, for example with `nmcli connection up uuid $UUID`.

The UUID cannot be changed, except in offline mode. In that case, the special values "new", "generate" and "" are allowed to generate a new random UUID.

- Format: string

+ Format: a valid RFC4122 universally unique identifier (UUID).

@@ -479,9 +490,9 @@

802-1x.ca-cert

-

Contains the CA certificate if used by the EAP method specified in the "eap" property.

-

Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

-

Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.

+

Contains the path to the CA certificate if used by the EAP method specified in the 802-1x.eap property.

+

This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

+

Note that enabling 802-1x.system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.

Format: filesystem path

@@ -516,8 +527,7 @@

802-1x.client-cert

-

Contains the client certificate if used by the EAP method specified in the "eap" property.

-

Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.

+

Contains the path to the client certificate if used by the EAP method specified in the 802-1x.eap property.

Format: filesystem path

@@ -575,6 +585,14 @@ +

802-1x.openssl-ciphers

+ +

Define openssl_ciphers for wpa_supplicant. Openssl sometimes moves ciphers among SECLEVELs, thus compiled-in default value in wpa_supplicant (as modified by some linux distributions) sometimes prevents to connect to old servers that do not support new protocols.

+

+ Format: string

+ + +

802-1x.optional

Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.

@@ -699,9 +717,9 @@

802-1x.phase2-ca-cert

-

Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.

-

Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

-

Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.

+

Contains the path to the "phase 2" CA certificate if used by the EAP method specified in the 802-1x.phase2-auth or 802-1x.phase2-autheap properties.

+

This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

+

Note that enabling 802-1x.system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.

Format: filesystem path

@@ -736,8 +754,7 @@

802-1x.phase2-client-cert

-

Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.

-

Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

+

Contains the path to the "phase 2" client certificate if used by the EAP method specified in the 802-1x.phase2-auth or 802-1x.phase2-autheap properties.

Format: filesystem path

@@ -779,8 +796,7 @@

802-1x.phase2-private-key

-

Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls".

-

Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.

+

The path to the "phase 2" inner private key when the 802-1x.phase2-auth or 802-1x.phase2-autheap property is set to "tls".

Format: filesystem path

@@ -788,7 +804,7 @@

802-1x.phase2-private-key-password

-

The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.

+

The password used to decrypt the "phase 2" private key specified in the 802-1x.phase2-private-key property. This is normally used by secret agents, not directly by users.

Format: string

@@ -835,9 +851,7 @@

802-1x.private-key

-

Contains the private key when the "eap" property is set to "tls".

-

Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.

-

WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.

+

The path to the private key when the 802-1.eap property is set to "tls".

Format: filesystem path

@@ -845,7 +859,7 @@

802-1x.private-key-password

-

The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.

+

The password used to decrypt the private key specified in the 802-1x.private-key property. This is normally used by secret agents, not directly by users.

Format: string

@@ -2772,7 +2786,7 @@ Alias: ip4

A list of IPv4 addresses and their prefix length. Multiple addresses can be separated by comma. For example "192.168.1.5/24, 10.1.0.5/24". The addresses are listed in decreasing priority, meaning the first address will be the primary address.

- Format: list of ipv4.addresses objects

+ Format: a comma separated list of addresses

@@ -2886,6 +2900,16 @@ +

ipv4.dhcp-send-release

+ +

Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is "default" (-1). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE.

+

+ Format: ternary

+

+ Valid values: true/yes/on, false/no/off, default/unknown

+ + +

ipv4.dhcp-timeout

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).

@@ -2925,7 +2949,7 @@

When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.

The valid "ipv4.dns-options" and "ipv6.dns-options" get merged together.

- Format: list of strings

+ Format: a comma separated list of DNS options

@@ -3150,7 +3174,7 @@ For details see also `man ip-route`.

- Format: list of ipv4.routes objects

+ Format: a comma separated list of routes

@@ -3166,7 +3190,7 @@ fixed priority. Example: priority 5 from 192.167.4.0/24 table 45

- Format: list of ipv4.routing-rules objects

+ Format: a comma separated list of routing rules

@@ -3196,7 +3220,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

If not specified, when creating a new profile the default is "default".

Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.

- Format: choice (NMSettingIP6ConfigAddrGenMode)

+ Format: one of "eui64" (0), "stable-privacy" (1), "default" (3) or "default-or-eui64" (2)

Valid values: eui64 (0), stable-privacy (1), default-or-eui64 (2), default (3)

@@ -3208,7 +3232,7 @@ Example: priority 5 from 192.167.4.0/24 table 45 Alias: ip6

A list of IPv6 addresses and their prefix length. Multiple addresses can be separated by comma. For example "2001:db8:85a3::8a2e:370:7334/64, 2001:db8:85a3::5/64". The addresses are listed in decreasing priority, meaning the first address will be the primary address. This can make a difference with IPv6 source address selection (RFC 6724, section 5).

- Format: list of ipv6.addresses objects

+ Format: a comma separated list of addresses

@@ -3284,6 +3308,16 @@ Example: priority 5 from 192.167.4.0/24 table 45 +

ipv6.dhcp-send-release

+ +

Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is "default" (-1). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE.

+

+ Format: ternary

+

+ Valid values: true/yes/on, false/no/off, default/unknown

+ + +

ipv6.dhcp-timeout

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).

@@ -3315,7 +3349,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.

The valid "ipv4.dns-options" and "ipv6.dns-options" get merged together.

- Format: list of strings

+ Format: a comma separated list of DNS options

@@ -3381,8 +3415,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

ipv6.ip6-privacy

Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses).

-

Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy".

-

If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr".

+

If set to "-1" (unknown) for a connection, the value is taken from the global "ipv6.ip6-privacy" setting. If the global setting is unspecified or also set to "-1", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/use_tempaddr" from before NetworkManager started.

Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.

Format: choice (NMSettingIP6ConfigPrivacy)

@@ -3554,7 +3587,7 @@ Example: priority 5 from 192.167.4.0/24 table 45 For details see also `man ip-route`.

- Format: list of ipv6.routes objects

+ Format: a comma separated list of routes

@@ -3570,7 +3603,29 @@ fixed priority. Example: priority 5 from 1:2:3::5/128 table 45

- Format: list of ipv6.routing-rules objects

+ Format: a comma separated list of routing rules

+ + + +

ipv6.temp-preferred-lifetime

+ +

The preferred lifetime of autogenerated temporary addresses, in seconds.

+

If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-preferred-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_prefered_lft" from before NetworkManager started.

+

+ Format: integer

+

+ Valid values: 0 - 2147483647

+ + + +

ipv6.temp-valid-lifetime

+ +

The valid lifetime of autogenerated temporary addresses, in seconds.

+

If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-valid-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_valid_lft" from before NetworkManager started.

+

+ Format: integer

+

+ Valid values: 0 - 2147483647

@@ -5042,7 +5097,7 @@ Linux traffic control subsystem

- Format: list of tc.qdiscs objects

+ Format: GPtrArray(NMTCQdisc)

@@ -5144,7 +5199,7 @@ Linux traffic control subsystem

- Format: list of tc.tfilters objects

+ Format: GPtrArray(NMTCTfilter)

@@ -6057,6 +6112,14 @@ Linux traffic control subsystem +

802-3-ethernet.mac-address-denylist

+ +

If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).

+

+ Format: list of MAC addresses

+ + +

802-3-ethernet.mtu

@@ -6349,6 +6412,14 @@ Linux traffic control subsystem +

802-11-wireless.mac-address-denylist

+ +

A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").

+

+ Format: list of MAC addresses

+ + +

802-11-wireless.mac-address-randomization

One of "default" (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), "never" (1) (never randomize the MAC address), or "always" (2) (always randomize the MAC address).

diff --git a/docs/api/html/settings-802-11-wireless.html b/docs/api/html/settings-802-11-wireless.html index 0d402d10..c740d610 100644 --- a/docs/api/html/settings-802-11-wireless.html +++ b/docs/api/html/settings-802-11-wireless.html @@ -136,6 +136,12 @@ Note that marking the network as hidden may be a privacy issue for you (in infra A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55"). +
mac-address-denylist
+
array of string
+

+A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply.  Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").
+
+
 
mac-address-randomization

 
uint32

 
0

diff --git a/docs/api/html/settings-802-1x.html b/docs/api/html/settings-802-1x.html
index f72bffab..e889c1be 100644
--- a/docs/api/html/settings-802-1x.html
+++ b/docs/api/html/settings-802-1x.html
@@ -146,6 +146,12 @@ Certificate data is specified using a "scheme"; two are currently supported: blo
 Identity string for EAP authentication methods.  Often the user's user or login name.
 
 
+
openssl-ciphers

+
string

+

+Define openssl_ciphers for wpa_supplicant. Openssl sometimes moves ciphers among SECLEVELs, thus compiled-in default value in wpa_supplicant (as modified by some linux distributions) sometimes prevents to connect to old servers that do not support new protocols.
+
+
 
optional

 
boolean

 
FALSE

diff --git a/docs/api/html/settings-802-3-ethernet.html b/docs/api/html/settings-802-3-ethernet.html
index a182b834..9323cf39 100644
--- a/docs/api/html/settings-802-3-ethernet.html
+++ b/docs/api/html/settings-802-3-ethernet.html
@@ -110,6 +110,12 @@ If the value contains more than one additional MAC addresses, one of them is cho
 If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
 
 
+
mac-address-denylist

+
array of string

+

+If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
+
+
 
mtu

 
uint32

 
0

diff --git a/docs/api/html/settings-connection.html b/docs/api/html/settings-connection.html
index afd9d6cc..06693539 100644
--- a/docs/api/html/settings-connection.html
+++ b/docs/api/html/settings-connection.html
@@ -97,7 +97,9 @@ Depending on "connection.multi-connect", a profile can (auto)connect only once a
 
autoconnect-slaves

 
NMSettingConnectionAutoconnectSlaves (int32)

 

-Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.
+Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.
+
+Deprecated 1.46. Use "autoconnect-ports" instead, this is just an alias.
 
 
 
controller

@@ -116,6 +118,12 @@ The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "oppor
 This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
 
 
+
down-on-poweroff

+
int32

+
-1

+Whether the connection will be brought down before the system is powered off.  The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as 0 (no).
+
+
 
gateway-ping-timeout

 
uint32

 
0

@@ -167,9 +175,9 @@ Deprecated 1.46. Use "controller" instead, this is just an alias.
 
-1

 Whether mDNS is enabled for the connection.
 
-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").
+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.
 
-This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
+This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. Currently the only supported DNS plugin is systemd-resolved. For systemd-resolved, the default is configurable via MulticastDNS= setting in resolved.conf.
 
 
 
metered

diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html
index 587db9c2..2ce34426 100644
--- a/docs/api/html/settings-ipv4.html
+++ b/docs/api/html/settings-ipv4.html
@@ -159,6 +159,12 @@ This property is currently not implemented for DHCPv6.
 If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.
 
 
+
dhcp-send-release

+
NMTernary (int32)

+

+Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE.
+
+
 
dhcp-timeout

 
int32

 
0

diff --git a/docs/api/html/settings-ipv6.html b/docs/api/html/settings-ipv6.html
index 54b78c27..ae18ca4c 100644
--- a/docs/api/html/settings-ipv6.html
+++ b/docs/api/html/settings-ipv6.html
@@ -173,6 +173,12 @@ This property is currently not implemented for DHCPv6.
 If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.
 
 
+
dhcp-send-release

+
NMTernary (int32)

+

+Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE.
+
+
 
dhcp-timeout

 
int32

 
0

@@ -266,9 +272,7 @@ Note that the gateway usually conflicts with routing that NetworkManager configu
 

 Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941.  If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64.  This enhances privacy, but could cause problems in some applications, on the other hand.  The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses).
 
-Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy".
-
-If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr".
+If set to "-1" (unknown) for a connection, the value is taken from the global "ipv6.ip6-privacy" setting. If the global setting is unspecified or also set to "-1", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/use_tempaddr" from before NetworkManager started.
 
 Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.
 
@@ -368,6 +372,22 @@ Array of IPv6 route structures.  Each IPv6 route structure is composed of an IPv
 Array of dictionaries for routing rules. Each routing rule supports the following options: action (y), dport-end (q), dport-start (q), family (i), from (s), from-len (y), fwmark (u), fwmask (u), iifname (s), invert (b), ipproto (s), oifname (s), priority (u), sport-end (q), sport-start (q), supress-prefixlength (i), table (u), to (s), tos (y), to-len (y), range-end (u), range-start (u).
 
 
+
temp-preferred-lifetime

+
int32

+
0

+The preferred lifetime of autogenerated temporary addresses, in seconds.
+
+If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-preferred-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_prefered_lft" from before NetworkManager started.
+
+
+
temp-valid-lifetime

+
int32

+
0

+The valid lifetime of autogenerated temporary addresses, in seconds.
+
+If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-valid-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_valid_lft" from before NetworkManager started.
+
+
 
token

 
string

 

-- 
cgit 1.3.0-6-gf8a5