From 70e18d99b8e3e77bb37e218d7ac582130156f8ef Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 25 Jan 2024 09:46:18 +0100 Subject: New upstream version 1.45.90 --- docs/api/html/NetworkManager-dispatcher.html | 15 +- docs/api/html/NetworkManager.conf.html | 23 +- docs/api/html/NetworkManager.devhelp2 | 14 +- docs/api/html/NetworkManager.html | 40 +- docs/api/html/ch01.html | 3 + ...org.freedesktop.NetworkManager.AccessPoint.html | 11 + ....freedesktop.NetworkManager.Device.Generic.html | 4 +- ...-org.freedesktop.NetworkManager.Device.Hsr.html | 113 ++ ...freedesktop.NetworkManager.Device.IPTunnel.html | 6 +- ...eedesktop.NetworkManager.Device.Infiniband.html | 2 +- ...g.freedesktop.NetworkManager.Device.Lowpan.html | 2 +- ...g.freedesktop.NetworkManager.Device.Macsec.html | 2 +- ....freedesktop.NetworkManager.Device.Macvlan.html | 2 +- ...rg.freedesktop.NetworkManager.Device.Modem.html | 2 +- ...freedesktop.NetworkManager.Device.OlpcMesh.html | 2 +- ...reedesktop.NetworkManager.Device.OvsBridge.html | 2 +- ....freedesktop.NetworkManager.Device.OvsPort.html | 2 +- ...org.freedesktop.NetworkManager.Device.Team.html | 2 +- ...-org.freedesktop.NetworkManager.Device.Tun.html | 2 +- ...org.freedesktop.NetworkManager.Device.Veth.html | 2 +- ...org.freedesktop.NetworkManager.Device.Vlan.html | 2 +- ...-org.freedesktop.NetworkManager.Device.Vrf.html | 2 +- ...rg.freedesktop.NetworkManager.Device.Vxlan.html | 2 +- ....freedesktop.NetworkManager.Device.WifiP2P.html | 4 +- ...reedesktop.NetworkManager.Device.WireGuard.html | 2 +- ...rg.freedesktop.NetworkManager.Device.Wired.html | 2 +- ...freedesktop.NetworkManager.Device.Wireless.html | 4 +- ...org.freedesktop.NetworkManager.Device.Wpan.html | 2 +- ...s-org.freedesktop.NetworkManager.IP4Config.html | 20 +- ...s-org.freedesktop.NetworkManager.IP6Config.html | 11 +- docs/api/html/index.html | 20 +- docs/api/html/ix01.html | 354 ++-- docs/api/html/license.html | 11 +- docs/api/html/nm-dbus-types.html | 34 +- docs/api/html/nm-openvswitch.html | 4 +- docs/api/html/nm-settings-dbus.html | 191 +- docs/api/html/nm-settings-ifcfg-rh.html | 56 +- docs/api/html/nm-settings-keyfile.html | 67 +- docs/api/html/nm-settings-nmcli.html | 2009 +++++++++++++++----- docs/api/html/nmcli-examples.html | 4 +- docs/api/html/ref-dbus-devices.html | 3 + 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 | 8 +- docs/api/html/settings-802-11-wireless.html | 16 +- 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 | 2 +- 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 | 24 +- docs/api/html/settings-dcb.html | 18 +- 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 | 6 +- docs/api/html/settings-hostname.html | 16 +- docs/api/html/settings-hsr.html | 89 + docs/api/html/settings-infiniband.html | 2 +- docs/api/html/settings-ip-tunnel.html | 8 +- docs/api/html/settings-ipv4.html | 22 +- docs/api/html/settings-ipv6.html | 20 +- docs/api/html/settings-link.html | 8 +- docs/api/html/settings-loopback.html | 4 +- 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-other-config.html | 4 +- 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 | 4 +- docs/api/html/settings-serial.html | 2 +- docs/api/html/settings-sriov.html | 8 +- 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 | 4 +- docs/api/html/settings-user.html | 2 +- docs/api/html/settings-veth.html | 4 +- docs/api/html/settings-vlan.html | 4 +- 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 | 2 +- docs/api/html/spec.html | 3 + 99 files changed, 2523 insertions(+), 885 deletions(-) create mode 100644 docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Hsr.html create mode 100644 docs/api/html/settings-hsr.html (limited to 'docs/api/html') diff --git a/docs/api/html/NetworkManager-dispatcher.html b/docs/api/html/NetworkManager-dispatcher.html index 88ed3634..b8ef62c3 100644 --- a/docs/api/html/NetworkManager-dispatcher.html +++ b/docs/api/html/NetworkManager-dispatcher.html @@ -51,8 +51,9 @@ device an operation just happened on, and second the action. For device actions, the interface is the name of the kernel interface suitable for IP configuration. Thus it is either VPN_IP_IFACE, DEVICE_IP_IFACE, or DEVICE_IFACE, as applicable. - For the hostname action the device name is always "none" - and for connectivity-change it is empty. + For the hostname action the device name is always + "none". For connectivity-change and + dns-change it is empty.

The actions are:

@@ -158,6 +159,16 @@ The connection was reapplied on the device.

+ + + +

dns-change

+ The DNS configuration has changed. This action is raised even if + NetworkManager is configured to not manage resolv.conf (for example, + via dns=none). In such case, the dispatch script can discover the + DNS configuration provided by currently active connections by + looking at file /run/NetworkManager/resolv.conf +

diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index 42c5b4b6..c8d8792f 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -452,17 +452,6 @@ no-auto-default=*

-

slaves-order

-

- This key specifies in which order slave connections are - auto-activated on boot or when the master activates - them. Allowed values are name (order - connection by interface name, the default), or - index (order slaves by their kernel - index). -

- -

firewall-backend

The firewall backend for configuring masquerading @@ -644,7 +633,9 @@ domains=ALL

and restart the daemon with systemctl restart NetworkManager. Then - reproduce the problem. You can find the logs in syslog (for example journalctl). + reproduce the problem. You can find the logs in syslog (for example + journalctl, or journalctl -u NetworkManager + to show only logs from NetworkManager).

Any settings here are overridden by the --log-level @@ -792,7 +783,7 @@ ipv6.ip6-privacy=0

Not all properties can be overwritten, only the following properties are supported to have their default values configured - (see nm-settings(5) for details). + (see nm-settings-nmcli(5) for details).

@@ -1327,7 +1318,7 @@ managed=1

Like the per-connection settings ethernet.generate-mac-address-mask and wifi.generate-mac-address-mask, this allows to configure the - generated MAC addresses during scanning. See nm-settings(5) + generated MAC addresses during scanning. See nm-settings-nmcli(5) for details.

@@ -1655,7 +1646,7 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16 private keys in plain text, so it will be made readable only to root, and the plugin will ignore files that are readable or writable by any user or group other than root. See "Secret flag types" - in nm-settings(5) + in nm-settings-nmcli(5) for how to avoid storing passwords in plain text.

@@ -1891,7 +1882,7 @@ interface-name:vboxnet*,except:interface-name:vboxnet2 nmcli(1), nmcli-examples(7), nm-online(1), - nm-settings(5), + nm-settings-nmcli(5), nm-applet(1), nm-connection-editor(1)

diff --git a/docs/api/html/NetworkManager.devhelp2 b/docs/api/html/NetworkManager.devhelp2 index 850eb5c0..252bb748 100644 --- a/docs/api/html/NetworkManager.devhelp2 +++ b/docs/api/html/NetworkManager.devhelp2 @@ -70,6 +70,7 @@ + @@ -103,6 +104,7 @@ + @@ -309,6 +311,11 @@ + + + + + @@ -474,6 +481,7 @@ + @@ -598,6 +606,7 @@ + @@ -615,8 +624,9 @@ - - + + + diff --git a/docs/api/html/NetworkManager.html b/docs/api/html/NetworkManager.html index 678e9f1c..4f2bcb04 100644 --- a/docs/api/html/NetworkManager.html +++ b/docs/api/html/NetworkManager.html @@ -177,7 +177,8 @@ - + +

NM_UNMANAGED

If set to "1" or "true", the device is @@ -186,7 +187,40 @@ nmcli device set "$DEVICE" managed yes or "device*.managed=1" in NetworkManager.conf.

- + + +

ID_NET_MANAGED_BY

+

+ If NM_UNMANAGED is set, this has no effect. Otherwise, + if the attribute is set to anything but + "org.freedesktop.NetworkManager", the device is unmanaged. +

+ + +

NM_AUTO_DEFAULT_LINK_LOCAL_ONLY

+

+ If set to "1" or "true", the + automatically generated connections "Wired connection N" will only + enable link local addressing for IPv4 and IPv6. This can be useful + on thunderbolt devices or host-to-host USB devices. +

+ + +

ID_NET_AUTO_LINK_LOCAL_ONLY

+

+ Honored and treated the same as if NM_AUTO_DEFAULT_LINK_LOCAL_ONLY + were set. +

+ + +

ID_NET_DHCP_BROADCAST

+

+ If set to "1" or "true", use + broadcast requests for DHCPv4 offers. This can make sense of devices + that can't handle unicast messages until being configured. +

+ +
@@ -344,7 +378,7 @@ nmcli(1), nmcli-examples(7), nm-online(1), - nm-settings(5), + nm-settings-nmcli(5), nm-applet(1), nm-connection-editor(1), udev(7) diff --git a/docs/api/html/ch01.html b/docs/api/html/ch01.html index a6dee91a..df0ac05d 100644 --- a/docs/api/html/ch01.html +++ b/docs/api/html/ch01.html @@ -174,6 +174,9 @@ hostname — Hostname settings
+hsr — HSR/PRP Settings +
+
link — Link settings
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.AccessPoint.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.AccessPoint.html index 31349078..2a1817fc 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.AccessPoint.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.AccessPoint.html @@ -43,6 +43,7 @@ HwAddress readable s Mode readable u MaxBitrate readable u +Bandwidth readable u Strength readable y LastSeen readable i @@ -152,6 +153,16 @@ The maximum bitrate this access point is capable of, in kilobits/second
+

The "Bandwidth" property

+
+Bandwidth  readable   u
+
+

+The bandwidth announced by the access point in MHz. +

+
+
+

The "Strength" property

 Strength  readable   y
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Generic.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Generic.html
index 654fc147..bc8f07b5 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Generic.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Generic.html
@@ -7,7 +7,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
 Home
 Up
 Prev
-Next
+Next
 
 

 

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Hsr.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Hsr.html
new file mode 100644
index 00000000..6475f3a1
--- /dev/null
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Hsr.html
@@ -0,0 +1,113 @@
+
+
+
+
+org.freedesktop.NetworkManager.Device.Hsr: NetworkManager Reference Manual
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

+

+

+
+
+

+
org.freedesktop.NetworkManager.Device.Hsr

+
org.freedesktop.NetworkManager.Device.Hsr — HSR Device.

+

+

+
Properties

+
+Port1               readable   o
+Port2               readable   o
+SupervisionAddress  readable   s
+MulticastSpec       readable   y
+Prp                 readable   b
+

+

+

+
Description

+

+

+

+

+

+

+
Property Details

+

+
The "Port1" property

+
+Port1  readable   o
+

+

+The device's port1 device.
+

+
Since 1.46

+

+

+

+
The "Port2" property

+
+Port2  readable   o
+

+

+The device's port2 device.
+

+
Since 1.46

+

+

+

+
The "SupervisionAddress" property

+
+SupervisionAddress  readable   s
+

+

+The supervision MAC address.
+

+
Since 1.46

+

+

+

+
The "MulticastSpec" property

+
+MulticastSpec  readable   y
+

+

+The last byte of the supervision address.
+

+
Since 1.46

+

+

+

+
The "Prp" property

+
+Prp  readable   b
+

+

+Whether the PRP protocol is used or not.
+

+
Since 1.46

+

+

+

+

+
Generated by GTK-Doc V1.33.1

+
+
\ No newline at end of file
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html
index 19b57766..6d88d32f 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html
@@ -6,7 +6,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
 
 Home
 Up
-Prev
+Prev
 Next
 
 

@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Mode                readable   u
 Parent              readable   o
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html
index 2aef5cdb..03a3be82 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 HwAddress  readable   s
 Carrier    readable   b
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html
index 68e709aa..84d8151a 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 HwAddress  readable   s
 Parent     readable   o
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html
index 9f868062..f0c5c0fe 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Parent         readable   o
 Sci            readable   t
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html
index b7ffeaf3..3c545c48 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Parent     readable   o
 Mode       readable   s
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html
index b55163c1..b7434e88 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 ModemCapabilities    readable   u
 CurrentCapabilities  readable   u
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html
index 631e01b3..4f302d28 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 HwAddress      readable   s
 Companion      readable   o
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 571a45e6..ad89fdce 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Slaves  readable   ao
 

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 4dcf9283..a220330d 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Slaves  readable   ao
 

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 8340f542..56feac4c 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 HwAddress  readable   s
 Carrier    readable   b
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html
index 4ff42e7a..3ab9992c 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Owner       readable   x
 Group       readable   x
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html
index d2ba1876..055bda30 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Peer  readable   o
 

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html
index 0a17c6ef..835faa63 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 HwAddress  readable   s
 Carrier    readable   b
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html
index a37962e2..936b3622 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Table  readable   u
 

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html
index 38f938f8..7b1b46a7 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Parent      readable   o
 HwAddress   readable   s
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html
index 4f99d38e..4b216327 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html
@@ -41,14 +41,14 @@
 

 

 

-
Signals

+
Signals

 
 PeerAdded   (o peer);
 PeerRemoved (o peer);
 

 

 

-
Properties

+
Properties

 
 HwAddress  readable   s
 Peers      readable   ao
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html
index ab48943e..88aa571b 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 PublicKey   readable   ay
 ListenPort  readable   q
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html
index 94fcf349..7985e8d5 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 HwAddress        readable   s
 PermHwAddress    readable   s
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html
index ba1206a8..24f66676 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html
@@ -42,14 +42,14 @@
 

 

 

-
Signals

+
Signals

 
 AccessPointAdded   (o access_point);
 AccessPointRemoved (o access_point);
 

 

 

-
Properties

+
Properties

 
 HwAddress             readable   s
 PermHwAddress         readable   s
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html
index 28bba258..28bd9568 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 HwAddress  readable   s
 

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.IP4Config.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.IP4Config.html
index ef2a7e63..8fd35c68 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.IP4Config.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.IP4Config.html
@@ -67,7 +67,10 @@ Addresses  readable   aau
 

 Array of arrays of IPv4 address/prefix/gateway. All 3 elements of each
 array are in network byte order. Essentially: [(addr, prefix, gateway),
-(addr, prefix, gateway), ...] Deprecated: use AddressData and Gateway
+(addr, prefix, gateway), ...].
+

+

+DEPRECATED: use AddressData and Gateway
 

 

 

@@ -103,7 +106,10 @@ Arrays of IPv4 route/prefix/next-hop/metric. All 4 elements of each tuple
 are in network byte order. 'route' and 'next hop' are IPv4 addresses,
 while prefix and metric are simple unsigned integers. Essentially:
 [(route, prefix, next-hop, metric), (route, prefix, next-hop, metric),
-...] Deprecated: use RouteData
+...].
+

+

+DEPRECATED: use RouteData
 

 

 

@@ -125,7 +131,10 @@ address string) and "prefix" (a uint). Some routes may include "next-hop"
 Nameservers  readable   au

-The nameservers in use. Deprecated: use NameserverData +The nameservers in use. +

+

+DEPRECATED: use NameserverData

@@ -189,7 +198,10 @@ WinsServers readable au

The Windows Internet Name Service servers associated with the connection. -Each address is in network byte order. Deprecated: use WinsServerData +Each address is in network byte order. +

+

+DEPRECATED: use WinsServerData

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.IP6Config.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.IP6Config.html index 7b5e167e..6b0d33d1 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.IP6Config.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.IP6Config.html @@ -62,8 +62,10 @@ Addresses readable a(ayuay)

-Array of tuples of IPv6 address/prefix/gateway. Deprecated: use -AddressData and Gateway. +Array of tuples of IPv6 address/prefix/gateway. +

+

+DEPRECATED: use AddressData and Gateway.

@@ -95,7 +97,10 @@ The gateway in use. Routes readable a(ayuayu)

-Tuples of IPv6 route/prefix/next-hop/metric. Deprecated: use RouteData +Tuples of IPv6 route/prefix/next-hop/metric. +

+

+DEPRECATED: use RouteData.

diff --git a/docs/api/html/index.html b/docs/api/html/index.html index 929c65da..8a02ac76 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@

- for NetworkManager 1.44.2 + for NetworkManager 1.45.90 The latest version of this documentation can be found on-line at https://networkmanager.dev/docs/api/latest/. @@ -31,17 +31,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You may obtain a copy of the GNU Free Documentation License from the Free Software - Foundation by visiting their Web site or by writing - to: - -

-


-   The Free Software Foundation, Inc.,
-   51 Franklin Street - Fifth Floor,
-   Boston, MA 02110-1301,
-   USA
-

-

+ Foundation by visiting their Web site.

