From 88c227d90a6b7b388c5c85d72802a0ca8f05ed5c Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 13 Jan 2022 22:30:39 +0100 Subject: New upstream version 1.34.0 --- ...-org.freedesktop.NetworkManager.Device.Bond.xml | 5 +- ...rg.freedesktop.NetworkManager.Device.Bridge.xml | 5 +- ...-org.freedesktop.NetworkManager.Device.Team.xml | 5 +- .../dbus-org.freedesktop.NetworkManager.Device.xml | 14 + docs/api/html/NetworkManager.conf.html | 4 + docs/api/html/NetworkManager.devhelp2 | 2 + docs/api/html/ch01.html | 3 + ...org.freedesktop.NetworkManager.Device.Bond.html | 5 +- ...g.freedesktop.NetworkManager.Device.Bridge.html | 5 +- ...reedesktop.NetworkManager.Device.OvsBridge.html | 5 +- ....freedesktop.NetworkManager.Device.OvsPort.html | 5 +- ...org.freedesktop.NetworkManager.Device.Team.html | 5 +- ...dbus-org.freedesktop.NetworkManager.Device.html | 16 + docs/api/html/index.html | 7 +- docs/api/html/ix01.html | 52 +- docs/api/html/nm-settings-dbus.html | 49 +- docs/api/html/nm-settings-ifcfg-rh.html | 98 ++-- docs/api/html/nm-settings-nmcli.html | 535 +++++++++++++++++++-- docs/api/html/nmcli.html | 32 +- docs/api/html/ref-settings.html | 3 + docs/api/html/settings-6lowpan.html | 2 +- docs/api/html/settings-802-11-olpc-mesh.html | 2 +- .../html/settings-802-11-wireless-security.html | 2 +- docs/api/html/settings-802-11-wireless.html | 2 +- docs/api/html/settings-802-1x.html | 2 +- docs/api/html/settings-802-3-ethernet.html | 4 +- docs/api/html/settings-adsl.html | 2 +- docs/api/html/settings-bluetooth.html | 2 +- docs/api/html/settings-bond-port.html | 69 +++ docs/api/html/settings-bond.html | 2 +- docs/api/html/settings-bridge-port.html | 2 +- docs/api/html/settings-bridge.html | 2 +- docs/api/html/settings-cdma.html | 2 +- docs/api/html/settings-connection.html | 12 +- docs/api/html/settings-dcb.html | 6 +- docs/api/html/settings-dummy.html | 2 +- docs/api/html/settings-ethtool.html | 2 +- docs/api/html/settings-generic.html | 2 +- docs/api/html/settings-gsm.html | 2 +- docs/api/html/settings-hostname.html | 8 +- docs/api/html/settings-infiniband.html | 2 +- docs/api/html/settings-ip-tunnel.html | 2 +- docs/api/html/settings-ipv4.html | 2 +- docs/api/html/settings-ipv6.html | 2 +- docs/api/html/settings-macsec.html | 2 +- docs/api/html/settings-macvlan.html | 2 +- docs/api/html/settings-match.html | 2 +- docs/api/html/settings-ovs-bridge.html | 2 +- docs/api/html/settings-ovs-dpdk.html | 2 +- docs/api/html/settings-ovs-external-ids.html | 4 +- docs/api/html/settings-ovs-interface.html | 2 +- docs/api/html/settings-ovs-patch.html | 2 +- docs/api/html/settings-ovs-port.html | 2 +- docs/api/html/settings-ppp.html | 2 +- docs/api/html/settings-pppoe.html | 2 +- docs/api/html/settings-proxy.html | 2 +- docs/api/html/settings-serial.html | 2 +- docs/api/html/settings-sriov.html | 2 +- docs/api/html/settings-tc.html | 2 +- docs/api/html/settings-team-port.html | 2 +- docs/api/html/settings-team.html | 2 +- docs/api/html/settings-tun.html | 2 +- docs/api/html/settings-user.html | 2 +- docs/api/html/settings-veth.html | 4 +- docs/api/html/settings-vlan.html | 2 +- docs/api/html/settings-vpn.html | 2 +- docs/api/html/settings-vrf.html | 2 +- docs/api/html/settings-vxlan.html | 2 +- docs/api/html/settings-wifi-p2p.html | 2 +- docs/api/html/settings-wimax.html | 2 +- docs/api/html/settings-wireguard.html | 2 +- docs/api/html/settings-wpan.html | 6 +- docs/api/html/style.css | 6 +- docs/api/network-manager-docs.xml | 2 +- docs/api/settings-spec.xml | 10 +- docs/api/version.xml | 2 +- 76 files changed, 866 insertions(+), 210 deletions(-) create mode 100644 docs/api/html/settings-bond-port.html (limited to 'docs/api') diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bond.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bond.xml index c01c434f..12e733d8 100644 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bond.xml +++ b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bond.xml @@ -48,8 +48,9 @@ Carrier readable b Slaves readable ao - Array of object paths representing devices which are currently enslaved to - this device. + DEPRECATED. Use the "Ports" property in + "org.freedesktop.NetworkManager.Device" instead which exists since + version NetworkManager 1.34.0. diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml index eb26d682..23e4fd61 100644 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml +++ b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml @@ -48,8 +48,9 @@ Carrier readable b Slaves readable ao - Array of object paths representing devices which are currently enslaved to - this device. + DEPRECATED. Use the "Ports" property in + "org.freedesktop.NetworkManager.Device" instead which exists since + version NetworkManager 1.34.0. diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Team.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Team.xml index c4ede1be..6c80dad3 100644 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Team.xml +++ b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Team.xml @@ -49,8 +49,9 @@ Carrier readable b Slaves readable ao - Array of object paths representing devices which are currently enslaved to - this device. + DEPRECATED. Use the "Ports" property in + "org.freedesktop.NetworkManager.Device" instead which exists since + version NetworkManager 1.34.0. diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml index 6b4d67a7..bebd9e58 100644 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml +++ b/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml @@ -60,6 +60,7 @@ Ip6Connectivity readable u InterfaceFlags readable u HwAddress readable s +Ports readable ao @@ -545,6 +546,19 @@ HwAddress readable s Since: 1.24 + + The "Ports" property + org.freedesktop.NetworkManager.Device:Ports + +Ports readable ao + + The port devices of the controller device. + Array of object paths representing devices which are currently set as + port of this device. This replaces the 'Slaves' properties on the + device-specific D-Bus interfaces. + Since: 1.34 + + diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index e8efb5e7..d1a0cc39 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -752,6 +752,10 @@ ipv6.ip6-privacy=0

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

+

connection.dns-over-tls

+

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

+ +

connection.stable-id

diff --git a/docs/api/html/NetworkManager.devhelp2 b/docs/api/html/NetworkManager.devhelp2 index fdb8d01c..613b9266 100644 --- a/docs/api/html/NetworkManager.devhelp2 +++ b/docs/api/html/NetworkManager.devhelp2 @@ -67,6 +67,7 @@ + @@ -283,6 +284,7 @@ + diff --git a/docs/api/html/ch01.html b/docs/api/html/ch01.html index 4cbe2f6d..9863c8bd 100644 --- a/docs/api/html/ch01.html +++ b/docs/api/html/ch01.html @@ -168,6 +168,9 @@ wpan — IEEE 802.15.4 (WPAN) MAC Settings
+bond-port — Bond Port Settings +
+
hostname — Hostname settings
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Bond.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Bond.html index 941bedef..7799cb8a 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Bond.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Bond.html @@ -75,8 +75,9 @@ Carrier readable b 
 Slaves  readable   ao
-

Array of object paths representing devices which are currently enslaved to - this device. +

DEPRECATED. Use the "Ports" property in + "org.freedesktop.NetworkManager.Device" instead which exists since + version NetworkManager 1.34.0.

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Bridge.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Bridge.html index c4142b6f..43bdf84d 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Bridge.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Bridge.html @@ -75,8 +75,9 @@ Carrier readable b 
 Slaves  readable   ao
-

Array of object paths representing devices which are currently enslaved to - this device. +

DEPRECATED. Use the "Ports" property in + "org.freedesktop.NetworkManager.Device" instead which exists since + version NetworkManager 1.34.0.

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html index 117372d6..e5e0d5ab 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html @@ -49,8 +49,9 @@ 
 Slaves  readable   ao
-

Array of object paths representing ports which are currently enslaved to - this bridge. +

DEPRECATED. Use the "Ports" property in + "org.freedesktop.NetworkManager.Device" instead which exists since + version NetworkManager 1.34.0.

Since: 1.14

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html index bbae6f4a..542df52b 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html @@ -49,8 +49,9 @@ 
 Slaves  readable   ao
-

Array of object paths representing interfaces which are currently enslaved to - this port. +