@@ -270,6 +260,9 @@ hostname — Hostname settings
+hsr — HSR/PRP Settings +
+
link — Link settings
@@ -336,6 +329,9 @@ org.freedesktop.NetworkManager.Device.Generic — Unrecognized Device.
+org.freedesktop.NetworkManager.Device.Hsr — HSR Device. +
+
org.freedesktop.NetworkManager.Device.IPTunnel — IP Tunneling Device.
diff --git a/docs/api/html/ix01.html b/docs/api/html/ix01.html index e7c79395..48f7980f 100644 --- a/docs/api/html/ix01.html +++ b/docs/api/html/ix01.html @@ -28,13 +28,15 @@
org.freedesktop.NetworkManager.AccessPoint, org.freedesktop.NetworkManager.AccessPoint
+
org.freedesktop.NetworkManager.AccessPoint:Bandwidth, The "Bandwidth" property +
org.freedesktop.NetworkManager.AccessPoint:Flags, The "Flags" property
org.freedesktop.NetworkManager.AccessPoint:Frequency, The "Frequency" property
org.freedesktop.NetworkManager.AccessPoint:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.AccessPoint:LastSeen, The "LastSeen" property +
org.freedesktop.NetworkManager.AccessPoint:LastSeen, The "LastSeen" property
org.freedesktop.NetworkManager.AccessPoint:MaxBitrate, The "MaxBitrate" property
@@ -44,7 +46,7 @@
org.freedesktop.NetworkManager.AccessPoint:Ssid, The "Ssid" property
-
org.freedesktop.NetworkManager.AccessPoint:Strength, The "Strength" property +
org.freedesktop.NetworkManager.AccessPoint:Strength, The "Strength" property
org.freedesktop.NetworkManager.AccessPoint:WpaFlags, The "WpaFlags" property
@@ -102,117 +104,129 @@
org.freedesktop.NetworkManager.Device.GetAppliedConnection(), The GetAppliedConnection() method
-
org.freedesktop.NetworkManager.Device.Infiniband, org.freedesktop.NetworkManager.Device.Infiniband +
org.freedesktop.NetworkManager.Device.Hsr, org.freedesktop.NetworkManager.Device.Hsr +
+
org.freedesktop.NetworkManager.Device.Hsr:MulticastSpec, The "MulticastSpec" property +
+
org.freedesktop.NetworkManager.Device.Hsr:Port1, The "Port1" property +
+
org.freedesktop.NetworkManager.Device.Hsr:Port2, The "Port2" property +
+
org.freedesktop.NetworkManager.Device.Hsr:Prp, The "Prp" property +
+
org.freedesktop.NetworkManager.Device.Hsr:SupervisionAddress, The "SupervisionAddress" property +
+
org.freedesktop.NetworkManager.Device.Infiniband, org.freedesktop.NetworkManager.Device.Infiniband
-
org.freedesktop.NetworkManager.Device.Infiniband:Carrier, The "Carrier" property +
org.freedesktop.NetworkManager.Device.Infiniband:Carrier, The "Carrier" property
-
org.freedesktop.NetworkManager.Device.Infiniband:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.Infiniband:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.IPTunnel, org.freedesktop.NetworkManager.Device.IPTunnel +
org.freedesktop.NetworkManager.Device.IPTunnel, org.freedesktop.NetworkManager.Device.IPTunnel
-
org.freedesktop.NetworkManager.Device.IPTunnel:EncapsulationLimit, The "EncapsulationLimit" property +
org.freedesktop.NetworkManager.Device.IPTunnel:EncapsulationLimit, The "EncapsulationLimit" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:Flags, The "Flags" property +
org.freedesktop.NetworkManager.Device.IPTunnel:Flags, The "Flags" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:FlowLabel, The "FlowLabel" property +
org.freedesktop.NetworkManager.Device.IPTunnel:FlowLabel, The "FlowLabel" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:FwMark, The "FwMark" property +
org.freedesktop.NetworkManager.Device.IPTunnel:FwMark, The "FwMark" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:InputKey, The "InputKey" property +
org.freedesktop.NetworkManager.Device.IPTunnel:InputKey, The "InputKey" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:Local, The "Local" property +
org.freedesktop.NetworkManager.Device.IPTunnel:Local, The "Local" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:Mode, The "Mode" property +
org.freedesktop.NetworkManager.Device.IPTunnel:Mode, The "Mode" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:OutputKey, The "OutputKey" property +
org.freedesktop.NetworkManager.Device.IPTunnel:OutputKey, The "OutputKey" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:Parent, The "Parent" property +
org.freedesktop.NetworkManager.Device.IPTunnel:Parent, The "Parent" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:PathMtuDiscovery, The "PathMtuDiscovery" property +
org.freedesktop.NetworkManager.Device.IPTunnel:PathMtuDiscovery, The "PathMtuDiscovery" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:Remote, The "Remote" property +
org.freedesktop.NetworkManager.Device.IPTunnel:Remote, The "Remote" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:Tos, The "Tos" property +
org.freedesktop.NetworkManager.Device.IPTunnel:Tos, The "Tos" property
-
org.freedesktop.NetworkManager.Device.IPTunnel:Ttl, The "Ttl" property +
org.freedesktop.NetworkManager.Device.IPTunnel:Ttl, The "Ttl" property
-
org.freedesktop.NetworkManager.Device.Loopback, org.freedesktop.NetworkManager.Device.Loopback +
org.freedesktop.NetworkManager.Device.Loopback, org.freedesktop.NetworkManager.Device.Loopback
-
org.freedesktop.NetworkManager.Device.Lowpan, org.freedesktop.NetworkManager.Device.Lowpan +
org.freedesktop.NetworkManager.Device.Lowpan, org.freedesktop.NetworkManager.Device.Lowpan
-
org.freedesktop.NetworkManager.Device.Lowpan:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.Lowpan:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.Lowpan:Parent, The "Parent" property +
org.freedesktop.NetworkManager.Device.Lowpan:Parent, The "Parent" property
-
org.freedesktop.NetworkManager.Device.Macsec, org.freedesktop.NetworkManager.Device.Macsec +
org.freedesktop.NetworkManager.Device.Macsec, org.freedesktop.NetworkManager.Device.Macsec
-
org.freedesktop.NetworkManager.Device.Macsec:CipherSuite, The "CipherSuite" property +
org.freedesktop.NetworkManager.Device.Macsec:CipherSuite, The "CipherSuite" property
-
org.freedesktop.NetworkManager.Device.Macsec:EncodingSa, The "EncodingSa" property +
org.freedesktop.NetworkManager.Device.Macsec:EncodingSa, The "EncodingSa" property
-
org.freedesktop.NetworkManager.Device.Macsec:Encrypt, The "Encrypt" property +
org.freedesktop.NetworkManager.Device.Macsec:Encrypt, The "Encrypt" property
-
org.freedesktop.NetworkManager.Device.Macsec:Es, The "Es" property +
org.freedesktop.NetworkManager.Device.Macsec:Es, The "Es" property
-
org.freedesktop.NetworkManager.Device.Macsec:IcvLength, The "IcvLength" property +
org.freedesktop.NetworkManager.Device.Macsec:IcvLength, The "IcvLength" property
-
org.freedesktop.NetworkManager.Device.Macsec:IncludeSci, The "IncludeSci" property +
org.freedesktop.NetworkManager.Device.Macsec:IncludeSci, The "IncludeSci" property
-
org.freedesktop.NetworkManager.Device.Macsec:Parent, The "Parent" property +
org.freedesktop.NetworkManager.Device.Macsec:Parent, The "Parent" property
-
org.freedesktop.NetworkManager.Device.Macsec:Protect, The "Protect" property +
org.freedesktop.NetworkManager.Device.Macsec:Protect, The "Protect" property
-
org.freedesktop.NetworkManager.Device.Macsec:ReplayProtect, The "ReplayProtect" property +
org.freedesktop.NetworkManager.Device.Macsec:ReplayProtect, The "ReplayProtect" property
-
org.freedesktop.NetworkManager.Device.Macsec:Scb, The "Scb" property +
org.freedesktop.NetworkManager.Device.Macsec:Scb, The "Scb" property
-
org.freedesktop.NetworkManager.Device.Macsec:Sci, The "Sci" property +
org.freedesktop.NetworkManager.Device.Macsec:Sci, The "Sci" property
-
org.freedesktop.NetworkManager.Device.Macsec:Validation, The "Validation" property +
org.freedesktop.NetworkManager.Device.Macsec:Validation, The "Validation" property
-
org.freedesktop.NetworkManager.Device.Macsec:Window, The "Window" property +
org.freedesktop.NetworkManager.Device.Macsec:Window, The "Window" property
-
org.freedesktop.NetworkManager.Device.Macvlan, org.freedesktop.NetworkManager.Device.Macvlan +
org.freedesktop.NetworkManager.Device.Macvlan, org.freedesktop.NetworkManager.Device.Macvlan
-
org.freedesktop.NetworkManager.Device.Macvlan:Mode, The "Mode" property +
org.freedesktop.NetworkManager.Device.Macvlan:Mode, The "Mode" property
-
org.freedesktop.NetworkManager.Device.Macvlan:NoPromisc, The "NoPromisc" property +
org.freedesktop.NetworkManager.Device.Macvlan:NoPromisc, The "NoPromisc" property
-
org.freedesktop.NetworkManager.Device.Macvlan:Parent, The "Parent" property +
org.freedesktop.NetworkManager.Device.Macvlan:Parent, The "Parent" property
-
org.freedesktop.NetworkManager.Device.Macvlan:Tap, The "Tap" property +
org.freedesktop.NetworkManager.Device.Macvlan:Tap, The "Tap" property
-
org.freedesktop.NetworkManager.Device.Modem, org.freedesktop.NetworkManager.Device.Modem +
org.freedesktop.NetworkManager.Device.Modem, org.freedesktop.NetworkManager.Device.Modem
-
org.freedesktop.NetworkManager.Device.Modem:Apn, The "Apn" property +
org.freedesktop.NetworkManager.Device.Modem:Apn, The "Apn" property
-
org.freedesktop.NetworkManager.Device.Modem:CurrentCapabilities, The "CurrentCapabilities" property +
org.freedesktop.NetworkManager.Device.Modem:CurrentCapabilities, The "CurrentCapabilities" property
-
org.freedesktop.NetworkManager.Device.Modem:DeviceId, The "DeviceId" property +
org.freedesktop.NetworkManager.Device.Modem:DeviceId, The "DeviceId" property
-
org.freedesktop.NetworkManager.Device.Modem:ModemCapabilities, The "ModemCapabilities" property +
org.freedesktop.NetworkManager.Device.Modem:ModemCapabilities, The "ModemCapabilities" property
-
org.freedesktop.NetworkManager.Device.Modem:OperatorCode, The "OperatorCode" property +
org.freedesktop.NetworkManager.Device.Modem:OperatorCode, The "OperatorCode" property
-
org.freedesktop.NetworkManager.Device.OlpcMesh, org.freedesktop.NetworkManager.Device.OlpcMesh +
org.freedesktop.NetworkManager.Device.OlpcMesh, org.freedesktop.NetworkManager.Device.OlpcMesh
-
org.freedesktop.NetworkManager.Device.OlpcMesh:ActiveChannel, The "ActiveChannel" property +
org.freedesktop.NetworkManager.Device.OlpcMesh:ActiveChannel, The "ActiveChannel" property
-
org.freedesktop.NetworkManager.Device.OlpcMesh:Companion, The "Companion" property +
org.freedesktop.NetworkManager.Device.OlpcMesh:Companion, The "Companion" property
-
org.freedesktop.NetworkManager.Device.OlpcMesh:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.OlpcMesh:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.OvsBridge, org.freedesktop.NetworkManager.Device.OvsBridge +
org.freedesktop.NetworkManager.Device.OvsBridge, org.freedesktop.NetworkManager.Device.OvsBridge
-
org.freedesktop.NetworkManager.Device.OvsBridge:Slaves, The "Slaves" property +
org.freedesktop.NetworkManager.Device.OvsBridge:Slaves, The "Slaves" property
-
org.freedesktop.NetworkManager.Device.OvsInterface, org.freedesktop.NetworkManager.Device.OvsInterface +
org.freedesktop.NetworkManager.Device.OvsInterface, org.freedesktop.NetworkManager.Device.OvsInterface
-
org.freedesktop.NetworkManager.Device.OvsPort, org.freedesktop.NetworkManager.Device.OvsPort +
org.freedesktop.NetworkManager.Device.OvsPort, org.freedesktop.NetworkManager.Device.OvsPort
-
org.freedesktop.NetworkManager.Device.OvsPort:Slaves, The "Slaves" property +
org.freedesktop.NetworkManager.Device.OvsPort:Slaves, The "Slaves" property
-
org.freedesktop.NetworkManager.Device.Ppp, org.freedesktop.NetworkManager.Device.Ppp +
org.freedesktop.NetworkManager.Device.Ppp, org.freedesktop.NetworkManager.Device.Ppp
org.freedesktop.NetworkManager.Device.Reapply(), The Reapply() method
@@ -224,97 +238,97 @@
org.freedesktop.NetworkManager.Device.Statistics:TxBytes, The "TxBytes" property
-
org.freedesktop.NetworkManager.Device.Team, org.freedesktop.NetworkManager.Device.Team +
org.freedesktop.NetworkManager.Device.Team, org.freedesktop.NetworkManager.Device.Team
-
org.freedesktop.NetworkManager.Device.Team:Carrier, The "Carrier" property +
org.freedesktop.NetworkManager.Device.Team:Carrier, The "Carrier" property
-
org.freedesktop.NetworkManager.Device.Team:Config, The "Config" property +
org.freedesktop.NetworkManager.Device.Team:Config, The "Config" property
-
org.freedesktop.NetworkManager.Device.Team:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.Team:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.Team:Slaves, The "Slaves" property +
org.freedesktop.NetworkManager.Device.Team:Slaves, The "Slaves" property
-
org.freedesktop.NetworkManager.Device.Tun, org.freedesktop.NetworkManager.Device.Tun +
org.freedesktop.NetworkManager.Device.Tun, org.freedesktop.NetworkManager.Device.Tun
-
org.freedesktop.NetworkManager.Device.Tun:Group, The "Group" property +
org.freedesktop.NetworkManager.Device.Tun:Group, The "Group" property
-
org.freedesktop.NetworkManager.Device.Tun:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.Tun:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.Tun:Mode, The "Mode" property +
org.freedesktop.NetworkManager.Device.Tun:Mode, The "Mode" property
-
org.freedesktop.NetworkManager.Device.Tun:MultiQueue, The "MultiQueue" property +
org.freedesktop.NetworkManager.Device.Tun:MultiQueue, The "MultiQueue" property
-
org.freedesktop.NetworkManager.Device.Tun:NoPi, The "NoPi" property +
org.freedesktop.NetworkManager.Device.Tun:NoPi, The "NoPi" property
-
org.freedesktop.NetworkManager.Device.Tun:Owner, The "Owner" property +
org.freedesktop.NetworkManager.Device.Tun:Owner, The "Owner" property
-
org.freedesktop.NetworkManager.Device.Tun:VnetHdr, The "VnetHdr" property +
org.freedesktop.NetworkManager.Device.Tun:VnetHdr, The "VnetHdr" property
-
org.freedesktop.NetworkManager.Device.Veth, org.freedesktop.NetworkManager.Device.Veth +
org.freedesktop.NetworkManager.Device.Veth, org.freedesktop.NetworkManager.Device.Veth
-
org.freedesktop.NetworkManager.Device.Veth:Peer, The "Peer" property +
org.freedesktop.NetworkManager.Device.Veth:Peer, The "Peer" property
-
org.freedesktop.NetworkManager.Device.Vlan, org.freedesktop.NetworkManager.Device.Vlan +
org.freedesktop.NetworkManager.Device.Vlan, org.freedesktop.NetworkManager.Device.Vlan
-
org.freedesktop.NetworkManager.Device.Vlan:Carrier, The "Carrier" property +
org.freedesktop.NetworkManager.Device.Vlan:Carrier, The "Carrier" property
-
org.freedesktop.NetworkManager.Device.Vlan:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.Vlan:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.Vlan:Parent, The "Parent" property +
org.freedesktop.NetworkManager.Device.Vlan:Parent, The "Parent" property
-
org.freedesktop.NetworkManager.Device.Vlan:VlanId, The "VlanId" property +
org.freedesktop.NetworkManager.Device.Vlan:VlanId, The "VlanId" property
-
org.freedesktop.NetworkManager.Device.Vrf, org.freedesktop.NetworkManager.Device.Vrf +
org.freedesktop.NetworkManager.Device.Vrf, org.freedesktop.NetworkManager.Device.Vrf
-
org.freedesktop.NetworkManager.Device.Vrf:Table, The "Table" property +
org.freedesktop.NetworkManager.Device.Vrf:Table, The "Table" property
-
org.freedesktop.NetworkManager.Device.Vxlan, org.freedesktop.NetworkManager.Device.Vxlan +
org.freedesktop.NetworkManager.Device.Vxlan, org.freedesktop.NetworkManager.Device.Vxlan
-
org.freedesktop.NetworkManager.Device.Vxlan:Ageing, The "Ageing" property +
org.freedesktop.NetworkManager.Device.Vxlan:Ageing, The "Ageing" property
-
org.freedesktop.NetworkManager.Device.Vxlan:DstPort, The "DstPort" property +
org.freedesktop.NetworkManager.Device.Vxlan:DstPort, The "DstPort" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Group, The "Group" property +
org.freedesktop.NetworkManager.Device.Vxlan:Group, The "Group" property
-
org.freedesktop.NetworkManager.Device.Vxlan:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.Vxlan:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Id, The "Id" property +
org.freedesktop.NetworkManager.Device.Vxlan:Id, The "Id" property
-
org.freedesktop.NetworkManager.Device.Vxlan:L2miss, The "L2miss" property +
org.freedesktop.NetworkManager.Device.Vxlan:L2miss, The "L2miss" property
-
org.freedesktop.NetworkManager.Device.Vxlan:L3miss, The "L3miss" property +
org.freedesktop.NetworkManager.Device.Vxlan:L3miss, The "L3miss" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Learning, The "Learning" property +
org.freedesktop.NetworkManager.Device.Vxlan:Learning, The "Learning" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Limit, The "Limit" property +
org.freedesktop.NetworkManager.Device.Vxlan:Limit, The "Limit" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Local, The "Local" property +
org.freedesktop.NetworkManager.Device.Vxlan:Local, The "Local" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Parent, The "Parent" property +
org.freedesktop.NetworkManager.Device.Vxlan:Parent, The "Parent" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Proxy, The "Proxy" property +
org.freedesktop.NetworkManager.Device.Vxlan:Proxy, The "Proxy" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Rsc, The "Rsc" property +
org.freedesktop.NetworkManager.Device.Vxlan:Rsc, The "Rsc" property
-
org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMax, The "SrcPortMax" property +
org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMax, The "SrcPortMax" property
-
org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMin, The "SrcPortMin" property +
org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMin, The "SrcPortMin" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Tos, The "Tos" property +
org.freedesktop.NetworkManager.Device.Vxlan:Tos, The "Tos" property
-
org.freedesktop.NetworkManager.Device.Vxlan:Ttl, The "Ttl" property +
org.freedesktop.NetworkManager.Device.Vxlan:Ttl, The "Ttl" property
-
org.freedesktop.NetworkManager.Device.WireGuard, org.freedesktop.NetworkManager.Device.WireGuard +
org.freedesktop.NetworkManager.Device.WireGuard, org.freedesktop.NetworkManager.Device.WireGuard
-
org.freedesktop.NetworkManager.Device.WireGuard:FwMark, The "FwMark" property +
org.freedesktop.NetworkManager.Device.WireGuard:FwMark, The "FwMark" property
-
org.freedesktop.NetworkManager.Device.WireGuard:ListenPort, The "ListenPort" property +
org.freedesktop.NetworkManager.Device.WireGuard:ListenPort, The "ListenPort" property
-
org.freedesktop.NetworkManager.Device.WireGuard:PublicKey, The "PublicKey" property +
org.freedesktop.NetworkManager.Device.WireGuard:PublicKey, The "PublicKey" property
-
org.freedesktop.NetworkManager.Device.Wpan, org.freedesktop.NetworkManager.Device.Wpan +
org.freedesktop.NetworkManager.Device.Wpan, org.freedesktop.NetworkManager.Device.Wpan
-
org.freedesktop.NetworkManager.Device.Wpan:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.Wpan:HwAddress, The "HwAddress" property
org.freedesktop.NetworkManager.Device::StateChanged, The "StateChanged" signal
@@ -665,6 +679,8 @@
config, team, team-port
+
controller, connection +
crtscts, ppp
@@ -684,59 +700,59 @@
device-id, gsm
-
org.freedesktop.NetworkManager.Device.Wired, org.freedesktop.NetworkManager.Device.Wired +
org.freedesktop.NetworkManager.Device.Wired, org.freedesktop.NetworkManager.Device.Wired
-
org.freedesktop.NetworkManager.Device.Wired:Carrier, The "Carrier" property +
org.freedesktop.NetworkManager.Device.Wired:Carrier, The "Carrier" property
-
org.freedesktop.NetworkManager.Device.Wired:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.Wired:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.Wired:PermHwAddress, The "PermHwAddress" property +
org.freedesktop.NetworkManager.Device.Wired:PermHwAddress, The "PermHwAddress" property
-
org.freedesktop.NetworkManager.Device.Wired:S390Subchannels, The "S390Subchannels" property +
org.freedesktop.NetworkManager.Device.Wired:S390Subchannels, The "S390Subchannels" property
-
org.freedesktop.NetworkManager.Device.Wired:Speed, The "Speed" property +
org.freedesktop.NetworkManager.Device.Wired:Speed, The "Speed" property
-
org.freedesktop.NetworkManager.Device.Wireless, org.freedesktop.NetworkManager.Device.Wireless +
org.freedesktop.NetworkManager.Device.Wireless, org.freedesktop.NetworkManager.Device.Wireless
-
org.freedesktop.NetworkManager.Device.Wireless.GetAccessPoints(), The GetAccessPoints() method +
org.freedesktop.NetworkManager.Device.Wireless.GetAccessPoints(), The GetAccessPoints() method
-
org.freedesktop.NetworkManager.Device.Wireless.GetAllAccessPoints(), The GetAllAccessPoints() method +
org.freedesktop.NetworkManager.Device.Wireless.GetAllAccessPoints(), The GetAllAccessPoints() method
-
org.freedesktop.NetworkManager.Device.Wireless.RequestScan(), The RequestScan() method +
org.freedesktop.NetworkManager.Device.Wireless.RequestScan(), The RequestScan() method
-
org.freedesktop.NetworkManager.Device.Wireless::AccessPointAdded, The "AccessPointAdded" signal +
org.freedesktop.NetworkManager.Device.Wireless::AccessPointAdded, The "AccessPointAdded" signal
-
org.freedesktop.NetworkManager.Device.Wireless::AccessPointRemoved, The "AccessPointRemoved" signal +
org.freedesktop.NetworkManager.Device.Wireless::AccessPointRemoved, The "AccessPointRemoved" signal
-
org.freedesktop.NetworkManager.Device.Wireless:AccessPoints, The "AccessPoints" property +
org.freedesktop.NetworkManager.Device.Wireless:AccessPoints, The "AccessPoints" property
-
org.freedesktop.NetworkManager.Device.Wireless:ActiveAccessPoint, The "ActiveAccessPoint" property +
org.freedesktop.NetworkManager.Device.Wireless:ActiveAccessPoint, The "ActiveAccessPoint" property
-
org.freedesktop.NetworkManager.Device.Wireless:Bitrate, The "Bitrate" property +
org.freedesktop.NetworkManager.Device.Wireless:Bitrate, The "Bitrate" property
-
org.freedesktop.NetworkManager.Device.Wireless:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.Wireless:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.Wireless:LastScan, The "LastScan" property +
org.freedesktop.NetworkManager.Device.Wireless:LastScan, The "LastScan" property
-
org.freedesktop.NetworkManager.Device.Wireless:Mode, The "Mode" property +
org.freedesktop.NetworkManager.Device.Wireless:Mode, The "Mode" property
-
org.freedesktop.NetworkManager.Device.Wireless:PermHwAddress, The "PermHwAddress" property +
org.freedesktop.NetworkManager.Device.Wireless:PermHwAddress, The "PermHwAddress" property
-
org.freedesktop.NetworkManager.Device.Wireless:WirelessCapabilities, The "WirelessCapabilities" property +
org.freedesktop.NetworkManager.Device.Wireless:WirelessCapabilities, The "WirelessCapabilities" property
-
org.freedesktop.NetworkManager.Device.WifiP2P, org.freedesktop.NetworkManager.Device.WifiP2P +
org.freedesktop.NetworkManager.Device.WifiP2P, org.freedesktop.NetworkManager.Device.WifiP2P
-
org.freedesktop.NetworkManager.Device.WifiP2P.StartFind(), The StartFind() method +
org.freedesktop.NetworkManager.Device.WifiP2P.StartFind(), The StartFind() method
-
org.freedesktop.NetworkManager.Device.WifiP2P.StopFind(), The StopFind() method +
org.freedesktop.NetworkManager.Device.WifiP2P.StopFind(), The StopFind() method
-
org.freedesktop.NetworkManager.Device.WifiP2P::PeerAdded, The "PeerAdded" signal +
org.freedesktop.NetworkManager.Device.WifiP2P::PeerAdded, The "PeerAdded" signal
-
org.freedesktop.NetworkManager.Device.WifiP2P::PeerRemoved, The "PeerRemoved" signal +
org.freedesktop.NetworkManager.Device.WifiP2P::PeerRemoved, The "PeerRemoved" signal
-
org.freedesktop.NetworkManager.Device.WifiP2P:HwAddress, The "HwAddress" property +
org.freedesktop.NetworkManager.Device.WifiP2P:HwAddress, The "HwAddress" property
-
org.freedesktop.NetworkManager.Device.WifiP2P:Peers, The "Peers" property +
org.freedesktop.NetworkManager.Device.WifiP2P:Peers, The "Peers" property
dhcp-anycast-address, 802-11-olpc-mesh
@@ -776,7 +792,7 @@
dns-options, ipv4, ipv6
-
dns-over-tls, connection +
dns-over-tls, connection
dns-priority, ipv4, ipv6
@@ -833,11 +849,11 @@
gateway, ipv4, ipv6
-
gateway-ping-timeout, connection +
gateway-ping-timeout, connection
generate-mac-address-mask, 802-3-ethernet, 802-11-wireless
-
gro-max-size, link +
gro-max-size, link
group, tun, 802-11-wireless-security
@@ -845,9 +861,9 @@
group-forward-mask, bridge
-
gso-max-segments, link +
gso-max-segments, link
-
gso-max-size, link +
gso-max-size, link
@@ -867,7 +883,7 @@

I

-
id, connection, vlan, vxlan +
id, connection, vlan, vxlan
identity, 802-1x
@@ -883,7 +899,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
@@ -935,9 +951,9 @@
listen-port, wireguard
-
lldp, connection +
lldp, connection
-
llmnr, connection +
llmnr, connection
local, ip-tunnel, vxlan
@@ -1052,7 +1068,7 @@
org.freedesktop.NetworkManager:WwanHardwareEnabled, The "WwanHardwareEnabled" property
-
master, connection +
master, connection
max-age, bridge
@@ -1064,9 +1080,9 @@
mcast-snooping-enable, ovs-bridge
-
mdns, connection +
mdns, connection
-
metered, connection +
metered, connection
method, ipv4, ipv6, proxy
@@ -1080,15 +1096,15 @@
mppe-stateful, ppp
-
mptcp-flags, connection +
mptcp-flags, connection
mru, ppp
mtu, cdma, gsm, infiniband, ipv6, ip-tunnel, ppp, 802-3-ethernet, wireguard, 802-11-wireless, loopback
-
mud-url, connection +
mud-url, connection
-
multi-connect, connection +
multi-connect, connection
multi-queue, tun
@@ -1114,6 +1130,8 @@
multicast-snooping, bridge
+
multicast-spec, hsr +
multicast-startup-query-count, bridge
multicast-startup-query-interval, bridge @@ -1289,7 +1307,7 @@
peers, wireguard
-
permissions, connection +
permissions, connection
persistent, vpn
@@ -1343,19 +1361,25 @@
port, macsec, 802-3-ethernet
+
port-type, connection +
+
port1, hsr +
+
port2, hsr +
powersave, 802-11-wireless
-
org.freedesktop.NetworkManager.PPP, org.freedesktop.NetworkManager.PPP +
org.freedesktop.NetworkManager.PPP, org.freedesktop.NetworkManager.PPP
-
org.freedesktop.NetworkManager.PPP.NeedSecrets(), The NeedSecrets() method +
org.freedesktop.NetworkManager.PPP.NeedSecrets(), The NeedSecrets() method
-
org.freedesktop.NetworkManager.PPP.SetIfindex(), The SetIfindex() method +
org.freedesktop.NetworkManager.PPP.SetIfindex(), The SetIfindex() method
-
org.freedesktop.NetworkManager.PPP.SetIp4Config(), The SetIp4Config() method +
org.freedesktop.NetworkManager.PPP.SetIp4Config(), The SetIp4Config() method
-
org.freedesktop.NetworkManager.PPP.SetIp6Config(), The SetIp6Config() method +
org.freedesktop.NetworkManager.PPP.SetIp6Config(), The SetIp6Config() method
-
org.freedesktop.NetworkManager.PPP.SetState(), The SetState() method +
org.freedesktop.NetworkManager.PPP.SetState(), The SetState() method
prio, team-port, bond-port
@@ -1393,6 +1417,8 @@
proxy, vxlan
+
prp, hsr +
psk, 802-11-wireless-security
psk-flags, 802-11-wireless-security @@ -1415,7 +1441,7 @@
rate, 802-11-wireless
-
read-only, connection +
read-only, connection
refuse-chap, ppp
@@ -1482,7 +1508,7 @@
s390-subchannels, 802-3-ethernet
-
secondaries, connection +
secondaries, connection
secrets, vpn
@@ -1504,7 +1530,7 @@
sim-operator-id, gsm
-
slave-type, connection +
slave-type, connection
source-port-max, vxlan
@@ -1514,7 +1540,7 @@
ssid, 802-11-olpc-mesh, 802-11-wireless
-
stable-id, connection +
stable-id, connection
sticky, team-port
@@ -1543,7 +1569,7 @@
timeout, vpn
-
timestamp, connection +
timestamp, connection
token, ipv6
@@ -1559,9 +1585,9 @@
tx-power, 802-11-wireless
-
tx-queue-length, link +
tx-queue-length, link
-
type, connection, bluetooth, ovs-interface +
type, connection, bluetooth, ovs-interface
@@ -1572,7 +1598,7 @@
username, adsl, cdma, gsm, pppoe
-
uuid, connection +
uuid, connection
@@ -1650,9 +1676,9 @@

W

-
wait-activation-delay, connection +
wait-activation-delay, connection
-
wait-device-timeout, connection +
wait-device-timeout, connection
wake-on-lan, 802-3-ethernet
@@ -1704,7 +1730,7 @@

Z

-
zone, connection +
zone, connection
diff --git a/docs/api/html/license.html b/docs/api/html/license.html index e1b68486..2295747f 100644 --- a/docs/api/html/license.html +++ b/docs/api/html/license.html @@ -37,16 +37,7 @@

You should have received a copy of the GNU - General Public License along with this program; - if not, write to the -

-


-        Free Software Foundation, Inc.,
-        51 Franklin Street - Fifth Floor,
-        Boston, MA 02110-1301,
-        USA
-      

-

+ General Public License along with this program.

A copy of the GNU General Public License diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html index 287647e3..c494bce2 100644 --- a/docs/api/html/nm-dbus-types.html +++ b/docs/api/html/nm-dbus-types.html @@ -840,6 +840,21 @@   + + +

NM_DEVICE_TYPE_HSR

+

+ + +

= 33

+

+ + +

A HSR/PRP device. Since: 1.46.

+

+ +  + @@ -1135,6 +1150,21 @@ +

NM_WIFI_DEVICE_CAP_FREQ_6GHZ

+

+ + +

= 0x00000800

+

+ + +

device supports 6GHz frequencies. Since: 1.46.

+

+ +  + + +

NM_WIFI_DEVICE_CAP_MESH

@@ -3106,7 +3136,7 @@

enum NMMetered

-

The NMMetered enum has two different purposes: one is to configure "connection.metered" setting of a connection profile in NMSettingConnection, and the other is to express the actual metered state of the NMDevice at a given moment.

+

The NMMetered enum has two different purposes: one is to configure "connection.metered" setting of a connection profile in NMSettingConnection, and the other is to express the actual metered state of the NMDevice at a given moment.

For the connection profile only NM_METERED_UNKNOWN, NM_METERED_NO and NM_METERED_YES are allowed.

The device's metered state at runtime is determined by the profile which is currently active. If the profile explicitly specifies NM_METERED_NO or NM_METERED_YES, then the device's metered state is as such. If the connection profile leaves it undecided at NM_METERED_UNKNOWN (the default), then NetworkManager tries to guess the metered state, for example based on the device type or on DHCP options (like Android devices exposing a "ANDROID_METERED" DHCP vendor option). This then leads to either NM_METERED_GUESS_NO or NM_METERED_GUESS_YES.

Most applications probably should treat the runtime state NM_METERED_GUESS_YES like NM_METERED_YES, and all other states as not metered.

@@ -4079,7 +4109,7 @@

-

by default, creating a checkpoint fails if there are already existing checkoints that reference the same devices. With this flag, creation of such checkpoints is allowed, however, if an older checkpoint that references overlapping devices gets rolled back, it will automatically destroy this checkpoint during rollback. This allows to create several overlapping checkpoints in parallel, and rollback to them at will. With the special case that rolling back to an older checkpoint will invalidate all overlapping younger checkpoints. This opts-in that the checkpoint can be automatically destroyed by the rollback of an older checkpoint. Since: 1.12.

+

by default, creating a checkpoint fails if there are already existing checkpoints that reference the same devices. With this flag, creation of such checkpoints is allowed, however, if an older checkpoint that references overlapping devices gets rolled back, it will automatically destroy this checkpoint during rollback. This allows to create several overlapping checkpoints in parallel, and rollback to them at will. With the special case that rolling back to an older checkpoint will invalidate all overlapping younger checkpoints. This opts-in that the checkpoint can be automatically destroyed by the rollback of an older checkpoint. Since: 1.12.

  diff --git a/docs/api/html/nm-openvswitch.html b/docs/api/html/nm-openvswitch.html index d8cd6353..358fb062 100644 --- a/docs/api/html/nm-openvswitch.html +++ b/docs/api/html/nm-openvswitch.html @@ -144,7 +144,7 @@ Connection 'ovs-slave-eth2' (475ac1bf-30b2-4534-a877-27f33f58b082) successfully $ nmcli conn add type ethernet conn.interface eth3 master bond0 Connection 'ovs-slave-eth3' (8dedeecb-ed12-482b-b77a-24a4fb835136) successfully added. -

It's just a Port with multiple interfaces. See nm-settings manual for +

It's just a Port with multiple interfaces. See nm-settings-nmcli manual for Bonding options you can use with "nmcli c add" or "nmcli c modify". You could even set a VLAN tag on the same Port to do VLAN tagging and bonding at the same time.

@@ -166,7 +166,7 @@ Connection 'ovs-slave-eth3' (8dedeecb-ed12-482b-b77a-24a4fb835136) successfully RFC 7047: The Open vSwitch Database Management Protocol, ovs-vsctl(8), ovs-vswitchd.conf.db(5), - nm-settings(5), + nm-settings-nmcli(5), nmcli(1)

diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index 9810171f..145b2ad0 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -157,6 +157,13 @@ Depending on "connection.multi-connect", a profile can (auto)connect only once a +controller +string +  +Interface name of the controller device or UUID of the controller connection. + + + dns-over-tls int32 -1 @@ -214,7 +221,9 @@ This feature requires a plugin which supports LLMNR. Otherwise, the setting has master string   -Interface name of the master device or UUID of the master connection. +Interface name of the master device or UUID of the master connection. + +Deprecated 1.46. Use "controller" instead, this is just an alias. @@ -288,6 +297,13 @@ At this time only the "user" [type] is allowed. Any other values are ignored an +port-type +string +  +Setting name of the device type of this port's controller connection (eg, "bond"), or NULL if this connection is not a port. + + + read-only boolean FALSE @@ -307,7 +323,9 @@ This property is deprecated since version 1.44.This property is deprecated and h slave-type string   -Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave. +Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave. + +Deprecated 1.46. Use "port-type" instead, this is just an alias. @@ -320,7 +338,7 @@ The stable-id is used for generating IPv6 stable private addresses with ipv6.add 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. See NetworkManager(8) manual about the secret-key and the host identity. -The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" 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. +The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-SSID, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. "${NETWORK_SSID}" uses the SSID for Wi-Fi networks and falls back to "${CONNECTION}" on other networks. 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 "default${CONNECTION}" go generate an ID unique per connection profile. @@ -1288,7 +1306,7 @@ where $vid is either a single id between 1 and 4094 or a range, represented as a app-fcoe-flags NMSettingDcbFlags (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). +Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing). @@ -1304,35 +1322,35 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject app-fcoe-priority int32 -1 -The 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. +The 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 0x1 (enable) flag. app-fip-flags NMSettingDcbFlags (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). +Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing). app-fip-priority int32 -1 -The 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. +The 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 0x1 (enable) flag. app-iscsi-flags NMSettingDcbFlags (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). +Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing). app-iscsi-priority int32 -1 -The 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. +The 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 0x1 (enable) flag. @@ -1353,7 +1371,7 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject priority-flow-control-flags NMSettingDcbFlags (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). +Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing). @@ -1367,7 +1385,7 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject priority-group-flags NMSettingDcbFlags (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). +Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing). @@ -1476,7 +1494,9 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject apn string   -The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9. +The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9. + +If the APN is unset (the default) then it may be detected based on "auto-config" setting. The property can be explicitly set to the empty string to prevent that and use no APN. @@ -1695,9 +1715,9 @@ For other connection types, adding such an automatic route is currently not supp dad-timeout int32 -1 -Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. +Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4. -The property is currently implemented only for IPv4. +A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms). A value greater than zero is a timeout in milliseconds. Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property. @@ -1714,7 +1734,9 @@ The special value "duid" generates a RFC4361-compliant client identifier based o The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key. -If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin. +The special value "none" prevents any client identifier from being sent. Note that this is normally not recommended. + +If unset, a globally configured default from NetworkManager.conf is used. If still unset, the default depends on the DHCP plugin. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won't sent any client-id otherwise. @@ -1737,9 +1759,9 @@ If unset, a globally configured default is used. If still unset, the default dep 0 Flags for the DHCP hostname and FQDN. -Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. +Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update). When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6. -When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests. +When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests. @@ -1807,15 +1829,17 @@ Set to 2147483647 (MAXINT32) for infinity. dns-options array of string   -Array of DNS options as described in man 5 resolv.conf. +Array of DNS options to be added to resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. -The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". +The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options. + +In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below). The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. -When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added. +When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present. @@ -2002,7 +2026,7 @@ Array of IPv4 route structures. Each IPv4 route structure is composed of 4 32-b 3 Configure the method for creating the IPv6 interface identifier of addresses for RFC4862 IPv6 Stateless Address Autoconfiguration and IPv6 Link Local. -The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3). +The permitted values are: 0 (eui64), 1 (stable-privacy). 2 (default-or-eui64) or 3 (default). If the property is set to "eui64", the addresses will be generated using the interface token derived from the hardware address. This makes the host part of the address constant, making it possible to track the host's presence when it changes networks. The address changes when the interface hardware is replaced. If a duplicate address is detected, there is no fallback to generate another address. When configured, the "ipv6.token" is used instead of the MAC address to generate addresses for stateless autoconfiguration. @@ -2043,9 +2067,9 @@ For other connection types, adding such an automatic route is currently not supp dad-timeout int32 -1 -Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. +Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4. -The property is currently implemented only for IPv4. +A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms). A value greater than zero is a timeout in milliseconds. Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property. @@ -2076,9 +2100,9 @@ When the property is unset, the global value provided for "ipv6.dhcp-duid" is us 0 Flags for the DHCP hostname and FQDN. -Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. +Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update). When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6. -When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests. +When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests. @@ -2146,15 +2170,17 @@ Set to 2147483647 (MAXINT32) for infinity. dns-options array of string   -Array of DNS options as described in man 5 resolv.conf. +Array of DNS options to be added to resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. -The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". +The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options. + +In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below). The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. -When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added. +When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present. @@ -2368,14 +2394,14 @@ When set, the token is used as IPv6 interface identifier instead of the hardware encapsulation-limit uint32 0 -How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1) to ip-tunnel flags. +How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add 0x1 (ip6-ign-encap-limit) to ip-tunnel flags. flags uint32 0 -Tunnel flags. Currently, the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20). They are valid only for IPv6 tunnels. +Tunnel flags. Currently, the following values are supported: 0x1 (ip6-ign-encap-limit), 0x2 (ip6-use-orig-tclass), 0x4 (ip6-use-orig-flowlabel), 0x8 (ip6-mip6-dev), 0x10 (ip6-rcv-dscp-copy), 0x20 (ip6-use-orig-fwmark). They are valid only for IPv6 tunnels. @@ -2410,7 +2436,7 @@ When set, the token is used as IPv6 interface identifier instead of the hardware mode uint32 0 -The tunneling mode. Valid values: NM_IP_TUNNEL_MODE_IPIP (1), NM_IP_TUNNEL_MODE_GRE (2), NM_IP_TUNNEL_MODE_SIT (3), NM_IP_TUNNEL_MODE_ISATAP (4), NM_IP_TUNNEL_MODE_VTI (5), NM_IP_TUNNEL_MODE_IP6IP6 (6), NM_IP_TUNNEL_MODE_IPIP6 (7), NM_IP_TUNNEL_MODE_IP6GRE (8), NM_IP_TUNNEL_MODE_VTI6 (9), NM_IP_TUNNEL_MODE_GRETAP (10) and NM_IP_TUNNEL_MODE_IP6GRETAP (11) +The tunneling mode. Valid values: 1 (ipip), 2 (gre), 3 (sit), 4 (isatap), 5 (vti), 6 (ip6ip6), 7 (ipip6), 8 (ip6gre), 9 (vti6), 10 (gretap) and 11 (ip6gretap) @@ -3175,7 +3201,7 @@ The property is valid only for ports with mode "trunk", "native-tagged", or "nat method int32 0 -Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0) +Method for proxy configuration, Default is 0 (none) @@ -3275,11 +3301,11 @@ The property is valid only for ports with mode "trunk", "native-tagged", or "nat   Whether to autoprobe virtual functions by a compatible driver. -If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF. +If set to 1 (true), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF. -If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them. +If set to 0 (false), VFs will not be claimed and no network interfaces will be created for them. -When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1). +When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 1 (true). @@ -3601,7 +3627,7 @@ If the "tc" setting is not present, NetworkManager doesn't touch the filters pre mode uint32 1 -The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one. +The operating mode of the virtual device. Allowed values are 1 (tun) to create a layer 3 device and 2 (tap) to create an Ethernet-like layer 2 one. @@ -3690,7 +3716,7 @@ If the "tc" setting is not present, NetworkManager doesn't touch the filters pre flags NMVlanFlags (uint32)   -One or more flags which control the behavior and features of the VLAN interface. Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol). +One or more flags which control the behavior and features of the VLAN interface. Flags include 0x1 (reorder-headers) (reordering of output packet headers), 0x2 (gvrp) (use of the GVRP protocol), and 0x4 (loose-binding) (loose binding of the interface to its master device's operating state). 0x8 (mvrp) (use of the MVRP protocol). The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0. @@ -4172,7 +4198,7 @@ Currently, NetworkManager itself does nothing with this information. However, s3 wake-on-lan uint32 1 -The 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). +The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of 0x2 (phy), 0x4 (unicast), 0x8 (multicast), 0x10 (broadcast), 0x20 (arp), 0x40 (magic) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager). @@ -4301,13 +4327,13 @@ Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ip ap-isolation NMTernary (int32)   -Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode. +Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from -1 (default) only when the interface is configured in AP mode. -If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc. +If set to 1 (true), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc. -If set to NM_TERNARY_FALSE (0), devices can talk to each other. +If set to 0 (false), devices can talk to each other. -When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0). +When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 0 (false). @@ -4393,7 +4419,7 @@ Note that marking the network as hidden may be a privacy issue for you (in infra mac-address-randomization uint32 0 -One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address). +One of 0 (default) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), 1 (never) (never randomize the MAC address), or 2 (always) (always randomize the MAC address). This property is deprecated since version 1.4.Use the "cloned-mac-address" property instead. @@ -4416,7 +4442,7 @@ This property is deprecated since version 1.4.Use the "cloned-mac-address" prope powersave uint32 0 -One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved. +One of 2 (disable) (disable Wi-Fi power saving), 3 (enable) (enable Wi-Fi power saving), 1 (ignore) (don't touch currently configure setting) or 0 (default) (use the globally configured value). All other values are reserved. @@ -4464,7 +4490,7 @@ This property is deprecated since version 1.44.This property is not implemented wake-on-wlan uint32 1 -The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager). +The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of 0x2 (any), 0x4 (disconnect), 0x8 (magic), 0x10 (gtk-rekey-failure), 0x20 (eap-identity-request), 0x40 (4way-handshake), 0x80 (rfkill-release), 0x100 (tcp) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager). @@ -4499,7 +4525,7 @@ This property is deprecated since version 1.44.This property is not implemented fils int32 0 -Indicates 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. +Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of 0 (default) (use global default value), 1 (disable) (disable FILS), 2 (optional) (enable FILS if the supplicant and the access point support it) or 3 (required) (enable FILS and fail if not supported). When set to 0 (default) and no global default is set, FILS will be optionally enabled. @@ -4550,7 +4576,7 @@ This property must be set for any Wi-Fi connection that uses security. pmf int32 0 -Indicates 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. +Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of 0 (default) (use global default value), 1 (disable) (disable PMF), 2 (optional) (enable PMF if the supplicant and the access point support it) or 3 (required) (enable PMF and fail if not supported). When set to 0 (default) and no global default is set, PMF will be optionally enabled. @@ -4585,7 +4611,7 @@ This property must be set for any Wi-Fi connection that uses security. wep-key-type NMWepKeyType (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. +Controls the interpretation of WEP keys. Allowed values are 1 (key), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or 2 (passphrase), 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. @@ -4752,7 +4778,7 @@ WPS can be disabled by setting this property to a value of 1.   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). +When set to -1 (default), 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 1 (true). @@ -4761,18 +4787,18 @@ When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used   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). +When set to -1 (default), 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 1 (true). only-from-default NMTernary (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 1 (true), 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. +If set to 0 (false), 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). +When set to -1 (default), 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 0 (false). @@ -4790,7 +4816,56 @@ Negative values have the special effect of excluding other connections with a gr
-