DEPRECATED. Use the "Ports" property in + "org.freedesktop.NetworkManager.Device" instead which exists since + version NetworkManager 1.34.0.

Since: 1.14

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html index d9780576..ad6d735f 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html @@ -76,8 +76,9 @@ Carrier readable b 
 Slaves  readable   ao
-

Array of object paths representing devices which are currently enslaved to - this device. +

DEPRECATED. Use the "Ports" property in + "org.freedesktop.NetworkManager.Device" instead which exists since + version NetworkManager 1.34.0.

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html index 058b5b5e..2cb81d13 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html @@ -88,6 +88,7 @@ Ip6Connectivity readable u InterfaceFlags readable u HwAddress readable s +Ports readable ao
@@ -602,6 +603,21 @@ HwAddress readable s

Since: 1.24

+
+
+

The "Ports" property

+
+Ports  readable   ao
+
+

The port devices of the controller device. +

+

Array of object paths representing devices which are currently set as + port of this device. This replaces the 'Slaves' properties on the + device-specific D-Bus interfaces. +

+

Since: 1.34 +

+
diff --git a/docs/api/html/index.html b/docs/api/html/index.html index d9fbb4a1..e53118af 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,10 +16,10 @@

- for NetworkManager 1.32.12 + for NetworkManager 1.34.0 The latest version of this documentation can be found on-line at - https://developer.gnome.org/NetworkManager/stable/. + https://networkmanager.dev/docs/api/latest/.

Copyright © 2012, 2013, 2014, 2015, 2016, 2017, 2018 The NetworkManager Authors

@@ -261,6 +261,9 @@ wpan — IEEE 802.15.4 (WPAN) MAC Settings
+bond-port — Bond Port Settings +
+
hostname — Hostname settings
diff --git a/docs/api/html/ix01.html b/docs/api/html/ix01.html index 289ae66a..2ee52be7 100644 --- a/docs/api/html/ix01.html +++ b/docs/api/html/ix01.html @@ -368,6 +368,8 @@
org.freedesktop.NetworkManager.Device:PhysicalPortId, The "PhysicalPortId" property
+
org.freedesktop.NetworkManager.Device:Ports, The "Ports" property +
org.freedesktop.NetworkManager.Device:Real, The "Real" property
org.freedesktop.NetworkManager.Device:State, The "State" property @@ -760,6 +762,8 @@
dns-options, ipv4, ipv6
+
dns-over-tls, connection +
dns-priority, ipv4, ipv6
dns-search, ipv4, ipv6 @@ -802,9 +806,9 @@
forward-delay, bridge
-
from-dhcp, hostname +
from-dhcp, hostname
-
from-dns-lookup, hostname +
from-dns-lookup, hostname
fwmark, wireguard
@@ -815,7 +819,7 @@
gateway, ipv4, ipv6
-
gateway-ping-timeout, connection +
gateway-ping-timeout, connection
generate-mac-address-mask, 802-3-ethernet, 802-11-wireless
@@ -843,7 +847,7 @@

I

-
id, connection, vlan, vxlan +
id, connection, vlan, vxlan
identity, 802-1x
@@ -855,7 +859,7 @@
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
@@ -905,9 +909,9 @@
listen-port, wireguard
-
lldp, connection +
lldp, connection
-
llmnr, connection +
llmnr, connection
local, ip-tunnel, vxlan
@@ -1018,7 +1022,7 @@
org.freedesktop.NetworkManager:WwanHardwareEnabled, The "WwanHardwareEnabled" property
-
master, connection +
master, connection
max-age, bridge
@@ -1030,9 +1034,9 @@
mcast-snooping-enable, ovs-bridge
-
mdns, connection +
mdns, connection
-
metered, connection +
metered, connection
method, ipv4, ipv6, proxy
@@ -1050,9 +1054,9 @@
mtu, cdma, gsm, infiniband, ip-tunnel, ppp, 802-3-ethernet, wireguard, 802-11-wireless
-
mud-url, connection +
mud-url, connection
-
multi-connect, connection +
multi-connect, connection
multi-queue, tun
@@ -1184,7 +1188,7 @@

O

-
only-from-default, hostname +
only-from-default, hostname
optional, 802-1x
@@ -1237,7 +1241,7 @@
peers, wireguard
-
permissions, connection +
permissions, connection
persistent, vpn
@@ -1352,7 +1356,7 @@
qdiscs, tc
-
queue-id, team-port +
queue-id, team-port, bond-port
@@ -1363,7 +1367,7 @@
rate, 802-11-wireless
-
read-only, connection +
read-only, connection
refuse-chap, ppp
@@ -1426,7 +1430,7 @@
s390-subchannels, 802-3-ethernet
-
secondaries, connection +
secondaries, connection
secrets, vpn
@@ -1448,7 +1452,7 @@
sim-operator-id, gsm
-
slave-type, connection +
slave-type, connection
source-port-max, vxlan
@@ -1458,7 +1462,7 @@
ssid, 802-11-olpc-mesh, 802-11-wireless
-
stable-id, connection +
stable-id, connection
sticky, team-port
@@ -1487,7 +1491,7 @@
timeout, vpn
-
timestamp, connection +
timestamp, connection
token, ipv6
@@ -1501,7 +1505,7 @@
tx-power, 802-11-wireless
-
type, connection, bluetooth, ovs-interface +
type, connection, bluetooth, ovs-interface
@@ -1512,7 +1516,7 @@
username, adsl, cdma, gsm, pppoe
-
uuid, connection +
uuid, connection
@@ -1590,7 +1594,7 @@

W

-
wait-device-timeout, connection +
wait-device-timeout, connection
wake-on-lan, 802-3-ethernet
@@ -1642,7 +1646,7 @@

Z

-
zone, connection +
zone, connection
diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index 2fab4fd2..f9307059 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -122,14 +122,14 @@ autoconnect boolean TRUE -Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles. +Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles. autoconnect-priority int32 0 -The autoconnect priority. If the connection is set to autoconnect, connections with higher priority will be preferred. Defaults to 0. The higher number means higher priority. +The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen. @@ -147,6 +147,13 @@ +dns-over-tls +int32 +-1 +Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. + + + gateway-ping-timeout uint32 0 @@ -1155,8 +1162,8 @@ app-fcoe-mode string -"fabric" -The FCoE controller mode; either "fabric" (default) or "vn2vn". +  +The FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric". @@ -3600,7 +3607,7 @@ s390-options dict of string to string {} -Dictionary of key/value pairs of s390-specific device options. Both keys and values must be strings. Allowed keys include "portno", "layer2", "portname", "protocol", among others. Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]). +Dictionary of key/value pairs of s390-specific device options. Both keys and values must be strings. Allowed keys include "portno", "layer2", "portname", "protocol", among others. Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]). Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface. @@ -4097,7 +4104,33 @@
-

hostname setting

+

bond-port setting

+

Bond Port Settings.

+
++++++ + + + + + + + + + + + + +
Key NameValue TypeDefault ValueValue Description
+queue-iduint320The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.
+
+
+
+

hostname setting

Hostname settings.

@@ -4146,7 +4179,7 @@
-

ovs-external-ids setting

+

ovs-external-ids setting

OVS External IDs Settings.

@@ -4172,7 +4205,7 @@
-

veth setting

+

veth setting

Veth Settings.

diff --git a/docs/api/html/nm-settings-ifcfg-rh.html b/docs/api/html/nm-settings-ifcfg-rh.html index 0315a5eb..b4400d0d 100644 --- a/docs/api/html/nm-settings-ifcfg-rh.html +++ b/docs/api/html/nm-settings-ifcfg-rh.html @@ -602,7 +602,32 @@ Example: IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12

-

Table 13. bond setting

+

Table 13. bond-port setting

+
++++++ + + + + + + + + + + + + +
PropertyIfcfg-rh VariableDefaultDescription
queue-idBONDING_OPTS: queue-id=0Queue ID. + +Allowed values: 0 - 65535
+
+
+

Table 14. bond setting

@@ -627,7 +652,7 @@ Example: BONDING_OPTS="miimon=100 mode=broadcast"

-

Table 14. bridge-port setting

+

Table 15. bridge-port setting

@@ -676,7 +701,7 @@ Example: BRIDGE_PORT_VLANS="1 pvid untagged,20,300-400 untagged"

-

Table 15. bridge setting

+

Table 16. bridge setting

@@ -915,7 +940,7 @@ Example: BRIDGING_OPTS="multicast_startup_query_interval=4000"
-

Table 16. connection setting

+

Table 17. connection setting