link setting

+

hsr setting

+

HSR/PRP Settings.

+
++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Key NameValue TypeDefault ValueValue Description
+multicast-specuint320The last byte of supervision address.
+port1string The port1 interface name of the HSR. This property is mandatory.
+port2string The port2 interface name of the HSR. This property is mandatory.
+prpbooleanFALSEThe protocol used by the interface, whether it is PRP or HSR.
+
+
+
+

link setting

Link settings.

@@ -4839,7 +4914,7 @@ Negative values have the special effect of excluding other connections with a gr
-

loopback setting

+

loopback setting

Loopback Link Settings.

@@ -4865,7 +4940,7 @@ Negative values have the special effect of excluding other connections with a gr
-

ovs-external-ids setting

+

ovs-external-ids setting

OVS External IDs Settings.

@@ -4891,7 +4966,7 @@ Negative values have the special effect of excluding other connections with a gr
-

ovs-other-config setting

+

ovs-other-config setting

OVS Other Config Settings.

@@ -4917,7 +4992,7 @@ Negative values have the special effect of excluding other connections with a gr
-

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 187e6a08..890e4643 100644 --- a/docs/api/html/nm-settings-ifcfg-rh.html +++ b/docs/api/html/nm-settings-ifcfg-rh.html @@ -32,7 +32,7 @@

Description

NetworkManager is based on the concept of connection profiles that contain - network configuration (see nm-settings(5) for details). The profiles can be + network configuration (see nm-settings-nmcli(5) for details). The profiles can be stored in various formats. NetworkManager uses plugins for reading and writing the data. The plugins can be configured in NetworkManager.conf(5).

@@ -1843,7 +1843,25 @@ Example: HOSTNAME_ONLY_FROM_DEFAULT=0,1

-

Table 23. infiniband setting

+

Table 23. hsr setting

+
++++++ + + + + + + + +
PropertyIfcfg-rh VariableDefaultDescription
+
+
+

Table 24. infiniband setting

@@ -1898,7 +1916,7 @@ Example: PHYSDEV=ib0

-

Table 24. ipv4 setting

+

Table 25. ipv4 setting

@@ -2033,14 +2051,14 @@ Example: IPV4_DNS_PRIORITY=20 - + - + @@ -2106,7 +2124,7 @@ Example: IPV4_LINK_LOCAL=auto
IPV4_AUTO_ROUTE_EXT_GW(+) yesVPN connections will default to add the route automatically unless this setting is set to %FALSE. For other connection types, adding such an automatic route is currently not supported and setting this to %TRUE has no effect.VPN connections will default to add the route automatically unless this setting is set to FALSE. For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.
replace-local-rule IPV4_REPLACE_LOCAL_RULE(+) noConnections will default to keep the autogenerated priority 0 local rule unless this setting is set to %TRUE.Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.
dhcp-client-id

-

Table 25. ipv6 setting

+

Table 26. ipv6 setting

@@ -2249,14 +2267,14 @@ Example: IPV6_RES_OPTIONS=ndots:2 timeout:3 - + - + @@ -2318,7 +2336,7 @@ Example: DHCPV6_PD_HINT=2001:db8:1111:2220::/60 DHCPV6_PD_HINT=:
IPV6_AUTO_ROUTE_EXT_GW(+) yesVPN connections will default to add the route automatically unless this setting is set to %FALSE. For other connection types, adding such an automatic route is currently not supported and setting this to %TRUE has no effect.VPN connections will default to add the route automatically unless this setting is set to FALSE. For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.
replace-local-rule IPV6_REPLACE_LOCAL_RULE(+) noConnections will default to keep the autogenerated priority 0 local rule unless this setting is set to %TRUE.Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.
ip6-privacy

-

Table 26. match setting

+

Table 27. match setting

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

-

Table 27. ovs-external-ids setting

+

Table 28. ovs-external-ids setting

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

-

Table 28. ovs-other-config setting

+

Table 29. ovs-other-config setting

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

-

Table 29. proxy setting

+

Table 30. proxy setting

@@ -2432,7 +2450,7 @@ Example: PAC_SCRIPT="function FindProxyForURL (url, host) { retu

-

Table 30. sriov setting

+

Table 31. sriov setting

@@ -2477,7 +2495,7 @@ Example: SRIOV_AUTOPROBE_DRIVERS=0,1

-

Table 31. tc setting

+

Table 32. tc setting

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

-

Table 32. team setting

+

Table 33. team setting

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

-

Table 33. team-port setting

+

Table 34. team-port setting

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

-

Table 34. user setting

+

Table 35. user setting

@@ -2585,7 +2603,7 @@ Example: NM_USER_FOO__BAR=something

-

Table 35. vlan setting

+

Table 36. vlan setting

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

See Also

-

nm-settings(5), +

nm-settings-nmcli(5), nm-settings-keyfile(5), NetworkManager(8), NetworkManager.conf(5), diff --git a/docs/api/html/nm-settings-keyfile.html b/docs/api/html/nm-settings-keyfile.html index 12b405b1..6779fa4c 100644 --- a/docs/api/html/nm-settings-keyfile.html +++ b/docs/api/html/nm-settings-keyfile.html @@ -32,7 +32,7 @@

Description

NetworkManager is based on the concept of connection profiles that contain - network configuration (see nm-settings(5) for details). The profiles can be + network configuration (see nm-settings-nmcli(5) for details). The profiles can be stored in various formats. NetworkManager uses plugins for reading and writing the data. The plugins can be configured in NetworkManager.conf(5).

@@ -53,21 +53,30 @@

File Format

The keyfile config format is a simple .ini-style - format. It consists of sections (groups) of key-value pairs. Each section - corresponds to a setting name as described in the settings specification - (nm-settings(5)). Each configuration key/value - pair in the section is one of the properties listed in the settings - specification. The majority of properties of the specification is written - in the same format into the keyfile too. However - some values are inconvenient for people to use. These are stored in the - files in more readable ways. These properties are described below. - An example could be IP addresses that are not written as integer arrays, - but more reasonably as "1.2.3.4/12 1.2.3.254". + format. It consists of sections (groups) of key-value pairs. More information of the generic key file format can be found at GLib key file format (Lines beginning with a '#' are comments, lists are separated by character ; etc.).

+

+ Each section corresponds to a setting name as described in the settings + specification (nm-settings-nmcli(5)). Each key/value pair in a + section is one of the properties from the specification. +

+

+ The majority of properties are written in the same format as the + specification into the keyfile. However, some + values are inconvenient for people to use so they are stored in the + keyfile in more readable ways. These properties + that differ from the specification are described below. + An example could be IP addresses that are not written as integer arrays, + but more reasonably as "1.2.3.4/12 1.2.3.254". + Also, some lists of complex values (addresses, routes, routing-rules), + instead of using a semicolon separated list, use one key-value pair + per list element, with the key being the singular of the property name + followed by the numeric index (i.e address1, address2, ...). +

Users can create or modify the keyfile connection files manually, even if that is not the recommended way of managing the profiles. @@ -175,7 +184,7 @@ id=4 There are several exceptions to this rule, mainly for making keyfile syntax easier for humans. The exceptions handled specially by keyfile plugin are listed below. Refer to - nm-settings(5) + nm-settings-nmcli(5) for all available settings and properties and their description.

Name aliases.  @@ -372,6 +381,22 @@ Example: gateway=192.168.100.1 Example: route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16 +

+ + + + + + + + + + +
routes (attributes)route1_options, route2_options, ...key=val[,key=val...]Attributes defined for the routes, if any. The supported attributes are explained in ipv4.routes entry in `man nm-settings-nmcli`. + +Example: route1_options=mtu=1000,onlink=true
routing-rulesrouting-rule1, routing-rule2, ...routing rule stringRouting rules as defined with `ip rule add`, but with mandatory fixed priority. + +Example: routing-rule1=priority 5 from 192.167.4.0/24 table 45
@@ -423,6 +448,22 @@ Example: gateway=abbe::1 Example: route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11:5403 + +routes (attributes) +route1_options, route2_options, ... +key=val[,key=val...] +Attributes defined for the routes, if any. The supported attributes are explained in ipv6.routes entry in `man nm-settings-nmcli`. + +Example: route1_options=mtu=1000,onlink=true + + +routing-rules +routing-rule1, routing-rule2, ... +routing rule string +Routing rules as defined with `ip rule add`, but with mandatory fixed priority. + +Example: routing-rule1=priority 5 from 2001:4860:4860::/64 table 45 + @@ -558,7 +599,7 @@ Example: password=Popocatepetl

See Also

-

nm-settings(5), +

nm-settings-nmcli(5), nm-settings-ifcfg-rh(5), NetworkManager(8), NetworkManager.conf(5), diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index 40cf154e..4c1c8914 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -84,7 +84,9 @@

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

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

@@ -99,6 +101,8 @@

Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.

Format: boolean

+

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

@@ -106,7 +110,9 @@

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

+ Format: integer

+

+ Valid values: -999 - 999

@@ -114,7 +120,11 @@

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

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

+

+ Special values: default (-1), forever (0)

@@ -122,7 +132,19 @@

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.

- Format: NMSettingConnectionAutoconnectSlaves (int32)

+ Format: choice (NMSettingConnectionAutoconnectSlaves)

+

+ Valid values: default (-1), no (0), yes (1)

+ + + +

connection.controller

+ +

+ Alias: controller

+

Interface name of the controller device or UUID of the controller connection.

+

+ Format: string

@@ -132,7 +154,9 @@

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

+ Format: choice (NMSettingConnectionDnsOverTls)

+

+ Valid values: default (-1), no (0), opportunistic (1), yes (2)

@@ -140,7 +164,9 @@

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 600

@@ -170,7 +196,9 @@

Whether LLDP is enabled for the connection.

- Format: int32

+ Format: choice (NMSettingConnectionLldp)

+

+ Valid values: default (-1), disable (0), enable-rx/enable (1)

@@ -180,7 +208,9 @@

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.

- Format: int32

+ Format: choice (NMSettingConnectionLlmnr)

+

+ Valid values: default (-1), no (0), resolve (1), yes (2)

@@ -189,6 +219,7 @@

Alias: master

Interface name of the master device or UUID of the master connection.

+

Deprecated 1.46. Use "controller" instead, this is just an alias.

Format: string

@@ -200,7 +231,9 @@

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.

- Format: int32

+ Format: choice (NMSettingConnectionMdns)

+

+ Valid values: default (-1), no (0), resolve (1), yes (2)

@@ -209,7 +242,9 @@

Whether the connection is metered.

When updating this property on a currently activated connection, the change takes effect immediately.

- Format: NMMetered (int32)

+ Format: ternary

+

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

@@ -225,7 +260,9 @@

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

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

- Format: uint32

+ Format: flags (NMMptcpFlags)

+

+ Valid values: none/default (0x0), disabled (0x1), enabled (0x2), also-without-sysctl (0x4), also-without-default-route (0x8), signal (0x10), subflow (0x20), backup (0x40), fullmesh (0x80)

@@ -243,7 +280,9 @@

Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.

- Format: int32

+ Format: choice (NMConnectionMultiConnect)

+

+ Valid values: default (0), single (1), manual-multiple (2), multiple (3)

@@ -252,7 +291,19 @@

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

- Format: array of string

+ Format: list of strings

+ + + +

connection.port-type

+ +

+ Alias: port-type

+

Setting name of the device type of this port's controller connection (eg, "bond"), or NULL if this connection is not a port.

+

+ Format: string

+

+ Valid values: bond, bridge, ovs-bridge, ovs-port, team, vrf

@@ -260,7 +311,7 @@

List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.

- Format: array of string

+ Format: list of strings

@@ -269,8 +320,11 @@

Alias: slave-type

Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.

+

Deprecated 1.46. Use "port-type" instead, this is just an alias.

Format: string

+

+ Valid values: bond, bridge, ovs-bridge, ovs-port, team, vrf

@@ -279,7 +333,7 @@

This 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 to derive the DHCP client identifier with ipv4.dhcp-client-id=stable, the DHCPv6 DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid] and the DHCP IAID with ipv4.iaid=stable and ipv6.iaid=stable.

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. See NetworkManager(8) manual about the secret-key and the host identity.

-

The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" 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.

+

The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-SSID, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. "${NETWORK_SSID}" uses the SSID for Wi-Fi networks and falls back to "${CONNECTION}" on other networks. 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 "default${CONNECTION}" go generate an ID unique per connection profile.

Format: string

@@ -291,7 +345,7 @@

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

- Format: uint64

+ Format: read only

@@ -302,6 +356,8 @@

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

Format: string

+

+ Valid values: 6lowpan, 802-11-olpc-mesh, 802-11-wireless, 802-3-ethernet, adsl, bluetooth, bond, bridge, cdma, dummy, generic, gsm, hsr, infiniband, ip-tunnel, loopback, macsec, macvlan, ovs-bridge, ovs-dpdk, ovs-interface, ovs-patch, ovs-port, pppoe, team, tun, veth, vlan, vpn, vrf, vxlan, wifi-p2p, wimax, wireguard, wpan

@@ -310,7 +366,7 @@

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

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

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

+ Format: string

@@ -319,7 +375,9 @@

Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.

The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

@@ -328,7 +386,9 @@

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

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

@@ -385,7 +445,7 @@

List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.

- Format: array of string

+ Format: list of strings

@@ -401,7 +461,9 @@

A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.

- Format: int32

+ Format: integer

+

+ Valid values: 0 - 2147483647

@@ -411,7 +473,7 @@

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

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

- Format: byte array

+ Format: filesystem path

@@ -427,10 +489,9 @@

Flags indicating how to handle the "ca-cert-password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -448,7 +509,7 @@

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

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

- Format: byte array

+ Format: filesystem path

@@ -464,10 +525,9 @@

Flags indicating how to handle the "client-cert-password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -491,7 +551,9 @@

The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.

- Format: array of string

+ Format: list of strings

+

+ Valid values: leap, md5, tls, peap, ttls, sim, fast, pwd

@@ -508,6 +570,8 @@

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

Format: boolean

+

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

@@ -531,10 +595,9 @@

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -542,7 +605,7 @@

Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.

- Format: byte array

+ Format: bytes

@@ -550,10 +613,9 @@

Flags indicating how to handle the "password-raw" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -561,7 +623,9 @@

Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. TLS time checks can be also disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x and tls_disable_time_checks settings. See the wpa_supplicant documentation for more details.

- Format: uint32

+ Format: flags (NMSetting8021xAuthFlags)

+

+ Valid values: none (0x0), tls-1-0-disable (0x1), tls-1-1-disable (0x2), tls-1-2-disable (0x4), tls-disable-time-checks (0x8), tls-1-3-disable (0x10), tls-1-0-enable (0x20), tls-1-1-enable (0x40), tls-1-2-enable (0x80), tls-1-3-enable (0x100), all (0x1ff)

@@ -570,6 +634,8 @@

Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details.

Format: string

+

+ Valid values: 0, 1, 2, 3

@@ -578,6 +644,8 @@

Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details.

Format: string

+

+ Valid values: 0, 1

@@ -586,6 +654,8 @@

Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version.

Format: string

+

+ Valid values: 0, 1

@@ -593,7 +663,7 @@

List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.

- Format: array of string

+ Format: list of strings

@@ -602,6 +672,8 @@

Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.

Format: string

+

+ Valid values: pap, chap, mschap, mschapv2, gtc, otp, md5, tls

@@ -610,6 +682,8 @@

Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.

Format: string

+

+ Valid values: md5, mschapv2, otp, gtc, tls

@@ -619,7 +693,7 @@

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

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

- Format: byte array

+ Format: filesystem path

@@ -635,10 +709,9 @@

Flags indicating how to handle the "phase2-ca-cert-password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -647,7 +720,7 @@

UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property.

If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.

- Format: string

+ Format: filesystem path

@@ -656,7 +729,7 @@

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

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

- Format: byte array

+ Format: filesystem path

@@ -672,10 +745,9 @@

Flags indicating how to handle the "phase2-client-cert-password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -700,7 +772,7 @@

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

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

- Format: byte array

+ Format: filesystem path

@@ -716,10 +788,9 @@

Flags indicating how to handle the "phase2-private-key-password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -746,10 +817,9 @@

Flags indicating how to handle the "pin" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -759,7 +829,7 @@

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

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

- Format: byte array

+ Format: filesystem path

@@ -775,10 +845,9 @@

Flags indicating how to handle the "private-key-password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -798,6 +867,8 @@

When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).

Format: boolean

+

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

@@ -824,6 +895,8 @@

Encapsulation of ADSL connection. Can be "vcmux" or "llc".

Format: string

+

+ Valid values: vcmux, llc

@@ -841,10 +914,9 @@

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -855,6 +927,8 @@

ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm".

Format: string

+

+ Valid values: pppoa, pppoe, ipoatm

@@ -872,7 +946,9 @@

VCI of ADSL connection

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65536

@@ -880,7 +956,9 @@

VPI of ADSL connection

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65536

@@ -906,7 +984,7 @@ Alias: addr

The Bluetooth address of the device.

- Format: byte array

+ Format: MAC address

@@ -917,6 +995,8 @@

Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.

Format: string

+

+ Valid values: dun, panu, nap

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

Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).

- Format: dict of string to string

+ Format: list of key/value options

@@ -964,7 +1044,9 @@ Alias: ageing-time

The Ethernet MAC address aging time, in seconds.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 1000000

@@ -974,7 +1056,9 @@ Alias: forward-delay

The Spanning Tree Protocol (STP) forwarding delay, in seconds.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 30

@@ -983,7 +1067,7 @@

If specified, The MAC address of the multicast group this bridge uses for STP.

The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.

- Format: byte array

+ Format: MAC address

@@ -993,7 +1077,9 @@ Alias: group-forward-mask

A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -1003,7 +1089,9 @@ Alias: hello-time

The Spanning Tree Protocol (STP) hello time, in seconds.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 10

@@ -1017,7 +1105,7 @@ This property is deprecated since version 1.12. Use the "cloned-mac-address" property instead.

- Format: byte array

+ Format: MAC address

@@ -1027,7 +1115,9 @@ Alias: max-age

The Spanning Tree Protocol (STP) maximum message age, in seconds.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 40

@@ -1035,7 +1125,9 @@

Set maximum size of multicast hash table (value must be a power of 2).

- Format: uint32

+ Format: integer

+

+ Valid values: 1 - 4294967295

@@ -1043,7 +1135,9 @@

Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -1051,7 +1145,9 @@

Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

@@ -1059,7 +1155,9 @@

Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

@@ -1068,6 +1166,8 @@

Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.

Format: boolean

+

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

@@ -1075,7 +1175,9 @@

If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

@@ -1083,7 +1185,9 @@

Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

@@ -1091,7 +1195,9 @@

Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

@@ -1100,6 +1206,8 @@

If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.

Format: boolean

+

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

@@ -1109,6 +1217,8 @@

Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).

Format: string

+

+ Valid values: auto, disabled, enabled

@@ -1119,6 +1229,8 @@

Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.

Format: boolean

+

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

@@ -1126,7 +1238,9 @@

Set the number of IGMP queries to send during startup phase.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -1134,7 +1248,9 @@

Sets the time (in deciseconds) between queries sent out at startup to determine membership information.

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

@@ -1144,7 +1260,9 @@ Alias: priority

Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -1155,6 +1273,8 @@

Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.

Format: boolean

+

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

@@ -1162,7 +1282,9 @@

The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4094

@@ -1171,6 +1293,8 @@

Control whether VLAN filtering is enabled on the bridge.

Format: boolean

+

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

@@ -1180,6 +1304,8 @@

Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.

Format: string

+

+ Valid values: 802.1Q, 802.1ad

@@ -1188,6 +1314,8 @@

Controls whether per-VLAN stats accounting is enabled.

Format: boolean

+

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

@@ -1198,7 +1326,7 @@

$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...

where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.

- Format: array of vardict

+ Format: list of bridge.vlans objects

@@ -1225,6 +1353,8 @@

Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.

Format: boolean

+

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

@@ -1234,7 +1364,9 @@ Alias: path-cost

The Spanning Tree Protocol (STP) port cost for destinations via this port.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -1244,7 +1376,9 @@ Alias: priority

The Spanning Tree Protocol (STP) priority of this bridge port.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 63

@@ -1255,7 +1389,7 @@

$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...

where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.

- Format: array of vardict

+ Format: list of bridge-port.vlans objects

@@ -1279,7 +1413,9 @@

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -1305,10 +1441,9 @@

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -1340,9 +1475,11 @@

dcb.app-fcoe-flags

-

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

+

Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).

+

+ Format: flags (NMSettingDcbFlags)

- Format: NMSettingDcbFlags (uint32)

+ Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)

@@ -1352,46 +1489,64 @@

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

+

+ Valid values: fabric, vn2vn

dcb.app-fcoe-priority

-

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

+

The 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 "enable" (0x1) flag.

+

+ Format: integer

- Format: int32

+ Valid values: -1 - 7

+

+ Special values: unset (-1)

dcb.app-fip-flags

-

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

+

Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).

+

+ Format: flags (NMSettingDcbFlags)

- Format: NMSettingDcbFlags (uint32)

+ Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)

dcb.app-fip-priority

-

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

+

The 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 "enable" (0x1) flag.

+

+ Format: integer

+

+ Valid values: -1 - 7

- Format: int32

+ Special values: unset (-1)

dcb.app-iscsi-flags

-

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

+

Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).

- Format: NMSettingDcbFlags (uint32)

+ Format: flags (NMSettingDcbFlags)

+

+ Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)

dcb.app-iscsi-priority

-

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

+

The 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 "enable" (0x1) flag.

+

+ Format: integer

- Format: int32

+ Valid values: -1 - 7

+

+ Special values: unset (-1)

@@ -1399,7 +1554,9 @@

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

- Format: array of uint32

+ Format: list of integers

+

+ Valid values: 0 - 100

@@ -1407,15 +1564,19 @@

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

- Format: array of uint32

+ Format: list of booleans

+

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

dcb.priority-flow-control-flags

-

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

+

Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).

+

+ Format: flags (NMSettingDcbFlags)

- Format: NMSettingDcbFlags (uint32)

+ Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)

@@ -1423,15 +1584,19 @@

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

- Format: array of uint32

+ Format: list of integers

+

+ Valid values: 0 - 100

dcb.priority-group-flags

-

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

+

Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).

+

+ Format: flags (NMSettingDcbFlags)

- Format: NMSettingDcbFlags (uint32)

+ Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)

@@ -1439,7 +1604,9 @@

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

- Format: array of uint32

+ Format: list of integers

+

+ Valid values: 0 - 7, 15

@@ -1447,7 +1614,9 @@

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

- Format: array of uint32

+ Format: list of booleans

+

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

@@ -1455,7 +1624,9 @@

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

- Format: array of uint32

+ Format: list of integers

+

+ Valid values: 0 - 7

@@ -1475,352 +1646,832 @@ +

ethtool.channels-combined

+ +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + + +

ethtool.channels-other

+ +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + + +

ethtool.channels-rx

+ +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + + +

ethtool.channels-tx

+ +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + +

ethtool.coalesce-adaptive-rx

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-adaptive-tx

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-pkt-rate-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-pkt-rate-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-frames

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-frames-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-frames-irq

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-frames-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-usecs

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-usecs-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-usecs-irq

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-usecs-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-sample-interval

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-stats-block-usecs

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-frames

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-frames-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-frames-irq

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-frames-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-usecs

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-usecs-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-usecs-irq

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-usecs-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + + +

ethtool.eee-enabled

+ +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-esp-hw-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-esp-tx-csum-hw-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-fcoe-mtu

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-gro

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-gso

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-highdma

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-hw-tc-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-l2-fwd-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-loopback

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-lro

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-macsec-hw-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-ntuple

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-all

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-fcs

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-gro-hw

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-gro-list

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-udp-gro-forwarding

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-udp_tunnel-port-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-vlan-filter

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-vlan-stag-filter

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-vlan-stag-hw-parse

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rxhash

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rxvlan

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-sg

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tls-hw-record

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tls-hw-rx-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tls-hw-tx-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tso

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-fcoe-crc

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-ip-generic

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-ipv4

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-ipv6

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-sctp

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-esp-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-fcoe-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gre-csum-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gre-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gso-list

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gso-partial

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gso-robust

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-ipxip4-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-ipxip6-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-nocache-copy

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-scatter-gather

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-scatter-gather-fraglist

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-sctp-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tcp-ecn-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tcp-mangleid-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tcp-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tcp6-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tunnel-remcsum-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-udp-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-udp_tnl-csum-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-udp_tnl-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-vlan-stag-hw-insert

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-txvlan

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.pause-autoneg

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.pause-rx

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.pause-tx

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.ring-rx

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.ring-rx-jumbo

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.ring-rx-mini

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.ring-tx

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ @@ -1844,6 +2495,7 @@

Alias: apn

The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.

+

If the APN is unset (the default) then it may be detected based on "auto-config" setting. The property can be explicitly set to the empty string to prevent that and use no APN.

Format: string

@@ -1854,6 +2506,8 @@

When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.

Format: boolean

+

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

@@ -1870,6 +2524,8 @@

When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.

Format: boolean

+

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

@@ -1886,6 +2542,8 @@

For LTE modems, this setting determines whether the initial EPS bearer shall be configured when bringing up the connection. It is inferred TRUE if initial-eps-bearer-apn is set.

Format: boolean

+

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

@@ -1893,7 +2551,9 @@

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -1930,10 +2590,9 @@

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -1949,10 +2608,9 @@

Flags indicating how to handle the "pin" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -2004,7 +2662,7 @@ Alias: mac

If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).

- Format: byte array

+ Format: Infiniband MAC address

@@ -2014,7 +2672,9 @@ Alias: mtu

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -2026,7 +2686,11 @@

With the p-key set, the interface name is always "$parent.$p_key". Setting "connection.interface-name" to another name is not supported.

Note that kernel will internally always set the full membership bit, although the interface name does not reflect that. Usually the user would want to configure a full membership p-key with 0x8000 flag set.

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 65535

+

+ Special values: default (-1)

@@ -2047,6 +2711,8 @@

The IP-over-InfiniBand transport mode. Either "datagram" or "connected".

Format: string

+

+ Valid values: datagram, connected

@@ -2072,7 +2738,7 @@ Alias: ip4

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

- Format: a comma separated list of addresses

+ Format: list of ipv4.addresses objects

@@ -2081,16 +2747,22 @@

VPN connections will default to add the route automatically unless this setting is set to FALSE.

For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.

- Format: NMTernary (int32)

+ Format: ternary

+

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

ipv4.dad-timeout

-

Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds.

-

The property is currently implemented only for IPv4.

+

Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.

+

A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms). A value greater than zero is a timeout in milliseconds. Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 30000

+

+ Special values: default (-1), off (0)

@@ -2101,9 +2773,12 @@

The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset.

The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id.

The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.

-

If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.

+

The special value "none" prevents any client identifier from being sent. Note that this is normally not recommended.

+

If unset, a globally configured default from NetworkManager.conf is used. If still unset, the default depends on the DHCP plugin. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won't sent any client-id otherwise.

Format: string

+

+ Special values: mac, perm-mac, duid, ipv6-duid, stable, none

@@ -2126,10 +2801,12 @@

ipv4.dhcp-hostname-flags

Flags for the DHCP hostname and FQDN.

-

Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.

-

When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.

+

Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are "fqdn-serv-update" (0x1), "fqdn-encoded" (0x2) and "fqdn-no-update" (0x4). When no FQDN flag is set and "fqdn-clear-flags" (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and "fqdn-clear-flags" (0x8) is not set, the standard FQDN flags are set in the request: "fqdn-serv-update" (0x1), "fqdn-encoded" (0x2) for IPv4 and "fqdn-serv-update" (0x1) for IPv6.

+

When this property is set to the default value "none" (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also "none" (0x0), then the standard FQDN flags described above are sent in the DHCP requests.

+

+ Format: flags (NMDhcpHostnameFlags)

- Format: uint32

+ Valid values: none (0x0), fqdn-serv-update (0x1), fqdn-encoded (0x2), fqdn-no-update (0x4), fqdn-clear-flags (0x8)

@@ -2150,7 +2827,7 @@

For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24").

This property is currently not implemented for DHCPv6.

- Format: array of string

+ Format: list of IPv4 addresses

@@ -2159,6 +2836,8 @@

If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.

Format: boolean

+

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

@@ -2167,7 +2846,11 @@

A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).

Set to 2147483647 (MAXINT32) for infinity.

- Format: int32

+ Format: integer

+

+ Valid values: 0 - 2147483647

+

+ Special values: default (0), infinity (2147483647)

@@ -2184,7 +2867,7 @@

Array of IP addresses of DNS servers.

For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved.

- Format: array of uint32

+ Format: list of IPv4 addresses

@@ -2197,7 +2880,7 @@

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

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

- Format: a comma separated list of DNS options

+ Format: list of strings

@@ -2212,7 +2895,9 @@

When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.

When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

@@ -2222,7 +2907,7 @@

When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.

When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).

- Format: array of string

+ Format: list of strings

@@ -2234,7 +2919,7 @@

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

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

- Format: string

+ Format: IPv4 address

@@ -2243,6 +2928,8 @@

When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.

Format: boolean

+

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

@@ -2251,6 +2938,8 @@

When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.

Format: boolean

+

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

@@ -2259,7 +2948,9 @@

Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server.

When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default".

- Format: int32

+ Format: choice (NMSettingIP4LinkLocal)

+

+ Valid values: default (0), auto (1), disabled (2), enabled (3)

@@ -2268,6 +2959,8 @@

If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.

Format: boolean

+

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

@@ -2289,6 +2982,8 @@

Format: string

+

+ Valid values: auto, link-local, manual, shared, disabled

@@ -2297,6 +2992,8 @@

If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.

Format: boolean

+

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

@@ -2304,7 +3001,9 @@

Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -2315,7 +3014,11 @@

Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout.

A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

+

+ Special values: default (-1), infinity (2147483647)

@@ -2323,7 +3026,9 @@

The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

@@ -2334,7 +3039,11 @@

If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.

Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

+ Special values: unspec (0), main (254)

@@ -2396,7 +3105,7 @@ For details see also `man ip-route`.

- Format: a comma separated list of routes

+ Format: list of ipv4.routes objects

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

- Format: a comma separated list of routing rules

+ Format: list of ipv4.routing-rules objects

@@ -2442,7 +3151,9 @@ Example: priority 5 from 192.167.4.0/24 table 45

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

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

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

+ Format: choice (NMSettingIP6ConfigAddrGenMode)

+

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

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

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

- Format: a comma separated list of addresses

+ Format: list of ipv6.addresses objects

@@ -2461,7 +3172,9 @@ Example: priority 5 from 192.167.4.0/24 table 45

VPN connections will default to add the route automatically unless this setting is set to FALSE.

For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -2488,10 +3201,12 @@ Example: priority 5 from 192.167.4.0/24 table 45

ipv6.dhcp-hostname-flags

Flags for the DHCP hostname and FQDN.

-

Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.

-

When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.

+

Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are "fqdn-serv-update" (0x1), "fqdn-encoded" (0x2) and "fqdn-no-update" (0x4). When no FQDN flag is set and "fqdn-clear-flags" (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and "fqdn-clear-flags" (0x8) is not set, the standard FQDN flags are set in the request: "fqdn-serv-update" (0x1), "fqdn-encoded" (0x2) for IPv4 and "fqdn-serv-update" (0x1) for IPv6.

+

When this property is set to the default value "none" (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also "none" (0x0), then the standard FQDN flags described above are sent in the DHCP requests.

+

+ Format: flags (NMDhcpHostnameFlags)

- Format: uint32

+ Valid values: none (0x0), fqdn-serv-update (0x1), fqdn-encoded (0x2), fqdn-no-update (0x4), fqdn-clear-flags (0x8)

@@ -2519,6 +3234,8 @@ Example: priority 5 from 192.167.4.0/24 table 45

If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.

Format: boolean

+

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

@@ -2527,7 +3244,11 @@ Example: priority 5 from 192.167.4.0/24 table 45

A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).

Set to 2147483647 (MAXINT32) for infinity.

- Format: int32

+ Format: integer

+

+ Valid values: 0 - 2147483647

+

+ Special values: default (0), infinity (2147483647)

@@ -2536,7 +3257,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

Array of IP addresses of DNS servers.

For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved.

- Format: array of byte array

+ Format: list of IPv6 addresses

@@ -2549,7 +3270,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

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

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

- Format: a comma separated list of DNS options

+ Format: list of strings

@@ -2564,7 +3285,9 @@ Example: priority 5 from 192.167.4.0/24 table 45

When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.

When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

@@ -2574,7 +3297,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.

When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).

- Format: array of string

+ Format: list of strings

@@ -2586,7 +3309,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

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

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

- Format: string

+ Format: IPv6 address

@@ -2595,6 +3318,8 @@ Example: priority 5 from 192.167.4.0/24 table 45

When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.

Format: boolean

+

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

@@ -2603,6 +3328,8 @@ Example: priority 5 from 192.167.4.0/24 table 45

When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.

Format: boolean

+

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

@@ -2613,7 +3340,9 @@ Example: priority 5 from 192.167.4.0/24 table 45

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

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

- Format: NMSettingIP6ConfigPrivacy (int32)

+ Format: choice (NMSettingIP6ConfigPrivacy)

+

+ Valid values: unknown (-1), disabled (0), prefer-public-addr (1), prefer-temp-addr (2)

@@ -2622,6 +3351,8 @@ Example: priority 5 from 192.167.4.0/24 table 45

If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.

Format: boolean

+

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

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

Format: string

+

+ Valid values: ignore, auto, dhcp, link-local, manual, shared, disabled

@@ -2657,7 +3390,9 @@ Example: priority 5 from 192.167.4.0/24 table 45

Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect.

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -2666,6 +3401,8 @@ Example: priority 5 from 192.167.4.0/24 table 45

If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.

Format: boolean

+

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

@@ -2674,7 +3411,11 @@ Example: priority 5 from 192.167.4.0/24 table 45

A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device.

Set to 2147483647 (MAXINT32) for infinity.

- Format: int32

+ Format: integer

+

+ Valid values: 0 - 2147483647

+

+ Special values: default (0), infinity (2147483647)

@@ -2682,7 +3423,9 @@ Example: priority 5 from 192.167.4.0/24 table 45

Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -2693,7 +3436,11 @@ Example: priority 5 from 192.167.4.0/24 table 45

Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout.

A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

+

+ Special values: default (-1), infinity (2147483647)

@@ -2701,7 +3448,9 @@ Example: priority 5 from 192.167.4.0/24 table 45

The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

@@ -2712,7 +3461,11 @@ Example: priority 5 from 192.167.4.0/24 table 45

If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.

Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

+ Special values: unspec (0), main (254)

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

- Format: a comma separated list of routes

+ Format: list of ipv6.routes objects

@@ -2772,7 +3525,7 @@ fixed priority. Example: priority 5 from 1:2:3::5/128 table 45

- Format: a comma separated list of routing rules

+ Format: list of ipv6.routing-rules objects

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

How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add 0x1 (ip6-ign-encap-limit) to ip-tunnel flags.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

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

Tunnel flags. Currently, the following values are supported: 0x1 (ip6-ign-encap-limit), 0x2 (ip6-use-orig-tclass), 0x4 (ip6-use-orig-flowlabel), 0x8 (ip6-mip6-dev), 0x10 (ip6-rcv-dscp-copy) and 0x20 (ip6-use-orig-fwmark). They are valid only for IPv6 tunnels.

- Format: uint32

+ Format: flags (NMIPTunnelFlags)

+

+ Valid values: none (0x0), ip6-ign-encap-limit (0x1), ip6-use-orig-tclass (0x2), ip6-use-orig-flowlabel (0x4), ip6-mip6-dev (0x8), ip6-rcv-dscp-copy (0x10), ip6-use-orig-fwmark (0x20)

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

The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 1048575

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

The fwmark value to assign to tunnel packets. This property can be set to a non zero value only on VTI and VTI6 tunnels.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -2857,7 +3618,9 @@ Example: priority 5 from 1:2:3::5/128 table 45 Alias: mode

The tunneling mode. Valid values: ipip (1), gre (2), sit (3), isatap (4), vti (5), ip6ip6 (6), ipip6 (7), ip6gre (8), vti6 (9), gretap (10) and ip6gretap (11)

- Format: uint32

+ Format: choice (NMIPTunnelMode)

+

+ Valid values: ipip (1), gre (2), sit (3), isatap (4), vti (5), ip6ip6 (6), ipip6 (7), ip6gre (8), vti6 (9), gretap (10), ip6gretap (11)

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

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -2892,6 +3657,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Whether to enable Path MTU Discovery on this tunnel.

Format: boolean

+

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

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

The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

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

The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

@@ -2944,6 +3715,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Whether the transmitted traffic must be encrypted.

Format: boolean

+

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

@@ -2961,10 +3734,9 @@ Example: priority 5 from 1:2:3::5/128 table 45

Flags indicating how to handle the "mka-cak" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -2984,7 +3756,9 @@ Example: priority 5 from 1:2:3::5/128 table 45 Alias: mode

Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.

- Format: int32

+ Format: choice (NMSettingMacsecMode)

+

+ Valid values: psk (0), eap (1)

@@ -3004,7 +3778,9 @@ Example: priority 5 from 1:2:3::5/128 table 45 Alias: port

The port component of the SCI (Secure Channel Identifier), between 1 and 65534.

- Format: int32

+ Format: integer

+

+ Valid values: 1 - 65534

@@ -3013,6 +3789,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Specifies whether the SCI (Secure Channel Identifier) is included in every packet.

Format: boolean

+

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

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

Specifies the validation mode for incoming frames.

- Format: int32

+ Format: choice (NMSettingMacsecValidation)

+

+ Valid values: disable (0), check (1), strict (2)

@@ -3046,7 +3826,9 @@ Example: priority 5 from 1:2:3::5/128 table 45 Alias: mode

The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.

- Format: uint32

+ Format: choice (NMSettingMacvlanMode)

+

+ Valid values: vepa (1), bridge (2), private (3), passthru (4), source (5)

@@ -3065,6 +3847,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Whether the interface should be put in promiscuous mode.

Format: boolean

+

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

@@ -3075,6 +3859,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Whether the interface should be a MACVTAP.

Format: boolean

+

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

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

A list of driver names to match. Each element is a shell wildcard pattern.

See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.

- Format: array of string

+ Format: list of strings

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

A list of interface names to match. Each element is a shell wildcard pattern.

An element can be prefixed with a pipe symbol (|) or an ampersand (&). The former means that the element is optional and the latter means that it is mandatory. If there are any optional elements, than the match evaluates to true if at least one of the optional element matches (logical OR). If there are any mandatory elements, then they all must match (logical AND). By default, an element is optional. This means that an element "foo" behaves the same as "|foo". An element can also be inverted with exclamation mark (!) between the pipe symbol (or the ampersand) and before the pattern. Note that "!foo" is a shortcut for the mandatory match "&!foo". Finally, a backslash can be used at the beginning of the element (after the optional special characters) to escape the start of the pattern. For example, "&\\!a" is an mandatory match for literally "!a".

- Format: array of string

+ Format: list of strings

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

A list of kernel command line arguments to match. This may be used to check whether a specific kernel command line option is set (or unset, if prefixed with the exclamation mark). The argument must either be a single word, or an assignment (i.e. two words, joined by "="). In the former case the kernel command line is searched for the word appearing as is, or as left hand side of an assignment. In the latter case, the exact assignment is looked for with right and left hand side matching. Wildcard patterns are not supported.

See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the match.

- Format: array of string

+ Format: list of strings

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

Each element of the list is a shell wildcard pattern.

See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.

- Format: array of string

+ Format: list of strings