@@ -1109,6 +1134,15 @@ Example: LLMNR=yes Allowed values: yes,no,resolve + + + + + + @@ -1133,7 +1167,7 @@ Allowed values: a valid URL that points to recommended policy fo
dns-over-tlsDNS_OVER_TLS(+) +missing variable means global defaultWhether or not DNSOverTls is enabled for the connection + +Allowed values: yes,no,opportunistic
wait-device-timeout DEVTIMEOUT(+)

-

Table 17. dcb setting

+

Table 18. dcb setting

@@ -1268,7 +1302,7 @@ Example: DCB_PG_UP2TC=01623701 used explicitly to enable DCB so that the rest of the DCB_* variables can apply.

-

Table 18. ethtool setting

+

Table 19. ethtool setting

@@ -1286,7 +1320,7 @@ Example: DCB_PG_UP2TC=01623701

-

Table 19. hostname setting

+

Table 20. hostname setting

@@ -1341,7 +1375,7 @@ Example: HOSTNAME_ONLY_FROM_DEFAULT=0,1

-

Table 20. infiniband setting

+

Table 21. infiniband setting

@@ -1396,7 +1430,7 @@ Example: PHYSDEV=ib0

-

Table 21. ipv4 setting

+

Table 22. ipv4 setting

@@ -1573,7 +1607,7 @@ Example: DHCP_VENDOR_CLASS_IDENTIFIER=foo

-

Table 22. ipv6 setting

+

Table 23. ipv6 setting

@@ -1762,7 +1796,7 @@ Example: DHCPV6_DUID=LL; DHCPV6_DUID=0301deadbeef0001; DHCPV6_DU

-

Table 23. match setting

+

Table 24. match setting

@@ -1787,7 +1821,7 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"

-

Table 24. ovs-bridge setting

+

Table 25. ovs-bridge setting

@@ -1805,7 +1839,7 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"

-

Table 25. ovs-dpdk setting

+

Table 26. ovs-dpdk setting

@@ -1823,7 +1857,7 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"

-

Table 26. ovs-external-ids setting

+

Table 27. ovs-external-ids setting

@@ -1841,7 +1875,7 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"

-

Table 27. ovs-interface setting

+

Table 28. ovs-interface setting

@@ -1859,7 +1893,7 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"

-

Table 28. ovs-patch setting

+

Table 29. ovs-patch setting

@@ -1877,7 +1911,7 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"

-

Table 29. ovs-port setting

+

Table 30. ovs-port setting

@@ -1895,7 +1929,7 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"

-

Table 30. proxy setting

+

Table 31. proxy setting

@@ -1948,7 +1982,7 @@ Example: PAC_SCRIPT=/home/joe/proxy.pac

-

Table 31. sriov setting

+

Table 32. sriov setting

@@ -1993,7 +2027,7 @@ Example: SRIOV_AUTOPROBE_DRIVERS=0,1

-

Table 32. tc setting

+

Table 33. tc setting

@@ -2030,7 +2064,7 @@ Example: FILTER1="parent ffff: matchall action simple sdata Inpu

-

Table 33. team-port setting

+

Table 34. team-port setting

@@ -2053,7 +2087,7 @@ Example: FILTER1="parent ffff: matchall action simple sdata Inpu

-

Table 34. team setting

+

Table 35. team setting

@@ -2076,7 +2110,7 @@ Example: FILTER1="parent ffff: matchall action simple sdata Inpu

-

Table 35. user setting

+

Table 36. user setting

@@ -2101,7 +2135,7 @@ Example: NM_USER_FOO__BAR=something

-

Table 36. veth setting

+

Table 37. veth setting

@@ -2119,7 +2153,7 @@ Example: NM_USER_FOO__BAR=something

-

Table 37. vlan setting

+

Table 38. vlan setting

@@ -2182,7 +2216,7 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12

-

Table 38. vrf setting

+

Table 39. vrf setting

@@ -2200,7 +2234,7 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12

-

Table 39. wifi-p2p setting

+

Table 40. wifi-p2p setting

@@ -2218,7 +2252,7 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12

-

Table 40. 802-3-ethernet setting

+

Table 41. 802-3-ethernet setting

@@ -2339,7 +2373,7 @@ Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"

-

Table 41. wireguard setting

+

Table 42. wireguard setting

@@ -2357,7 +2391,7 @@ Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"

-

Table 42. 802-11-wireless-security setting

+

Table 43. 802-11-wireless-security setting

@@ -2539,7 +2573,7 @@ Allowed values: default, disable, optional, required

-

Table 43. 802-11-wireless setting

+

Table 44. 802-11-wireless setting

@@ -2696,7 +2730,7 @@ Allowed values: "yes", "no"

-

Table 44. wpan setting

+

Table 45. wpan setting

diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index 1ce647f7..0043313f 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -91,7 +91,7 @@ @@ -99,7 +99,7 @@ @@ -121,6 +121,14 @@ + + + + @@ -408,8 +416,8 @@ @@ -474,8 +482,8 @@ @@ -492,8 +500,8 @@ @@ -574,8 +582,8 @@ @@ -608,8 +616,8 @@ @@ -650,8 +658,8 @@ @@ -676,8 +684,8 @@ @@ -702,8 +710,8 @@ @@ -764,8 +772,8 @@ @@ -1214,8 +1222,8 @@ @@ -1257,7 +1265,7 @@ @@ -1818,8 +1826,8 @@ @@ -1836,8 +1844,8 @@ @@ -2550,8 +2558,8 @@ @@ -3148,8 +3156,8 @@ @@ -3345,17 +3353,424 @@ @@ -4155,7 +4570,7 @@ @@ -4268,8 +4683,8 @@ @@ -4508,8 +4923,8 @@ @@ -4558,8 +4973,8 @@ @@ -4568,8 +4983,8 @@ @@ -4701,7 +5116,31 @@
-

hostname setting

+

bond-port setting

+

Bond Port Settings.

+

+ Properties: +

+

Alias: autoconnect

-

Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.

+

Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.

Format: boolean

autoconnect-priority

 -

The autoconnect priority. If the connection is set to autoconnect, connections with higher priority will be preferred. Defaults to 0. The higher number means higher priority.

+

The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.

Format: int32

dns-over-tls

 +

Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

+

+ Format: int32

+

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.

@@ -374,8 +382,8 @@

ca-cert-password-flags

Flags indicating how to handle the "ca-cert-password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

client-cert-password-flags

Flags indicating how to handle the "client-cert-password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

password-raw-flags

Flags indicating how to handle the "password-raw" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

phase2-ca-cert-password-flags

Flags indicating how to handle the "phase2-ca-cert-password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

phase2-client-cert-password-flags

Flags indicating how to handle the "phase2-client-cert-password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

phase2-private-key-password-flags

Flags indicating how to handle the "phase2-private-key-password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

pin-flags

Flags indicating how to handle the "pin" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

private-key-password-flags

Flags indicating how to handle the "private-key-password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

app-fcoe-mode

 -

The FCoE controller mode; either "fabric" (default) or "vn2vn".

+

The FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".

Format: string

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

pin-flags

Flags indicating how to handle the "pin" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

mka-cak-flags

Flags indicating how to handle the "mka-cak" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

qdiscs

 -

Array of TC queueing disciplines. When the "tc" setting is present, qdiscs from this property are applied upon activation. If the property is empty, all qdiscs are removed and the device will only have the default qdisc assigned by kernel according to the "net.core.default_qdisc" sysctl. If the "tc" setting is not present, NetworkManager doesn't touch the qdiscs present on the interface.

- Format: array of vardict

+Array of TC queueing disciplines. qdisc is a basic block in the +Linux traffic control subsystem +

+

+Each qdisc can be specified by the following attributes: +

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

+handle HANDLE +

+specifies the qdisc handle. A qdisc, which potentially can have children, gets +assigned a major number, called a 'handle', leaving the minor number namespace +available for classes. The handle is expressed as '10:'. It is customary to +explicitly assign a handle to qdiscs expected to have children. +

+parent HANDLE +

+specifies the handle of the parent qdisc the current qdisc must be +attached to. +

+root +

+specifies that the qdisc is attached to the root of device. +

+KIND +

+this is the qdisc kind. NetworkManager currently supports the +following kinds: fq_codel, sfq, tbf. Each qdisc kind has a +different set of parameters, described below. There are also some +kinds like pfifo, pfifo_fast, prio supported by NetworkManager +but their parameters are not supported by NetworkManager. +

+

+Parameters for 'fq_codel': +

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

+limit U32 +

+the hard limit on the real queue size. When this limit is +reached, incoming packets are dropped. Default is 10240 packets. +

+memory_limit U32 +

+sets a limit on the total number of bytes that can be queued in +this FQ-CoDel instance. The lower of the packet limit of the +limit parameter and the memory limit will be enforced. Default is +32 MB. +

+flows U32 +