@@ -3157,7 +3943,9 @@ Example: priority 5 from 1:2:3::5/128 table 45 Alias: channel

Channel on which the mesh network to join is located.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

Anycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request.

This is currently only implemented by dhclient DHCP plugin.

- Format: byte array

+ Format: MAC address

@@ -3178,7 +3966,7 @@ Example: priority 5 from 1:2:3::5/128 table 45 Alias: ssid

SSID of the mesh network to join.

- Format: byte array

+ Format: string

@@ -3203,6 +3991,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

The data path type. One of "system", "netdev" or empty.

Format: string

+

+ Valid values: system, netdev

@@ -3211,6 +4001,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

The bridge failure mode. One of "secure", "standalone" or empty.

Format: string

+

+ Valid values: secure, standalone

@@ -3219,6 +4011,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Enable or disable multicast snooping.

Format: boolean

+

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

@@ -3227,6 +4021,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Enable or disable RSTP.

Format: boolean

+

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

@@ -3235,6 +4031,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Enable or disable STP.

Format: boolean

+

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

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

Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

The rx queue size (number of rx descriptors) for DPDK ports. Must be zero or a power of 2 between 1 and 4096, and supported by the hardware. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures 2048 descriptors.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4096

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

The tx queue size (number of tx descriptors) for DPDK ports. Must be zero or a power of 2 between 1 and 4096, and supported by the hardware. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures 2048 descriptors.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4096

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

Open vSwitch openflow port number. Defaults to zero which means that port number will not be specified and it will be chosen randomly by ovs. OpenFlow ports are the network interfaces for passing packets between OpenFlow processing and the rest of the network. OpenFlow switches connect logically to each other via their OpenFlow ports.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65279

@@ -3315,6 +4121,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

The interface type. Either "internal", "system", "patch", "dpdk", or empty.

Format: string

+

+ Valid values: internal, system, patch, dpdk

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

The time port must be inactive in order to be considered down.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -3369,6 +4179,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".

Format: string

+

+ Valid values: active-backup, balance-slb, balance-tcp

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

The time port must be active before it starts forwarding traffic.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -3385,6 +4199,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

LACP mode. One of "active", "off", or "passive".

Format: string

+

+ Valid values: active, off, passive

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

The VLAN tag in the range 0-4095.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4095

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

A list of VLAN ranges that this port trunks.

The property is valid only for ports with mode "trunk", "native-tagged", or "native-untagged port". If it is empty, the port trunks all VLANs.

- Format: array of vardict

+ Format: list of ovs-port.trunks objects

@@ -3410,6 +4228,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk", "dot1q-tunnel" or unset.

Format: string

+

+ Valid values: access, native-tagged, native-untagged, trunk, dot1q-tunnel

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

If non-zero, instruct pppd to set the serial port to the specified baudrate. This value should normally be left as 0 to automatically choose the speed.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -3442,6 +4264,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, specify that pppd should set the serial port to use hardware flow control with RTS and CTS signals. This value should normally be set to FALSE.

Format: boolean

+

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

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

If non-zero, instruct pppd to presume the connection to the peer has failed if the specified number of LCP echo-requests go unanswered by the peer. The "lcp-echo-interval" property must also be set to a non-zero value if this property is used.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

If non-zero, instruct pppd to send an LCP echo-request frame to the peer every n seconds (where n is the specified value). Note that some PPP peers will respond to echo requests and some will not, and it is not possible to autodetect this.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -3466,6 +4294,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, stateful MPPE is used. See pppd documentation for more information on stateful MPPE.

Format: boolean

+

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

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

If non-zero, instruct pppd to request that the peer send packets no larger than the specified size. If non-zero, the MRU should be between 128 and 16384.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 16384

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

If non-zero, instruct pppd to send packets no larger than the specified size.

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -3490,6 +4324,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, Van Jacobsen TCP header compression will not be requested.

Format: boolean

+

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

@@ -3498,6 +4334,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, do not require the other side (usually the PPP server) to authenticate itself to the client. If FALSE, require authentication from the remote side. In almost all cases, this should be TRUE.

Format: boolean

+

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

@@ -3506,6 +4344,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, BSD compression will not be requested.

Format: boolean

+

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

@@ -3514,6 +4354,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, "deflate" compression will not be requested.

Format: boolean

+

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

@@ -3522,6 +4364,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, the CHAP authentication method will not be used.

Format: boolean

+

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

@@ -3530,6 +4374,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, the EAP authentication method will not be used.

Format: boolean

+

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

@@ -3538,6 +4384,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, the MSCHAP authentication method will not be used.

Format: boolean

+

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

@@ -3546,6 +4394,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, the MSCHAPv2 authentication method will not be used.

Format: boolean

+

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

@@ -3554,6 +4404,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, the PAP authentication method will not be used.

Format: boolean

+

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

@@ -3562,6 +4414,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session. If either 64-bit or 128-bit MPPE is not available the session will fail. Note that MPPE is not used on mobile broadband connections.

Format: boolean

+

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

@@ -3570,6 +4424,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

If TRUE, 128-bit MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session, and the "require-mppe" property must also be set to TRUE. If 128-bit MPPE is not available the session will fail.

Format: boolean

+

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

@@ -3613,10 +4469,9 @@ Example: priority 5 from 1:2:3::5/128 table 45

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -3663,6 +4518,8 @@ Example: priority 5 from 1:2:3::5/128 table 45

Whether the proxy configuration is for browser only.

Format: boolean

+

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

@@ -3670,9 +4527,11 @@ Example: priority 5 from 1:2:3::5/128 table 45

Alias: method

-

Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)

+

Method for proxy configuration, Default is "none" (0)

- Format: int32

+ Format: choice (NMSettingProxyMethod)

+

+ Valid values: none (0), auto (1)

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

Speed to use for communication over the serial port. Note that this value usually has no effect for mobile broadband modems as they generally ignore speed settings and use the highest available speed.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

Byte-width of the serial communication. The 8 in "8n1" for example.

- Format: uint32

+ Format: integer

+

+ Valid values: 5 - 8

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

Parity setting of the serial port.

- Format: NMSettingSerialParity (byte)

+ Format: choice (NMSettingSerialParity)

+

+ Valid values: none/N/n (0), even/E/e (1), odd/O/o (2)

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

Time to delay between each byte sent to the modem, in microseconds.

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

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

Number of stop bits for communication on the serial port. Either 1 or 2. The 1 in "8n1" for example.

- Format: uint32

+ Format: integer

+

+ Valid values: 1 - 2

@@ -3771,11 +4640,13 @@ Example: priority 5 from 1:2:3::5/128 table 45

sriov.autoprobe-drivers

Whether to autoprobe virtual functions by a compatible driver.

-

If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.

-

If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them.

-

When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1).

+

If set to "true" (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.

+

If set to "false" (0), VFs will not be claimed and no network interfaces will be created for them.

+

When set to "default" (-1), the global default is used; in case the global default is unspecified it is assumed to be "true" (1).

- Format: NMTernary (int32)

+ Format: ternary

+

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

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

The total number of virtual functions to create.

Note that when the sriov setting is present NetworkManager enforces the number of virtual functions on the interface (also when it is zero) during activation and resets it upon deactivation. To prevent any changes to SR-IOV parameters don't add a sriov setting to the connection.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

"ID[.PRIORITY[.PROTO]]".

PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.

- Format: array of vardict

+ Format: list of sriov.vfs objects

@@ -4076,7 +4949,7 @@ Linux traffic control subsystem

- Format: GPtrArray(NMTCQdisc)

+ Format: list of tc.qdiscs objects

@@ -4178,7 +5051,7 @@ Linux traffic control subsystem

- Format: GPtrArray(NMTCTfilter)

+ Format: list of tc.tfilters objects

@@ -4212,7 +5085,7 @@ Linux traffic control subsystem

Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.

- Format: array of vardict

+ Format: list of team.link-watchers objects

@@ -4220,7 +5093,11 @@ Linux traffic control subsystem

Corresponds to the teamd mcast_rejoin.count.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), disabled (0)

@@ -4228,7 +5105,11 @@ Linux traffic control subsystem

Corresponds to the teamd mcast_rejoin.interval.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), default (0)

@@ -4236,7 +5117,11 @@ Linux traffic control subsystem

Corresponds to the teamd notify_peers.count.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), disabled (0)

@@ -4244,7 +5129,11 @@ Linux traffic control subsystem

Corresponds to the teamd notify_peers.interval.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), default (0)

@@ -4253,6 +5142,8 @@ Linux traffic control subsystem

Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".

Format: string

+

+ Valid values: broadcast, roundrobin, random, activebackup, loadbalance, lacp

@@ -4261,6 +5152,8 @@ Linux traffic control subsystem

Corresponds to the teamd runner.active.

Format: boolean

+

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

@@ -4269,6 +5162,8 @@ Linux traffic control subsystem

Corresponds to the teamd runner.agg_select_policy.

Format: string

+

+ Valid values: lacp_prio, lacp_prio_stable, bandwidth, count, port_config

@@ -4277,6 +5172,8 @@ Linux traffic control subsystem

Corresponds to the teamd runner.fast_rate.

Format: boolean

+

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

@@ -4285,6 +5182,8 @@ Linux traffic control subsystem

Corresponds to the teamd runner.hwaddr_policy.

Format: string

+

+ Valid values: same_all, by_active, only_active

@@ -4292,7 +5191,11 @@ Linux traffic control subsystem

Corresponds to the teamd runner.min_ports.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), default (1)

@@ -4300,7 +5203,11 @@ Linux traffic control subsystem

Corresponds to the teamd runner.sys_prio.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), default (65535)

@@ -4309,6 +5216,8 @@ Linux traffic control subsystem

Corresponds to the teamd runner.tx_balancer.name.

Format: string

+

+ Valid values: basic

@@ -4316,7 +5225,11 @@ Linux traffic control subsystem

Corresponds to the teamd runner.tx_balancer.interval.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), default (50)

@@ -4324,7 +5237,9 @@ Linux traffic control subsystem

Corresponds to the teamd runner.tx_hash.

- Format: array of string

+ Format: list of strings

+

+ Valid values: eth, vlan, ipv4, ipv6, ip, l3, tcp, udp, sctp, l4

@@ -4358,7 +5273,11 @@ Linux traffic control subsystem

Corresponds to the teamd ports.PORTIFNAME.lacp_key.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), default (0)

@@ -4366,7 +5285,11 @@ Linux traffic control subsystem

Corresponds to the teamd ports.PORTIFNAME.lacp_prio.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), default (255)

@@ -4374,7 +5297,7 @@ Linux traffic control subsystem

Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.

- Format: array of vardict

+ Format: list of team-port.link-watchers objects

@@ -4382,7 +5305,11 @@ Linux traffic control subsystem

Corresponds to the teamd ports.PORTIFNAME.prio.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (0), default (0)

@@ -4390,7 +5317,11 @@ Linux traffic control subsystem

Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

+ Special values: unset (-1), default (0)

@@ -4399,6 +5330,8 @@ Linux traffic control subsystem

Corresponds to the teamd ports.PORTIFNAME.sticky.

Format: boolean

+

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

@@ -4432,9 +5365,11 @@ Linux traffic control subsystem

Alias: mode

-

The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one.

+

The operating mode of the virtual device. Allowed values are "tun" (1) to create a layer 3 device and "tap" (2) to create an Ethernet-like layer 2 one.

- Format: uint32

+ Format: choice (NMSettingTunMode)

+

+ Valid values: tun (1), tap (2)

@@ -4445,6 +5380,8 @@ Linux traffic control subsystem

If the property is set to TRUE, the interface will support multiple file descriptors (queues) to parallelize packet sending or receiving. Otherwise, the interface will only support a single queue.

Format: boolean

+

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

@@ -4465,6 +5402,8 @@ Linux traffic control subsystem

If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.

Format: boolean

+

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

@@ -4475,6 +5414,8 @@ Linux traffic control subsystem

If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.

Format: boolean

+

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

@@ -4500,7 +5441,7 @@ Linux traffic control subsystem Alias: egress

For outgoing packets, a list of mappings from Linux SKB priorities to 802.1p priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".

- Format: array of string

+ Format: list of vlan.egress-priority-map objects

@@ -4508,10 +5449,12 @@ Linux traffic control subsystem

Alias: flags

-

One or more flags which control the behavior and features of the VLAN interface. Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol).

+

One or more flags which control the behavior and features of the VLAN interface. Flags include "reorder-headers" (0x1) (reordering of output packet headers), "gvrp" (0x2) (use of the GVRP protocol), and "loose-binding" (0x4) (loose binding of the interface to its master device's operating state). "mvrp" (0x8) (use of the MVRP protocol).

The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.

- Format: NMVlanFlags (uint32)

+ Format: flags (NMVlanFlags)

+

+ Valid values: reorder-headers (0x1), gvrp (0x2), loose-binding (0x4), mvrp (0x8)

@@ -4521,7 +5464,9 @@ Linux traffic control subsystem Alias: id

The VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4095

@@ -4531,7 +5476,7 @@ Linux traffic control subsystem Alias: ingress

For incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".

- Format: array of string

+ Format: list of vlan.ingress-priority-map objects

@@ -4551,6 +5496,8 @@ Linux traffic control subsystem

Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.

Format: string

+

+ Valid values: 802.1Q, 802.1ad

@@ -4574,7 +5521,7 @@ Linux traffic control subsystem

Dictionary of key/value pairs of VPN plugin specific data. Both keys and values must be strings.

- Format: dict of string to string

+ Format: list of key/value options

@@ -4583,6 +5530,8 @@ Linux traffic control subsystem

If the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.

Format: boolean

+

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

@@ -4590,7 +5539,7 @@ Linux traffic control subsystem

Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys. Both keys and values must be strings.

- Format: dict of string to string

+ Format: list of key/value options

@@ -4608,7 +5557,9 @@ Linux traffic control subsystem

Timeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -4643,7 +5594,9 @@ Linux traffic control subsystem Alias: table

The routing table for this VRF.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -4666,7 +5619,9 @@ Linux traffic control subsystem

Specifies the lifetime in seconds of FDB entries learnt by the kernel.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -4676,7 +5631,9 @@ Linux traffic control subsystem Alias: destination-port

Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -4686,7 +5643,9 @@ Linux traffic control subsystem Alias: id

Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 16777215

@@ -4695,6 +5654,8 @@ Linux traffic control subsystem

Specifies whether netlink LL ADDR miss notifications are generated.

Format: boolean

+

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

@@ -4703,6 +5664,8 @@ Linux traffic control subsystem

Specifies whether netlink IP ADDR miss notifications are generated.

Format: boolean

+

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

@@ -4711,6 +5674,8 @@ Linux traffic control subsystem

Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.

Format: boolean

+

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

@@ -4718,7 +5683,9 @@ Linux traffic control subsystem

Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -4747,6 +5714,8 @@ Linux traffic control subsystem

Specifies whether ARP proxy is turned on.

Format: boolean

+

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

@@ -4765,6 +5734,8 @@ Linux traffic control subsystem

Specifies whether route short circuit is turned on.

Format: boolean

+

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

@@ -4774,7 +5745,9 @@ Linux traffic control subsystem Alias: source-port-max

Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -4784,7 +5757,9 @@ Linux traffic control subsystem Alias: source-port-min

Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -4792,7 +5767,9 @@ Linux traffic control subsystem

Specifies the TOS value to use in outgoing packets.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

@@ -4800,7 +5777,9 @@ Linux traffic control subsystem

Specifies the time-to-live value to use in outgoing packets.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

@@ -4826,7 +5805,7 @@ Linux traffic control subsystem Alias: peer

The P2P device that should be connected to. Currently, this is the only way to create or join a group.

- Format: string

+ Format: MAC address

@@ -4835,7 +5814,7 @@ Linux traffic control subsystem

The Wi-Fi Display (WFD) Information Elements (IEs) to set.

Wi-Fi Display requires a protocol specific information element to be set in certain Wi-Fi frames. These can be specified here for the purpose of establishing a connection. This setting is only useful when implementing a Wi-Fi Display client.

- Format: byte array

+ Format: bytes

@@ -4844,7 +5823,9 @@ Linux traffic control subsystem

Flags indicating which mode of WPS is to be used.

There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.

- Format: uint32

+ Format: flags (NMSettingWirelessSecurityWpsMethod)

+

+ Valid values: default (0x0), disabled (0x1), auto (0x2), pbc (0x4), pin (0x8)

@@ -4873,7 +5854,7 @@ Linux traffic control subsystem This property is deprecated since version 1.2. WiMAX is no longer supported.

- Format: byte array

+ Format: string

@@ -4886,7 +5867,7 @@ Linux traffic control subsystem This property is deprecated since version 1.2. WiMAX is no longer supported.

- Format: string

+ Format: MAC address

@@ -4912,7 +5893,9 @@ Linux traffic control subsystem

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.

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -4921,6 +5904,8 @@ Linux traffic control subsystem

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

Format: boolean

+

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

@@ -4933,7 +5918,9 @@ Linux traffic control subsystem

If unspecified, the value can be overwritten via global defaults, see manual of NetworkManager.conf. If still unspecified, it defaults to "preserve" (older versions of NetworkManager may use a different default value).

On D-Bus, this field is expressed as "assigned-mac-address" or the deprecated "cloned-mac-address".

- Format: byte array

+ Format: MAC address

+

+ Special values: preserve, permanent, random, stable

@@ -4942,6 +5929,8 @@ Linux traffic control subsystem

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

Format: string

+

+ Valid values: half, full

@@ -4963,7 +5952,7 @@ Linux traffic control subsystem Alias: mac

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

- Format: byte array

+ Format: MAC address

@@ -4971,7 +5960,7 @@ Linux traffic control subsystem

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

- Format: array of string

+ Format: list of MAC addresses

@@ -4981,7 +5970,9 @@ Linux traffic control subsystem Alias: mtu

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -4989,7 +5980,7 @@ Linux traffic control subsystem

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

- Format: string

+ Format: read only

@@ -4998,6 +5989,8 @@ Linux traffic control subsystem

s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.

Format: string

+

+ Valid values: qeth, lcs, ctc

@@ -5006,7 +5999,7 @@ Linux traffic control subsystem

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

+ Format: list of key/value options

@@ -5014,7 +6007,7 @@ Linux traffic control subsystem

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

- Format: array of string

+ Format: list of 802-3-ethernet.s390-subchannels objects

@@ -5022,15 +6015,19 @@ Linux traffic control subsystem

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

802-3-ethernet.wake-on-lan

-

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

+

The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of "phy" (0x2), "unicast" (0x4), "multicast" (0x8), "broadcast" (0x10), "arp" (0x20), "magic" (0x40) or the special values "default" (0x1) (to use global settings) and "ignore" (0x8000) (to disable management of Wake-on-LAN in NetworkManager).

+

+ Format: flags (NMSettingWiredWakeOnLan)

- Format: uint32

+ Valid values: phy (0x2), unicast (0x4), multicast (0x8), broadcast (0x10), arp (0x20), magic (0x40), default (0x1), ignore (0x8000)

@@ -5038,7 +6035,7 @@ Linux traffic control subsystem

If specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address. If NULL, no password will be required.

- Format: string

+ Format: MAC address

@@ -5063,7 +6060,9 @@ Linux traffic control subsystem

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -5073,7 +6072,9 @@ Linux traffic control subsystem

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. Since this automatism only makes sense if you also have a peer with an /0 allowed-ips, it is usually not necessary to enable this explicitly. However, you can disable it if you want to configure your own routing and rules.

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -5081,7 +6082,9 @@ Linux traffic control subsystem

Like ip4-auto-default-route, but for the IPv6 default route.

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -5089,7 +6092,9 @@ Linux traffic control subsystem

The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -5098,7 +6103,9 @@ Linux traffic control subsystem

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

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -5108,6 +6115,8 @@ Linux traffic control subsystem

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.

Format: boolean

+

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

@@ -5123,10 +6132,9 @@ Linux traffic control subsystem

Flags indicating how to handle the "private-key" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -5150,12 +6158,14 @@ Linux traffic control subsystem

802-11-wireless.ap-isolation

-

Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode.

-

If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.

-

If set to NM_TERNARY_FALSE (0), devices can talk to each other.

-

When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).

+

Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from "default" (-1) only when the interface is configured in AP mode.

+