+the number of flows into which the incoming packets are +classified. Due to the stochastic nature of hashing, multiple +flows may end up being hashed into the same slot. Newer flows +have priority over older ones. This parameter can be set only at +load time since memory has to be allocated for the hash table. +Default value is 1024. +

+target U32 +

+the acceptable minimum standing/persistent queue delay. This minimum +delay is identified by tracking the local minimum queue delay that packets +experience. The unit of measurement is microsecond(us). Default value is 5ms. +

+interval U32 +

+used to ensure that the measured minimum delay does not become too stale. +The minimum delay must be experienced in the last epoch of length .B +interval. It should be set on the order of the worst-case RTT +through the bottleneck to give endpoints sufficient time to +react. Default value is 100ms. +

+quantum U32 +

+the number of bytes used as 'deficit' in the fair queuing +algorithm. Default is set to 1514 bytes which corresponds to the +Ethernet MTU plus the hardware header length of 14 bytes. +

+ecn BOOL +

+can be used to mark packets instead of dropping them. ecn is turned +on by default. +

+ce_threshold U32 +

+sets a threshold above which all packets are marked with ECN +Congestion Experienced. This is useful for DCTCP-style congestion +control algorithms that require marking at very shallow queueing +thresholds. +

+

+Parameters for 'sfq': +

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

+divisor U32 +

+can be used to set a different hash table size, available +from kernel 2.6.39 onwards. The specified divisor must be +a power of two and cannot be larger than 65536. Default +value: 1024. +

+limit U32 +

+Upper limit of the SFQ. Can be used to reduce the default +length of 127 packets. +

+depth U32 +

+Limit of packets per flow. Default to +127 and can be lowered. +

+perturb_period U32 +

+Interval in seconds for queue algorithm perturbation. +Defaults to 0, which means that no perturbation occurs. Do +not set too low for each perturbation may cause some +packet reordering or losses. Advised value: 60 This value +has no effect when external flow classification is used. +Its better to increase divisor value to lower risk of hash +collisions. +

+quantum U32 +

+Amount of bytes a flow is allowed to dequeue during a +round of the round robin process. Defaults to the MTU of +the interface which is also the advised value and the +minimum value. +

+flows U32 +

+Default value is 127. +

+

+Parameters for 'tbf': +

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

+rate U64 +

+Bandwidth or rate. These parameters accept a floating +point number, possibly followed by either a unit (both SI +and IEC units supported), or a float followed by a percent +character to specify the rate as a percentage of the +device's speed. +

+burst U32 +

 +

+Also known as buffer or maxburst. Size of the bucket, in +bytes. This is the maximum amount of bytes that tokens can +be available for instantaneously. In general, larger +shaping rates require a larger buffer. For 10mbit/s on +Intel, you need at least 10kbyte buffer if you want to +reach your configured rate! +

+

+If your buffer is too small, packets may be dropped +because more tokens arrive per timer tick than fit in your +bucket. The minimum buffer size can be calculated by +dividing the rate by HZ. +

+

+Token usage calculations are performed using a table which +by default has a resolution of 8 packets. This resolution +can be changed by specifying the cell size with the burst. +For example, to specify a 6000 byte buffer with a 16 byte +cell size, set a burst of 6000/16. You will probably never +have to set this. Must be an integral power of 2. +

+

+limit U32 +

+Limit is the number of bytes that can be queued waiting +for tokens to become available. +

+latency U32 +

+specifies the maximum amount of time a packet can +sit in the TBF. The latency calculation takes into account +the size of the bucket, the rate and possibly the peakrate +(if set). The latency and limit are mutually exclusive. +

+

+ Format: GPtrArray(NMTCQdisc)

tfilters

 -

Array of TC traffic filters. When the "tc" setting is present, filters from this property are applied upon activation. If the property is empty, NetworkManager removes all the filters. If the "tc" setting is not present, NetworkManager doesn't touch the filters present on the interface.

- Format: array of vardict

+Array of TC traffic filters. Traffic control can manage the packet content during +classification by using filters. +

+

+Each tfilters can be specified by the following attributes: +

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

+handle HANDLE +

+specifies the tfilters handle. A filter is used by a classful qdisc to determine in which class +a packet will be enqueued. It is important to notice that filters reside within qdiscs. Therefore, +see qdiscs handle for detailed information. +

+parent HANDLE +

+specifies the handle of the parent qdisc the current qdisc must be +attached to. +

+root +

+specifies that the qdisc is attached to the root of device. +

+KIND +

+this is the tfilters kind. NetworkManager currently supports +following kinds: mirred, simple. Each filter kind has a +different set of actions, described below. There are also some +other kinds like matchall, basic, u32 supported by NetworkManager. +

+

+Actions for 'mirred': +

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

+egress bool +

+Define whether the packet should exit from the interface. +

+ingress bool +

+Define whether the packet should come into the interface. +

+mirror bool +

+Define whether the packet should be copied to the destination space. +

+redirect bool +

+Define whether the packet should be moved to the destination space. +

+

+Action for 'simple': +

+
++++ + + + + +

+sdata char[32] +

+The actual string to print. +

+

+ Format: GPtrArray(NMTCTfilter)

s390-options

 -

Dictionary of key/value pairs of s390-specific device options. Both keys and values must be strings. Allowed keys include "portno", "layer2", "portname", "protocol", among others. Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).

+

Dictionary of key/value pairs of s390-specific device options. Both keys and values must be strings. Allowed keys include "portno", "layer2", "portname", "protocol", among others. Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]). Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.

Format: dict of string to string

private-key-flags

Flags indicating how to handle the "private-key" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

leap-password-flags

Flags indicating how to handle the "leap-password" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

psk-flags

Flags indicating how to handle the "psk" property. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)

wep-key-flags

Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties. - See the section called “Secret flag types:” for flag values. -

+ See the section called “Secret flag types:” for flag values. +

Format: NMSettingSecretFlags (uint32)
++++ + + + + +

queue-id

 +

+ Alias: queue-id

+

The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.

+

+ Format: uint32

+
+
+
+
+

hostname setting

Hostname settings.

Properties: @@ -4749,7 +5188,7 @@

-

veth setting

+

veth setting

Veth Settings.

Properties: diff --git a/docs/api/html/nmcli.html b/docs/api/html/nmcli.html index 5e10c868..d33f9424 100644 --- a/docs/api/html/nmcli.html +++ b/docs/api/html/nmcli.html @@ -640,13 +640,13 @@ internally blocked from autoconnecting again. Hence it will not autoconnect until reboot or until the user performs an action that unblocks autoconnect, like modifying the profile or explicitly activating it.

-

In most cases you may want to use device disconnect +

In most cases you may want to use device down command instead.

The connection is identified by its name, UUID or D-Bus path. If ID is ambiguous, a keyword id, uuid, path or apath can be used.

-

See connection show above for the description of +

See connection show above for the description of the ID-specifying keywords.

If --wait option is not specified, the default timeout will be 10 seconds.

@@ -939,7 +939,7 @@

Device Management Commands

-

nmcli device { status | show | set | connect | reapply | modify | disconnect | delete | monitor | wifi | lldp } [ARGUMENTS...]

+

nmcli device { status | show | set | up | connect | reapply | modify | down | disconnect | delete | monitor | wifi | lldp } [ARGUMENTS...]

Show and manage network interfaces.

@@ -982,7 +982,7 @@ + + + + + + + +

- connect + up ifname

@@ -992,12 +992,20 @@

If no compatible connection exists, a new profile with default settings will be created and activated. This differentiates nmcli connection up ifname "$DEVICE" from - nmcli device connect "$DEVICE"

+ nmcli device up "$DEVICE"

If --wait option is not specified, the default timeout will be 90 seconds.

+ connect + ifname +

Alias for command up. Before version 1.34.0 up + was not supported.

reapply ifname @@ -1023,7 +1031,7 @@

- disconnect + down ifname...

@@ -1035,6 +1043,14 @@

+ disconnect + ifname... +

Alias for command down. Before version 1.34.0 down + was not supported.

delete ifname... @@ -1179,7 +1195,7 @@ according to Wi-Fi device capabilities and activates it on the device. The hotspot is secured with WPA if device/driver supports that, otherwise WEP is used. Use connection down or device - disconnect to stop the hotspot.

+ down to stop the hotspot.

Parameters of the hotspot can be influenced by the optional parameters:

@@ -1646,7 +1662,7 @@ - +

shows the status for all devices.

nmcli dev disconnect em2

nmcli dev down em2

disconnects a connection on interface em2 and marks the device as unavailable for auto-connecting. As a result, no connection will automatically be activated on the device until the device's 'autoconnect' is set to TRUE or diff --git a/docs/api/html/ref-settings.html b/docs/api/html/ref-settings.html index e09dc7b4..b2bacf2e 100644 --- a/docs/api/html/ref-settings.html +++ b/docs/api/html/ref-settings.html @@ -172,6 +172,9 @@ wpan — IEEE 802.15.4 (WPAN) MAC Settings

+bond-port — Bond Port Settings +
+
hostname — Hostname settings
diff --git a/docs/api/html/settings-6lowpan.html b/docs/api/html/settings-6lowpan.html index 9c89ffd6..7daf602d 100644 --- a/docs/api/html/settings-6lowpan.html +++ b/docs/api/html/settings-6lowpan.html @@ -38,7 +38,7 @@ Properties
-

Table 46. 

+

Table 47. 

diff --git a/docs/api/html/settings-802-11-olpc-mesh.html b/docs/api/html/settings-802-11-olpc-mesh.html index 2056a462..1dd33145 100644 --- a/docs/api/html/settings-802-11-olpc-mesh.html +++ b/docs/api/html/settings-802-11-olpc-mesh.html @@ -38,7 +38,7 @@ Properties
-

Table 66. 

+

Table 67. 

diff --git a/docs/api/html/settings-802-11-wireless-security.html b/docs/api/html/settings-802-11-wireless-security.html index 61fc285d..033d365e 100644 --- a/docs/api/html/settings-802-11-wireless-security.html +++ b/docs/api/html/settings-802-11-wireless-security.html @@ -38,7 +38,7 @@ Properties
-

Table 91. 

+

Table 92. 

diff --git a/docs/api/html/settings-802-11-wireless.html b/docs/api/html/settings-802-11-wireless.html index 71cafdf5..ecdbfab9 100644 --- a/docs/api/html/settings-802-11-wireless.html +++ b/docs/api/html/settings-802-11-wireless.html @@ -38,7 +38,7 @@ Properties
-

Table 90. 

+

Table 91. 

diff --git a/docs/api/html/settings-802-1x.html b/docs/api/html/settings-802-1x.html index 9747c482..a1f6f6cf 100644 --- a/docs/api/html/settings-802-1x.html +++ b/docs/api/html/settings-802-1x.html @@ -38,7 +38,7 @@ Properties
-

Table 47. 

+

Table 48. 

diff --git a/docs/api/html/settings-802-3-ethernet.html b/docs/api/html/settings-802-3-ethernet.html index 28eeeb1b..3b38ba11 100644 --- a/docs/api/html/settings-802-3-ethernet.html +++ b/docs/api/html/settings-802-3-ethernet.html @@ -38,7 +38,7 @@ Properties
-

Table 88. 

+

Table 89. 

@@ -123,7 +123,7 @@ - + diff --git a/docs/api/html/settings-adsl.html b/docs/api/html/settings-adsl.html index 1eb087dc..baa6ce9c 100644 --- a/docs/api/html/settings-adsl.html +++ b/docs/api/html/settings-adsl.html @@ -38,7 +38,7 @@ Properties
-

Table 48. 

+

Table 49. 

s390-options
 
dict of string to string
 
{}
Dictionary of key/value pairs of s390-specific device options. Both keys and values must be strings. Allowed keys include "portno", "layer2", "portname", "protocol", among others. Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).Dictionary of key/value pairs of s390-specific device options. Both keys and values must be strings. Allowed keys include "portno", "layer2", "portname", "protocol", among others. Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]). Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface. 
s390-subchannels
diff --git a/docs/api/html/settings-bluetooth.html b/docs/api/html/settings-bluetooth.html index e7ceaf7f..76216b18 100644 --- a/docs/api/html/settings-bluetooth.html +++ b/docs/api/html/settings-bluetooth.html @@ -38,7 +38,7 @@ Properties
-

Table 49. 

+

Table 50. 

diff --git a/docs/api/html/settings-bond-port.html b/docs/api/html/settings-bond-port.html new file mode 100644 index 00000000..4516d8c5 --- /dev/null +++ b/docs/api/html/settings-bond-port.html @@ -0,0 +1,69 @@ + + + + +bond-port: NetworkManager Reference Manual + + + + + + + + + +
+ + + + + + +
+
+
+ + +
+

bond-port

+

bond-port — Bond Port Settings

+
+
+

+ Properties +

+
+

Table 94. 

+
++++++ + + + + + + + + + + + + +
Key NameValue TypeDefault ValueValue Description
queue-id
uint32
0
The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.
+
+


+
+
+
+
Generated by GTK-Doc V1.33.0
+ + \ No newline at end of file diff --git a/docs/api/html/settings-bond.html b/docs/api/html/settings-bond.html index 268ae38e..77da2c93 100644 --- a/docs/api/html/settings-bond.html +++ b/docs/api/html/settings-bond.html @@ -38,7 +38,7 @@ Properties
-

Table 50. 

+

Table 51. 

diff --git a/docs/api/html/settings-bridge-port.html b/docs/api/html/settings-bridge-port.html index 6eb7d93a..5c2aa4f7 100644 --- a/docs/api/html/settings-bridge-port.html +++ b/docs/api/html/settings-bridge-port.html @@ -38,7 +38,7 @@ Properties
-

Table 52. 

+

Table 53. 

diff --git a/docs/api/html/settings-bridge.html b/docs/api/html/settings-bridge.html index 5cee3c11..b19b3f0f 100644 --- a/docs/api/html/settings-bridge.html +++ b/docs/api/html/settings-bridge.html @@ -38,7 +38,7 @@ Properties
-

Table 51. 

+

Table 52. 

diff --git a/docs/api/html/settings-cdma.html b/docs/api/html/settings-cdma.html index a32fa537..fb29acc4 100644 --- a/docs/api/html/settings-cdma.html +++ b/docs/api/html/settings-cdma.html @@ -38,7 +38,7 @@ Properties
-

Table 53. 

+

Table 54. 

diff --git a/docs/api/html/settings-connection.html b/docs/api/html/settings-connection.html index 79025e4a..0756d597 100644 --- a/docs/api/html/settings-connection.html +++ b/docs/api/html/settings-connection.html @@ -38,7 +38,7 @@ Properties
-

Table 45. 

+

Table 46. 

@@ -63,13 +63,13 @@ - + - + @@ -84,6 +84,12 @@ + + + + + + diff --git a/docs/api/html/settings-dcb.html b/docs/api/html/settings-dcb.html index d3274cf1..784cff03 100644 --- a/docs/api/html/settings-dcb.html +++ b/docs/api/html/settings-dcb.html @@ -38,7 +38,7 @@ Properties
-

Table 54. 

+

Table 55. 

autoconnect
 
boolean
 
TRUE
Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles. 
autoconnect-priority
 
int32
 
0
The autoconnect priority. If the connection is set to autoconnect, connections with higher priority will be preferred. Defaults to 0. The higher number means higher priority.The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen. 
autoconnect-retries
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. 
dns-over-tls
int32
-1
Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
gateway-ping-timeout
 
uint32
 
0
@@ -62,8 +62,8 @@ - - + + diff --git a/docs/api/html/settings-dummy.html b/docs/api/html/settings-dummy.html index 6bc0ab4d..d5c7d25c 100644 --- a/docs/api/html/settings-dummy.html +++ b/docs/api/html/settings-dummy.html @@ -38,7 +38,7 @@ Properties
-

Table 55. 

+

Table 56. 

app-fcoe-mode
 
string
"fabric"
The FCoE controller mode; either "fabric" (default) or "vn2vn".
The FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".
 

 

 
app-fcoe-priority

 
diff --git a/docs/api/html/settings-ethtool.html b/docs/api/html/settings-ethtool.html
index adf9071e..011f8cb5 100644
--- a/docs/api/html/settings-ethtool.html
+++ b/docs/api/html/settings-ethtool.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 56. 

+
Table 57. 

 

 
 

 
diff --git a/docs/api/html/settings-generic.html b/docs/api/html/settings-generic.html
index cdc71b1c..2e03accd 100644
--- a/docs/api/html/settings-generic.html
+++ b/docs/api/html/settings-generic.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 57. 

+
Table 58. 

 

 
 

 
diff --git a/docs/api/html/settings-gsm.html b/docs/api/html/settings-gsm.html
index a48daf44..a0c4cca8 100644
--- a/docs/api/html/settings-gsm.html
+++ b/docs/api/html/settings-gsm.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 58. 

+
Table 59. 

 

 
 

 
diff --git a/docs/api/html/settings-hostname.html b/docs/api/html/settings-hostname.html
index 0caf2ce7..f93dd8f9 100644
--- a/docs/api/html/settings-hostname.html
+++ b/docs/api/html/settings-hostname.html
@@ -6,7 +6,7 @@
 
-
+
@@ -21,7 +21,7 @@
 
-
+

 
 

 
 
 
 
 
 
Home
 UpPrevPrev
 Next
 

 

@@ -34,11 +34,11 @@
 

 

 

-

+

             Properties
         

 