If set to "true" (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.

+

If set to "false" (0), devices can talk to each other.

+

When set to "default" (-1), the global default is used; in case the global default is unspecified it is assumed to be "false" (0).

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -5164,6 +6174,8 @@ Linux traffic control subsystem

802.11 frequency band of the network. One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11. This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible. This setting depends on specific driver capability and may not work with all drivers.

Format: string

+

+ Valid values: a, bg

@@ -5172,7 +6184,7 @@ Linux traffic control subsystem

If specified, directs the device to only associate with the given access point. This capability is highly driver dependent and not supported by all devices. Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future.

Locking a client profile to a certain BSSID will prevent roaming and also disable background scanning. That can be useful, if there is only one access point for the SSID.

- Format: byte array

+ Format: MAC address

@@ -5180,7 +6192,9 @@ Linux traffic control subsystem

Wireless channel to use for the Wi-Fi connection. The device will only join (or create for Ad-Hoc networks) a Wi-Fi network on the specified channel. Because channel numbers overlap between bands, this property also requires the "band" property to be set.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -5189,11 +6203,13 @@ Linux traffic control subsystem

Alias: cloned-mac

If specified, request that the device use this MAC address instead. This is known as MAC cloning or spoofing.

-

Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random" and "stable" are supported. "preserve" means not to touch the MAC address on activation. "permanent" means to use the permanent hardware address of the device. "random" creates a random MAC address on each connect. "stable" creates a hashed MAC address based on connection.stable-id and a machine dependent key.

+

Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random", "stable" and "stable-ssid" are supported. "preserve" means not to touch the MAC address on activation. "permanent" means to use the permanent hardware address of the device. "random" creates a random MAC address on each connect. "stable" creates a hashed MAC address based on connection.stable-id and a machine dependent key. "stable-ssid" creates a hashed MAC address based on the SSID, the same as setting the stable-id to "${NETWORK_SSID}".

If unspecified, the value can be overwritten via global defaults, see manual of NetworkManager.conf. If still unspecified, it defaults to "preserve" (older versions of NetworkManager may use a different default value).

On D-Bus, this field is expressed as "assigned-mac-address" or the deprecated "cloned-mac-address".

- Format: byte array

+ Format: MAC address

+

+ Special values: preserve, permanent, random, stable, stable-ssid

@@ -5217,6 +6233,8 @@ Linux traffic control subsystem

Note that marking the network as hidden may be a privacy issue for you (in infrastructure mode) or client stations (in AP mode), as the explicit probe-scans are distinctly recognizable on the air.

Format: boolean

+

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

@@ -5226,7 +6244,7 @@ Linux traffic control subsystem Alias: mac

If specified, this connection will only apply to the Wi-Fi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).

- Format: byte array

+ Format: MAC address

@@ -5234,18 +6252,20 @@ Linux traffic control subsystem

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

- Format: array of string

+ Format: list of MAC addresses

802-11-wireless.mac-address-randomization

-

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

+

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

This property is deprecated since version 1.4. Use the "cloned-mac-address" property instead.

- Format: uint32

+ Format: choice (NMSettingMacRandomization)

+

+ Valid values: default (0), never (1), always (2)

@@ -5256,6 +6276,8 @@ Linux traffic control subsystem

Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap". If blank, infrastructure is assumed.

Format: string

+

+ Valid values: infrastructure, adhoc, ap, mesh

@@ -5265,15 +6287,19 @@ Linux traffic control subsystem Alias: mtu

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.

- Format: uint32

+ Format: integer

+

+ Special values: auto

802-11-wireless.powersave

-

One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.

+

One of "disable" (2) (disable Wi-Fi power saving), "enable" (3) (enable Wi-Fi power saving), "ignore" (1) (don't touch currently configure setting) or "default" (0) (use the globally configured value). All other values are reserved.

- Format: uint32

+ Format: choice (NMSettingWirelessPowersave)

+

+ Valid values: default (0), ignore (1), disable (2), enable (3)

@@ -5282,7 +6308,7 @@ Linux traffic control subsystem

A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network. NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.

This is not a regular property that the user would configure. Instead, NetworkManager automatically sets the seen BSSIDs and tracks them internally in "/var/lib/NetworkManager/seen-bssids" file.

- Format: array of string

+ Format: read only

@@ -5292,15 +6318,17 @@ Linux traffic control subsystem Alias: ssid

SSID of the Wi-Fi network. Must be specified.

- Format: byte array

+ Format: string

802-11-wireless.wake-on-wlan

-

The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).

+

The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of "any" (0x2), "disconnect" (0x4), "magic" (0x8), "gtk-rekey-failure" (0x10), "eap-identity-request" (0x20), "4way-handshake" (0x40), "rfkill-release" (0x80), "tcp" (0x100) or the special values "default" (0x1) (to use global settings) and "ignore" (0x8000) (to disable management of Wake-on-LAN in NetworkManager).

- Format: uint32

+ Format: flags (NMSettingWirelessWakeOnWLan)

+

+ Valid values: any (0x2), disconnect (0x4), magic (0x8), gtk-rekey-failure (0x10), eap-identity-request (0x20), 4way-handshake (0x40), rfkill-release (0x80), tcp (0x100), all (0x1fe), default (0x1), ignore (0x8000)

@@ -5327,14 +6355,18 @@ Linux traffic control subsystem

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

Format: string

+

+ Valid values: open, shared, leap

802-11-wireless-security.fils

-

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

+

Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of "default" (0) (use global default value), "disable" (1) (disable FILS), "optional" (2) (enable FILS if the supplicant and the access point support it) or "required" (3) (enable FILS and fail if not supported). When set to "default" (0) and no global default is set, FILS will be optionally enabled.

- Format: int32

+ Format: choice (NMSettingWirelessSecurityFils)

+

+ Valid values: default (0), disable (1), optional (2), required (3)

@@ -5342,7 +6374,9 @@ Linux traffic control subsystem

A 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".

- Format: array of string

+ Format: list of strings

+

+ Valid values: wep40, wep104, tkip, ccmp

@@ -5352,6 +6386,8 @@ Linux traffic control subsystem

This property must be set for any Wi-Fi connection that uses security.

Format: string

+

+ Valid values: none, ieee8021x, wpa-psk, wpa-eap, wpa-eap-suite-b-192, sae, owe

@@ -5367,10 +6403,9 @@ Linux traffic control subsystem

Flags indicating how to handle the "leap-password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -5386,15 +6421,19 @@ Linux traffic control subsystem

A 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".

- Format: array of string

+ Format: list of strings

+

+ Valid values: tkip, ccmp

802-11-wireless-security.pmf

-

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

+

Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of "default" (0) (use global default value), "disable" (1) (disable PMF), "optional" (2) (enable PMF if the supplicant and the access point support it) or "required" (3) (enable PMF and fail if not supported). When set to "default" (0) and no global default is set, PMF will be optionally enabled.

+

+ Format: choice (NMSettingWirelessSecurityPmf)

- Format: int32

+ Valid values: default (0), disable (1), optional (2), required (3)

@@ -5402,7 +6441,9 @@ Linux traffic control subsystem

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

- Format: array of string

+ Format: list of strings

+

+ Valid values: wpa, rsn

@@ -5418,10 +6459,9 @@ Linux traffic control subsystem

Flags indicating how to handle the "psk" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -5429,18 +6469,19 @@ Linux traffic control subsystem

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

802-11-wireless-security.wep-key-type

-

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.

+

Controls the interpretation of WEP keys. Allowed values are "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 "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.

+

+ Format: choice (NMWepKeyType)

- Format: NMWepKeyType (uint32)

+ Valid values: unknown (0), key (1), passphrase (2)

@@ -5480,7 +6521,9 @@ Linux traffic control subsystem

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 3

@@ -5490,7 +6533,9 @@ Linux traffic control subsystem

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.

- Format: uint32

+ Format: flags (NMSettingWirelessSecurityWpsMethod)

+

+ Valid values: default (0x0), disabled (0x1), auto (0x2), pbc (0x4), pin (0x8)

@@ -5516,7 +6561,11 @@ Linux traffic control subsystem Alias: channel

IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".

- Format: int32

+ Format: integer

+

+ Valid values: -32768 - 32767

+

+ Special values: default (-1)

@@ -5526,7 +6575,7 @@ Linux traffic control subsystem Alias: mac

If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.

- Format: string

+ Format: WPAN MAC address

@@ -5536,7 +6585,11 @@ Linux traffic control subsystem Alias: page

IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".

- Format: int32

+ Format: integer

+

+ Valid values: -32768 - 32767

+

+ Special values: default (-1)

@@ -5546,7 +6599,11 @@ Linux traffic control subsystem Alias: pan-id

IEEE 802.15.4 Personal Area Network (PAN) identifier.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

+

+ Special values: unset (0xffff)

@@ -5556,7 +6613,11 @@ Linux traffic control subsystem Alias: short-addr

Short IEEE 802.15.4 address to be used within a restricted environment.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

+

+ Special values: unset (0xffff)

@@ -5582,7 +6643,9 @@ Linux traffic control subsystem Alias: prio

The port priority for bond active port re-selection during failover. A higher number means a higher priority in selection. The primary port has the highest priority. This option is only compatible with active-backup, balance-tlb and balance-alb modes.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

@@ -5592,7 +6655,9 @@ Linux traffic control subsystem 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

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -5615,28 +6680,34 @@ Linux traffic control subsystem

hostname.from-dhcp

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

+

When set to "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 "true" (1).

+

+ Format: ternary

- Format: NMTernary (int32)

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

hostname.from-dns-lookup

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

+

When set to "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 "true" (1).

- Format: NMTernary (int32)

+ Format: ternary

+

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

hostname.only-from-default

-

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

+

If set to "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 "false" (0), the hostname can be set from this device even if it doesn't have the default route.

+

When set to "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 "false" (0).

+

+ Format: ternary

- Format: NMTernary (int32)

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

@@ -5646,7 +6717,67 @@ Linux traffic control subsystem

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.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+ + + + + +
+
+

hsr setting

+

HSR/PRP Settings.

+

+ Properties: +

+
++++ + + + + + + + + + + + + + + + + @@ -5654,7 +6785,7 @@ Linux traffic control subsystem
-

link setting

+

link setting

Link settings.

Properties: @@ -5670,7 +6801,11 @@ Linux traffic control subsystem

@@ -5678,7 +6813,11 @@ Linux traffic control subsystem @@ -5686,7 +6825,11 @@ Linux traffic control subsystem @@ -5694,7 +6837,11 @@ Linux traffic control subsystem @@ -5702,7 +6849,7 @@ Linux traffic control subsystem
-

loopback setting

+

loopback setting

Loopback Link Settings.

Properties: @@ -5719,14 +6866,16 @@ Linux traffic control subsystem Alias: mtu

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.

- Format: uint32

+ Format: integer

+

+ Special values: auto

hsr.multicast-spec

 +

+ Alias: multicast-spec

+

The last byte of supervision address.

+

+ Format: integer

+

+ Valid values: 0 - 255

+

hsr.port1

 +

+ Alias: port1

+

The port1 interface name of the HSR. This property is mandatory.

+

+ Format: string

+

hsr.port2

 +

+ Alias: port2

+

The port2 interface name of the HSR. This property is mandatory.

+

+ Format: string

+

hsr.prp

 +

The protocol used by the interface, whether it is PRP or HSR.

+

+ Format: boolean

+

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

The maximum size of a packet built by the Generic Receive Offload stack for this device. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

+

+ Special values: default (-1)

The maximum segments of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

+

+ Special values: default (-1)

The maximum size of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

+

+ Special values: default (-1)

The size of the transmit queue for the device, in number of packets. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

+

+ Special values: default (-1)
-

veth setting

+

veth setting

Veth Settings.

Properties: diff --git a/docs/api/html/nmcli-examples.html b/docs/api/html/nmcli-examples.html index 0a832ab7..fdbed744 100644 --- a/docs/api/html/nmcli-examples.html +++ b/docs/api/html/nmcli-examples.html @@ -187,7 +187,7 @@ B,DISPATCH This command activates a VPN connection profile enabling nmcli to interact with the user ('--ask'): this will allow nmcli to prompt for the VPN password on the command line when the password-flags are set to '0x02' ('always ask', see - nm-settings(5) + nm-settings-nmcli(5) ). This is particularly useful for OTP based VPNs, as the user needs to be prompted for the password each time the connection is activated. @@ -697,7 +697,7 @@ Type "Yes" to commit the changes: Yesnmcli(1), NetworkManager(8), NetworkManager.conf(5), - nm-settings(5), + nm-settings-nmcli(5), nm-online(1), nm-applet(1), nm-connection-editor(1) diff --git a/docs/api/html/ref-dbus-devices.html b/docs/api/html/ref-dbus-devices.html index ffff3da4..91027634 100644 --- a/docs/api/html/ref-dbus-devices.html +++ b/docs/api/html/ref-dbus-devices.html @@ -48,6 +48,9 @@ org.freedesktop.NetworkManager.Device.Generic — Unrecognized Device.

+org.freedesktop.NetworkManager.Device.Hsr — HSR Device. +
+
org.freedesktop.NetworkManager.Device.IPTunnel — IP Tunneling Device.
diff --git a/docs/api/html/ref-settings.html b/docs/api/html/ref-settings.html index 1beceeb8..ce26570f 100644 --- a/docs/api/html/ref-settings.html +++ b/docs/api/html/ref-settings.html @@ -178,6 +178,9 @@ hostname — Hostname settings
+hsr — HSR/PRP Settings +
+
link — Link settings
diff --git a/docs/api/html/settings-6lowpan.html b/docs/api/html/settings-6lowpan.html index 0f6ffd16..867de0e9 100644 --- a/docs/api/html/settings-6lowpan.html +++ b/docs/api/html/settings-6lowpan.html @@ -38,7 +38,7 @@ Properties
-

Table 37. 

+

Table 38. 

diff --git a/docs/api/html/settings-802-11-olpc-mesh.html b/docs/api/html/settings-802-11-olpc-mesh.html index f67b9882..8ac352c8 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 57. 

+

Table 58. 

diff --git a/docs/api/html/settings-802-11-wireless-security.html b/docs/api/html/settings-802-11-wireless-security.html index c6eded77..dedb108d 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 82. 

+

Table 83. 

@@ -63,7 +63,7 @@ - + @@ -107,7 +107,7 @@ This property must be set for any Wi-Fi connection that uses security. - + @@ -137,7 +137,7 @@ This property must be set for any Wi-Fi connection that uses security. - + diff --git a/docs/api/html/settings-802-11-wireless.html b/docs/api/html/settings-802-11-wireless.html index 3589a25c..0d402d10 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 81. 

+

Table 82. 

fils
 
int32
 
0
Indicates 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.Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of 0 (default) (use global default value), 1 (disable) (disable FILS), 2 (optional) (enable FILS if the supplicant and the access point support it) or 3 (required) (enable FILS and fail if not supported). When set to 0 (default) and no global default is set, FILS will be optionally enabled. 
group
 
pmf
 
int32
 
0
Indicates 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.Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of 0 (default) (use global default value), 1 (disable) (disable PMF), 2 (optional) (enable PMF if the supplicant and the access point support it) or 3 (required) (enable PMF and fail if not supported). When set to 0 (default) and no global default is set, PMF will be optionally enabled. 
proto
 
wep-key-type
 
NMWepKeyType (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.Controls the interpretation of WEP keys.  Allowed values are 1 (key), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or 2 (passphrase), 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-key0

 
@@ -57,13 +57,13 @@
 
-
+When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 0 (false).
@@ -139,7 +139,7 @@ Note that marking the network as hidden may be a privacy issue for you (in infra
 
-
+
@@ -157,7 +157,7 @@ Note that marking the network as hidden may be a privacy issue for you (in infra
 
-
+
@@ -195,7 +195,7 @@ This is not a regular property that the user would configure. Instead, NetworkMa
 
-
+

 
 

ap-isolation

 
NMTernary (int32)

 
Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode.
+Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from -1 (default) only when the interface is configured in AP mode.
 
-If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.
+If set to 1 (true), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.
 
-If set to NM_TERNARY_FALSE (0), devices can talk to each other.
+If set to 0 (false), devices can talk to each other.
 
-When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).
 

 

 
assigned-mac-address
mac-address-randomization

 
uint32

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

 

 
mode
powersave

 
uint32

 
0
One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.One of 2 (disable) (disable Wi-Fi power saving), 3 (enable) (enable Wi-Fi power saving), 1 (ignore) (don't touch currently configure setting) or 0 (default) (use the globally configured value). All other values are reserved.
 

 

 
rate
wake-on-wlan

 
uint32

 
1
The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of 0x2 (any), 0x4 (disconnect), 0x8 (magic), 0x10 (gtk-rekey-failure), 0x20 (eap-identity-request), 0x40 (4way-handshake), 0x80 (rfkill-release), 0x100 (tcp) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).
 

 
 

diff --git a/docs/api/html/settings-802-1x.html b/docs/api/html/settings-802-1x.html
index 32c1d60e..f72bffab 100644
--- a/docs/api/html/settings-802-1x.html
+++ b/docs/api/html/settings-802-1x.html
@@ -38,7 +38,7 @@
             Properties
         
 

-
Table 38. 

+
Table 39. 

 
diff --git a/docs/api/html/settings-802-3-ethernet.html b/docs/api/html/settings-802-3-ethernet.html
index 100e5f46..a182b834 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 79. 

+
Table 80. 

 

 
 

 
@@ -151,7 +151,7 @@ Currently, NetworkManager itself does nothing with this information. However, s3
 
-
+
diff --git a/docs/api/html/settings-adsl.html b/docs/api/html/settings-adsl.html
index e387739d..b380f612 100644
--- a/docs/api/html/settings-adsl.html
+++ b/docs/api/html/settings-adsl.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 39. 

+
Table 40. 

 

 
 

wake-on-lan

 
uint32

 
1
The 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).The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of 0x2 (phy), 0x4 (unicast), 0x8 (multicast), 0x10 (broadcast), 0x20 (arp), 0x40 (magic) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).
 

 

 
wake-on-lan-password

 
diff --git a/docs/api/html/settings-bluetooth.html b/docs/api/html/settings-bluetooth.html
index 9c329bbc..4ca42c86 100644
--- a/docs/api/html/settings-bluetooth.html
+++ b/docs/api/html/settings-bluetooth.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 40. 

+
Table 41. 

 

 
 

 
diff --git a/docs/api/html/settings-bond-port.html b/docs/api/html/settings-bond-port.html
index 9b2eb6e5..f924f9d9 100644
--- a/docs/api/html/settings-bond-port.html
+++ b/docs/api/html/settings-bond-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 84. 

+
Table 85. 

 

 
 

 
diff --git a/docs/api/html/settings-bond.html b/docs/api/html/settings-bond.html
index f76e24d1..0fc4d41c 100644
--- a/docs/api/html/settings-bond.html
+++ b/docs/api/html/settings-bond.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 41. 

+
Table 42. 

 

 
 

 
diff --git a/docs/api/html/settings-bridge-port.html b/docs/api/html/settings-bridge-port.html
index 689f63ab..9a666227 100644
--- a/docs/api/html/settings-bridge-port.html
+++ b/docs/api/html/settings-bridge-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 43. 

+
Table 44. 

 

 
 

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

-
Table 42. 

+
Table 43. 

 

 
 

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

-
Table 44. 

+
Table 45. 

 

 
 

 
diff --git a/docs/api/html/settings-connection.html b/docs/api/html/settings-connection.html
index cb7262c2..d451fb79 100644
--- a/docs/api/html/settings-connection.html
+++ b/docs/api/html/settings-connection.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 36. 

+
Table 37. 

 

 
 

 
@@ -94,6 +94,12 @@ Depending on "connection.multi-connect", a profile can (auto)connect only once a
 
+
+
+
+
+
+
@@ -145,7 +151,9 @@ This feature requires a plugin which supports LLMNR. Otherwise, the setting has
 
-
+
@@ -212,6 +220,12 @@ If the per-profile value is unspecified (the default), a global connection defau
 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.
+
+
+
+
+
+
@@ -227,7 +241,9 @@ At this time only the "user" [type] is allowed.  Any other values are ignored an
 
-
+
@@ -239,7 +255,7 @@ The stable-id is used for generating IPv6 stable private addresses with ipv6.add
 
 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. See NetworkManager(8) manual about the secret-key and the host identity.
 
-The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" 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.
+The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-SSID, per-boot, or every time.  The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. "${NETWORK_SSID}" uses the SSID for Wi-Fi networks and falls back to "${CONNECTION}" on other networks. 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 "default${CONNECTION}" go generate an ID unique per connection profile.
diff --git a/docs/api/html/settings-dcb.html b/docs/api/html/settings-dcb.html
index 7f179d8f..21152664 100644
--- a/docs/api/html/settings-dcb.html
+++ b/docs/api/html/settings-dcb.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 45. 

+
Table 46. 

 

 
 

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.
 

 
controller
string
Interface name of the controller device or UUID of the controller connection.

 
dns-over-tls

 
int32

 
-1
master

 
string

 
Interface name of the master device or UUID of the master connection.Interface name of the master device or UUID of the master connection.
+
+Deprecated 1.46. Use "controller" instead, this is just an alias.
 

 

 
mdns

 

 
port-type
string
Setting name of the device type of this port's controller connection (eg, "bond"), or NULL if this connection is not a port.

 
read-only

 
boolean

 
FALSE
slave-type

 
string

 
Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.
+
+Deprecated 1.46. Use "port-type" instead, this is just an alias.
 

 

 
stable-id

 

 
@@ -57,7 +57,7 @@
 