-
Table 93. 

+
Table 95. 

 
diff --git a/docs/api/html/settings-infiniband.html b/docs/api/html/settings-infiniband.html
index 702d1bf4..b14cc1c7 100644
--- a/docs/api/html/settings-infiniband.html
+++ b/docs/api/html/settings-infiniband.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 59. 

+
Table 60. 

 

 
 

 
diff --git a/docs/api/html/settings-ip-tunnel.html b/docs/api/html/settings-ip-tunnel.html
index 929ffa40..4a154d49 100644
--- a/docs/api/html/settings-ip-tunnel.html
+++ b/docs/api/html/settings-ip-tunnel.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 62. 

+
Table 63. 

 

 
 

 
diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html
index 4f91166b..20cd3236 100644
--- a/docs/api/html/settings-ipv4.html
+++ b/docs/api/html/settings-ipv4.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 60. 

+
Table 61. 

 

 
 

 
diff --git a/docs/api/html/settings-ipv6.html b/docs/api/html/settings-ipv6.html
index 62a1be5a..af20a399 100644
--- a/docs/api/html/settings-ipv6.html
+++ b/docs/api/html/settings-ipv6.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 61. 

+
Table 62. 

 

 
 

 
diff --git a/docs/api/html/settings-macsec.html b/docs/api/html/settings-macsec.html
index ecc6f69f..de743ee4 100644
--- a/docs/api/html/settings-macsec.html
+++ b/docs/api/html/settings-macsec.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 63. 

+
Table 64. 

 

 
 

 
diff --git a/docs/api/html/settings-macvlan.html b/docs/api/html/settings-macvlan.html
index 3cf2fc00..b09ca148 100644
--- a/docs/api/html/settings-macvlan.html
+++ b/docs/api/html/settings-macvlan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 64. 

+
Table 65. 

 

 
 

 
diff --git a/docs/api/html/settings-match.html b/docs/api/html/settings-match.html
index 2a326ed8..172d0694 100644
--- a/docs/api/html/settings-match.html
+++ b/docs/api/html/settings-match.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 65. 

+
Table 66. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-bridge.html b/docs/api/html/settings-ovs-bridge.html
index 29239f40..011e49bc 100644
--- a/docs/api/html/settings-ovs-bridge.html
+++ b/docs/api/html/settings-ovs-bridge.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 67. 

+
Table 68. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-dpdk.html b/docs/api/html/settings-ovs-dpdk.html
index a40d5fd0..cd91106d 100644
--- a/docs/api/html/settings-ovs-dpdk.html
+++ b/docs/api/html/settings-ovs-dpdk.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 68. 

+
Table 69. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-external-ids.html b/docs/api/html/settings-ovs-external-ids.html
index 0ec0c4e8..1a196728 100644
--- a/docs/api/html/settings-ovs-external-ids.html
+++ b/docs/api/html/settings-ovs-external-ids.html
@@ -34,11 +34,11 @@
 

 
 


 

 

-

+

             Properties
         

 

-
Table 94. 

+
Table 96. 

 
diff --git a/docs/api/html/settings-ovs-interface.html b/docs/api/html/settings-ovs-interface.html
index 71aff775..931527db 100644
--- a/docs/api/html/settings-ovs-interface.html
+++ b/docs/api/html/settings-ovs-interface.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 69. 

+
Table 70. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-patch.html b/docs/api/html/settings-ovs-patch.html
index 9fb817bb..c916043d 100644
--- a/docs/api/html/settings-ovs-patch.html
+++ b/docs/api/html/settings-ovs-patch.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 70. 

+
Table 71. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-port.html b/docs/api/html/settings-ovs-port.html
index 56f45834..2aa91ff7 100644
--- a/docs/api/html/settings-ovs-port.html
+++ b/docs/api/html/settings-ovs-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 71. 

+
Table 72. 

 

 
 

 
diff --git a/docs/api/html/settings-ppp.html b/docs/api/html/settings-ppp.html
index faff1d83..493cf752 100644
--- a/docs/api/html/settings-ppp.html
+++ b/docs/api/html/settings-ppp.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 72. 

+
Table 73. 

 

 
 

 
diff --git a/docs/api/html/settings-pppoe.html b/docs/api/html/settings-pppoe.html
index 339e0aa9..277dde3d 100644
--- a/docs/api/html/settings-pppoe.html
+++ b/docs/api/html/settings-pppoe.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 73. 

+
Table 74. 

 

 
 

 
diff --git a/docs/api/html/settings-proxy.html b/docs/api/html/settings-proxy.html
index 3cfe06f4..8c1104d3 100644
--- a/docs/api/html/settings-proxy.html
+++ b/docs/api/html/settings-proxy.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 74. 

+
Table 75. 

 

 
 

 
diff --git a/docs/api/html/settings-serial.html b/docs/api/html/settings-serial.html
index 5caaa483..ff473d40 100644
--- a/docs/api/html/settings-serial.html
+++ b/docs/api/html/settings-serial.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 75. 

+
Table 76. 

 

 
 

 
diff --git a/docs/api/html/settings-sriov.html b/docs/api/html/settings-sriov.html
index 0317c775..9f7fded6 100644
--- a/docs/api/html/settings-sriov.html
+++ b/docs/api/html/settings-sriov.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 76. 

+
Table 77. 

 

 
 

 
diff --git a/docs/api/html/settings-tc.html b/docs/api/html/settings-tc.html
index 68379633..ebcf0f23 100644
--- a/docs/api/html/settings-tc.html
+++ b/docs/api/html/settings-tc.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 77. 

+
Table 78. 

 

 
 

 
diff --git a/docs/api/html/settings-team-port.html b/docs/api/html/settings-team-port.html
index e493d426..7fe18f0a 100644
--- a/docs/api/html/settings-team-port.html
+++ b/docs/api/html/settings-team-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 79. 

+
Table 80. 

 

 
 

 
diff --git a/docs/api/html/settings-team.html b/docs/api/html/settings-team.html
index c4ae06b0..99cd91ee 100644
--- a/docs/api/html/settings-team.html
+++ b/docs/api/html/settings-team.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 78. 

+
Table 79. 

 

 
 

 
diff --git a/docs/api/html/settings-tun.html b/docs/api/html/settings-tun.html
index 20af9291..46e23d62 100644
--- a/docs/api/html/settings-tun.html
+++ b/docs/api/html/settings-tun.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 80. 

+
Table 81. 

 

 
 

 
diff --git a/docs/api/html/settings-user.html b/docs/api/html/settings-user.html
index a00fac44..33e64f03 100644
--- a/docs/api/html/settings-user.html
+++ b/docs/api/html/settings-user.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 81. 

+
Table 82. 

 

 
 

 
diff --git a/docs/api/html/settings-veth.html b/docs/api/html/settings-veth.html
index 761b4f72..d53121c9 100644
--- a/docs/api/html/settings-veth.html
+++ b/docs/api/html/settings-veth.html
@@ -34,11 +34,11 @@
 

 
 


 

 

-

+

             Properties
         

 

-
Table 95. 

+
Table 97. 

 
diff --git a/docs/api/html/settings-vlan.html b/docs/api/html/settings-vlan.html
index 33787e8a..be1e1d1f 100644
--- a/docs/api/html/settings-vlan.html
+++ b/docs/api/html/settings-vlan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 82. 

+
Table 83. 

 

 
 

 
diff --git a/docs/api/html/settings-vpn.html b/docs/api/html/settings-vpn.html
index db059516..afd1ac72 100644
--- a/docs/api/html/settings-vpn.html
+++ b/docs/api/html/settings-vpn.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 83. 

+
Table 84. 

 

 
 

 
diff --git a/docs/api/html/settings-vrf.html b/docs/api/html/settings-vrf.html
index 839bf8c9..6c49c512 100644
--- a/docs/api/html/settings-vrf.html
+++ b/docs/api/html/settings-vrf.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 84. 

+
Table 85. 

 

 
 

 
diff --git a/docs/api/html/settings-vxlan.html b/docs/api/html/settings-vxlan.html
index 6da8eb52..a0ec0963 100644
--- a/docs/api/html/settings-vxlan.html
+++ b/docs/api/html/settings-vxlan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 85. 

+
Table 86. 

 

 
 

 
diff --git a/docs/api/html/settings-wifi-p2p.html b/docs/api/html/settings-wifi-p2p.html
index dc9c2592..9fe0a90b 100644
--- a/docs/api/html/settings-wifi-p2p.html
+++ b/docs/api/html/settings-wifi-p2p.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 86. 

+
Table 87. 

 

 
 

 
diff --git a/docs/api/html/settings-wimax.html b/docs/api/html/settings-wimax.html
index ee0f1112..d733d7fd 100644
--- a/docs/api/html/settings-wimax.html
+++ b/docs/api/html/settings-wimax.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 87. 

+
Table 88. 

 

 
 

 
diff --git a/docs/api/html/settings-wireguard.html b/docs/api/html/settings-wireguard.html
index e632ffdf..01157792 100644
--- a/docs/api/html/settings-wireguard.html
+++ b/docs/api/html/settings-wireguard.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 89. 

+
Table 90. 

 

 
 

 
diff --git a/docs/api/html/settings-wpan.html b/docs/api/html/settings-wpan.html
index 6fdbaa22..b0e3b24b 100644
--- a/docs/api/html/settings-wpan.html
+++ b/docs/api/html/settings-wpan.html
@@ -7,7 +7,7 @@
 
-
+
@@ -22,7 +22,7 @@
 
-
+

 
 

 
 
 
 
 
Home
 Up
 PrevNextNext
 

 

 

@@ -38,7 +38,7 @@
             Properties
         
 

-
Table 92. 

+
Table 93. 

 
diff --git a/docs/api/html/style.css b/docs/api/html/style.css
index c2b3cf7b..c163abaa 100644
--- a/docs/api/html/style.css
+++ b/docs/api/html/style.css
@@ -456,9 +456,9 @@ acronym,abbr
 }
 
 pre { line-height: 125%; }
-td.linenos pre { color: #000000; background-color: #f0f0f0; padding-left: 5px; padding-right: 5px; }
-span.linenos { color: #000000; background-color: #f0f0f0; padding-left: 5px; padding-right: 5px; }
-td.linenos pre.special { color: #000000; background-color: #ffffc0; padding-left: 5px; padding-right: 5px; }
+td.linenos .normal { color: inherit; background-color: transparent; padding-left: 5px; padding-right: 5px; }
+span.linenos { color: inherit; background-color: transparent; padding-left: 5px; padding-right: 5px; }
+td.linenos .special { color: #000000; background-color: #ffffc0; padding-left: 5px; padding-right: 5px; }
 span.linenos.special { color: #000000; background-color: #ffffc0; padding-left: 5px; padding-right: 5px; }
 .hll { background-color: #ffffcc }
 .c { color: #408080; font-style: italic } /* Comment */
diff --git a/docs/api/network-manager-docs.xml b/docs/api/network-manager-docs.xml
index a2fc76d7..77b7e017 100644
--- a/docs/api/network-manager-docs.xml
+++ b/docs/api/network-manager-docs.xml
@@ -9,7 +9,7 @@
     
       for NetworkManager &version;
       The latest version of this documentation can be found on-line at
-      https://developer.gnome.org/NetworkManager/stable/.
+      https://networkmanager.dev/docs/api/latest/.
     
diff --git a/docs/api/settings-spec.xml b/docs/api/settings-spec.xml
index 88502796..fed4f093 100644
--- a/docs/api/settings-spec.xml
+++ b/docs/api/settings-spec.xml
@@ -2,7 +2,7 @@
 
 Configuration SettingsconnectionGeneral Connection Profile Settings
             Properties
-        

 
 

 
     
Key NameValue TypeDefault ValueValue Descriptionauth-retriesauth-retriesint32-1The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. Currently, this only applies to 802-1x authentication.autoconnectautoconnectbooleanTRUEWhether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.autoconnect-priorityautoconnect-priorityint320The autoconnect priority. If the connection is set to autoconnect, connections with higher priority will be preferred. Defaults to 0. The higher number means higher priority.autoconnect-retriesautoconnect-retriesint32-1The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.autoconnect-slavesautoconnect-slavesNMSettingConnectionAutoconnectSlaves (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.gateway-ping-timeoutgateway-ping-timeoutuint320If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.ididstringA human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".interface-nameinterface-namestringThe name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.lldplldpint32-1Whether LLDP is enabled for the connection.llmnrllmnrint32-1Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. 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.mastermasterstringInterface name of the master device or UUID of the master connection.mdnsmdnsint32-1Whether 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.meteredmeteredNMMetered (int32)Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.mud-urlmud-urlstringIf configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". The special value "none" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".multi-connectmulti-connectint320Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.permissionspermissionsarray of stringAn array of strings defining what access a given user has to this connection.  If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list.  When this is not empty, the connection can be active only when one of the specified users is logged into an active session.  Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed.  Any other values are ignored and reserved for future use.  [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use.  All of [type], [id], and [reserved] must be valid UTF-8.read-onlyread-onlybooleanFALSEFALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.secondariessecondariesarray of stringList of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.slave-typeslave-typestringSetting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.stable-idstable-idstringThis represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret-key. The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.timestamptimestampuint640The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).typetypestringBase type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).uuiduuidstringA universally unique identifier for the connection, for example generated with libuuid.  It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network.  For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").wait-device-timeoutwait-device-timeoutint32-1Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.zonezonestringThe trust level of a the connection.  Free form case-insensitive string (for example "Home", "Work", "Public").  NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately.
6lowpan6LoWPAN Settings
+        Key NameValue TypeDefault ValueValue Descriptionauth-retriesauth-retriesint32-1The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. Currently, this only applies to 802-1x authentication.autoconnectautoconnectbooleanTRUEWhether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.autoconnect-priorityautoconnect-priorityint320The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.autoconnect-retriesautoconnect-retriesint32-1The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.autoconnect-slavesautoconnect-slavesNMSettingConnectionAutoconnectSlaves (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.dns-over-tlsdns-over-tlsint32-1Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.gateway-ping-timeoutgateway-ping-timeoutuint320If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.ididstringA human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".interface-nameinterface-namestringThe name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.lldplldpint32-1Whether LLDP is enabled for the connection.llmnrllmnrint32-1Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. 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.mastermasterstringInterface name of the master device or UUID of the master connection.mdnsmdnsint32-1Whether 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.meteredmeteredNMMetered (int32)Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.mud-urlmud-urlstringIf configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". The special value "none" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".multi-connectmulti-connectint320Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.permissionspermissionsarray of stringAn array of strings defining what access a given user has to this connection.  If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list.  When this is not empty, the connection can be active only when one of the specified users is logged into an active session.  Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed.  Any other values are ignored and reserved for future use.  [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use.  All of [type], [id], and [reserved] must be valid UTF-8.read-onlyread-onlybooleanFALSEFALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.secondariessecondariesarray of stringList of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.slave-typeslave-typestringSetting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.stable-idstable-idstringThis represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret-key. The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.timestamptimestampuint640The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).typetypestringBase type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).uuiduuidstringA universally unique identifier for the connection, for example generated with libuuid.  It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network.  For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").wait-device-timeoutwait-device-timeoutint32-1Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.zonezonestringThe trust level of a the connection.  Free form case-insensitive string (for example "Home", "Work", "Public").  NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately.
6lowpan6LoWPAN Settings
             Properties
         Key NameValue TypeDefault ValueValue DescriptionparentparentstringIf given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.
802-1xIEEE 802.1x Authentication Settings
             Properties
@@ -20,7 +20,7 @@
             Properties
         Key NameValue TypeDefault ValueValue Descriptionmtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.numbernumberstringThe number to dial to establish the connection to the CDMA-based mobile broadband network, if any.  If not specified, the default number (#777) is used when required.passwordpasswordstringThe password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.usernameusernamestringThe username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.
dcbData Center Bridging Settings
             Properties
-        Key NameValue TypeDefault ValueValue Descriptionapp-fcoe-flagsapp-fcoe-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-fcoe-modeapp-fcoe-modestring"fabric"The FCoE controller mode; either "fabric" (default) or "vn2vn".app-fcoe-priorityapp-fcoe-priorityint32-1The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.app-fip-flagsapp-fip-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-fip-priorityapp-fip-priorityint32-1The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.app-iscsi-flagsapp-iscsi-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-iscsi-priorityapp-iscsi-priorityint32-1The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.priority-bandwidthpriority-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use.  The sum of all percentages for priorities which belong to the same group must total 100 percents.priority-flow-controlpriority-flow-controlarray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.priority-flow-control-flagspriority-flow-control-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).priority-group-bandwidthpriority-group-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group.  Allowed values are 0 - 100, and the sum of all values must total 100 percents.priority-group-flagspriority-group-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).priority-group-idpriority-group-idarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID.  Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.priority-strict-bandwidthpriority-strict-bandwidtharray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.priority-traffic-classpriority-traffic-classarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.
dummyDummy Link Settings
+        Key NameValue TypeDefault ValueValue Descriptionapp-fcoe-flagsapp-fcoe-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-fcoe-modeapp-fcoe-modestringThe FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".app-fcoe-priorityapp-fcoe-priorityint32-1The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.app-fip-flagsapp-fip-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-fip-priorityapp-fip-priorityint32-1The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.app-iscsi-flagsapp-iscsi-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-iscsi-priorityapp-iscsi-priorityint32-1The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.priority-bandwidthpriority-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use.  The sum of all percentages for priorities which belong to the same group must total 100 percents.priority-flow-controlpriority-flow-controlarray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.priority-flow-control-flagspriority-flow-control-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).priority-group-bandwidthpriority-group-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group.  Allowed values are 0 - 100, and the sum of all values must total 100 percents.priority-group-flagspriority-group-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).priority-group-idpriority-group-idarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID.  Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.priority-strict-bandwidthpriority-strict-bandwidtharray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.priority-traffic-classpriority-traffic-classarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.
dummyDummy Link Settings
             Properties
         Key NameValue TypeDefault ValueValue Description
ethtoolEthtool Ethernet Settings
             Properties
@@ -88,7 +88,7 @@
             Properties
         Key NameValue TypeDefault ValueValue Descriptionmac-addressmac-addressbyte arrayIf specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing). Deprecated: 1network-namenetwork-namestringNetwork Service Provider (NSP) name of the WiMAX network this connection should use. Deprecated: 1
802-3-ethernetWired Ethernet Settings
             Properties
-        Key NameValue TypeDefault ValueValue Descriptionaccept-all-mac-addressesaccept-all-mac-addressesNMTernary (int32)When TRUE, setup the interface to accept packets for all MAC addresses. This is enabling the kernel interface flag IFF_PROMISC. When FALSE, the interface will only accept the packets with the interface destination mac address or broadcast.assigned-mac-addressassigned-mac-addressstringThe new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".auto-negotiateauto-negotiatebooleanFALSEWhen TRUE, enforce auto-negotiation of speed and duplex mode. If "speed" and "duplex" properties are both specified, only that single mode will be advertised and accepted during the link auto-negotiation process: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. When FALSE, "speed" and "duplex" properties should be both set or link configuration will be skipped.cloned-mac-addresscloned-mac-addressbyte arrayThis D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".duplexduplexstringWhen a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.generate-mac-address-maskgenerate-mac-address-maskstringWith "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.mac-addressmac-addressbyte arrayIf specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).mac-address-blacklistmac-address-blacklistarray of stringIf 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).mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.portportstringSpecific port type to use if the device supports multiple attachment methods.  One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.s390-nettypes390-nettypestrings390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.s390-optionss390-optionsdict of string to string{}Dictionary of key/value pairs of s390-specific device options.  Both keys and values must be strings.  Allowed keys include "portno", "layer2", "portname", "protocol", among others.  Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).s390-subchannelss390-subchannelsarray of stringIdentifies specific subchannels that this network device uses for communication with z/VM or s390 host.  Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels.  The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.speedspeeduint320When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.wake-on-lanwake-on-lanuint321The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).wake-on-lan-passwordwake-on-lan-passwordstringIf specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address.  If NULL, no password will be required.
wireguardWireGuard Settings
+        Key NameValue TypeDefault ValueValue Descriptionaccept-all-mac-addressesaccept-all-mac-addressesNMTernary (int32)When TRUE, setup the interface to accept packets for all MAC addresses. This is enabling the kernel interface flag IFF_PROMISC. When FALSE, the interface will only accept the packets with the interface destination mac address or broadcast.assigned-mac-addressassigned-mac-addressstringThe new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".auto-negotiateauto-negotiatebooleanFALSEWhen TRUE, enforce auto-negotiation of speed and duplex mode. If "speed" and "duplex" properties are both specified, only that single mode will be advertised and accepted during the link auto-negotiation process: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. When FALSE, "speed" and "duplex" properties should be both set or link configuration will be skipped.cloned-mac-addresscloned-mac-addressbyte arrayThis D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".duplexduplexstringWhen a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.generate-mac-address-maskgenerate-mac-address-maskstringWith "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.mac-addressmac-addressbyte arrayIf specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).mac-address-blacklistmac-address-blacklistarray of stringIf 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).mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.portportstringSpecific port type to use if the device supports multiple attachment methods.  One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.s390-nettypes390-nettypestrings390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.s390-optionss390-optionsdict of string to string{}Dictionary of key/value pairs of s390-specific device options.  Both keys and values must be strings.  Allowed keys include "portno", "layer2", "portname", "protocol", among others.  Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]). Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.s390-subchannelss390-subchannelsarray of stringIdentifies specific subchannels that this network device uses for communication with z/VM or s390 host.  Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels.  The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.speedspeeduint320When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.wake-on-lanwake-on-lanuint321The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).wake-on-lan-passwordwake-on-lan-passwordstringIf specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address.  If NULL, no password will be required.
wireguardWireGuard Settings
             Properties
         Key NameValue TypeDefault ValueValue Descriptionfwmarkfwmarkuint320The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise, it is a 32-bit fwmark for outgoing packets. Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.ip4-auto-default-routeip4-auto-default-routeNMTernary (int32)Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing". Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route. Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips.ip6-auto-default-routeip6-auto-default-routeNMTernary (int32)Like ip4-auto-default-route, but for the IPv6 default route.listen-portlisten-portuint320The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments. If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, this does not take into account the current routes at the time of activation.peer-routespeer-routesbooleanTRUEWhether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively. Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.peerspeersarray of 'a{sv}'Array of dictionaries for the WireGuard peers.private-keyprivate-keystringThe 256 bit private-key in base64 encoding.private-key-flagsprivate-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "private-key" property.
802-11-wirelessWi-Fi Settings
             Properties
@@ -96,7 +96,9 @@
             Properties
         Key NameValue TypeDefault ValueValue Descriptionauth-algauth-algstringWhen WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here.  One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP.  When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.filsfilsint320Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection.  One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported).  When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.groupgrouparray of stringA list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list.  For maximum compatibility leave this property empty.  Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".key-mgmtkey-mgmtstringKey management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only). This property must be set for any Wi-Fi connection that uses security.leap-passwordleap-passwordstringThe login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").leap-password-flagsleap-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "leap-password" property.leap-usernameleap-usernamestringThe login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").pairwisepairwisearray of stringA list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty.  Each list element may be one of "tkip" or "ccmp".pmfpmfint320Indicates whether Protected Management Frames (802.11w) must be enabled for the connection.  One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported).  When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.protoprotoarray of stringList of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN).  If not specified, both WPA and RSN connections are allowed.pskpskstringPre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.psk-flagspsk-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "psk" property.wep-key-flagswep-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.wep-key-typewep-key-typeNMWepKeyType (uint32)Controls the interpretation of WEP keys.  Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.wep-key0wep-key0stringIndex 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key1wep-key1stringIndex 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key2wep-key2stringIndex 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key3wep-key3stringIndex 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-tx-keyidxwep-tx-keyidxuint320When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here.  Valid values are 0 (default key) through 3.  Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.wps-methodwps-methoduint320Flags indicating which mode of WPS is to be used if any. There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities. WPS can be disabled by setting this property to a value of 1.
wpanIEEE 802.15.4 (WPAN) MAC Settings
             Properties
-        Key NameValue TypeDefault ValueValue Descriptionchannelchannelint32-1IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".mac-addressmac-addressstringIf specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.pagepageint32-1IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".pan-idpan-iduint3265535IEEE 802.15.4 Personal Area Network (PAN) identifier.short-addressshort-addressuint3265535Short IEEE 802.15.4 address to be used within a restricted environment.
hostnameHostname settings
+        Key NameValue TypeDefault ValueValue Descriptionchannelchannelint32-1IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".mac-addressmac-addressstringIf specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.pagepageint32-1IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".pan-idpan-iduint3265535IEEE 802.15.4 Personal Area Network (PAN) identifier.short-addressshort-addressuint3265535Short IEEE 802.15.4 address to be used within a restricted environment.
bond-portBond Port Settings
+            Properties
+        Key NameValue TypeDefault ValueValue Descriptionqueue-idqueue-iduint320The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.
hostnameHostname settings
             Properties
         Key NameValue TypeDefault ValueValue Descriptionfrom-dhcpfrom-dhcpNMTernary (int32)Whether the system hostname can be determined from DHCP on this connection. When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).from-dns-lookupfrom-dns-lookupNMTernary (int32)Whether the system hostname can be determined from reverse DNS lookup of addresses on this device. When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).only-from-defaultonly-from-defaultNMTernary (int32)If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6). If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route. When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).prioritypriorityint320The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority. If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100. Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.
ovs-external-idsOVS External IDs Settings
             Properties
diff --git a/docs/api/version.xml b/docs/api/version.xml
index 62d91158..2b17ffd5 100644
--- a/docs/api/version.xml
+++ b/docs/api/version.xml
@@ -1 +1 @@
-1.32.12
+1.34.0
-- 
cgit 1.3.0-6-gf8a5