-
+
@@ -71,31 +71,31 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject
 
-
+
-
+
-
+
-
+
-
+
@@ -113,7 +113,7 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject
 
-
+
@@ -125,7 +125,7 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject
 
-
+
diff --git a/docs/api/html/settings-dummy.html b/docs/api/html/settings-dummy.html
index 5193e674..63d50436 100644
--- a/docs/api/html/settings-dummy.html
+++ b/docs/api/html/settings-dummy.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 46. 

+
Table 47. 

 

 
 

app-fcoe-flags

 
NMSettingDcbFlags (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).Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
app-fcoe-mode
app-fcoe-priority

 
int32

 
-1
The 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.The 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 0x1 (enable) flag.
 

 

 
app-fip-flags

 
NMSettingDcbFlags (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).Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
app-fip-priority

 
int32

 
-1
The 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.The 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 0x1 (enable) flag.
 

 

 
app-iscsi-flags

 
NMSettingDcbFlags (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).Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
app-iscsi-priority

 
int32

 
-1
The 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.The 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 0x1 (enable) flag.
 

 

 
priority-bandwidth
priority-flow-control-flags

 
NMSettingDcbFlags (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).Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
priority-group-bandwidth
priority-group-flags

 
NMSettingDcbFlags (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).Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
priority-group-id

 
diff --git a/docs/api/html/settings-ethtool.html b/docs/api/html/settings-ethtool.html
index 0013fe8d..d89dda9f 100644
--- a/docs/api/html/settings-ethtool.html
+++ b/docs/api/html/settings-ethtool.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 47. 

+
Table 48. 

 

 
 

 
diff --git a/docs/api/html/settings-generic.html b/docs/api/html/settings-generic.html
index 5c1254d8..4beac3ac 100644
--- a/docs/api/html/settings-generic.html
+++ b/docs/api/html/settings-generic.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 48. 

+
Table 49. 

 

 
 

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

-
Table 49. 

+
Table 50. 

 

 
 

 
@@ -57,7 +57,9 @@
 
-
+
diff --git a/docs/api/html/settings-hostname.html b/docs/api/html/settings-hostname.html
index 4f6fe458..acaffc6f 100644
--- a/docs/api/html/settings-hostname.html
+++ b/docs/api/html/settings-hostname.html
@@ -7,7 +7,7 @@
 
-
+
@@ -22,7 +22,7 @@
 
-
+

 
 

apn

 
string

 
The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network.  The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network.  The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.
+
+If the APN is unset (the default) then it may be detected based on "auto-config" setting. The property can be explicitly set to the empty string to prevent that and use no APN.
 

 

 
auto-config

 
 
 
 
 Home
 Up
 PrevNextNext
 

 

 

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

-
Table 85. 

+
Table 86. 

 
@@ -59,7 +59,7 @@
 
+When set to -1 (default), 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 1 (true).
@@ -67,17 +67,17 @@ When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used
 
+When set to -1 (default), 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 1 (true).
-
+When set to -1 (default), 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 0 (false).
diff --git a/docs/api/html/settings-hsr.html b/docs/api/html/settings-hsr.html
new file mode 100644
index 00000000..855002f8
--- /dev/null
+++ b/docs/api/html/settings-hsr.html
@@ -0,0 +1,89 @@
+
+
+
+
+hsr: NetworkManager Reference Manual
+
+
+
+
+
+
+
+
+
+

 
 


 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-lookup

 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-default

 
NMTernary (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 1 (true), 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.
+If set to 0 (false), 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).
 

 

 
priority

+
+
+
+
+
+
+

+

+

+
+
+

+
hsr

+
hsr — HSR/PRP Settings

+

+

+

+            Properties
+        

+

+
Table 87. 

+

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






Key NameValue TypeDefault ValueValue Description
multicast-spec
uint32
0
The last byte of supervision address.
port1
string
The port1 interface name of the HSR. This property is mandatory.
port2
string
The port2 interface name of the HSR. This property is mandatory.
prp
boolean
FALSE
The protocol used by the interface, whether it is PRP or HSR.

+

+


+

+

+

+
Generated by GTK-Doc V1.33.1

+
+
\ No newline at end of file
diff --git a/docs/api/html/settings-infiniband.html b/docs/api/html/settings-infiniband.html
index c7a5e73c..797cd995 100644
--- a/docs/api/html/settings-infiniband.html
+++ b/docs/api/html/settings-infiniband.html
@@ -38,7 +38,7 @@
             Properties
         
 

-
Table 50. 

+
Table 51. 

 
diff --git a/docs/api/html/settings-ip-tunnel.html b/docs/api/html/settings-ip-tunnel.html
index 25615224..5fcffc84 100644
--- a/docs/api/html/settings-ip-tunnel.html
+++ b/docs/api/html/settings-ip-tunnel.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 53. 

+
Table 54. 

 

 
 

 
@@ -57,13 +57,13 @@
 
-
+
-
+
@@ -93,7 +93,7 @@
 
-
+
diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html
index 37aaaed0..74379ebf 100644
--- a/docs/api/html/settings-ipv4.html
+++ b/docs/api/html/settings-ipv4.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 51. 

+
Table 52. 

 

 
 

encapsulation-limit

 
uint32

 
0
How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1) to ip-tunnel flags.How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add 0x1 (ip6-ign-encap-limit) to ip-tunnel flags.
 

 

 
flags

 
uint32

 
0
Tunnel flags. Currently, the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20). They are valid only for IPv6 tunnels.Tunnel flags. Currently, the following values are supported: 0x1 (ip6-ign-encap-limit), 0x2 (ip6-use-orig-tclass), 0x4 (ip6-use-orig-flowlabel), 0x8 (ip6-mip6-dev), 0x10 (ip6-rcv-dscp-copy), 0x20 (ip6-use-orig-fwmark). They are valid only for IPv6 tunnels.
 

 

 
flow-label
mode

 
uint32

 
0
The tunneling mode. Valid values: NM_IP_TUNNEL_MODE_IPIP (1), NM_IP_TUNNEL_MODE_GRE (2), NM_IP_TUNNEL_MODE_SIT (3), NM_IP_TUNNEL_MODE_ISATAP (4), NM_IP_TUNNEL_MODE_VTI (5), NM_IP_TUNNEL_MODE_IP6IP6 (6), NM_IP_TUNNEL_MODE_IPIP6 (7), NM_IP_TUNNEL_MODE_IP6GRE (8), NM_IP_TUNNEL_MODE_VTI6 (9), NM_IP_TUNNEL_MODE_GRETAP (10) and NM_IP_TUNNEL_MODE_IP6GRETAP (11)The tunneling mode. Valid values: 1 (ipip), 2 (gre), 3 (sit), 4 (isatap), 5 (vti), 6 (ip6ip6), 7 (ipip6), 8 (ip6gre), 9 (vti6), 10 (gretap) and 11 (ip6gretap)
 

 

 
mtu

 
@@ -78,9 +78,9 @@ For other connection types, adding such an automatic route is currently not supp
 
-
+A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.
@@ -96,7 +96,9 @@ The special value "duid" generates a RFC4361-compliant client identifier based o
 
 The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.
 
-If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.
+The special value "none" prevents any client identifier from being sent. Note that this is normally not recommended.
+
+If unset, a globally configured default from NetworkManager.conf is used. If still unset, the default depends on the DHCP plugin. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won't sent any client-id otherwise.
@@ -116,9 +118,9 @@ If unset, a globally configured default is used. If still unset, the default dep
 
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.
@@ -178,15 +180,17 @@ Set to 2147483647 (MAXINT32) for infinity.
-
+When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.
diff --git a/docs/api/html/settings-ipv6.html b/docs/api/html/settings-ipv6.html
index 2e8747cc..70d0f5ed 100644
--- a/docs/api/html/settings-ipv6.html
+++ b/docs/api/html/settings-ipv6.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 52. 

+
Table 53. 

 

 
 

dad-timeout

 
int32

 
-1
Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail.  A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero).  A value greater than zero is a timeout in milliseconds.
+Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
 
-The property is currently implemented only for IPv4.
 

 

 
dhcp-client-id

 

 

 
dhcp-fqdn
0

 Flags for the DHCP hostname and FQDN.
 
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
 
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.
 

 

 
dhcp-iaid

 
dns-options

 
array of string

 
Array of DNS options as described in man 5 resolv.conf.
+Array of DNS options to be added to resolv.conf.
 
 NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
+
+In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
 
 The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
 
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.
 

 

 
dns-priority

 
@@ -59,7 +59,7 @@
 
-
+A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.
@@ -126,9 +126,9 @@ When the property is unset, the global value provided for "ipv6.dhcp-duid" is us
 
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.
@@ -188,15 +188,17 @@ Set to 2147483647 (MAXINT32) for infinity.
-
+When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.
diff --git a/docs/api/html/settings-link.html b/docs/api/html/settings-link.html
index c06d98d7..be92482b 100644
--- a/docs/api/html/settings-link.html
+++ b/docs/api/html/settings-link.html
@@ -6,7 +6,7 @@
 
-
+
@@ -21,7 +21,7 @@
 
-
+

 
 

3

 Configure the method for creating the IPv6 interface identifier of addresses for RFC4862 IPv6 Stateless Address Autoconfiguration and IPv6 Link Local.
 
-The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3).
+The permitted values are: 0 (eui64), 1 (stable-privacy). 2 (default-or-eui64) or 3 (default).
 
 If the property is set to "eui64", the addresses will be generated using the interface token derived from the hardware address. This makes the host part of the address constant, making it possible to track the host's presence when it changes networks. The address changes when the interface hardware is replaced. If a duplicate address is detected, there is no fallback to generate another address. When configured, the "ipv6.token" is used instead of the MAC address to generate addresses for stateless autoconfiguration.
 
@@ -96,9 +96,9 @@ For other connection types, adding such an automatic route is currently not supp
 
dad-timeout

 
int32

 
-1
Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail.  A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero).  A value greater than zero is a timeout in milliseconds.
+Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
 
-The property is currently implemented only for IPv4.
 

 

 
dhcp-duid
0

 Flags for the DHCP hostname and FQDN.
 
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
 
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.
 

 

 
dhcp-iaid

 
dns-options

 
array of string

 
Array of DNS options as described in man 5 resolv.conf.
+Array of DNS options to be added to resolv.conf.
 
 NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
+
+In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
 
 The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
 
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.
 

 

 
dns-priority

 
 
 
 
 
 Home
 UpPrevPrev
 Next
 

 

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

 

-

+

             Properties
         

 

-
Table 86. 

+
Table 88. 

 
diff --git a/docs/api/html/settings-loopback.html b/docs/api/html/settings-loopback.html
index d8073387..5cd6ee73 100644
--- a/docs/api/html/settings-loopback.html
+++ b/docs/api/html/settings-loopback.html
@@ -34,11 +34,11 @@
 

 
 


 

 

-

+

             Properties
         

 

-
Table 87. 

+
Table 89. 

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

-
Table 54. 

+
Table 55. 

 

 
 

 
diff --git a/docs/api/html/settings-macvlan.html b/docs/api/html/settings-macvlan.html
index 54733b85..44b2492f 100644
--- a/docs/api/html/settings-macvlan.html
+++ b/docs/api/html/settings-macvlan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 55. 

+
Table 56. 

 

 
 

 
diff --git a/docs/api/html/settings-match.html b/docs/api/html/settings-match.html
index 828fb6e7..497e4466 100644
--- a/docs/api/html/settings-match.html
+++ b/docs/api/html/settings-match.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 56. 

+
Table 57. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-bridge.html b/docs/api/html/settings-ovs-bridge.html
index bfa44b26..57383e6f 100644
--- a/docs/api/html/settings-ovs-bridge.html
+++ b/docs/api/html/settings-ovs-bridge.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 58. 

+
Table 59. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-dpdk.html b/docs/api/html/settings-ovs-dpdk.html
index 39eed1ef..9a0b4851 100644
--- a/docs/api/html/settings-ovs-dpdk.html
+++ b/docs/api/html/settings-ovs-dpdk.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 59. 

+
Table 60. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-external-ids.html b/docs/api/html/settings-ovs-external-ids.html
index ad8a703b..82082f8d 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 88. 

+
Table 90. 

 
diff --git a/docs/api/html/settings-ovs-interface.html b/docs/api/html/settings-ovs-interface.html
index 0e3b830e..43790176 100644
--- a/docs/api/html/settings-ovs-interface.html
+++ b/docs/api/html/settings-ovs-interface.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 60. 

+
Table 61. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-other-config.html b/docs/api/html/settings-ovs-other-config.html
index bd188e63..c7d3322b 100644
--- a/docs/api/html/settings-ovs-other-config.html
+++ b/docs/api/html/settings-ovs-other-config.html
@@ -34,11 +34,11 @@
 

 
 


 

 

-

+

             Properties
         

 

-
Table 89. 

+
Table 91. 

 
diff --git a/docs/api/html/settings-ovs-patch.html b/docs/api/html/settings-ovs-patch.html
index e97d2974..0e6d7603 100644
--- a/docs/api/html/settings-ovs-patch.html
+++ b/docs/api/html/settings-ovs-patch.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 61. 

+
Table 62. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-port.html b/docs/api/html/settings-ovs-port.html
index e53d3aba..00946903 100644
--- a/docs/api/html/settings-ovs-port.html
+++ b/docs/api/html/settings-ovs-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 62. 

+
Table 63. 

 

 
 

 
diff --git a/docs/api/html/settings-ppp.html b/docs/api/html/settings-ppp.html
index a8d08545..339ff0e2 100644
--- a/docs/api/html/settings-ppp.html
+++ b/docs/api/html/settings-ppp.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 63. 

+
Table 64. 

 

 
 

 
diff --git a/docs/api/html/settings-pppoe.html b/docs/api/html/settings-pppoe.html
index 7dee82f6..a16d8144 100644
--- a/docs/api/html/settings-pppoe.html
+++ b/docs/api/html/settings-pppoe.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 64. 

+
Table 65. 

 

 
 

 
diff --git a/docs/api/html/settings-proxy.html b/docs/api/html/settings-proxy.html
index 15deb102..443f0918 100644
--- a/docs/api/html/settings-proxy.html
+++ b/docs/api/html/settings-proxy.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 65. 

+
Table 66. 

 

 
 

 
@@ -63,7 +63,7 @@
 
-
+
diff --git a/docs/api/html/settings-serial.html b/docs/api/html/settings-serial.html
index e8397851..54a5051e 100644
--- a/docs/api/html/settings-serial.html
+++ b/docs/api/html/settings-serial.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 66. 

+
Table 67. 

 

 
 

method

 
int32

 
0
Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)Method for proxy configuration, Default is 0 (none)
 

 

 
pac-script

 
diff --git a/docs/api/html/settings-sriov.html b/docs/api/html/settings-sriov.html
index 7610c14b..3d3b9aa5 100644
--- a/docs/api/html/settings-sriov.html
+++ b/docs/api/html/settings-sriov.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 67. 

+
Table 68. 

 

 
 

 
@@ -59,11 +59,11 @@
 
+When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 1 (true).
diff --git a/docs/api/html/settings-tc.html b/docs/api/html/settings-tc.html
index abc54523..2fcefc9a 100644
--- a/docs/api/html/settings-tc.html
+++ b/docs/api/html/settings-tc.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 68. 

+
Table 69. 

 

 
 


 Whether to autoprobe virtual functions by a compatible driver.
 
-If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.
+If set to 1 (true), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.
 
-If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them.
+If set to 0 (false), VFs will not be claimed and no network interfaces will be created for them.
 
-When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1).
 

 

 
total-vfs

 
diff --git a/docs/api/html/settings-team-port.html b/docs/api/html/settings-team-port.html
index 73db2e13..04aaab22 100644
--- a/docs/api/html/settings-team-port.html
+++ b/docs/api/html/settings-team-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 70. 

+
Table 71. 

 

 
 

 
diff --git a/docs/api/html/settings-team.html b/docs/api/html/settings-team.html
index c6adf30a..17dbd11d 100644
--- a/docs/api/html/settings-team.html
+++ b/docs/api/html/settings-team.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 69. 

+
Table 70. 

 

 
 

 
diff --git a/docs/api/html/settings-tun.html b/docs/api/html/settings-tun.html
index a5b5a994..15306dee 100644
--- a/docs/api/html/settings-tun.html
+++ b/docs/api/html/settings-tun.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 71. 

+
Table 72. 

 

 
 

 
@@ -63,7 +63,7 @@
 
-
+
diff --git a/docs/api/html/settings-user.html b/docs/api/html/settings-user.html
index 704c4580..6a2340c3 100644
--- a/docs/api/html/settings-user.html
+++ b/docs/api/html/settings-user.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 72. 

+
Table 73. 

 

 
 

mode

 
uint32

 
1
The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one.The operating mode of the virtual device. Allowed values are 1 (tun) to create a layer 3 device and 2 (tap) to create an Ethernet-like layer 2 one.
 

 

 
multi-queue

 
diff --git a/docs/api/html/settings-veth.html b/docs/api/html/settings-veth.html
index 586a57bd..98e577fa 100644
--- a/docs/api/html/settings-veth.html
+++ b/docs/api/html/settings-veth.html
@@ -34,11 +34,11 @@
 

 
 


 

 

-

+

             Properties
         

 

-
Table 90. 

+
Table 92. 

 
diff --git a/docs/api/html/settings-vlan.html b/docs/api/html/settings-vlan.html
index f6d6f1aa..0ae6d9e6 100644
--- a/docs/api/html/settings-vlan.html
+++ b/docs/api/html/settings-vlan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 73. 

+
Table 74. 

 

 
 

 
@@ -63,7 +63,7 @@
 
-
diff --git a/docs/api/html/settings-vpn.html b/docs/api/html/settings-vpn.html
index 612a69dd..783d33e1 100644
--- a/docs/api/html/settings-vpn.html
+++ b/docs/api/html/settings-vpn.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 74. 

+
Table 75. 

 

 
 

flags

 
NMVlanFlags (uint32)

 
One or more flags which control the behavior and features of the VLAN interface.  Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol).
+One or more flags which control the behavior and features of the VLAN interface.  Flags include 0x1 (reorder-headers) (reordering of output packet headers), 0x2 (gvrp) (use of the GVRP protocol), and 0x4 (loose-binding) (loose binding of the interface to its master device's operating state). 0x8 (mvrp) (use of the MVRP protocol).
 
 The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.
 

 
diff --git a/docs/api/html/settings-vrf.html b/docs/api/html/settings-vrf.html
index d9f90e04..87012fcb 100644
--- a/docs/api/html/settings-vrf.html
+++ b/docs/api/html/settings-vrf.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 75. 

+
Table 76. 

 

 
 

 
diff --git a/docs/api/html/settings-vxlan.html b/docs/api/html/settings-vxlan.html
index be0edb5a..4c0df3f2 100644
--- a/docs/api/html/settings-vxlan.html
+++ b/docs/api/html/settings-vxlan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 76. 

+
Table 77. 

 

 
 

 
diff --git a/docs/api/html/settings-wifi-p2p.html b/docs/api/html/settings-wifi-p2p.html
index ac0865b7..64ce4ada 100644
--- a/docs/api/html/settings-wifi-p2p.html
+++ b/docs/api/html/settings-wifi-p2p.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 77. 

+
Table 78. 

 

 
 

 
diff --git a/docs/api/html/settings-wimax.html b/docs/api/html/settings-wimax.html
index 56bf88d7..5c05752b 100644
--- a/docs/api/html/settings-wimax.html
+++ b/docs/api/html/settings-wimax.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 78. 

+
Table 79. 

 

 
 

 
diff --git a/docs/api/html/settings-wireguard.html b/docs/api/html/settings-wireguard.html
index 685061fb..9e1859ba 100644
--- a/docs/api/html/settings-wireguard.html
+++ b/docs/api/html/settings-wireguard.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 80. 

+
Table 81. 

 

 
 

 
diff --git a/docs/api/html/settings-wpan.html b/docs/api/html/settings-wpan.html
index 4fddfd2a..a5986d80 100644
--- a/docs/api/html/settings-wpan.html
+++ b/docs/api/html/settings-wpan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 83. 

+
Table 84. 

 

 
 

 
diff --git a/docs/api/html/spec.html b/docs/api/html/spec.html
index a4ec537b..b41e5ef1 100644
--- a/docs/api/html/spec.html
+++ b/docs/api/html/spec.html
@@ -72,6 +72,9 @@
 org.freedesktop.NetworkManager.Device.Generic — Unrecognized Device.

+org.freedesktop.NetworkManager.Device.Hsr — HSR Device.
+

+

 org.freedesktop.NetworkManager.Device.IPTunnel — IP Tunneling Device.
 

-- 
cgit 1.3.0-6-gf8a5