From 1372848511cb896b80b51ed1a3e9606bd9816631 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Fri, 10 Feb 2023 11:50:34 +0100 Subject: New upstream version 1.42.0 --- docs/api/html/NetworkManager-dispatcher.html | 6 + .../html/NetworkManager-wait-online.service.html | 171 +- docs/api/html/NetworkManager.conf.html | 4 + docs/api/html/NetworkManager.devhelp2 | 649 ++-- docs/api/html/NetworkManager.html | 14 +- docs/api/html/ch01.html | 110 +- ...freedesktop.NetworkManager.Device.IPTunnel.html | 12 + ...eedesktop.NetworkManager.Device.Infiniband.html | 4 +- ...freedesktop.NetworkManager.Device.Loopback.html | 45 + ...g.freedesktop.NetworkManager.Device.Lowpan.html | 6 +- ...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 +- ...dbus-org.freedesktop.NetworkManager.Device.html | 4 +- .../html/gdbus-org.freedesktop.NetworkManager.html | 23 + docs/api/html/index.html | 117 +- docs/api/html/ix01.html | 428 +-- docs/api/html/manpages.html | 2 +- docs/api/html/nm-dbus-types.html | 108 +- docs/api/html/nm-settings-dbus.html | 1518 +++++---- docs/api/html/nm-settings-ifcfg-rh.html | 3235 ++++++++++---------- docs/api/html/nm-settings-keyfile.html | 200 +- docs/api/html/nm-settings-nmcli.html | 1797 ++++++----- docs/api/html/nmcli.html | 33 + docs/api/html/ref-dbus-devices.html | 3 + docs/api/html/ref-settings.html | 110 +- docs/api/html/settings-6lowpan.html | 4 +- docs/api/html/settings-802-11-olpc-mesh.html | 4 +- .../html/settings-802-11-wireless-security.html | 4 +- docs/api/html/settings-802-11-wireless.html | 4 +- docs/api/html/settings-802-1x.html | 4 +- docs/api/html/settings-802-3-ethernet.html | 4 +- docs/api/html/settings-adsl.html | 4 +- docs/api/html/settings-bluetooth.html | 4 +- docs/api/html/settings-bond-port.html | 4 +- docs/api/html/settings-bond.html | 4 +- docs/api/html/settings-bridge-port.html | 4 +- docs/api/html/settings-bridge.html | 4 +- docs/api/html/settings-cdma.html | 4 +- docs/api/html/settings-connection.html | 4 +- docs/api/html/settings-dcb.html | 4 +- docs/api/html/settings-dummy.html | 4 +- docs/api/html/settings-ethtool.html | 4 +- docs/api/html/settings-generic.html | 4 +- docs/api/html/settings-gsm.html | 4 +- docs/api/html/settings-hostname.html | 8 +- docs/api/html/settings-infiniband.html | 4 +- docs/api/html/settings-ip-tunnel.html | 10 +- docs/api/html/settings-ipv4.html | 22 +- docs/api/html/settings-ipv6.html | 22 +- docs/api/html/settings-loopback.html | 69 + docs/api/html/settings-macsec.html | 4 +- docs/api/html/settings-macvlan.html | 4 +- docs/api/html/settings-match.html | 4 +- docs/api/html/settings-ovs-bridge.html | 4 +- docs/api/html/settings-ovs-dpdk.html | 16 +- docs/api/html/settings-ovs-external-ids.html | 14 +- docs/api/html/settings-ovs-interface.html | 16 +- docs/api/html/settings-ovs-other-config.html | 69 + docs/api/html/settings-ovs-patch.html | 4 +- docs/api/html/settings-ovs-port.html | 10 +- docs/api/html/settings-ppp.html | 4 +- docs/api/html/settings-pppoe.html | 4 +- docs/api/html/settings-proxy.html | 4 +- docs/api/html/settings-serial.html | 4 +- docs/api/html/settings-sriov.html | 4 +- docs/api/html/settings-tc.html | 4 +- docs/api/html/settings-team-port.html | 4 +- docs/api/html/settings-team.html | 4 +- docs/api/html/settings-tun.html | 4 +- docs/api/html/settings-user.html | 4 +- docs/api/html/settings-veth.html | 10 +- docs/api/html/settings-vlan.html | 10 +- docs/api/html/settings-vpn.html | 4 +- docs/api/html/settings-vrf.html | 4 +- docs/api/html/settings-vxlan.html | 4 +- docs/api/html/settings-wifi-p2p.html | 4 +- docs/api/html/settings-wimax.html | 4 +- docs/api/html/settings-wireguard.html | 4 +- docs/api/html/settings-wpan.html | 4 +- docs/api/html/spec.html | 3 + 95 files changed, 4928 insertions(+), 4156 deletions(-) create mode 100644 docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Loopback.html create mode 100644 docs/api/html/settings-loopback.html create mode 100644 docs/api/html/settings-ovs-other-config.html (limited to 'docs/api/html') diff --git a/docs/api/html/NetworkManager-dispatcher.html b/docs/api/html/NetworkManager-dispatcher.html index 6c899110..88ed3634 100644 --- a/docs/api/html/NetworkManager-dispatcher.html +++ b/docs/api/html/NetworkManager-dispatcher.html @@ -152,6 +152,12 @@ The network connectivity state has changed (no connectivity, went online, etc).

+ +

reapply

+

+ The connection was reapplied on the device. +

+

diff --git a/docs/api/html/NetworkManager-wait-online.service.html b/docs/api/html/NetworkManager-wait-online.service.html index 76b703a0..c951c7b6 100644 --- a/docs/api/html/NetworkManager-wait-online.service.html +++ b/docs/api/html/NetworkManager-wait-online.service.html @@ -24,132 +24,102 @@

NetworkManager-wait-online.service

-

NetworkManager-wait-online.service — Wait for network to come online

+

NetworkManager-wait-online.service — Wait for the network to come online

Description

- NetworkManager-wait-online.service delays network-online.target until network - is ready. + The NetworkManager-wait-online service is a oneshot + systemd service that delays reaching the network-online target until + NetworkManager reports that the startup is completed on the D-Bus.

- The systemd target network-online.target acts as a synchronization point - for services to start after network is configured. Such services should - order themselves After=network-online.target - (and never After=NetworkManager-wait-online.service). - NetworkManager-wait-online.service is a one-shot service - that itself is ordered Before=network-online.target - and this way delays the target until the network is configured. + When the system boots, for example, remote mounts defined in /etc/fstab, + require that the network is up. For this, these systemd units contain the + After=network-online.target setting to order themselves after this + target. NetworkManager-wait-online ensures that the + network-online target is reached only after the network is available.

- NetworkManager-wait-online.service itself is almost not configurable - itself. Instead the connection profiles and configuration in NetworkManager affects - the behavior. + Optimally, all services on the host react dynamically to network changes and systemd + services do not need to be configured to start after reaching the + network-online target. In this case, + NetworkManager-wait-online.service has no effect and does not delay + the boot time. On the other hand, if you encounter a long boot time due to the delay + of NetworkManager-wait-online, investigate the services that require + network access and fix them.

- In the best case, all services on the system can react to networking changes dynamically and - no service orders itself after network-online.target. That way, - NetworkManager-wait-online.service has no effect and, for example, - does not delay the boot. That means, if the problem is a long boot time related to - NetworkManager-wait-online.service, a possible solution is to - investigate the services that claim to require network and fix those. + Except for the time out value in the NetworkManager-wait-online.service + unit, you cannot configure this service. Instead, settings in NetworkManager and the + connection profiles affect the behavior:

-

- For services that require network configured, - NetworkManager-wait-online.service is the default implementation - provided by NetworkManager to delay the target. But it does nothing magical. With - special requirements, it may be sensible to disable NetworkManager-wait-online.service - and replace it with a similar service that better implements the requirement. -

-

- NetworkManager-wait-online.service blocks until - NetworkManager logs "startup complete" and announces startup complete - on D-Bus. How long that takes depends on the network - and the NetworkManager configuration. If it takes longer than expected, then - the reasons need to be investigated in NetworkManager. -

-

- There are various reasons what affects NetworkManager reaching "startup complete" - and how long NetworkManager-wait-online.service blocks. -

  • - In general, startup complete is not reached as long as NetworkManager is busy - activating a device and as long as there are profiles in activating state. - During boot, NetworkManager starts autoactivating - suitable profiles that are configured to autoconnect. If activation fails, - NetworkManager might retry right away (depending on connection.autoconnect-retries - setting). While trying and retrying, NetworkManager is busy until all - profiles and devices either reached an activated or disconnected state - and no further events are expected. -

    + Startup is not complete as long as NetworkManager profiles are in an activating + state. During boot, NetworkManager starts profiles with the + connection.autoconnect=yes setting. If activation fails, + NetworkManager retries the activation depending on the value of the + connection.autoconnect-retries setting. +

    -

    + NetworkManager reports startup complete when all profiles and devices are either + activated or in a disconnect state and no further events are expected. +

    +
    • +

  • - Basically, as long as there are devices and connections in activating - state visible with nmcli device and nmcli connection, - startup is still pending. -

    + When a device reaches the activate state depends on its configuration. For example, + with a profile that has both IPv4 and IPv6 enabled, by default, NetworkManager + considers the device as fully activated already when only one of the address + families is ready. +

    +

    + The ipv4.may-fail and ipv6.may-fail settings + control this behavior. Additionally, the following settings influence when the + two address families complete: ipv4.required-timeout, + ipv6.required-timeout, ipv4.dhcp-timeout, + and ipv6.ra-timeout. For details, see + nm-settings-nmcli(5). +

  • - When a device reaches activated state, depends on its configuration. - For example, with a profile with both IPv4 and IPv6 addressing - enabled, the device is possibly considered fully activated when - either of the address families is ready. This can be controlled with the - ipv4.may-fail and ipv6.may-fail - settings, to indicate that the address family is required. - There are also ipv4.required-timeout and ipv6.required-timeout - settings which affect how long to wait for an address family. - Likewise, properties like ipv4.dhcp-timeout and - ipv6.ra-timeout affect how long NetworkManager - will try the IP configuration before giving up. -

    • -

  • - For example, a bridge or bond profile cannot do IP configuration - without ports. When booting with such profiles that autoactivate - without ports, NetworkManager-wait-online.service blocks until timeout. - This is a configuration error. -

    • + NetworkManager cannot set IP addresses on bridge and bond devices that have ports + that do not auto-activate. Because of this configuration error, + NetworkManager-wait-online blocks until the service reaches + its timeout value. +

  • - Dispatcher scripts for the "pre-up" event run at a late stage during activation - of a profile. These scripts block the activation for when NetworkManager considers - the profile fully activated. - See also NetworkManager-dispatcher(8) - for details. -

    • + Dispatcher scripts for the pre-up event run at a late stage + during activation of a profile. These scripts block the activation for when + NetworkManager considers the profile fully activated. For details, see + NetworkManager-dispatcher(8). +

  • - The connection property connection.wait-activation-delay also - adds an additional delay during activation and delays startup complete. This is to - workaround certain cases where a device is known to not be ready for a certain - amount of time. -

    • + The property connection.wait-activation-delay adds an additional + delay during activation and delays startup complete. This setting works around + certain cases where a device is known to not be ready for a certain amount of time. +

  • - The property connection.wait-device-timeout of the connection - profiles waits until the waited devices appear. This is useful if the driver - takes a longer time to detect the networking interfaces. Similar with the - connection.gateway-ping-timeout property. -

    • + The property connection.wait-device-timeout in the connection + profiles cause a delay until the waiting devices appear. This is useful if the + driver takes a longer time to detect the networking interfaces. This setting is + similar to the connection.gateway-ping-timeout property. +

  • - With Wi-Fi devices, NetworkManager needs to wait for the first scan - result to know which networks might be available. That always adds a delay. -

    • + With Wi-Fi devices, NetworkManager needs to wait for the first scan result to + know which networks are available. That adds a delay. +

  • - With ethernet devices, NetworkManager waits for carrier until the - configurable [device*].carrier-timeout is reached. - This is because some devices take a long time to detect carrier - and it means to boot with cable unplugged, will unnecessarily delay - NetworkManager-wait-online.service. -

    • + With Ethernet devices, NetworkManager waits for the carrier until the value in + [device*].carrier-timeout is reached. This is because some + devices take a long time to detect the carrier. Consequently, booting with cable + unplugged, unnecessarily delays NetworkManager-wait-online.service. +

-

-

-

- NetworkManager-wait-online.service internally uses - nm-online. -

Bugs

@@ -164,6 +134,7 @@ NetworkManager home page, NetworkManager(8), nm-online(1), + the network-online.target description in systemd.special(7)

diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index 34063973..0523fb54 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -975,6 +975,10 @@ ipv6.ip6-privacy=0

+

loopback.mtu

+

If configured explicitly to 0, the MTU is not reconfigured during device activation unless it is required due to IPv6 constraints. If left unspecified, a DHCP/IPv6 SLAAC provided value is used or the MTU is left unspecified on activation.

+ +

sriov.autoprobe-drivers

If left unspecified, drivers are autoprobed when the SR-IOV VF gets created.

diff --git a/docs/api/html/NetworkManager.devhelp2 b/docs/api/html/NetworkManager.devhelp2 index 52186b6b..1f1a58c1 100644 --- a/docs/api/html/NetworkManager.devhelp2 +++ b/docs/api/html/NetworkManager.devhelp2 @@ -70,7 +70,9 @@ + + @@ -102,6 +104,7 @@ + @@ -211,6 +214,7 @@ + @@ -314,6 +318,7 @@ + @@ -481,6 +486,7 @@ + @@ -541,327 +547,328 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/api/html/NetworkManager.html b/docs/api/html/NetworkManager.html index 1ce88b40..678e9f1c 100644 --- a/docs/api/html/NetworkManager.html +++ b/docs/api/html/NetworkManager.html @@ -150,9 +150,17 @@

--print-config

-

- Print the NetworkManager configuration to stdout and exit. -

+ +

+ Print the NetworkManager configuration to stdout and exit. See + NetworkManager.conf(5). + This does not include connection profiles. View them with nmcli connection. +

+

+ This reads configuration files from disk. If NetworkManager is currently running, + make sure that it has the same configuration loaded. +

+ diff --git a/docs/api/html/ch01.html b/docs/api/html/ch01.html index 56eda1b0..4a43e068 100644 --- a/docs/api/html/ch01.html +++ b/docs/api/html/ch01.html @@ -24,160 +24,166 @@ Configuration Settings
-connection — General Connection Profile Settings +connection — General Connection Profile Settings
-6lowpan — 6LoWPAN Settings +6lowpan — 6LoWPAN Settings
-802-1x — IEEE 802.1x Authentication Settings +802-1x — IEEE 802.1x Authentication Settings
-adsl — ADSL Settings +adsl — ADSL Settings
-bluetooth — Bluetooth Settings +bluetooth — Bluetooth Settings
-bond — Bonding Settings +bond — Bonding Settings
-bridge — Bridging Settings +bridge — Bridging Settings
-bridge-port — Bridge Port Settings +bridge-port — Bridge Port Settings
-cdma — CDMA-based Mobile Broadband Settings +cdma — CDMA-based Mobile Broadband Settings
-dcb — Data Center Bridging Settings +dcb — Data Center Bridging Settings
-dummy — Dummy Link Settings +dummy — Dummy Link Settings
-ethtool — Ethtool Ethernet Settings +ethtool — Ethtool Ethernet Settings
-generic — Generic Link Settings +generic — Generic Link Settings
-gsm — GSM-based Mobile Broadband Settings +gsm — GSM-based Mobile Broadband Settings
-infiniband — Infiniband Settings +infiniband — Infiniband Settings
-ipv4 — IPv4 Settings +ipv4 — IPv4 Settings
-ipv6 — IPv6 Settings +ipv6 — IPv6 Settings
-ip-tunnel — IP Tunneling Settings +ip-tunnel — IP Tunneling Settings
-macsec — MACSec Settings +macsec — MACSec Settings
-macvlan — MAC VLAN Settings +macvlan — MAC VLAN Settings
-match — Match settings +match — Match settings
-802-11-olpc-mesh — OLPC Wireless Mesh Settings +802-11-olpc-mesh — OLPC Wireless Mesh Settings
-ovs-bridge — OvsBridge Link Settings +ovs-bridge — OvsBridge Link Settings
-ovs-dpdk — OvsDpdk Link Settings +ovs-dpdk — OvsDpdk Link Settings
-ovs-interface — Open vSwitch Interface Settings +ovs-interface — Open vSwitch Interface Settings
-ovs-patch — OvsPatch Link Settings +ovs-patch — OvsPatch Link Settings
-ovs-port — OvsPort Link Settings +ovs-port — OvsPort Link Settings
-ppp — Point-to-Point Protocol Settings +ppp — Point-to-Point Protocol Settings
-pppoe — PPP-over-Ethernet Settings +pppoe — PPP-over-Ethernet Settings
-proxy — WWW Proxy Settings +proxy — WWW Proxy Settings
-serial — Serial Link Settings +serial — Serial Link Settings
-sriov — SR-IOV settings +sriov — SR-IOV settings
-tc — Linux Traffic Control Settings +tc — Linux Traffic Control Settings
-team — Teaming Settings +team — Teaming Settings
-team-port — Team Port Settings +team-port — Team Port Settings
-tun — Tunnel Settings +tun — Tunnel Settings
-user — General User Profile Settings +user — General User Profile Settings
-vlan — VLAN Settings +vlan — VLAN Settings
-vpn — VPN Settings +vpn — VPN Settings
-vrf — VRF settings +vrf — VRF settings
-vxlan — VXLAN Settings +vxlan — VXLAN Settings
-wifi-p2p — Wi-Fi P2P Settings +wifi-p2p — Wi-Fi P2P Settings
-wimax — WiMax Settings +wimax — WiMax Settings
-802-3-ethernet — Wired Ethernet Settings +802-3-ethernet — Wired Ethernet Settings
-wireguard — WireGuard Settings +wireguard — WireGuard Settings
-802-11-wireless — Wi-Fi Settings +802-11-wireless — Wi-Fi Settings
-802-11-wireless-security — Wi-Fi Security Settings +802-11-wireless-security — Wi-Fi Security Settings
-wpan — IEEE 802.15.4 (WPAN) MAC Settings +wpan — IEEE 802.15.4 (WPAN) MAC Settings
-bond-port — Bond Port Settings +bond-port — Bond Port Settings
-hostname — Hostname settings +hostname — Hostname settings
-ovs-external-ids — OVS External IDs Settings +loopback — Loopback Link Settings
-veth — Veth Settings +ovs-external-ids — OVS External IDs Settings +
+
+ovs-other-config — OVS Other Config Settings +
+
+veth — Veth Settings
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 cdf6a946..19b57766 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html @@ -46,6 +46,7 @@ OutputKey readable s EncapsulationLimit readable y FlowLabel readable u +FwMark readable u Flags readable u @@ -173,6 +174,17 @@ IPv6 tunnels.
+

The "FwMark" property

+
+FwMark  readable   u
+
+

+The fwmark value to assign to tunnel packets. This property applies only to +VTI tunnels. +

+
+
+

The "Flags" property

 Flags  readable   u
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 c706d1ff..2aef5cdb 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.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.Loopback.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Loopback.html
new file mode 100644
index 00000000..c522f1f7
--- /dev/null
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Loopback.html
@@ -0,0 +1,45 @@
+
+
+
+
+org.freedesktop.NetworkManager.Device.Loopback: NetworkManager Reference Manual
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

+

+

+
+
+

+
org.freedesktop.NetworkManager.Device.Loopback

+
org.freedesktop.NetworkManager.Device.Loopback — Loopback Device.

+

+

+
Description

+

+

+

+

+

+

+

+
Generated by GTK-Doc V1.33.1

+
+
\ No newline at end of file
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 8d85d33a..68e709aa 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html
@@ -6,7 +6,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
 
 Home
 Up
-Prev
+Prev
 Next
 
 

@@ -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 795aee21..9f868062 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 fcbb003c..b7ffeaf3 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 4b6cc204..b55163c1 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 2f71abd8..631e01b3 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 46b3fbd4..571a45e6 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 08cf13ba..4dcf9283 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 5864fd40..8340f542 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 8c05cf5c..4ff42e7a 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 46b788f2..d2ba1876 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 a55b8250..0a17c6ef 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 88e848a0..a37962e2 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 9349aa4c..38f938f8 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 2ef395cf..4f99d38e 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 60ad16dc..ab48943e 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 e62fe697..94fcf349 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 39d0305d..ba1206a8 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 4415fe36..28bba258 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.Device.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html
index f5026a1f..8da3cea1 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html
@@ -130,8 +130,8 @@ settings-connection, just like updating the settings-connection can make
 them different.
 

 

-Since 1.42, 1.40.10, "preserve-external-ip" flag (0x1) is supported to not
-remove externally added IP addresses and routes on the device during reapply.
+Since 1.42, "preserve-external-ip" flag (0x1) is supported to not remove
+externally added IP addresses and routes on the device during reapply.
 

 
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.html
index 96ae6b68..57560d60 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.html
@@ -108,6 +108,7 @@
 ActivatingConnection        readable   o
 Startup                     readable   b
 Version                     readable   s
+VersionInfo                 readable   au
 Capabilities                readable   au
 State                       readable   u
 Connectivity                readable   u
@@ -1057,6 +1058,28 @@ NetworkManager version.
 

+
The "VersionInfo" property

+
+VersionInfo  readable   au
+

+

+NetworkManager version and capabilities.
+

+

+The first element in the array is the NM_VERSION of the daemon. It is a binary representation
+of the "Version" and can be compared numerically. The version is encoded as
+"(major << 16 | minor << 8 | micro)".
+

+

+The following elements are a bitfield of static capabilities of the daemon. See
+#NMVersionInfoCapability for the available capability numbers.
+

+

+Since: 1.42
+

+

+

+

 
The "Capabilities" property

 
 Capabilities  readable   au
diff --git a/docs/api/html/index.html b/docs/api/html/index.html
index d4b84edd..f9ac99a9 100644
--- a/docs/api/html/index.html
+++ b/docs/api/html/index.html
@@ -16,7 +16,7 @@
 

 

 

 
 

 

-      for NetworkManager 1.40.12
+      for NetworkManager 1.42.0
 
       The latest version of this documentation can be found on-line at
       https://networkmanager.dev/docs/api/latest/.
@@ -79,7 +79,7 @@
 NetworkManager-dispatcher — Dispatch user scripts for NetworkManager
 
 

-NetworkManager-wait-online.service — Wait for network to come online
+NetworkManager-wait-online.service — Wait for the network to come online
 

 

 nmcli — command-line tool for controlling NetworkManager
@@ -120,160 +120,166 @@
 
Configuration Settings

 

 

-connection —  General Connection Profile Settings
+connection — General Connection Profile Settings
 

 

-6lowpan —  6LoWPAN Settings
+6lowpan — 6LoWPAN Settings
 

 

-802-1x —  IEEE 802.1x Authentication Settings
+802-1x — IEEE 802.1x Authentication Settings
 

 

-adsl —  ADSL Settings
+adsl — ADSL Settings
 

 

-bluetooth —  Bluetooth Settings
+bluetooth — Bluetooth Settings
 

 

-bond —  Bonding Settings
+bond — Bonding Settings
 

 

-bridge —  Bridging Settings
+bridge — Bridging Settings
 

 

-bridge-port —  Bridge Port Settings
+bridge-port — Bridge Port Settings
 

 

-cdma —  CDMA-based Mobile Broadband Settings
+cdma — CDMA-based Mobile Broadband Settings
 

 

-dcb —  Data Center Bridging Settings
+dcb — Data Center Bridging Settings
 

 

-dummy —  Dummy Link Settings
+dummy — Dummy Link Settings
 

 

-ethtool —  Ethtool Ethernet Settings
+ethtool — Ethtool Ethernet Settings
 

 

-generic —  Generic Link Settings
+generic — Generic Link Settings
 

 

-gsm —  GSM-based Mobile Broadband Settings
+gsm — GSM-based Mobile Broadband Settings
 

 

-infiniband —  Infiniband Settings
+infiniband — Infiniband Settings
 

 

-ipv4 —  IPv4 Settings
+ipv4 — IPv4 Settings
 

 

-ipv6 —  IPv6 Settings
+ipv6 — IPv6 Settings
 

 

-ip-tunnel —  IP Tunneling Settings
+ip-tunnel — IP Tunneling Settings
 

 

-macsec —  MACSec Settings
+macsec — MACSec Settings
 

 

-macvlan —  MAC VLAN Settings
+macvlan — MAC VLAN Settings
 

 

-match —  Match settings
+match — Match settings
 

 

-802-11-olpc-mesh —  OLPC Wireless Mesh Settings
+802-11-olpc-mesh — OLPC Wireless Mesh Settings
 

 

-ovs-bridge —  OvsBridge Link Settings
+ovs-bridge — OvsBridge Link Settings
 

 

-ovs-dpdk —  OvsDpdk Link Settings
+ovs-dpdk — OvsDpdk Link Settings
 

 

-ovs-interface —  Open vSwitch Interface Settings
+ovs-interface — Open vSwitch Interface Settings
 

 

-ovs-patch —  OvsPatch Link Settings
+ovs-patch — OvsPatch Link Settings
 

 

-ovs-port —  OvsPort Link Settings
+ovs-port — OvsPort Link Settings
 

 

-ppp —  Point-to-Point Protocol Settings
+ppp — Point-to-Point Protocol Settings
 

 

-pppoe —  PPP-over-Ethernet Settings
+pppoe — PPP-over-Ethernet Settings
 

 

-proxy —  WWW Proxy Settings
+proxy — WWW Proxy Settings
 

 

-serial —  Serial Link Settings
+serial — Serial Link Settings
 

 

-sriov —  SR-IOV settings
+sriov — SR-IOV settings
 

 

-tc —  Linux Traffic Control Settings
+tc — Linux Traffic Control Settings
 

 

-team —  Teaming Settings
+team — Teaming Settings
 

 

-team-port —  Team Port Settings
+team-port — Team Port Settings
 

 

-tun —  Tunnel Settings
+tun — Tunnel Settings
 

 

-user —  General User Profile Settings
+user — General User Profile Settings
 

 

-vlan —  VLAN Settings
+vlan — VLAN Settings
 

 

-vpn —  VPN Settings
+vpn — VPN Settings
 

 

-vrf —  VRF settings
+vrf — VRF settings
 

 

-vxlan —  VXLAN Settings
+vxlan — VXLAN Settings
 

 

-wifi-p2p —  Wi-Fi P2P Settings
+wifi-p2p — Wi-Fi P2P Settings
 

 

-wimax —  WiMax Settings
+wimax — WiMax Settings
 

 

-802-3-ethernet —  Wired Ethernet Settings
+802-3-ethernet — Wired Ethernet Settings
 

 

-wireguard —  WireGuard Settings
+wireguard — WireGuard Settings
 

 

-802-11-wireless —  Wi-Fi Settings
+802-11-wireless — Wi-Fi Settings
 

 

-802-11-wireless-security —  Wi-Fi Security Settings
+802-11-wireless-security — Wi-Fi Security Settings
 

 

-wpan —  IEEE 802.15.4 (WPAN) MAC Settings
+wpan — IEEE 802.15.4 (WPAN) MAC Settings
 

 

-bond-port —  Bond Port Settings
+bond-port — Bond Port Settings
 

 

-hostname —  Hostname settings
+hostname — Hostname settings
 

 

-ovs-external-ids —  OVS External IDs Settings
+loopback — Loopback Link Settings
 

 

-veth —  Veth Settings
+ovs-external-ids — OVS External IDs Settings
+

+

+ovs-other-config — OVS Other Config Settings
+

+

+veth — Veth Settings
 

 

 
Secret flag types

@@ -333,6 +339,9 @@
 org.freedesktop.NetworkManager.Device.Infiniband — Infiniband Device.
 
 

+org.freedesktop.NetworkManager.Device.Loopback — Loopback Device.
+

+

 org.freedesktop.NetworkManager.Device.Lowpan — 6LoWPAN Device.
 

 

diff --git a/docs/api/html/ix01.html b/docs/api/html/ix01.html
index d1897057..01dd7cd9 100644
--- a/docs/api/html/ix01.html
+++ b/docs/api/html/ix01.html
@@ -112,10 +112,12 @@
 

 
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:FwMark, The "FwMark" property
+

 
org.freedesktop.NetworkManager.Device.IPTunnel:InputKey, The "InputKey" property
 

 
org.freedesktop.NetworkManager.Device.IPTunnel:Local, The "Local" property
@@ -134,81 +136,83 @@
 

 
org.freedesktop.NetworkManager.Device.IPTunnel:Ttl, The "Ttl" property
 

-
org.freedesktop.NetworkManager.Device.Lowpan, org.freedesktop.NetworkManager.Device.Lowpan
+
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: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
 

@@ -220,97 +224,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
 

@@ -589,6 +593,8 @@
 
 
auto-negotiate, 802-3-ethernet
 

+
auto-route-ext-gw, ipv4, ipv6
+

 
autoconnect, connection
 

 
autoconnect-priority, connection
@@ -662,9 +668,9 @@
 

 
D

 

-
dad-timeout, ipv4, ipv6
+
dad-timeout, ipv4, ipv6
 

-
data, user, vpn, ovs-external-ids
+
data, user, vpn, ovs-external-ids, ovs-other-config
 

 
datapath-type, ovs-bridge
 

@@ -674,81 +680,81 @@
 

 
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
 

-
dhcp-client-id, ipv4
+
dhcp-client-id, ipv4
 

-
dhcp-duid, ipv6
+
dhcp-duid, ipv6
 

-
dhcp-fqdn, ipv4
+
dhcp-fqdn, ipv4
 

-
dhcp-hostname, ipv4, ipv6
+
dhcp-hostname, ipv4, ipv6
 

-
dhcp-hostname-flags, ipv4, ipv6
+
dhcp-hostname-flags, ipv4, ipv6
 

-
dhcp-iaid, ipv4, ipv6
+
dhcp-iaid, ipv4, ipv6
 

-
dhcp-reject-servers, ipv4, ipv6
+
dhcp-reject-servers, ipv4, ipv6
 

-
dhcp-send-hostname, ipv4, ipv6
+
dhcp-send-hostname, ipv4, ipv6
 

-
dhcp-timeout, ipv4, ipv6
+
dhcp-timeout, ipv4, ipv6
 

-
dhcp-vendor-class-identifier, ipv4
+
dhcp-vendor-class-identifier, ipv4
 

 
org.freedesktop.NetworkManager.DHCP4Config, org.freedesktop.NetworkManager.DHCP4Config
 

@@ -758,15 +764,17 @@
 
 
org.freedesktop.NetworkManager.DHCP6Config:Options, The "Options" property
 

-
dns, ipv4, ipv6
+
dns, ipv4, ipv6
 

-
dns-options, ipv4, ipv6
+
dns-data, ipv4, ipv6
+

+
dns-options, ipv4, ipv6
 

 
dns-over-tls, connection
 

-
dns-priority, ipv4, ipv6
+
dns-priority, ipv4, ipv6
 

-
dns-search, ipv4, ipv6
+
dns-search, ipv4, ipv6
 

 
domain-match, 802-1x
 

@@ -810,14 +818,14 @@
 
 
from-dns-lookup, hostname
 

-
fwmark, wireguard
+
fwmark, ip-tunnel, wireguard
 

 
 

 

 
G

 

-
gateway, ipv4, ipv6
+
gateway, ipv4, ipv6
 

 
gateway-ping-timeout, connection
 

@@ -851,13 +859,13 @@
 
 
identity, 802-1x
 

-
ignore-auto-dns, ipv4, ipv6
+
ignore-auto-dns, ipv4, ipv6
 

-
ignore-auto-routes, ipv4, ipv6
+
ignore-auto-routes, ipv4, ipv6
 

 
ingress-priority-map, vlan
 

-
input-key, ip-tunnel
+
input-key, ip-tunnel
 

 
interface-name, connection, bond, bridge, match, team, vlan
 

@@ -865,7 +873,7 @@
 
 
ip6-auto-default-route, wireguard
 

-
ip6-privacy, ipv6
+
ip6-privacy, ipv6
 

 

 

@@ -905,7 +913,7 @@
 
 
limit, vxlan
 

-
link-local, ipv4
+
link-local, ipv4
 

 
link-watchers, team, team-port
 

@@ -915,7 +923,7 @@
 
 
llmnr, connection
 

-
local, ip-tunnel, vxlan
+
local, ip-tunnel, vxlan
 

 
 

@@ -982,21 +990,21 @@
 
 
org.freedesktop.NetworkManager:AllDevices, The "AllDevices" property
 

-
org.freedesktop.NetworkManager:Capabilities, The "Capabilities" property
+
org.freedesktop.NetworkManager:Capabilities, The "Capabilities" property
 

 
org.freedesktop.NetworkManager:Checkpoints, The "Checkpoints" property
 

-
org.freedesktop.NetworkManager:Connectivity, The "Connectivity" property
+
org.freedesktop.NetworkManager:Connectivity, The "Connectivity" property
 

-
org.freedesktop.NetworkManager:ConnectivityCheckAvailable, The "ConnectivityCheckAvailable" property
+
org.freedesktop.NetworkManager:ConnectivityCheckAvailable, The "ConnectivityCheckAvailable" property
 

-
org.freedesktop.NetworkManager:ConnectivityCheckEnabled, The "ConnectivityCheckEnabled" property
+
org.freedesktop.NetworkManager:ConnectivityCheckEnabled, The "ConnectivityCheckEnabled" property
 

-
org.freedesktop.NetworkManager:ConnectivityCheckUri, The "ConnectivityCheckUri" property
+
org.freedesktop.NetworkManager:ConnectivityCheckUri, The "ConnectivityCheckUri" property
 

 
org.freedesktop.NetworkManager:Devices, The "Devices" property
 

-
org.freedesktop.NetworkManager:GlobalDnsConfiguration, The "GlobalDnsConfiguration" property
+
org.freedesktop.NetworkManager:GlobalDnsConfiguration, The "GlobalDnsConfiguration" property
 

 
org.freedesktop.NetworkManager:Metered, The "Metered" property
 

@@ -1010,10 +1018,12 @@
 
 
org.freedesktop.NetworkManager:Startup, The "Startup" property
 

-
org.freedesktop.NetworkManager:State, The "State" property
+
org.freedesktop.NetworkManager:State, The "State" property
 

 
org.freedesktop.NetworkManager:Version, The "Version" property
 

+
org.freedesktop.NetworkManager:VersionInfo, The "VersionInfo" property
+

 
org.freedesktop.NetworkManager:WimaxEnabled, The "WimaxEnabled" property
 

 
org.freedesktop.NetworkManager:WimaxHardwareEnabled, The "WimaxHardwareEnabled" property
@@ -1030,7 +1040,7 @@
 

 
max-age, bridge
 

-
may-fail, ipv4, ipv6
+
may-fail, ipv4, ipv6
 

 
mcast-rejoin-count, team
 

@@ -1042,7 +1052,7 @@
 
 
metered, connection
 

-
method, ipv4, ipv6, proxy
+
method, ipv4, ipv6, proxy
 

 
mka-cak, macsec
 

@@ -1050,7 +1060,7 @@
 
 
mka-ckn, macsec
 

-
mode, ip-tunnel, macsec, macvlan, tun, 802-11-wireless
+
mode, ip-tunnel, macsec, macvlan, tun, 802-11-wireless
 

 
mppe-stateful, ppp
 

@@ -1058,7 +1068,7 @@
 
 
mru, ppp
 

-
mtu, cdma, gsm, infiniband, ipv6, ip-tunnel, ppp, 802-3-ethernet, wireguard, 802-11-wireless
+
mtu, cdma, gsm, infiniband, ipv6, ip-tunnel, ppp, 802-3-ethernet, wireguard, 802-11-wireless, loopback
 

 
mud-url, connection
 

@@ -1099,79 +1109,85 @@
 

 
n-rxq, ovs-dpdk
 

+
n-rxq-desc, ovs-dpdk
+

+
n-txq-desc, ovs-dpdk
+

 
network-id, gsm
 

 
network-name, wimax
 

-
never-default, ipv4, ipv6
+
never-default, ipv4, ipv6
+

+
NM80211ApFlags, enum NM80211ApFlags
 

-
NM80211ApFlags, enum NM80211ApFlags
+
NM80211ApSecurityFlags, enum NM80211ApSecurityFlags
 

-
NM80211ApSecurityFlags, enum NM80211ApSecurityFlags
+
NM80211Mode, enum NM80211Mode
 

-
NM80211Mode, enum NM80211Mode
+
NMActivationStateFlags, enum NMActivationStateFlags
 

-
NMActivationStateFlags, enum NMActivationStateFlags
+
NMActiveConnectionState, enum NMActiveConnectionState
 

-
NMActiveConnectionState, enum NMActiveConnectionState
+
NMActiveConnectionStateReason, enum NMActiveConnectionStateReason
 

-
NMActiveConnectionStateReason, enum NMActiveConnectionStateReason
+
NMBluetoothCapabilities, enum NMBluetoothCapabilities
 

-
NMBluetoothCapabilities, enum NMBluetoothCapabilities
+
NMCapability, enum NMCapability
 

-
NMCapability, enum NMCapability
+
NMCheckpointCreateFlags, enum NMCheckpointCreateFlags
 

-
NMCheckpointCreateFlags, enum NMCheckpointCreateFlags
+
NMClientPermission, enum NMClientPermission
 

-
NMClientPermission, enum NMClientPermission
+
NMClientPermissionResult, enum NMClientPermissionResult
 

-
NMClientPermissionResult, enum NMClientPermissionResult
+
NMConnectionMultiConnect, enum NMConnectionMultiConnect
 

-
NMConnectionMultiConnect, enum NMConnectionMultiConnect
+
NMConnectivityState, enum NMConnectivityState
 

-
NMConnectivityState, enum NMConnectivityState
+
NMDeviceCapabilities, enum NMDeviceCapabilities
 

-
NMDeviceCapabilities, enum NMDeviceCapabilities
+
NMDeviceInterfaceFlags, enum NMDeviceInterfaceFlags
 

-
NMDeviceInterfaceFlags, enum NMDeviceInterfaceFlags
+
NMDeviceModemCapabilities, enum NMDeviceModemCapabilities
 

-
NMDeviceModemCapabilities, enum NMDeviceModemCapabilities
+
NMDeviceReapplyFlags, enum NMDeviceReapplyFlags
 

-
NMDeviceReapplyFlags, enum NMDeviceReapplyFlags
+
NMDeviceState, enum NMDeviceState
 

-
NMDeviceState, enum NMDeviceState
+
NMDeviceStateReason, enum NMDeviceStateReason
 

-
NMDeviceStateReason, enum NMDeviceStateReason
+
NMDeviceType, enum NMDeviceType
 

-
NMDeviceType, enum NMDeviceType
+
NMDeviceWifiCapabilities, enum NMDeviceWifiCapabilities
 

-
NMDeviceWifiCapabilities, enum NMDeviceWifiCapabilities
+
NMIPTunnelMode, enum NMIPTunnelMode
 

-
NMIPTunnelMode, enum NMIPTunnelMode
+
NMManagerReloadFlags, enum NMManagerReloadFlags
 

-
NMManagerReloadFlags, enum NMManagerReloadFlags
+
NMMetered, enum NMMetered
 

-
NMMetered, enum NMMetered
+
NMMptcpFlags, enum NMMptcpFlags
 

-
NMMptcpFlags, enum NMMptcpFlags
+
NMRadioFlags, enum NMRadioFlags
 

-
NMRadioFlags, enum NMRadioFlags
+
NMRollbackResult, enum NMRollbackResult
 

-
NMRollbackResult, enum NMRollbackResult
+
NMSecretAgentCapabilities, enum NMSecretAgentCapabilities
 

-
NMSecretAgentCapabilities, enum NMSecretAgentCapabilities
+
NMSecretAgentGetSecretsFlags, enum NMSecretAgentGetSecretsFlags
 

-
NMSecretAgentGetSecretsFlags, enum NMSecretAgentGetSecretsFlags
+
NMSettingsAddConnection2Flags, enum NMSettingsAddConnection2Flags
 

-
NMSettingsAddConnection2Flags, enum NMSettingsAddConnection2Flags
+
NMSettingsConnectionFlags, enum NMSettingsConnectionFlags
 

-
NMSettingsConnectionFlags, enum NMSettingsConnectionFlags
+
NMSettingsUpdate2Flags, enum NMSettingsUpdate2Flags
 

-
NMSettingsUpdate2Flags, enum NMSettingsUpdate2Flags
+
NMState, enum NMState
 

-
NMState, enum NMState
+
NMTernary, enum NMTernary
 

-
NMTernary, enum NMTernary
+
NMVersionInfoCapability, enum NMVersionInfoCapability
 

 
NMVpnConnectionState, enum NMVpnConnectionState
 

@@ -1181,7 +1197,7 @@
 
 
NMVpnServiceState, enum NMVpnServiceState
 

-
NMWimaxNspNetworkType, enum NMWimaxNspNetworkType
+
NMWimaxNspNetworkType, enum NMWimaxNspNetworkType
 

 
no-vj-comp, ppp
 

@@ -1202,13 +1218,15 @@
 

 
O

 

+
ofport-request, ovs-interface
+

 
only-from-default, hostname
 

 
optional, 802-1x
 

 
options, bond
 

-
output-key, ip-tunnel
+
output-key, ip-tunnel
 

 
owner, tun
 

@@ -1247,7 +1265,7 @@
 
 
path-cost, bridge-port
 

-
path-mtu-discovery, ip-tunnel
+
path-mtu-discovery, ip-tunnel
 

 
peer, ovs-patch, wifi-p2p, veth
 

@@ -1311,17 +1329,17 @@
 
 
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
 

@@ -1355,7 +1373,7 @@
 
 
proto, 802-11-wireless-security
 

-
protocol, adsl
+
protocol, adsl, vlan
 

 
proxy, vxlan
 

@@ -1377,7 +1395,7 @@
 

 
R

 

-
ra-timeout, ipv6
+
ra-timeout, ipv6
 

 
rate, 802-11-wireless
 

@@ -1393,21 +1411,23 @@
 
 
refuse-pap, ppp
 

-
remote, ip-tunnel, vxlan
+
remote, ip-tunnel, vxlan
 

 
require-mppe, ppp
 

 
require-mppe-128, ppp
 

-
required-timeout, ipv4, ipv6
+
required-timeout, ipv4, ipv6
 

-
route-data, ipv4, ipv6
+
route-data, ipv4, ipv6
 

-
route-metric, ipv4, ipv6
+
route-metric, ipv4, ipv6
 

-
route-table, ipv4, ipv6
+
route-table, ipv4, ipv6
 

-
routes, ipv4, ipv6
+
routes, ipv4, ipv6
+

+
routing-rules, ipv4, ipv6
 

 
rsc, vxlan
 

@@ -1507,15 +1527,17 @@
 
 
timestamp, connection
 

-
token, ipv6
+
token, ipv6
 

-
tos, ip-tunnel, vxlan
+
tos, ip-tunnel, vxlan
 

 
total-vfs, sriov
 

 
transport-mode, infiniband
 

-
ttl, ip-tunnel, vxlan
+
trunks, ovs-port
+

+
ttl, ip-tunnel, vxlan
 

 
tx-power, 802-11-wireless
 

@@ -1547,7 +1569,7 @@
 
 
vlan-filtering, bridge
 

-
vlan-mode, ovs-port
+
vlan-mode, ovs-port
 

 
vlan-protocol, bridge
 

diff --git a/docs/api/html/manpages.html b/docs/api/html/manpages.html
index 4ce24258..b3befb31 100644
--- a/docs/api/html/manpages.html
+++ b/docs/api/html/manpages.html
@@ -35,7 +35,7 @@
 NetworkManager-dispatcher — Dispatch user scripts for NetworkManager
 
 

-NetworkManager-wait-online.service — Wait for network to come online
+NetworkManager-wait-online.service — Wait for the network to come online
 

 

 nmcli — command-line tool for controlling NetworkManager
diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html
index 892a1924..5d7db24a 100644
--- a/docs/api/html/nm-dbus-types.html
+++ b/docs/api/html/nm-dbus-types.html
@@ -29,13 +29,33 @@
 
 

 

+
enum NMVersionInfoCapability

+
%_NM_VERSION_INFO_CAPABILITY_UNUSED: a dummy capability. It has no meaning, don't use it.

+
Currently no enum values are defined. These capabilities are exposed on D-Bus in the "VersionInfo" bit field.

+
Since: 1.42

+

+

+
Values

+

++++++
+
+







+

+

+

+

 
enum NMCapability

 
NMCapability names the numbers in the Capabilities property. Capabilities are positive numbers. They are part of stable API and a certain capability number is guaranteed not to change.

 
The range 0x7000 - 0x7FFF of capabilities is guaranteed not to be used by upstream NetworkManager. It could thus be used for downstream extensions.

 
Since: 1.6

 

 

-
Values

+
Values

 
@@ -84,7 +104,7 @@
 
NMState values indicate the current overall networking state.

-
Values

+
Values

 

 
 

 
 
@@ -222,7 +242,7 @@
 
enum NMConnectivityState

-
Values

+
Values

 

 
 

 
 
@@ -316,7 +336,7 @@
 
NMDeviceType values indicate the type of hardware represented by a device object.

-
Values

+
Values

 

 
 

 
 
@@ -805,6 +825,21 @@
 
+
+
+
+
+
+

 
 

 
 
 

+
NM_DEVICE_TYPE_LOOPBACK

+

+		
+
= 32

+

+		
+
a loopback interface. Since: 1.42.

+

+		 

 
 

 

@@ -815,7 +850,7 @@
 
General device capability flags.

 

 

-
Values

+
Values

 
@@ -909,7 +944,7 @@
 
802.11 specific device encryption and authentication capabilities.

-
Values

+
Values

 

 
 

 
 
@@ -1138,7 +1173,7 @@
 
802.11 access point flags.

-
Values

+
Values

 

 
 

 
 
@@ -1232,7 +1267,7 @@
 
802.11 access point security and authentication flags.  These flags describe the current security requirements of an access point as determined from the access point's beacon.

-
Values

+
Values

 

 
 

 
 
@@ -1476,7 +1511,7 @@
 
Indicates the 802.11 mode an access point or device is currently in.

-
Values

+
Values

 

 
 

 
 
@@ -1570,7 +1605,7 @@
 
NMBluetoothCapabilities values indicate the usable capabilities of a Bluetooth device.

-
Values

+
Values

 

 
 

 
 
@@ -1634,7 +1669,7 @@
 
NMDeviceModemCapabilities values indicate the generic radio access technology families a modem device supports.  For more information on the specific access technologies the device supports use the ModemManager D-Bus API.

-
Values

+
Values

 

 
 

 
 
@@ -1743,7 +1778,7 @@
 
WiMAX network type.

-
Values

+
Values

 

 
 

 
 
@@ -1821,7 +1856,7 @@
 
enum NMDeviceState

-
Values

+
Values

 

 
 

 
 
@@ -2035,7 +2070,7 @@
 
Device state change reason codes

-
Values

+
Values

 

 
 

 
 
@@ -3079,7 +3114,7 @@
 
Since: 1.2

-
Values

+
Values

 

 
 

 
 
@@ -3173,7 +3208,7 @@
 
Since: 1.14

-
Values

+
Values

 

 
 

 
 
@@ -3252,7 +3287,7 @@
 
NMActiveConnectionState values indicate the state of a connection to a specific network while it is starting, connected, or disconnecting from that network.

-
Values

+
Values

 

 
 

 
 
@@ -3347,7 +3382,7 @@
 
Since: 1.8

-
Values

+
Values

 

 
 

 
 
@@ -3591,7 +3626,7 @@
 
NMSecretAgentGetSecretsFlags values modify the behavior of a GetSecrets request.

-
Values

+
Values

 

 
 

 
 
@@ -3715,7 +3750,7 @@
 
NMSecretAgentCapabilities indicate various capabilities of the agent.

-
Values

+
Values

 

 
 

 
 
@@ -3765,7 +3800,7 @@
 
Since: 1.2

-
Values

+
Values

 

 
 

 
 
@@ -3965,7 +4000,7 @@
 
Since: 1.12 (public since 1.4, g-ir since 1.12)

-
Values

+
Values

 

 
 

 
 
@@ -4075,7 +4110,7 @@
 
Since: 1.4

-
Values

+
Values

 

 
 

 
 
@@ -4155,7 +4190,7 @@
 
Since: 1.12

-
Values

+
Values

 

 
 

 
 
@@ -4250,7 +4285,7 @@
 
Since: 1.10

-
Values

+
Values

 

 
 

 
 
@@ -4405,7 +4440,7 @@
 
Since: 1.20

-
Values

+
Values

 

 
 

 
 
@@ -4484,7 +4519,7 @@
 
Since: 1.12

-
Values

+
Values

 

 
 

 
 
@@ -4621,11 +4656,10 @@
 

 
enum NMDeviceReapplyFlags

 
Flags for the Reapply() D-Bus call of a device and nm_device_reapply_async().

-
Since: 1.42, 1.40.10

-
On 1.40.10+, no GFlags type is created.

+
Since: 1.42

 

 

-
Values

+
Values

 

 
 

@@ -4675,7 +4709,7 @@
 
Since: 1.14

-
Values

+
Values

 

 
 

 
 
@@ -4740,7 +4774,7 @@
 
Since: 1.22

-
Values

+
Values

 

 
 

 
 
@@ -4835,7 +4869,7 @@
 
Since: 1.22

-
Values

+
Values

 

 
 

 
 
@@ -4944,7 +4978,7 @@
 
NMClientPermission values indicate various permissions that NetworkManager clients can obtain to perform certain tasks on behalf of the current user.

-
Values

+
Values

 

 
 

 
 
@@ -5233,7 +5267,7 @@
 
NMClientPermissionResult values indicate what authorizations and permissions the user requires to obtain a given NMClientPermission

-
Values

+
Values

 

 
 

 
 
@@ -5313,7 +5347,7 @@
 
Since: 1.38

-
Values

+
Values

 

 
 

 
 
@@ -5377,7 +5411,7 @@
 
Since: 1.40

-
Values

+
Values

 

 
 

 
 
diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html
index fd1f0892..96bd6976 100644
--- a/docs/api/html/nm-settings-dbus.html
+++ b/docs/api/html/nm-settings-dbus.html
@@ -95,7 +95,7 @@
 

 
connection setting

-
 General Connection Profile Settings.

+
General Connection Profile Settings.

 

 
 

 
@@ -115,264 +115,264 @@
 auth-retries
-
+Currently, this only applies to 802-1x authentication.
-
+Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.
-
+
-
+
-
+
-
+This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
-
+
-
+
-
+For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.
-
+
-
+This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
-
+
-
+This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
-
+When updating this property on a currently activated connection, the change takes effect immediately.
-
+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).
-
+If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".
-
+
-
+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.
-
+
-
+
-
+
-
+If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.
-
+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).
-
+
-
+The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").
-
+The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.
-
+The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.
-
+When updating this property on a currently activated connection, the change takes effect immediately.

 
 

 
int32
 -1 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.
+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.
 

 

 
 autoconnect
 boolean
 TRUE Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.
+Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.
 
- Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile.
+Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile.
 
- Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.
+Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.
 
- If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined.
+If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined.
 
- Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.
 

 

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

 

 
 autoconnect-retries
 int32
 -1 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.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.
 

 

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

 

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

 

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

 

 
 id
 string
   A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".
 

 

 
 interface-name
 string
   The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings).
+The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings).
 
- For software devices this specifies the name of the created device.
+For software devices this specifies the name of the created device.
 
- For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.
 

 

 
 lldp
 int32
 -1 Whether LLDP is enabled for the connection.Whether LLDP is enabled for the connection.
 

 

 
 llmnr
 int32
 -1 Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.
+Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.
 
- The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").
+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.
 

 

 
 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.
 

 

 
 mdns
 int32
 -1 Whether mDNS is enabled for the connection.
+Whether mDNS is enabled for the connection.
 
- The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").
+The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (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.
 

 

 
 metered
 NMMetered (int32)
   Whether the connection is metered.
+Whether the connection is metered.
 
- When updating this property on a currently activated connection, the change takes effect immediately.
 

 

 
 mptcp-flags
 uint32
 0 Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints.
+Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints.
 
- If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered.
+If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered.
 
- The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags.
+The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags.
 
- Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless.
+Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless.
 
- Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that.
+Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that.
 
- When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.
+When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.
 
- If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl.
+If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl.
 
- NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp.
+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).
 

 

 
 mud-url
 string
   If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://".
+If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://".
 
- The special value "none" is allowed to indicate that no MUD URL is used.
+The special value "none" is allowed to indicate that no MUD URL is used.
 
- If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".
 

 

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

 

 
 permissions
 array of string
   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".
+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.
 

 

 
 read-only
 boolean
 FALSE FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.
 

 

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

 

 
 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.
 

 

 
 stable-id
 string
   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.
+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 as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid].
+The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid].
 
- Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.
+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 runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
+The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
 
- If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.
 

 

 
 timestamp
 uint64
 0 The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.
+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).
 

 

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

 

 
 uuid
 string
   A universally unique identifier for the connection, for example generated with libuuid.  It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network.  For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes.
+A universally unique identifier for the connection, for example generated with libuuid.  It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network.  For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes.
 
- The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").
 

 

 
 wait-activation-delay
 int32
 -1 Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.
+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.
 

 

 
 wait-device-timeout
 int32
 -1 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.
+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.
 

 

 
 zone
 string
   The trust level of a the connection.  Free form case-insensitive string (for example "Home", "Work", "Public").  NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall.
+The trust level of a the connection.  Free form case-insensitive string (for example "Home", "Work", "Public").  NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall.
 
- When updating this property on a currently activated connection, the change takes effect immediately.
 

 
 

@@ -380,7 +380,7 @@
 

 

 
6lowpan setting

-
 6LoWPAN Settings.

+
6LoWPAN Settings.

 
@@ -399,14 +399,14 @@
 parent
-
+

 
 

 
string
   If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.
 

 

 

 

 

 
802-1x setting

-
 IEEE 802.1x Authentication Settings.

+
IEEE 802.1x Authentication Settings.

 
@@ -426,351 +426,355 @@
 altsubject-matches
-
+
-
+
-
+
-
+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.
-
+
-
+
-
+If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.
-
+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.
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+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.
-
+
-
+
-
+If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.
-
+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.
-
+
-
+
-
+
-
+
-
+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.
-
+
-
+
-
+
-
+
-
+
-
+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.
-
+
-
+
-
+
-
+

 
 

 
array of string
   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.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.
 

 

 
 anonymous-identity
 string
   Anonymous identity string for EAP authentication methods.  Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.Anonymous identity string for EAP authentication methods.  Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.
 

 

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

 

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

 

 
 ca-cert-password
 string
   The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
 

 

 
 ca-cert-password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "ca-cert-password" property.Flags indicating how to handle the "ca-cert-password" property.
 

 

 
 ca-path
 string
   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 "ca-cert" property.
+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 "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.
 

 

 
 client-cert
 byte array
   Contains the client certificate if used by the EAP method specified in the "eap" property.
+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.
 

 

 
 client-cert-password
 string
   The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
 

 

 
 client-cert-password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "client-cert-password" property.Flags indicating how to handle the "client-cert-password" property.
 

 

 
 domain-match
 string
   Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.
 

 

 
 domain-suffix-match
 string
   Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.
 

 

 
 eap
 array of string
   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.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.
 

 

 
 identity
 string
   Identity string for EAP authentication methods.  Often the user's user or login name.Identity string for EAP authentication methods.  Often the user's user or login name.
 

 

 
 optional
 boolean
 FALSE 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.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.
 

 

 
 pac-file
 string
   UTF-8 encoded file path containing PAC for EAP-FAST.UTF-8 encoded file path containing PAC for EAP-FAST.
 

 

 
 password
 string
   UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.
 

 

 
 password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property.
 

 

 
 password-raw
 byte array
   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.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.
 

 

 
 password-raw-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "password-raw" property.Flags indicating how to handle the "password-raw" property.
 

 

 
 phase1-auth-flags
 uint32
 0 Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly 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 settings. See the wpa_supplicant documentation for more details.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.
 

 

 
 phase1-fast-provisioning
 string
   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.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.
 

 

 
 phase1-peaplabel
 string
   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.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.
 

 

 
 phase1-peapver
 string
   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.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.
 

 

 
 phase2-altsubject-matches
 array of string
   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.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.
 

 

 
 phase2-auth
 string
   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.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.
 

 

 
 phase2-autheap
 string
   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.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.
 

 

 
 phase2-ca-cert
 byte array
   Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.
+Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.
 
- Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.
+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.
 

 

 
 phase2-ca-cert-password
 string
   The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
 

 

 
 phase2-ca-cert-password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "phase2-ca-cert-password" property.Flags indicating how to handle the "phase2-ca-cert-password" property.
 

 

 
 phase2-ca-path
 string
   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.
+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.
 

 

 
 phase2-client-cert
 byte array
   Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.
+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.
 

 

 
 phase2-client-cert-password
 string
   The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
 

 

 
 phase2-client-cert-password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "phase2-client-cert-password" property.Flags indicating how to handle the "phase2-client-cert-password" property.
 

 

 
 phase2-domain-match
 string
   Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.
 

 

 
 phase2-domain-suffix-match
 string
   Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.
 

 

 
 phase2-private-key
 byte array
   Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls".
+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.
 

 

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

 

 
 phase2-private-key-password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "phase2-private-key-password" property.Flags indicating how to handle the "phase2-private-key-password" property.
 

 

 
 phase2-subject-match
 string
   Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed.  This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match.Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.
+
+This property is deprecated since version 1.2.Use "phase2-domain-suffix-match" instead.
 

 

 
 pin
 string
   PIN used for EAP authentication methods.PIN used for EAP authentication methods.
 

 

 
 pin-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "pin" property.Flags indicating how to handle the "pin" property.
 

 

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

 

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

 

 
 private-key-password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "private-key-password" property.Flags indicating how to handle the "private-key-password" property.
 

 

 
 subject-match
 string
   Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed.  This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match.Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.
+
+This property is deprecated since version 1.2.Use "phase2-domain-suffix-match" instead.
 

 

 
 system-ca-certs
 boolean
 FALSE 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).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).
 

 
 

@@ -778,7 +782,7 @@
 

 

 
adsl setting

-
 ADSL Settings.

+
ADSL Settings.

 
@@ -798,49 +802,49 @@
 encapsulation
-
+
-
+
-
+
-
+
-
+
-
+
-
+

 
 

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

 

 
 password
 string
   Password used to authenticate with the ADSL service.Password used to authenticate with the ADSL service.
 

 

 
 password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property.
 

 

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

 

 
 username
 string
   Username used to authenticate with the ADSL service.Username used to authenticate with the ADSL service.
 

 

 
 vci
 uint32
 0 VCI of ADSL connectionVCI of ADSL connection
 

 

 
 vpi
 uint32
 0 VPI of ADSL connectionVPI of ADSL connection
 

 
 

@@ -848,7 +852,7 @@
 

 

 
bluetooth setting

-
 Bluetooth Settings.

+
Bluetooth Settings.

 
@@ -868,14 +872,14 @@
 bdaddr
-
+
-
+

 
 

 
byte array
   The Bluetooth address of the device.The Bluetooth address of the device.
 

 

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

 
 

@@ -883,7 +887,7 @@
 

 

 
bond setting

-
 Bonding Settings.

+
Bonding Settings.

 
@@ -910,7 +914,7 @@
 options
-
+

 
 

 
dict of string to string
 {'mode': 'balance-rr'} 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]).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]).
 

 
 

@@ -918,7 +922,7 @@
 

 

 
bridge setting

-
 Bridging Settings.

+
Bridging Settings.

 
@@ -938,37 +942,37 @@
 ageing-time
-
+
-
+
-
+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.
-
+
-
+
-
+If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge.
+
+This property is deprecated since version 1.12.Use the "cloned-mac-address" property instead.
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+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).
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.
-
+
-
+where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.

 
 

 
uint32
 300 The Ethernet MAC address aging time, in seconds.The Ethernet MAC address aging time, in seconds.
 

 

 
 forward-delay
 uint32
 15 The Spanning Tree Protocol (STP) forwarding delay, in seconds.The Spanning Tree Protocol (STP) forwarding delay, in seconds.
 

 

 
 group-address
 byte array
   If specified, The MAC address of the multicast group this bridge uses for STP.
+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.
 

 

 
 group-forward-mask
 uint32
 0 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.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.
 

 

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

 

 
@@ -982,166 +986,168 @@
 mac-address
 byte array
   If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set.
+If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set.
 
- If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1
 

 

 
 max-age
 uint32
 20 The Spanning Tree Protocol (STP) maximum message age, in seconds.The Spanning Tree Protocol (STP) maximum message age, in seconds.
 

 

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

 

 
 multicast-last-member-count
 uint32
 2 Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.
 

 

 
 multicast-last-member-interval
 uint64
 100 Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.
 

 

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

 

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

 

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

 

 
 multicast-query-interval
 uint64
 12500 Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.
 

 

 
 multicast-query-response-interval
 uint64
 1000 Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.
 

 

 
 multicast-query-use-ifaddr
 boolean
 FALSE 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.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.
 

 

 
 multicast-router
 string
   Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work.
+Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work.
 
- 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).
 

 

 
 multicast-snooping
 boolean
 TRUE 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.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.
 

 

 
 multicast-startup-query-count
 uint32
 2 Set the number of IGMP queries to send during startup phase.Set the number of IGMP queries to send during startup phase.
 

 

 
 multicast-startup-query-interval
 uint64
 3125 Sets the time (in deciseconds) between queries sent out at startup to determine membership information.Sets the time (in deciseconds) between queries sent out at startup to determine membership information.
 

 

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

 

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

 

 
 vlan-default-pvid
 uint32
 1 The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.
 

 

 
 vlan-filtering
 boolean
 FALSE Control whether VLAN filtering is enabled on the bridge.Control whether VLAN filtering is enabled on the bridge.
 

 

 
 vlan-protocol
 string
   If specified, the protocol used for VLAN filtering.
+If specified, the protocol used for VLAN filtering.
 
- Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.
 

 

 
 vlan-stats-enabled
 boolean
 FALSE Controls whether per-VLAN stats accounting is enabled.Controls whether per-VLAN stats accounting is enabled.
 

 

 
 vlans
 array of vardict
   Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured  by the bridge.vlan-default-pvid property.
+Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured  by the bridge.vlan-default-pvid property.
 
- In nmcli the VLAN list can be specified with the following syntax:
+In nmcli the VLAN list can be specified with the following syntax:
 
- $vid [pvid] [untagged] [, $vid [pvid] [untagged]]...
+$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.
 

 
 

@@ -1149,7 +1155,7 @@
 

 

 
bridge-port setting

-
 Bridge Port Settings.

+
Bridge Port Settings.

 
@@ -1169,34 +1175,34 @@
 hairpin-mode
-
+
-
+
-
+
-
+where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.

 
 

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

 

 
 path-cost
 uint32
 100 The Spanning Tree Protocol (STP) port cost for destinations via this port.The Spanning Tree Protocol (STP) port cost for destinations via this port.
 

 

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

 

 
 vlans
 array of vardict
   Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property.
+Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property.
 
- In nmcli the VLAN list can be specified with the following syntax:
+In nmcli the VLAN list can be specified with the following syntax:
 
- $vid [pvid] [untagged] [, $vid [pvid] [untagged]]...
+$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.
 

 
 

@@ -1204,7 +1210,7 @@
 

 

 
cdma setting

-
 CDMA-based Mobile Broadband Settings.

+
CDMA-based Mobile Broadband Settings.

 
@@ -1224,35 +1230,35 @@
 mtu
-
+
-
+
-
+
-
+
-
+

 
 

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

 

 
 number
 string
   The number to dial to establish the connection to the CDMA-based mobile broadband network, if any.  If not specified, the default number (#777) is used when required.The number to dial to establish the connection to the CDMA-based mobile broadband network, if any.  If not specified, the default number (#777) is used when required.
 

 

 
 password
 string
   The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.
 

 

 
 password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property.
 

 

 
 username
 string
   The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.
 

 
 

@@ -1260,7 +1266,7 @@
 

 

 
dcb setting

-
 Data Center Bridging Settings.

+
Data Center Bridging Settings.

 
@@ -1280,107 +1286,107 @@
 app-fcoe-flags
-
+
-
+Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+

 
 

 
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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
 

 

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

 

 
 app-fcoe-priority
 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 NM_SETTING_DCB_FLAG_ENABLE (0x1) 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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
 

 

 
 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 NM_SETTING_DCB_FLAG_ENABLE (0x1) 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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
 

 

 
 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 NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.
 

 

 
 priority-bandwidth
 array of uint32
   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.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.
 

 

 
 priority-flow-control
 array of uint32
   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.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.
 

 

 
 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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
 

 

 
 priority-group-bandwidth
 array of uint32
   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.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.
 

 

 
 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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
 

 

 
 priority-group-id
 array of uint32
   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.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.
 

 

 
 priority-strict-bandwidth
 array of uint32
   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.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.
 

 

 
 priority-traffic-class
 array of uint32
   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.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.
 

 
 

@@ -1388,7 +1394,7 @@
 

 

 
dummy setting

-
 Dummy Link Settings.

+
Dummy Link Settings.

 
@@ -1408,7 +1414,7 @@
 

 
ethtool setting

-
 Ethtool Ethernet Settings.

+
Ethtool Ethernet Settings.

 

 
 

 
@@ -1428,7 +1434,7 @@
 

 
generic setting

-
 Generic Link Settings.

+
Generic Link Settings.

 

 
 

 
@@ -1448,7 +1454,7 @@
 

 
gsm setting

-
 GSM-based Mobile Broadband Settings.

+
GSM-based Mobile Broadband Settings.

 

 
 

 
@@ -1468,98 +1474,100 @@
 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.
 

 

 
 auto-config
 boolean
 FALSE 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.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.
 

 

 
 device-id
 string
   The device unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will only apply to the specified device.The device unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will only apply to the specified device.
 

 

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

 

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

 

 
 network-id
 string
   The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration.  If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration.  If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.
 

 

 
 number
 string
   Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1Legacy setting that used to help establishing PPP data sessions for GSM-based modems.
+
+This property is deprecated since version 1.16.User-provided values for this setting are no longer used.
 

 

 
 password
 string
   The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.
 

 

 
 password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property.
 

 

 
 pin
 string
   If the SIM is locked with a PIN it must be unlocked before any other operations are requested.  Specify the PIN here to allow operation of the device.If the SIM is locked with a PIN it must be unlocked before any other operations are requested.  Specify the PIN here to allow operation of the device.
 

 

 
 pin-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "pin" property.Flags indicating how to handle the "pin" property.
 

 

 
 sim-id
 string
   The SIM card unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.The SIM card unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.
 

 

 
 sim-operator-id
 string
   A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.
 

 

 
 username
 string
   The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.
 

 
 

@@ -1567,7 +1575,7 @@
 

 

 
infiniband setting

-
 Infiniband Settings.

+
Infiniband Settings.

 
@@ -1587,35 +1595,35 @@
 mac-address
-
+
-
+
-
+
-
+
-
+

 
 

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

 

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

 

 
 p-key
 int32
 -1 The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.
 

 

 
 parent
 string
   The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".
 

 

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

 
 

@@ -1623,7 +1631,7 @@
 

 

 
ipv4 setting

-
 IPv4 Settings.

+
IPv4 Settings.

 
@@ -1650,99 +1658,109 @@
 addresses
-
+
+
+
+
+
+
+
-
+The property is currently implemented only for IPv4.
-
+If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.
-
+
-
+
-
+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.
-
+
-
+This property is currently not implemented for DHCPv6.
-
+
-
+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.
-
+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.
-
+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).
-
+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".
-
+
-
+
-
+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".
-
+
-
+For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.
-
+
-
+A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).
-
+
-
+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.
-
+
+
+
+
+
+
+

 
 

 
array of array of uint32
  Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.  Array of IPv4 address structures.  Each IPv4 address structure is composed of 3 32-bit values; the first being the IPv4 address (network byte order), the second the prefix (1 - 32), and last the IPv4 gateway (network byte order). The gateway may be left as 0 if no gateway exists for that subnet.Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.
+Array of IPv4 address structures.  Each IPv4 address structure is composed of 3 32-bit values; the first being the IPv4 address (network byte order), the second the prefix (1 - 32), and last the IPv4 gateway (network byte order). The gateway may be left as 0 if no gateway exists for that subnet.

+auto-route-ext-gwNMTernary (int32) 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.
 

 

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

 

 
 dhcp-client-id
 string
   A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.
+A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.
 
- The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links.
+The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links.
 
- 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 "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 "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.
+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.
 

 

 
 dhcp-fqdn
 string
   If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.
 

 

 
 dhcp-hostname
 string
   If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.
 

 

 
 dhcp-hostname-flags
 uint32
 0 Flags for the DHCP hostname and FQDN.
+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 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.
 

 

 
 dhcp-iaid
 string
   A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.
 

 

 
 dhcp-reject-servers
 array of string
   Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.
+Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.
 
- 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").
+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.
 

 

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

 

 
 dhcp-timeout
 int32
 0 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).
+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.
 

 

 
 dhcp-vendor-class-identifier
 string
   The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.
 

 

 
@@ -1753,126 +1771,133 @@
 

 

 
+dns-dataarray of strings Array of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.

 dns-options
 array of string
   Array of DNS options as described in man 5 resolv.conf.
+Array of DNS options as described in man 5 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.
+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-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
 
- 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.
+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
 int32
 0 DNS servers priority.
+DNS servers priority.
 
- The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
+The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
 
- Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.
+Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.
 
- Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.
+Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.
 
- Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.
+Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.
 
- When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.
+When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.
 
- 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 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.
 

 

 
 dns-search
 array of string
   List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.
+List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.
 
- 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 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).
 

 

 
 gateway
 string
   The gateway associated with this configuration. This is only meaningful if "addresses" is also set.
+The gateway associated with this configuration. This is only meaningful if "addresses" is also set.
 
- 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.
+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".
 

 

 
 ignore-auto-dns
 boolean
 FALSE 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.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.
 

 

 
 ignore-auto-routes
 boolean
 FALSE 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.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.
 

 

 
 link-local
 int32
 0 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.
+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".
 

 

 
 may-fail
 boolean
 TRUE 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.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.
 

 

 
 method
 string
   IP configuration method.
+IP configuration method.
 
- NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.
+NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.
 
- In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.
+In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.
 
- For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.
+For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.
 
- For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.
 

 

 
 never-default
 boolean
 FALSE 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.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.
 

 

 
 required-timeout
 int32
 -1 The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.
+The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.
 
- This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.
+This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.
 
- 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.
+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).
 

 

 
@@ -1886,27 +1911,35 @@
 route-metric
 int64
 -1 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.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.
 

 

 
 route-table
 uint32
 0 Enable policy routing (source routing) and set the routing table used when adding routes.
+Enable policy routing (source routing) and set the routing table used when adding routes.
 
- This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.
+This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.
 
- 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.
+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.
 

 

 
 routes
 array of array of uint32
  Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.  Array of IPv4 route structures.  Each IPv4 route structure is composed of 4 32-bit values; the first being the destination IPv4 network or address (network byte order), the second the destination network or address prefix (1 - 32), the third being the next-hop (network byte order) if any, and the fourth being the route metric. If the metric is 0, NM will choose an appropriate default metric for the device. (There is no way to explicitly specify an actual metric of 0 with this property.)Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.
+Array of IPv4 route structures.  Each IPv4 route structure is composed of 4 32-bit values; the first being the destination IPv4 network or address (network byte order), the second the destination network or address prefix (1 - 32), the third being the next-hop (network byte order) if any, and the fourth being the route metric. If the metric is 0, NM will choose an appropriate default metric for the device. (There is no way to explicitly specify an actual metric of 0 with this property.)

+routing-rulesarray of 'a{sv}' Array of dictionaries for routing rules. Each routing rule supports the following options: action (y), dport-end (q), dport-start (q), family (i), from (s), from-len (y), fwmark (u), fwmask (u), iifname (s), invert (b), ipproto (s), oifname (s), priority (u), sport-end (q), sport-start (q), supress-prefixlength (i), table (u), to (s), tos (y), to-len (y), range-end (u), range-start (u).
 

 
 

@@ -1914,7 +1947,7 @@
 

 

 
ipv6 setting

-
 IPv6 Settings.

+
IPv6 Settings.

 
@@ -1934,17 +1967,17 @@
 addr-gen-mode
-
+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.
-
+
+
+
+
+
+
+
-
+The property is currently implemented only for IPv4.
-
+When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.
-
+
-
+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.
-
+
-
+This property is currently not implemented for DHCPv6.
-
+
-
+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.
-
+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.
-
+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).
-
+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".
-
+
-
+
-
+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.
-
+
-
+For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.
-
+
-
+
-
+Set to 2147483647 (MAXINT32) for infinity.
-
+A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).
-
+
-
+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.
-
+
+
+
+
+
+
+
-
+

 
 

 
int32
 3 Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. 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).
+Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. 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).
 
- If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced.
+If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced.
 
- The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced.
+The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced.
 
- The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively.
+The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively.
 
- For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions.
+For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions.
 
- 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.
 

 

 
@@ -1958,83 +1991,93 @@
 addresses
 array of legacy IPv6 address struct (a(ayuay))
  Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.  Array of IPv6 address structures.  Each IPv6 address structure is composed of an IPv6 address, a prefix length (0 - 128), and an IPv6 gateway address. The gateway may be zeroed out if no gateway exists for that subnet.Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.
+Array of IPv6 address structures.  Each IPv6 address structure is composed of an IPv6 address, a prefix length (0 - 128), and an IPv6 gateway address. The gateway may be zeroed out if no gateway exists for that subnet.

+auto-route-ext-gwNMTernary (int32) 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.
 

 

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

 

 
 dhcp-duid
 string
   A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option.
+A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option.
 
- The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id.
+The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id.
 
- The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk.
+The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk.
 
- The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt").
+The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt").
 
- When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.
 

 

 
 dhcp-hostname
 string
   If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.
 

 

 
 dhcp-hostname-flags
 uint32
 0 Flags for the DHCP hostname and FQDN.
+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 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.
 

 

 
 dhcp-iaid
 string
   A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.
 

 

 
 dhcp-reject-servers
 array of string
   Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.
+Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.
 
- 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").
+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.
 

 

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

 

 
 dhcp-timeout
 int32
 0 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).
+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.
 

 

 
@@ -2045,146 +2088,153 @@
 

 

 
+dns-dataarray of strings Array of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.

 dns-options
 array of string
   Array of DNS options as described in man 5 resolv.conf.
+Array of DNS options as described in man 5 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.
+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-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
 
- 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.
+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
 int32
 0 DNS servers priority.
+DNS servers priority.
 
- The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
+The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
 
- Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.
+Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.
 
- Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.
+Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.
 
- Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.
+Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.
 
- When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.
+When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.
 
- 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 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.
 

 

 
 dns-search
 array of string
   List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.
+List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.
 
- 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 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).
 

 

 
 gateway
 string
   The gateway associated with this configuration. This is only meaningful if "addresses" is also set.
+The gateway associated with this configuration. This is only meaningful if "addresses" is also set.
 
- 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.
+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".
 

 

 
 ignore-auto-dns
 boolean
 FALSE 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.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.
 

 

 
 ignore-auto-routes
 boolean
 FALSE 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.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.
 

 

 
 ip6-privacy
 NMSettingIP6ConfigPrivacy (int32)
   Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941.  If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64.  This enhances privacy, but could cause problems in some applications, on the other hand.  The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses).
+Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941.  If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64.  This enhances privacy, but could cause problems in some applications, on the other hand.  The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses).
 
- Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy".
+Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy".
 
- If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr".
+If 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.
 

 

 
 may-fail
 boolean
 TRUE 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.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.
 

 

 
 method
 string
   IP configuration method.
+IP configuration method.
 
- NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.
+NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.
 
- In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.
+In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.
 
- For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.
+For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.
 
- For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.
 

 

 
 mtu
 uint32
 0 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.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.
 

 

 
 never-default
 boolean
 FALSE 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.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.
 

 

 
 ra-timeout
 int32
 0 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.
+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.
 

 

 
 required-timeout
 int32
 -1 The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.
+The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.
 
- This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.
+This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.
 
- 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.
+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).
 

 

 
@@ -2198,34 +2248,42 @@
 route-metric
 int64
 -1 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.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.
 

 

 
 route-table
 uint32
 0 Enable policy routing (source routing) and set the routing table used when adding routes.
+Enable policy routing (source routing) and set the routing table used when adding routes.
 
- This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.
+This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.
 
- 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.
+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.
 

 

 
 routes
 array of legacy IPv6 route struct (a(ayuayu))
  Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.  Array of IPv6 route structures.  Each IPv6 route structure is composed of an IPv6 address, a prefix length (0 - 128), an IPv6 next hop address (which may be zeroed out if there is no next hop), and a metric. If the metric is 0, NM will choose an appropriate default metric for the device.Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.
+Array of IPv6 route structures.  Each IPv6 route structure is composed of an IPv6 address, a prefix length (0 - 128), an IPv6 next hop address (which may be zeroed out if there is no next hop), and a metric. If the metric is 0, NM will choose an appropriate default metric for the device.

+routing-rulesarray of 'a{sv}' Array of dictionaries for routing rules. Each routing rule supports the following options: action (y), dport-end (q), dport-start (q), family (i), from (s), from-len (y), fwmark (u), fwmask (u), iifname (s), invert (b), ipproto (s), oifname (s), priority (u), sport-end (q), sport-start (q), supress-prefixlength (i), table (u), to (s), tos (y), to-len (y), range-end (u), range-start (u).
 

 

 
 token
 string
   Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.
 

 
 

@@ -2233,7 +2291,7 @@
 

 

 
ip-tunnel setting

-
 IP Tunneling Settings.

+
IP Tunneling Settings.

 
@@ -2253,91 +2311,98 @@
 encapsulation-limit
-
+
-
+
-
+
+
+
+
+
+
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+

 
 

 
uint32
 0 How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.
 

 

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

 

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

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

 

 
 input-key
 string
   The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.
 

 

 
 local
 string
   The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.
 

 

 
 mode
 uint32
 0 The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).
 

 

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

 

 
 output-key
 string
   The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.
 

 

 
 parent
 string
   If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface.If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface.
 

 

 
 path-mtu-discovery
 boolean
 TRUE Whether to enable Path MTU Discovery on this tunnel.Whether to enable Path MTU Discovery on this tunnel.
 

 

 
 remote
 string
   The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.
 

 

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

 

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

 
 

@@ -2345,7 +2410,7 @@
 

 

 
macsec setting

-
 MACSec Settings.

+
MACSec Settings.

 
@@ -2365,63 +2430,63 @@
 encrypt
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+

 
 

 
boolean
 TRUE Whether the transmitted traffic must be encrypted.Whether the transmitted traffic must be encrypted.
 

 

 
 mka-cak
 string
   The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.
 

 

 
 mka-cak-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "mka-cak" property.Flags indicating how to handle the "mka-cak" property.
 

 

 
 mka-ckn
 string
   The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Must be a string of hexadecimal characters with a even length between 2 and 64.The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Must be a string of hexadecimal characters with a even length between 2 and 64.
 

 

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

 

 
 parent
 string
   If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.
 

 

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

 

 
 send-sci
 boolean
 TRUE Specifies whether the SCI (Secure Channel Identifier) is included in every packet.Specifies whether the SCI (Secure Channel Identifier) is included in every packet.
 

 

 
 validation
 int32
 2 Specifies the validation mode for incoming frames.Specifies the validation mode for incoming frames.
 

 
 

@@ -2429,7 +2494,7 @@
 

 

 
macvlan setting

-
 MAC VLAN Settings.

+
MAC VLAN Settings.

 
@@ -2449,28 +2514,28 @@
 mode
-
+
-
+
-
+
-
+

 
 

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

 

 
 parent
 string
   If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.
 

 

 
 promiscuous
 boolean
 TRUE Whether the interface should be put in promiscuous mode.Whether the interface should be put in promiscuous mode.
 

 

 
 tap
 boolean
 FALSE Whether the interface should be a MACVTAP.Whether the interface should be a MACVTAP.
 

 
 

@@ -2478,7 +2543,7 @@
 

 

 
match setting

-
 Match settings.

+
Match settings.

 
@@ -2498,42 +2563,42 @@
 driver
-
+See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the 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".
-
+See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the match.
-
+See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.

 
 

 
array of string
   A list of driver names to match. Each element is a shell wildcard pattern.
+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.
 

 

 
 interface-name
 array of string
   A list of interface names to match. Each element is a shell wildcard pattern.
+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".
 

 

 
 kernel-command-line
 array of string
   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.
+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.
 

 

 
 path
 array of string
   A list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier.
+A list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier.
 
- For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0".
+For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0".
 
- The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev").
+The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev").
 
- Each element of the list is a shell wildcard pattern.
+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.
 

 
 

@@ -2541,7 +2606,7 @@
 

 

 
802-11-olpc-mesh setting

-
 OLPC Wireless Mesh Settings.

+
OLPC Wireless Mesh Settings.

 
@@ -2561,23 +2626,23 @@
 channel
-
+
-
+This is currently only implemented by dhclient DHCP plugin.
-
+

 
 

 
uint32
 0 Channel on which the mesh network to join is located.Channel on which the mesh network to join is located.
 

 

 
 dhcp-anycast-address
 byte array
   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.
+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.
 

 

 
 ssid
 byte array
   SSID of the mesh network to join.SSID of the mesh network to join.
 

 
 

@@ -2585,7 +2650,7 @@
 

 

 
ovs-bridge setting

-
 OvsBridge Link Settings.

+
OvsBridge Link Settings.

 
@@ -2605,35 +2670,35 @@
 datapath-type
-
+
-
+
-
+
-
+
-
+

 
 

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

 

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

 

 
 mcast-snooping-enable
 boolean
 FALSE Enable or disable multicast snooping.Enable or disable multicast snooping.
 

 

 
 rstp-enable
 boolean
 FALSE Enable or disable RSTP.Enable or disable RSTP.
 

 

 
 stp-enable
 boolean
 FALSE Enable or disable STP.Enable or disable STP.
 

 
 

@@ -2641,7 +2706,7 @@
 

 

 
ovs-dpdk setting

-
 OvsDpdk Link Settings.

+
OvsDpdk Link Settings.

 
@@ -2661,14 +2726,28 @@
 devargs
-
+
-
+
+
+
+
+
+
+
+
+
+
+
+
+

 
 

 
string
   Open vSwitch DPDK device arguments.Open vSwitch DPDK device arguments.
 

 

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

+n-rxq-descuint320The 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.

+n-txq-descuint320The 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.
 

 
 

@@ -2676,7 +2755,7 @@
 

 

 
ovs-interface setting

-
 Open vSwitch Interface Settings.

+
Open vSwitch Interface Settings.

 
@@ -2690,19 +2769,28 @@
 
-
+
+
+
+
+
+
+
+
-
-
+
+
+

 
 

Default Value
 Value Description
 

+ofport-requestuint320Open 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.

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

 

 

 

 

 
ovs-patch setting

-
 OvsPatch Link Settings.

+
OvsPatch Link Settings.

 
@@ -2721,14 +2809,14 @@
 peer
-
+

 
 

 
string
   Specifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer.Specifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer.
 

 

 

 

 

 
ovs-port setting

-
 OvsPort Link Settings.

+
OvsPort Link Settings.

 
@@ -2748,42 +2836,51 @@
 bond-downdelay
-
+
-
+
-
+
-
+
-
+
+
+
+
+
+
+
-
+

 
 

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

 

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

 

 
 bond-updelay
 uint32
 0 The time port must be active before it starts forwarding traffic.The time port must be active before it starts forwarding traffic.
 

 

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

 

 
 tag
 uint32
 0 The VLAN tag in the range 0-4095.The VLAN tag in the range 0-4095.

+trunksarray of vardict 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.
 

 

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

 
 

@@ -2791,7 +2888,7 @@
 

 

 
ppp setting

-
 Point-to-Point Protocol Settings.

+
Point-to-Point Protocol Settings.

 
@@ -2811,126 +2908,126 @@
 baud
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+

 
 

 
uint32
 0 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.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.
 

 

 
 crtscts
 boolean
 FALSE 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.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.
 

 

 
 lcp-echo-failure
 uint32
 0 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.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.
 

 

 
 lcp-echo-interval
 uint32
 0 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.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.
 

 

 
 mppe-stateful
 boolean
 FALSE If TRUE, stateful MPPE is used.  See pppd documentation for more information on stateful MPPE.If TRUE, stateful MPPE is used.  See pppd documentation for more information on stateful MPPE.
 

 

 
 mru
 uint32
 0 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.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.
 

 

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

 

 
 no-vj-comp
 boolean
 FALSE If TRUE, Van Jacobsen TCP header compression will not be requested.If TRUE, Van Jacobsen TCP header compression will not be requested.
 

 

 
 noauth
 boolean
 TRUE 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.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.
 

 

 
 nobsdcomp
 boolean
 FALSE If TRUE, BSD compression will not be requested.If TRUE, BSD compression will not be requested.
 

 

 
 nodeflate
 boolean
 FALSE If TRUE, "deflate" compression will not be requested.If TRUE, "deflate" compression will not be requested.
 

 

 
 refuse-chap
 boolean
 FALSE If TRUE, the CHAP authentication method will not be used.If TRUE, the CHAP authentication method will not be used.
 

 

 
 refuse-eap
 boolean
 FALSE If TRUE, the EAP authentication method will not be used.If TRUE, the EAP authentication method will not be used.
 

 

 
 refuse-mschap
 boolean
 FALSE If TRUE, the MSCHAP authentication method will not be used.If TRUE, the MSCHAP authentication method will not be used.
 

 

 
 refuse-mschapv2
 boolean
 FALSE If TRUE, the MSCHAPv2 authentication method will not be used.If TRUE, the MSCHAPv2 authentication method will not be used.
 

 

 
 refuse-pap
 boolean
 FALSE If TRUE, the PAP authentication method will not be used.If TRUE, the PAP authentication method will not be used.
 

 

 
 require-mppe
 boolean
 FALSE 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.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.
 

 

 
 require-mppe-128
 boolean
 FALSE 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.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.
 

 
 

@@ -2938,7 +3035,7 @@
 

 

 
pppoe setting

-
 PPP-over-Ethernet Settings.

+
PPP-over-Ethernet Settings.

 
@@ -2958,35 +3055,35 @@
 parent
-
+
-
+
-
+
-
+
-
+

 
 

 
string
   If given, specifies the parent interface name on which this PPPoE connection should be created.  If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection.If given, specifies the parent interface name on which this PPPoE connection should be created.  If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection.
 

 

 
 password
 string
   Password used to authenticate with the PPPoE service.Password used to authenticate with the PPPoE service.
 

 

 
 password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property.
 

 

 
 service
 string
   If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service.  For most providers, this should be left blank.  It is only required if there are multiple access concentrators or a specific service is known to be required.If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service.  For most providers, this should be left blank.  It is only required if there are multiple access concentrators or a specific service is known to be required.
 

 

 
 username
 string
   Username used to authenticate with the PPPoE service.Username used to authenticate with the PPPoE service.
 

 
 

@@ -2994,7 +3091,7 @@
 

 

 
proxy setting

-
 WWW Proxy Settings.

+
WWW Proxy Settings.

 
@@ -3014,28 +3111,28 @@
 browser-only
-
+
-
+
-
+
-
+

 
 

 
boolean
 FALSE Whether the proxy configuration is for browser only.Whether the proxy configuration is for browser only.
 

 

 
 method
 int32
 0 Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)
 

 

 
 pac-script
 string
   PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.
 

 

 
 pac-url
 string
   PAC URL for obtaining PAC file.PAC URL for obtaining PAC file.
 

 
 

@@ -3043,7 +3140,7 @@
 

 

 
serial setting

-
 Serial Link Settings.

+
Serial Link Settings.

 
@@ -3063,14 +3160,14 @@
 baud
-
+
-
+
-
+
-
+

 
 

 
uint32
 57600 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.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.
 

 

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

 

 
@@ -3084,14 +3181,14 @@
 send-delay
 uint64
 0 Time to delay between each byte sent to the modem, in microseconds.Time to delay between each byte sent to the modem, in microseconds.
 

 

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

 
 

@@ -3099,7 +3196,7 @@
 

 

 
sriov setting

-
 SR-IOV settings.

+
SR-IOV settings.

 
@@ -3119,47 +3216,47 @@
 autoprobe-drivers
-
+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).
-
+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.
-
+PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.

 
 

 
NMTernary (int32)
   Whether to autoprobe virtual functions by a compatible driver.
+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_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.
+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).
 

 

 
 total-vfs
 uint32
 0 The total number of virtual functions to create.
+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.
 

 

 
 vfs
 array of vardict
   Array of virtual function descriptors.
+Array of virtual function descriptors.
 
- Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF.
+Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF.
 
- When represented as string a VF is in the form:
+When represented as string a VF is in the form:
 
- "INDEX [ATTR=VALUE[ ATTR=VALUE]...]".
+"INDEX [ATTR=VALUE[ ATTR=VALUE]...]".
 
- for example:
+for example:
 
- "2 mac=00:11:22:33:44:55 spoof-check=true".
+"2 mac=00:11:22:33:44:55 spoof-check=true".
 
- Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans.
+Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans.
 
- The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form
+The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form
 
- "ID[.PRIORITY[.PROTO]]".
+"ID[.PRIORITY[.PROTO]]".
 
- PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.
 

 
 

@@ -3167,7 +3264,7 @@
 

 

 
tc setting

-
 Linux Traffic Control Settings.

+
Linux Traffic Control Settings.

 
@@ -3187,22 +3284,22 @@
 qdiscs
-
+If the "tc" setting is not present, NetworkManager doesn't touch the qdiscs present on the interface.
-
+If the "tc" setting is not present, NetworkManager doesn't touch the filters present on the interface.

 
 

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

 

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

 
 

@@ -3210,7 +3307,7 @@
 

 

 
team setting

-
 Teaming Settings.

+
Teaming Settings.

 
@@ -3230,7 +3327,7 @@
 config
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+

 
 

 
string
   The JSON configuration for the team network interface.  The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used.  See man teamd.conf for the format details.The JSON configuration for the team network interface.  The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used.  See man teamd.conf for the format details.
 

 

 
@@ -3244,105 +3341,105 @@
 link-watchers
 array of vardict
   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.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.
 

 

 
 mcast-rejoin-count
 int32
 -1 Corresponds to the teamd mcast_rejoin.count.Corresponds to the teamd mcast_rejoin.count.
 

 

 
 mcast-rejoin-interval
 int32
 -1 Corresponds to the teamd mcast_rejoin.interval.Corresponds to the teamd mcast_rejoin.interval.
 

 

 
 notify-peers-count
 int32
 -1 Corresponds to the teamd notify_peers.count.Corresponds to the teamd notify_peers.count.
 

 

 
 notify-peers-interval
 int32
 -1 Corresponds to the teamd notify_peers.interval.Corresponds to the teamd notify_peers.interval.
 

 

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

 

 
 runner-active
 boolean
 TRUE Corresponds to the teamd runner.active.Corresponds to the teamd runner.active.
 

 

 
 runner-agg-select-policy
 string
   Corresponds to the teamd runner.agg_select_policy.Corresponds to the teamd runner.agg_select_policy.
 

 

 
 runner-fast-rate
 boolean
 FALSE Corresponds to the teamd runner.fast_rate.Corresponds to the teamd runner.fast_rate.
 

 

 
 runner-hwaddr-policy
 string
   Corresponds to the teamd runner.hwaddr_policy.Corresponds to the teamd runner.hwaddr_policy.
 

 

 
 runner-min-ports
 int32
 -1 Corresponds to the teamd runner.min_ports.Corresponds to the teamd runner.min_ports.
 

 

 
 runner-sys-prio
 int32
 -1 Corresponds to the teamd runner.sys_prio.Corresponds to the teamd runner.sys_prio.
 

 

 
 runner-tx-balancer
 string
   Corresponds to the teamd runner.tx_balancer.name.Corresponds to the teamd runner.tx_balancer.name.
 

 

 
 runner-tx-balancer-interval
 int32
 -1 Corresponds to the teamd runner.tx_balancer.interval.Corresponds to the teamd runner.tx_balancer.interval.
 

 

 
 runner-tx-hash
 array of string
   Corresponds to the teamd runner.tx_hash.Corresponds to the teamd runner.tx_hash.
 

 
 

@@ -3350,7 +3447,7 @@
 

 

 
team-port setting

-
 Team Port Settings.

+
Team Port Settings.

 
@@ -3370,49 +3467,49 @@
 config
-
+
-
+
-
+
-
+
-
+
-
+
-
+

 
 

 
string
   The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.
 

 

 
 lacp-key
 int32
 -1 Corresponds to the teamd ports.PORTIFNAME.lacp_key.Corresponds to the teamd ports.PORTIFNAME.lacp_key.
 

 

 
 lacp-prio
 int32
 -1 Corresponds to the teamd ports.PORTIFNAME.lacp_prio.Corresponds to the teamd ports.PORTIFNAME.lacp_prio.
 

 

 
 link-watchers
 array of vardict
   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.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.
 

 

 
 prio
 int32
 0 Corresponds to the teamd ports.PORTIFNAME.prio.Corresponds to the teamd ports.PORTIFNAME.prio.
 

 

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

 

 
 sticky
 boolean
 FALSE Corresponds to the teamd ports.PORTIFNAME.sticky.Corresponds to the teamd ports.PORTIFNAME.sticky.
 

 
 

@@ -3420,7 +3517,7 @@
 

 

 
tun setting

-
 Tunnel Settings.

+
Tunnel Settings.

 
@@ -3440,42 +3537,42 @@
 group
-
+
-
+
-
+
-
+
-
+
-
+

 
 

 
string
   The group ID which will own the device. If set to NULL everyone will be able to use the device.The group ID which will own the device. If set to NULL everyone will be able to use the device.
 

 

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

 

 
 multi-queue
 boolean
 FALSE 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.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.
 

 

 
 owner
 string
   The user ID which will own the device. If set to NULL everyone will be able to use the device.The user ID which will own the device. If set to NULL everyone will be able to use the device.
 

 

 
 pi
 boolean
 FALSE If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.
 

 

 
 vnet-hdr
 boolean
 FALSE If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.
 

 
 

@@ -3483,7 +3580,7 @@
 

 

 
user setting

-
 General User Profile Settings.

+
General User Profile Settings.

 
@@ -3502,14 +3599,14 @@
 data
-
+

 
 

 
dict of string to string
 {} A dictionary of key/value pairs with user data. This data is ignored by NetworkManager and can be used at the users discretion. The keys only support a strict ascii format, but the values can be arbitrary UTF8 strings up to a certain length.A dictionary of key/value pairs with user data. This data is ignored by NetworkManager and can be used at the users discretion. The keys only support a strict ascii format, but the values can be arbitrary UTF8 strings up to a certain length.
 

 

 

 

 

 
vlan setting

-
 VLAN Settings.

+
VLAN Settings.

 
@@ -3529,30 +3626,30 @@
 egress-priority-map
-
+
-
+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.
-
+
-
+
-
+
+
+
+
+
+
+

 
 

 
array of string
   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".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".
 

 

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

 

 
 id
 uint32
 0 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.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.
 

 

 
 ingress-priority-map
 array of string
   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".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".
 

 

 
@@ -3566,7 +3663,16 @@
 parent
 string
   If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.

+protocolstring Specifies the VLAN protocol to use for encapsulation.
+
+Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.
 

 
 

@@ -3574,7 +3680,7 @@
 

 

 
vpn setting

-
 VPN Settings.

+
VPN Settings.

 
@@ -3594,42 +3700,42 @@
 data
-
+
-
+
-
+
-
+
-
+
-
+

 
 

 
dict of string to string
 {} Dictionary of key/value pairs of VPN plugin specific data.  Both keys and values must be strings.Dictionary of key/value pairs of VPN plugin specific data.  Both keys and values must be strings.
 

 

 
 persistent
 boolean
 FALSE 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.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.
 

 

 
 secrets
 dict of string to string
 {} Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys.  Both keys and values must be strings.Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys.  Both keys and values must be strings.
 

 

 
 service-type
 string
   D-Bus service name of the VPN plugin that this setting uses to connect to its network.  i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.D-Bus service name of the VPN plugin that this setting uses to connect to its network.  i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.
 

 

 
 timeout
 uint32
 0 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.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.
 

 

 
 user-name
 string
   If the VPN connection requires a user name for authentication, that name should be provided here.  If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty.  If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.If the VPN connection requires a user name for authentication, that name should be provided here.  If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty.  If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.
 

 
 

@@ -3637,7 +3743,7 @@
 

 

 
vrf setting

-
 VRF settings.

+
VRF settings.

 
@@ -3656,14 +3762,14 @@
 table
-
+

 
 

 
uint32
 0 The routing table for this VRF.The routing table for this VRF.
 

 

 

 

 

 
vxlan setting

-
 VXLAN Settings.

+
VXLAN Settings.

 
@@ -3683,112 +3789,112 @@
 ageing
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+

 
 

 
uint32
 300 Specifies the lifetime in seconds of FDB entries learnt by the kernel.Specifies the lifetime in seconds of FDB entries learnt by the kernel.
 

 

 
 destination-port
 uint32
 8472 Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.
 

 

 
 id
 uint32
 0 Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.
 

 

 
 l2-miss
 boolean
 FALSE Specifies whether netlink LL ADDR miss notifications are generated.Specifies whether netlink LL ADDR miss notifications are generated.
 

 

 
 l3-miss
 boolean
 FALSE Specifies whether netlink IP ADDR miss notifications are generated.Specifies whether netlink IP ADDR miss notifications are generated.
 

 

 
 learning
 boolean
 TRUE Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.
 

 

 
 limit
 uint32
 0 Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.
 

 

 
 local
 string
   If given, specifies the source IP address to use in outgoing packets.If given, specifies the source IP address to use in outgoing packets.
 

 

 
 parent
 string
   If given, specifies the parent interface name or parent connection UUID.If given, specifies the parent interface name or parent connection UUID.
 

 

 
 proxy
 boolean
 FALSE Specifies whether ARP proxy is turned on.Specifies whether ARP proxy is turned on.
 

 

 
 remote
 string
   Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.
 

 

 
 rsc
 boolean
 FALSE Specifies whether route short circuit is turned on.Specifies whether route short circuit is turned on.
 

 

 
 source-port-max
 uint32
 0 Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.
 

 

 
 source-port-min
 uint32
 0 Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.
 

 

 
 tos
 uint32
 0 Specifies the TOS value to use in outgoing packets.Specifies the TOS value to use in outgoing packets.
 

 

 
 ttl
 uint32
 0 Specifies the time-to-live value to use in outgoing packets.Specifies the time-to-live value to use in outgoing packets.
 

 
 

@@ -3796,7 +3902,7 @@
 

 

 
wifi-p2p setting

-
 Wi-Fi P2P Settings.

+
Wi-Fi P2P Settings.

 
@@ -3816,25 +3922,25 @@
 peer
-
+
-
+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.
-
+There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.

 
 

 
string
   The P2P device that should be connected to. Currently, this is the only way to create or join a group.The P2P device that should be connected to. Currently, this is the only way to create or join a group.
 

 

 
 wfd-ies
 byte array
   The Wi-Fi Display (WFD) Information Elements (IEs) to set.
+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.
 

 

 
 wps-method
 uint32
 0 Flags indicating which mode of WPS is to be used.
+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.
 

 
 

@@ -3842,7 +3948,7 @@
 

 

 
wimax setting

-
 WiMax Settings.

+
WiMax Settings.

 
@@ -3862,14 +3968,18 @@
 mac-address
-
+
-
+

 
 

 
byte array
   If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing). Deprecated: 1If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing).
+
+This property is deprecated since version 1.2.WiMAX is no longer supported.
 

 

 
 network-name
 string
   Network Service Provider (NSP) name of the WiMAX network this connection should use. Deprecated: 1Network Service Provider (NSP) name of the WiMAX network this connection should use.
+
+This property is deprecated since version 1.2.WiMAX is no longer supported.
 

 
 

@@ -3877,7 +3987,7 @@
 

 

 
802-3-ethernet setting

-
 Wired Ethernet Settings.

+
Wired Ethernet Settings.

 
@@ -3897,7 +4007,7 @@
 accept-all-mac-addresses
-
+
-
+
-
+
-
+If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.
-
+
-
+
-
+
-
+
-
+
-
+Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.
-
+
-
+
-
+
-
+

 
 

 
NMTernary (int32)
   When TRUE, setup the interface to accept packets for all MAC addresses. This is enabling the kernel interface flag IFF_PROMISC. When FALSE, the interface will only accept the packets with the interface destination mac address or broadcast.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.
 

 

 
@@ -3911,7 +4021,7 @@
 auto-negotiate
 boolean
 FALSE 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.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.
 

 

 
@@ -3925,94 +4035,94 @@
 duplex
 string
   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.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.
 

 

 
 generate-mac-address-mask
 string
   With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.
+With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.
 
- If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.
+If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.
 
- If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.
+If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.
 
- If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.
+If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.
 
- If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.
 

 

 
 mac-address
 byte array
   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).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).
 

 

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

 

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

 

 
 port
 string
   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.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.
 

 

 
 s390-nettype
 string
   s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.
 

 

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

 

 
 s390-subchannels
 array of string
   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.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.
 

 

 
 speed
 uint32
 0 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.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.
 

 

 
 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 NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).
 

 

 
 wake-on-lan-password
 string
   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.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.
 

 
 

@@ -4020,7 +4130,7 @@
 

 

 
wireguard setting

-
 WireGuard Settings.

+
WireGuard Settings.

 
@@ -4040,52 +4150,52 @@
 fwmark
-
+Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.
-
+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.
-
+
-
+
-
+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.
-
+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.
-
+
-
+

 
 

 
uint32
 0 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.
+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.
 

 

 
 ip4-auto-default-route
 NMTernary (int32)
   Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing".
+Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing".
 
- Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route.
+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.
 

 

 
 ip6-auto-default-route
 NMTernary (int32)
   Like ip4-auto-default-route, but for the IPv6 default route.Like ip4-auto-default-route, but for the IPv6 default route.
 

 

 
 listen-port
 uint32
 0 The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.
 

 

 
 mtu
 uint32
 0 If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.
+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.
 

 

 
 peer-routes
 boolean
 TRUE Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively.
+Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively.
 
- Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.
 

 

 
@@ -4099,14 +4209,14 @@
 private-key
 string
   The 256 bit private-key in base64 encoding.The 256 bit private-key in base64 encoding.
 

 

 
 private-key-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "private-key" property.Flags indicating how to handle the "private-key" property.
 

 
 

@@ -4114,7 +4224,7 @@
 

 

 
802-11-wireless setting

-
 Wi-Fi Settings.

+
Wi-Fi Settings.

 
@@ -4134,13 +4244,13 @@
 ap-isolation
-
+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).
-
+
-
+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.
-
+
-
+If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.
-
+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.
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+

 
 

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

 

 
@@ -4154,23 +4264,23 @@
 band
 string
   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.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.
 

 

 
 bssid
 byte array
   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.
+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.
 

 

 
 channel
 uint32
 0 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.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.
 

 

 
@@ -4184,77 +4294,79 @@
 generate-mac-address-mask
 string
   With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.
+With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.
 
- If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.
+If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.
 
- If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.
+If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.
 
- If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.
+If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.
 
- If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.
 

 

 
 hidden
 boolean
 FALSE If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode.
+If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode.
 
- In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID.  However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution.
+In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID.  However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution.
 
- In AP mode, the created network does not broadcast its SSID.
+In AP mode, the created network does not broadcast its SSID.
 
- 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.
 

 

 
 mac-address
 byte array
   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).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).
 

 

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

 

 
 mac-address-randomization
 uint32
 0 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). This property is deprecated for 'cloned-mac-address'. Deprecated: 1One 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).
+
+This property is deprecated since version 1.4.Use the "cloned-mac-address" property instead.
 

 

 
 mode
 string
   Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.
 

 

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

 

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

 

 
 rate
 uint32
 0 If non-zero, directs the device to only use the specified bitrate for communication with the access point.  Units are in Kb/s, ie 5500 = 5.5 Mbit/s.  This property is highly driver dependent and not all devices support setting a static bitrate.If non-zero, directs the device to only use the specified bitrate for communication with the access point.  Units are in Kb/s, ie 5500 = 5.5 Mbit/s.  This property is highly driver dependent and not all devices support setting a static bitrate.
 

 

 
@@ -4268,28 +4380,28 @@
 seen-bssids
 array of string
   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.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.
 

 

 
 ssid
 byte array
   SSID of the Wi-Fi network. Must be specified.SSID of the Wi-Fi network. Must be specified.
 

 

 
 tx-power
 uint32
 0 If non-zero, directs the device to use the specified transmit power. Units are dBm.  This property is highly driver dependent and not all devices support setting a static transmit power.If non-zero, directs the device to use the specified transmit power. Units are dBm.  This property is highly driver dependent and not all devices support setting a static transmit power.
 

 

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

 
 

@@ -4297,7 +4409,7 @@
 

 

 
802-11-wireless-security setting

-
 Wi-Fi Security Settings.

+
Wi-Fi Security Settings.

 
@@ -4317,146 +4429,146 @@
 auth-alg
-
+
-
+
-
+
-
+This property must be set for any Wi-Fi connection that uses security.
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+WPS can be disabled by setting this property to a value of 1.

 
 

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

 

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

 

 
 group
 array of string
   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".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".
 

 

 
 key-mgmt
 string
   Key management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only).
+Key management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only).
 
- This property must be set for any Wi-Fi connection that uses security.
 

 

 
 leap-password
 string
   The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").
 

 

 
 leap-password-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "leap-password" property.Flags indicating how to handle the "leap-password" property.
 

 

 
 leap-username
 string
   The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").
 

 

 
 pairwise
 array of string
   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".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".
 

 

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

 

 
 proto
 array of string
   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.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.
 

 

 
 psk
 string
   Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.
 

 

 
 psk-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "psk" property.Flags indicating how to handle the "psk" property.
 

 

 
 wep-key-flags
 NMSettingSecretFlags (uint32)
   Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.
 

 

 
 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 NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.
 

 

 
 wep-key0
 string
   Index 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.Index 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.
 

 

 
 wep-key1
 string
   Index 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.Index 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.
 

 

 
 wep-key2
 string
   Index 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.Index 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.
 

 

 
 wep-key3
 string
   Index 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.Index 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.
 

 

 
 wep-tx-keyidx
 uint32
 0 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.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.
 

 

 
 wps-method
 uint32
 0 Flags indicating which mode of WPS is to be used if any.
+Flags indicating which mode of WPS is to be used if any.
 
- There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities.
+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.
 

 
 

@@ -4464,7 +4576,7 @@
 

 

 
wpan setting

-
 IEEE 802.15.4 (WPAN) MAC Settings.

+
IEEE 802.15.4 (WPAN) MAC Settings.

 
@@ -4484,35 +4596,35 @@
 channel
-
+
-
+
-
+
-
+
-
+

 
 

 
int32
 -1 IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".
 

 

 
 mac-address
 string
   If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.
 

 

 
 page
 int32
 -1 IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".
 

 

 
 pan-id
 uint32
 65535 IEEE 802.15.4 Personal Area Network (PAN) identifier.IEEE 802.15.4 Personal Area Network (PAN) identifier.
 

 

 
 short-address
 uint32
 65535 Short IEEE 802.15.4 address to be used within a restricted environment.Short IEEE 802.15.4 address to be used within a restricted environment.
 

 
 

@@ -4520,7 +4632,7 @@
 

 

 
bond-port setting

-
 Bond Port Settings.

+
Bond Port Settings.

 
@@ -4539,14 +4651,14 @@
 queue-id
-
+

 
 

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

 

 

 

 

 
hostname setting

-
 Hostname settings.

+
Hostname settings.

 
@@ -4566,48 +4678,74 @@
 from-dhcp
-
+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 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 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).
-
+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.

 
 

 
NMTernary (int32)
   Whether the system hostname can be determined from DHCP on this connection.
+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
 NMTernary (int32)
   Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.
+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 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.
+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).
 

 

 
 priority
 int32
 0 The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority.
+The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority.
 
- If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100.
+If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100.
 
- Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.
 

 
 

 

 

 

-
ovs-external-ids setting

-
 OVS External IDs Settings.

+
loopback setting

+
Loopback Link Settings.

+

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






Key NameValue TypeDefault ValueValue Description

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

+

+

+

+
ovs-external-ids setting

+
OVS External IDs Settings.

 
@@ -4626,14 +4764,40 @@
 data
-
+
+
+

 
 

 
dict of string to string
 {} A dictionary of key/value pairs with exernal-ids for OVS.A dictionary of key/value pairs with external-ids for OVS.

+

+

+

+
ovs-other-config setting

+
OVS Other Config Settings.

+

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






Key NameValue TypeDefault ValueValue Description

+datadict of string to string{}A dictionary of key/value pairs with other_config settings for OVS. See also "other_config" in the "ovs-vswitchd.conf.db" manual for the keys that OVS supports.
 

 

 

 

 

-
veth setting

-
 Veth Settings.

+
veth setting

+
Veth Settings.

 
@@ -4652,7 +4816,7 @@
 peer
-
+

 
 

 
string
   This property specifies the peer interface name of the veth. This property is mandatory.This property specifies the peer interface name of the veth. This property is mandatory.
 

 

 

diff --git a/docs/api/html/nm-settings-ifcfg-rh.html b/docs/api/html/nm-settings-ifcfg-rh.html
index 8189a493..d05f8335 100644
--- a/docs/api/html/nm-settings-ifcfg-rh.html
+++ b/docs/api/html/nm-settings-ifcfg-rh.html
@@ -274,8 +274,8 @@ DEVICETYPE=TeamPort
 

 

 

-
Table 12. 802-1x setting

-

+
Table 12. 802-11-wireless setting

+
@@ -290,370 +290,331 @@ DEVICETYPE=TeamPort
 
-
-
+
+
-
+Example: ESSID="Quick Net"
-
-
+
+
-
+Allowed values: Ad-Hoc, Managed (Auto)  [case insensitive]
-
-
+
-
+
-
-
+
+
-
+Example: CHANNEL=6
-
-
+
-
+Example: BSSID=00:1E:BD:64:83:21
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
+
+
-
+
-
-
+
+
+
+
+
+
+
-
-
+
+
-
-
+
-
+Allowed values: default, ignore, enable, disable
-
-
+
-
+Allowed values: default, never, always
-
-
+
+
-
+
+
+
+
+
+
+Allowed values: "yes", "no"
+
+

 
 
 

 
 
eapIEEE_8021X_EAP_METHODS(+)
-ssidESSID
  EAP method for 802.1X authentication.
-
-Example: IEEE_8021X_EAP_METHODS=PEAP
+SSID of Wi-Fi network.
 
-Allowed values: "LEAP", "PWD", "TLS", "PEAP", "TTLS", "FAST"
 

 
identityIEEE_8021X_IDENTITY(+)
-modeMODE
  Identity for EAP authentication methods.
+Wi-Fi network mode.
 
-Example: IEEE_8021X_IDENTITY=itsme
 

 
anonymous-identityIEEE_8021X_ANON_IDENTITY(+)
+bandBAND(+)
 
  Anonymous identity for EAP authentication methods.BAND alone is honored, but CHANNEL overrides BAND since it implies a band.
+
+Example: BAND=bg
+
+Allowed values: a, bg
 

 
pac-fileIEEE_8021X_PAC_FILE(+)
-channelCHANNEL
  File with PAC (Protected Access Credential) for EAP-FAST.
+Channel used for the Wi-Fi communication. Channels greater than 14 mean "a" band, otherwise the band is "bg".
 
-Example: IEEE_8021X_PAC_FILE=/home/joe/my-fast.pac
 

 
ca-certIEEE_8021X_CA_CERT(+)
+bssidBSSID(+)
 
  CA certificate for EAP.
+Restricts association only to a single AP.
 
-Example: IEEE_8021X_CA_CERT=/home/joe/cacert.crt
 

 
ca-pathIEEE_8021X_CA_PATH(+)
-rate(none)
  The search path for the certificate.This property is not handled by ifcfg-rh plugin.
 

 
subject-matchIEEE_8021X_SUBJECT_MATCH(+)
-tx-power(none)
  Substring to match subject of server certificate against.
-
-Example: IEEE_8021X_SUBJECT_MATCH="Red Hat"This property is not handled by ifcfg-rh plugin.
 

 
altsubject-matchesIEEE_8021X_ALTSUBJECT_MATCHES(+)
-mac-addressHWADDR
  List of strings to be matched against the altSubjectName.
-
-Example: IEEE_8021X_ALTSUBJECT_MATCHES="s1.domain.cc"Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.
 

 
domain-suffix-matchIEEE_8021X_DOMAIN_SUFFIX_MATCH(+)
-cloned-mac-addressMACADDR
  Suffix to match domain of server certificate against.Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).
 

 
domain-matchIEEE_8021X_DOMAIN_MATCH(+)
+generate-mac-address-maskGENERATE_MAC_ADDRESS_MASK(+)
 
  Value to match domain of server certificate against.the MAC address mask for generating randomized and stable cloned-mac-address.
 

 
client-certIEEE_8021X_CLIENT_CERT(+)
+mac-address-blacklistHWADDR_BLACKLIST(+)
 
  Client certificate for EAP.
-
-Example: IEEE_8021X_CLIENT_CERT=/home/joe/mycert.crtIt denies usage of the connection for any device whose address is listed.
 

 
phase1-peapverIEEE_8021X_PEAP_VERSION(+)
-seen-bssids(none)
  Use to force a specific PEAP version.
-
-Allowed values: 0, 1This property is not handled by ifcfg-rh plugin.
 

 
phase1-peaplabelIEEE_8021X_PEAP_FORCE_NEW_LABEL(+)
+mtuMTU MTU of the wireless interface.
hiddenSSID_HIDDEN(+)
 noUse to force the new PEAP label during key derivation.
-
-Allowed values: yes, no Whether the network hides the SSID.
 

 
phase1-fast-provisioningIEEE_8021X_FAST_PROVISIONING(+)
+powersavePOWERSAVE(+)
 
  Enable in-line provisioning of EAP-FAST credentials.
+Enables or disables Wi-Fi power saving.
 
-Example: IEEE_8021X_FAST_PROVISIONING="allow-auth allow-unauth"
+Example: POWERSAVE=enable
 
-Allowed values: space-separated list of these values [allow-auth, allow-unauth]
 

 
phase1-auth-flagsIEEE_8021X_PHASE1_AUTH_FLAGS(+)
+mac-address-randomizationMAC_ADDRESS_RANDOMIZATION(+)
 
  Authentication flags for the supplicant
+Enables or disables Wi-Fi MAC address randomization.
 
-Example: IEEE_8021X_PHASE1_AUTH_FLAGS="tls-1-0-disable tls-1-1-disable"
+Example: MAC_ADDRESS_RANDOMIZATION=always
 
-Allowed values: space-separated list of authentication flags names
 

 
phase2-authIEEE_8021X_INNER_AUTH_METHODS(+)
-security(none)
  Inner non-EAP authentication methods for TTLS or the inner EAP authentication method for PEAP. IEEE_8021X_INNER_AUTH_METHODS can contain values both for 'phase2-auth' and 'phase2-autheap' properties.
-
-Example: IEEE_8021X_INNER_AUTH_METHODS=PAP
+This property is deprecated and not handled by ifcfg-rh-plugin.
ap-isolationAP_ISOLATION(+)
+missing variable means global defaultWhether AP isolation is enabled
 
-Allowed values: "PAP", "CHAP", "MSCHAP", "MSCHAPV2", "GTC", "OTP", "MD5" and "TLS"
 

+

+

+
Table 13. 802-11-wireless-security setting

+

++++++
+
+
+
+
+
+
+
-
-
+
-
+
+
+
+
+
+
+Allowed values: 1, 2, 3, 4
-
-
+
-
+
-
-
+
-
-
+
+Allowed values: yes, no
-
-
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
+
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
+
+
-
+
-
-
+
-
-
-
-
-
-
-
-
-
-






PropertyIfcfg-rh VariableDefaultDescription

 
phase2-autheapIEEE_8021X_INNER_AUTH_METHODS(+)
+key-mgmtKEY_MGMT(+)
 
  Inner EAP-based authentication methods. Note that IEEE_8021X_INNER_AUTH_METHODS is also used for 'phase2-auth' values.
+Key management method.
 
-Example: IEEE_8021X_INNER_AUTH_METHODS="MSCHAPV2 EAP-TLS"
+Allowed values: none, ieee8021x, owe, wpa-psk, sae, wpa-eap, wpa-eap-suite-b-192
wep-tx-keyidxDEFAULTKEY1Index of active WEP key. Note that in ifcfg format the index starts counting at 1, while NetworkManager API otherwise is zero based.
 
-Allowed values: "EAP-MD5", "EAP-MSCHAPV2", "EAP-GTC", "EAP-OTP" and "EAP-TLS"
 

 
phase2-ca-pathIEEE_8021X_PHASE2_CA_PATH(+)
+auth-algSECURITYMODE(+)
 
  The search path for the certificate.Authentication algorithm for WEP.
+
+Allowed values: restricted, open, leap
 

 
phase2-subject-matchIEEE_8021X_PHASE2_SUBJECT_MATCH(+)
+protoWPA_ALLOW_WPA(+), WPA_ALLOW_WPA2(+)
  Substring to match subject of server certificate against.
+noAllowed WPA protocols, WPA and WPA2 (RSN).
 
-Example: IEEE_8021X_PHASE2_SUBJECT_MATCH="Red Hat"
 

 
phase2-altsubject-matchesIEEE_8021X_PHASE2_ALTSUBJECT_MATCHES(+)
+pairwiseCIPHER_PAIRWISE(+)
 
   Restrict pairwise encryption algorithms, specified as a space separated list.
+
+Allowed values: CCMP, TKIP
 

 
phase2-domain-suffix-matchIEEE_8021X_PHASE2_DOMAIN_SUFFIX_MATCH(+)
+groupCIPHER_GROUP(+)
 
  Suffix to match domain of server certificate for phase 2 against.Restrict group/broadcast encryption algorithms, specified as a space separated list.
+
+Allowed values: CCMP, TKIP, WEP40, WEP104
 

 
phase2-domain-matchIEEE_8021X_PHASE2_DOMAIN_MATCH(+)
+pmfPMF(+)
 
  Value to match domain of server certificate for phase 2 against.Enables or disables PMF (802.11w)
+
+Example: PMF=required
+
+Allowed values: default, disable, optional, required
 

 
phase2-client-certIEEE_8021X_INNER_CLIENT_CERT(+)
+leap-usernameIEEE_8021X_IDENTITY(+)
 
  Client certificate for inner EAP method.
-
-Example: IEEE_8021X_INNER_CLIENT_CERT=/home/joe/mycert.crtLogin name for LEAP.
 

 
passwordIEEE_8021X_PASSWORD(+)
+wep-key0KEY1, KEY_PASSPHRASE1(+)
 
  UTF-8 encoded password used for EAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent.The first WEP key (used in most networks). See also DEFAULTKEY for key index.
 

 
password-flagsIEEE_8021X_PASSWORD_FLAGS(+)
+wep-key1KEY2, KEY_PASSPHRASE2(+)
 
  Password flags for IEEE_8021X_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values)WEP key with index 1. See also DEFAULTKEY for key index.
 

 
password-rawIEEE_8021X_PASSWORD_RAW(+)
- password used for EAP, encoded as a hexadecimal string. It can also go to "key-" lookaside file.
-
-Example: IEEE_8021X_PASSWORD_RAW=041c8320083aa4bf
password-raw-flagsIEEE_8021X_PASSWORD_RAW_FLAGS(+)
- The secret flags for password-raw.
private-keyIEEE_8021X_PRIVATE_KEY(+)
+wep-key2KEY3, KEY_PASSPHRASE3(+)
 
  Private key for EAP-TLS.
-
-Example: IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12WEP key with index 2. See also DEFAULTKEY for key index.
 

 
private-key-passwordIEEE_8021X_PRIVATE_KEY_PASSWORD(+)
+wep-key3KEY4, KEY_PASSPHRASE4(+)
 
  Password for IEEE_8021X_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent.WEP key with index 3. See also DEFAULTKEY for key index.
 

 
private-key-password-flagsIEEE_8021X_PRIVATE_KEY_PASSWORD_FLAGS(+)
+wep-key-flagsWEP_KEY_FLAGS(+)
 
  Password flags for IEEE_8021X_PRIVATE_KEY_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values)Password flags for KEY<i>, KEY_PASSPHRASE<i> password. (see the section called “Secret flag types:” for _FLAGS values)
 

 
phase2-private-keyIEEE_8021X_INNER_PRIVATE_KEY(+)
-pskWPA_PSK
  Private key for inner authentication method for EAP-TLS.Pre-Shared-Key for WPA networks.
 

 
phase2-private-key-passwordIEEE_8021X_INNER_PRIVATE_KEY_PASSWORD(+)
+psk-flagsWPA_PSK_FLAGS(+)
 
  Password for IEEE_8021X_INNER_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent.Password flags for WPA_PSK_FLAGS. (see the section called “Secret flag types:” for _FLAGS values)
+
+Example: WPA_PSK_FLAGS=user
 

 
phase2-private-key-password-flagsIEEE_8021X_INNER_PRIVATE_KEY_PASSWORD_FLAGS(+)
+leap-passwordIEEE_8021X_PASSWORD(+)
 
  Password flags for IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values)Password for LEAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent.
 

 
pinIEEE_8021X_PIN(+)
+leap-password-flagsIEEE_8021X_PASSWORD_FLAGS(+)
 
  The pin secret used for EAP authentication methods.Password flags for IEEE_8021X_PASSWORD_FLAGS. (see the section called “Secret flag types:” for _FLAGS values)
 

 
pin-flagsIEEE_8021X_PIN_FLAGS(+)
+wep-key-typeKEY<i> or KEY_PASSPHRASE<i>(+); KEY_TYPE(+)
 
  The secret flags for the pin property.KEY is used for "key" type (10 or 26 hexadecimal characters, or 5 or 13 character string prefixed with "s:"). KEY_PASSPHRASE is used for WEP passphrases. KEY_TYPE specifies the key type and can be either 'key' or 'passphrase'. KEY_TYPE is redundant and can be omitted.
+
+Example: KEY1=s:ahoj, KEY1=0a1c45bc02, KEY_PASSPHRASE1=mysupersecretkey
 

 
system-ca-certsIEEE_8021X_SYSTEM_CA_CERTS(+)
-wps-methodWPS_METHOD
  a boolean value.Used to control the WPS methods to be used Valid values are "default", "auto", "disabled", "pin" and "pbc". If omitted, whatver the AP announces is used.
+
+Example: WPS_METHOD=disabled, WPS_METHOD="pin pbc"
 

 
auth-timeoutIEEE_8021X_AUTH_TIMEOUT(+)
+filsFILS(+)
 0Timeout in seconds for the 802.1X authentication. Zero means the global default or 25.
optionalIEEE_8021X_OPTIONAL(+) default=no
  whether the 802.1X authentication is optional

-

-

-
Table 13. bond-port setting

-

------
-
-
-
-
-
-
-
-
-
-
-
-
-






PropertyIfcfg-rh VariableDefaultDescription
queue-idBONDING_OPTS: queue-id=0Queue ID.
+Enables or disables FILS (802.11ai)
 
-Allowed values: 0 - 65535

-

-

-
Table 14. bond setting

-

------
-
-
-
-
-
-
-
-
-
-
-
-
+Allowed values: default, disable, optional, required
+
+






PropertyIfcfg-rh VariableDefaultDescription
optionsBONDING_OPTS Bonding options.
+Example: FILS=required
 
-Example: BONDING_OPTS="miimon=100 mode=broadcast"

 

 

 

-
Table 15. bridge-port setting

-

+
Table 14. 802-1x setting

+
@@ -668,527 +629,441 @@ Example: BONDING_OPTS="miimon=100 mode=broadcast"
-
-
-
-
+
+
+
+Example: IEEE_8021X_EAP_METHODS=PEAP
+
+Allowed values: "LEAP", "PWD", "TLS", "PEAP", "TTLS", "FAST"
-
-
-
-
+
+
+
+Example: IEEE_8021X_IDENTITY=itsme
-
-
-
-
+
+
+
+
-
-
+
+
-
+Example: IEEE_8021X_PAC_FILE=/home/joe/my-fast.pac
-
-

 
 
 

 
 
 
priorityBRIDGING_OPTS: priority=32STP priority.
+eapIEEE_8021X_EAP_METHODS(+)
+ EAP method for 802.1X authentication.
 
-Allowed values: 0 - 63
 

 
path-costBRIDGING_OPTS: path_cost=100STP cost.
+identityIEEE_8021X_IDENTITY(+)
+ Identity for EAP authentication methods.
 
-Allowed values: 1 - 65535
 

 
hairpin-modeBRIDGING_OPTS: hairpin_mode=yesHairpin mode of the bridge port.anonymous-identityIEEE_8021X_ANON_IDENTITY(+)
+ Anonymous identity for EAP authentication methods.
 

 
vlansBRIDGE_PORT_VLANSpac-fileIEEE_8021X_PAC_FILE(+)
+
  List of VLANs on the bridge port
+File with PAC (Protected Access Credential) for EAP-FAST.
 
-Example: BRIDGE_PORT_VLANS="1 pvid untagged,20,300-400 untagged"
 

-

-

-
Table 16. bridge setting

-

------
-
-
-
-
-
-
-
-
-
+
-
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+Example: IEEE_8021X_SUBJECT_MATCH="Red Hat"
-
-
-
-
+
+
+
+Example: IEEE_8021X_ALTSUBJECT_MATCHES="s1.domain.cc"
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+Example: IEEE_8021X_CLIENT_CERT=/home/joe/mycert.crt
-
-
-
-
+
+
+
+Allowed values: 0, 1
-
-
-
-
+
+
+
+Allowed values: yes, no
-
-
-
-
+
+
+
+Example: IEEE_8021X_FAST_PROVISIONING="allow-auth allow-unauth"
+
+Allowed values: space-separated list of these values [allow-auth, allow-unauth]
-
-
+
+
-
+Example: IEEE_8021X_PHASE1_AUTH_FLAGS="tls-1-0-disable tls-1-1-disable"
+
+Allowed values: space-separated list of authentication flags names
-
-
+
+
-
+Example: IEEE_8021X_INNER_AUTH_METHODS=PAP
+
+Allowed values: "PAP", "CHAP", "MSCHAP", "MSCHAPV2", "GTC", "OTP", "MD5" and "TLS"
-
-
+
+
-
+Example: IEEE_8021X_INNER_AUTH_METHODS="MSCHAPV2 EAP-TLS"
+
+Allowed values: "EAP-MD5", "EAP-MSCHAPV2", "EAP-GTC", "EAP-OTP" and "EAP-TLS"
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+Example: IEEE_8021X_PHASE2_SUBJECT_MATCH="Red Hat"
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+Example: IEEE_8021X_INNER_CLIENT_CERT=/home/joe/mycert.crt
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+Example: IEEE_8021X_PASSWORD_RAW=041c8320083aa4bf
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+Example: IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-






PropertyIfcfg-rh VariableDefaultDescription

 
mac-addressBRIDGE_MACADDR(+)
+ca-certIEEE_8021X_CA_CERT(+)
 
  MAC address of the bridge. Note that this requires a recent kernel support, originally introduced in 3.15 upstream kernel) BRIDGE_MACADDR for bridges is an NM extension.CA certificate for EAP.
+
+Example: IEEE_8021X_CA_CERT=/home/joe/cacert.crt
 

 
stpSTPnoSpan tree protocol participation.ca-pathIEEE_8021X_CA_PATH(+)
+ The search path for the certificate.
 

 
priorityBRIDGING_OPTS: priority=32768STP priority.
+subject-matchIEEE_8021X_SUBJECT_MATCH(+)
+ Substring to match subject of server certificate against.
 
-Allowed values: 0 - 32768
 

 
forward-delayDELAY15STP forwarding delay.
+altsubject-matchesIEEE_8021X_ALTSUBJECT_MATCHES(+)
+ List of strings to be matched against the altSubjectName.
 
-Allowed values: 2 - 30
 

 
hello-timeBRIDGING_OPTS: hello_time=2STP hello time.
-
-Allowed values: 1 - 10domain-suffix-matchIEEE_8021X_DOMAIN_SUFFIX_MATCH(+)
+ Suffix to match domain of server certificate against.
 

 
max-ageBRIDGING_OPTS: max_age=20STP maximum message age.
-
-Allowed values: 6 - 40domain-matchIEEE_8021X_DOMAIN_MATCH(+)
+ Value to match domain of server certificate against.
 

 
ageing-timeBRIDGING_OPTS: ageing_time=300Ethernet MAC ageing time.
+client-certIEEE_8021X_CLIENT_CERT(+)
+ Client certificate for EAP.
 
-Allowed values: 0 - 1000000
 

 
multicast-snoopingBRIDGING_OPTS: multicast_snooping=1IGMP snooping support.
+phase1-peapverIEEE_8021X_PEAP_VERSION(+)
+ Use to force a specific PEAP version.
 
-Allowed values: 0 or 1
 

 
vlan-filteringBRIDGING_OPTS: vlan_filtering=0VLAN filtering support.
+phase1-peaplabelIEEE_8021X_PEAP_FORCE_NEW_LABEL(+)
+noUse to force the new PEAP label during key derivation.
 
-Allowed values: 0 or 1
 

 
vlan-default-pvidBRIDGING_OPTS: default_pvid=1default VLAN PVID.
+phase1-fast-provisioningIEEE_8021X_FAST_PROVISIONING(+)
+ Enable in-line provisioning of EAP-FAST credentials.
 
-Allowed values: 0 - 4094
 

 
vlansBRIDGE_VLANSphase1-auth-flagsIEEE_8021X_PHASE1_AUTH_FLAGS(+)
+
  List of VLANs on the bridge
+Authentication flags for the supplicant
 
-Example: BRIDGE_VLANS="1 pvid untagged,20,300-400 untagged"
 

 
group-addressBRIDGING_OPTS: group_address=phase2-authIEEE_8021X_INNER_AUTH_METHODS(+)
+
  STP group address.
+Inner non-EAP authentication methods for TTLS or the inner EAP authentication method for PEAP. IEEE_8021X_INNER_AUTH_METHODS can contain values both for 'phase2-auth' and 'phase2-autheap' properties.
 
-Example: BRIDGING_OPTS="group_address=01:80:C2:00:00:0A"
 

 
vlan-protocolBRIDGING_OPTS: vlan_protocol=phase2-autheapIEEE_8021X_INNER_AUTH_METHODS(+)
+
  VLAN filtering protocol.
+Inner EAP-based authentication methods. Note that IEEE_8021X_INNER_AUTH_METHODS is also used for 'phase2-auth' values.
 
-Example: BRIDGING_OPTS="vlan_protocol=802.1Q"
 

 
vlan-stats-enabledBRIDGING_OPTS: vlan_stats_enabled=0
-
-
-Example: BRIDGING_OPTS="vlan_stats_enabled=1"phase2-ca-pathIEEE_8021X_PHASE2_CA_PATH(+)
+ The search path for the certificate.
 

 
multicast-routerBRIDGING_OPTS: multicast_router=auto
-
-
-Example: BRIDGING_OPTS="multicast_router=enabled"
+phase2-subject-matchIEEE_8021X_PHASE2_SUBJECT_MATCH(+)
+ Substring to match subject of server certificate against.
 
-Allowed values: auto, enabled, disabled
 

 
multicast-query-use-ifaddrBRIDGING_OPTS: multicast_query_use_ifaddr=0
-
-
-Example: BRIDGING_OPTS="multicast_query-use_ifaddr=1"phase2-altsubject-matchesIEEE_8021X_PHASE2_ALTSUBJECT_MATCHES(+)
+  
 

 
multicast-querierBRIDGING_OPTS: multicast_querier=0
-
-
-Example: BRIDGING_OPTS="multicast_querier=1"phase2-domain-suffix-matchIEEE_8021X_PHASE2_DOMAIN_SUFFIX_MATCH(+)
+ Suffix to match domain of server certificate for phase 2 against.
 

 
multicast-hash-maxBRIDGING_OPTS: multicast_hash_max=4096
-
-
-Example: BRIDGING_OPTS="multicast_hash_max=8192"phase2-domain-matchIEEE_8021X_PHASE2_DOMAIN_MATCH(+)
+ Value to match domain of server certificate for phase 2 against.
 

 
multicast-last-member-countBRIDGING_OPTS: multicast_last_member_count=2
-
+phase2-client-certIEEE_8021X_INNER_CLIENT_CERT(+)
+ Client certificate for inner EAP method.
 
-Example: BRIDGING_OPTS="multicast_last_member_count=4"
 

 
multicast-last-member-intervalBRIDGING_OPTS: multicast_last_member_interval=100
-
-
-Example: BRIDGING_OPTS="multicast_last_member_interval=200"passwordIEEE_8021X_PASSWORD(+)
+ UTF-8 encoded password used for EAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent.
 

 
multicast-membership-intervalBRIDGING_OPTS: multicast_membership_interval=26000
-
-
-Example: BRIDGING_OPTS="multicast_membership_interval=16000"password-flagsIEEE_8021X_PASSWORD_FLAGS(+)
+ Password flags for IEEE_8021X_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values)
 

 
multicast-querier-intervalBRIDGING_OPTS: multicast_querier_interval=25500
-
+password-rawIEEE_8021X_PASSWORD_RAW(+)
+ password used for EAP, encoded as a hexadecimal string. It can also go to "key-" lookaside file.
 
-Example: BRIDGING_OPTS="multicast_querier_interval=20000"
 

 
multicast-query-intervalBRIDGING_OPTS: multicast_query_interval=12500
-
-
-Example: BRIDGING_OPTS="multicast_query_interval=22500"password-raw-flagsIEEE_8021X_PASSWORD_RAW_FLAGS(+)
+ The secret flags for password-raw.
 

 
multicast-query-response-intervalBRIDGING_OPTS: multicast_query_response_interval=1000
-
+private-keyIEEE_8021X_PRIVATE_KEY(+)
+ Private key for EAP-TLS.
 
-Example: BRIDGING_OPTS="multicast_query_response_interval=2000"
 

 
multicast-startup-query-countBRIDGING_OPTS: multicast_startup_query_count=2
-
-
-Example: BRIDGING_OPTS="multicast_startup_query_count=4"private-key-passwordIEEE_8021X_PRIVATE_KEY_PASSWORD(+)
+ Password for IEEE_8021X_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent.
 

 
multicast-startup-query-intervalBRIDGING_OPTS: multicast_startup_query_interval=3125
-
-
-Example: BRIDGING_OPTS="multicast_startup_query_interval=4000"private-key-password-flagsIEEE_8021X_PRIVATE_KEY_PASSWORD_FLAGS(+)
+ Password flags for IEEE_8021X_PRIVATE_KEY_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values)
 

-

-

-
Table 17. connection setting

-

------
-
-
-
-
-
-
-
-
-
+
-
+
-
-
+
-
+
-
-
+
-
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
-
-
-
-
-
-
-
+
-
-
+
-
+
-
-
+
+
-
+
+
+






PropertyIfcfg-rh VariableDefaultDescription

 
idNAME(+)
+phase2-private-keyIEEE_8021X_INNER_PRIVATE_KEY(+)
 
  User friendly name for the connection profile.Private key for inner authentication method for EAP-TLS.
 

 
uuidUUID(+)
+phase2-private-key-passwordIEEE_8021X_INNER_PRIVATE_KEY_PASSWORD(+)
 
  UUID for the connection profile. When missing, NetworkManager creates the UUID itself (by hashing the filename).Password for IEEE_8021X_INNER_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent.
 

 
stable-idSTABLE_ID(+)
+phase2-private-key-password-flagsIEEE_8021X_INNER_PRIVATE_KEY_PASSWORD_FLAGS(+)
 
  Token to generate stable IDs.Password flags for IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values)
 

 
interface-nameDEVICEpinIEEE_8021X_PIN(+)
+
  Interface name of the device this profile is bound to. The variable can be left out when the profile should apply for more devices. Note that DEVICE can be required for some connection types.The pin secret used for EAP authentication methods.
 

 
typeTYPE (DEVICETYPE, DEVICE)pin-flagsIEEE_8021X_PIN_FLAGS(+)
+
  Base type of the connection. DEVICETYPE is used for teaming connections.
-
-Example: TYPE=Ethernet; TYPE=Bond; TYPE=Bridge; DEVICETYPE=TeamPort
-
-Allowed values: Ethernet, Wireless, InfiniBand, Bridge, Bond, Vlan, Team, TeamPortThe secret flags for the pin property.
 

 
permissionsUSERS(+)
+system-ca-certsIEEE_8021X_SYSTEM_CA_CERTS(+)
 
  Restrict to certain users the access to this connection, and allow the connection to be active only when at least one of the specified users is logged into an active session.
-
-Example: USERS="joe bob"
autoconnectONBOOTyesWhether the connection should be autoconnected (not only while booting).a boolean value.
 

 
autoconnect-priorityAUTOCONNECT_PRIORITY(+)
+auth-timeoutIEEE_8021X_AUTH_TIMEOUT(+)
 
 0Connection priority for automatic activation. Connections with higher numbers are preferred when selecting profiles for automatic activation.
-
-Example: AUTOCONNECT_PRIORITY=20
-
-Allowed values: -999 to 999Timeout in seconds for the 802.1X authentication. Zero means the global default or 25.
 

 
autoconnect-retriesAUTOCONNECT_RETRIES(+)
-optionalIEEE_8021X_OPTIONAL(+) default=no
  The number of times a connection should be autoactivated before giving up and switching to the next one.
-
-Example: AUTOCONNECT_RETRIES=1
-
-Allowed values: -1 (use global default), 0 (forever) or a positive valuewhether the 802.1X authentication is optional
 

+

+

+
Table 15. 802-3-ethernet setting

+

++++++
+
+
+
+
+
+
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
-
-
-
-
-
-
+
-
-
+
+
-
+
-
-
-
-
+
+
+
+
-
-
+
-
+
-
-
+
-
-
+
+Example: HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55"
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+Example: SUBCHANNELS=0.0.b00a,0.0.b00b,0.0.b00c
-
-
-
-
+
+
+
+Allowed values: "qeth", "lcs" or "ctc"
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
+
+
-
+Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"
-
-
+
+
-
-
-
-
-
-
-
+






PropertyIfcfg-rh VariableDefaultDescription

 
multi-connectMULTI_CONNECT(+)
-port(none)
  whether the profile can be active on multiple devices at a given moment. The values are numbers corresponding to #NMConnectionMultiConnect enum.
-
-Example: MULTI_CONNECT=3The property is not saved by the plugin.
 

 
zoneZONE(+)
-speedETHTOOL_OPTS
  Trust level of this connection. The string is usually used for a firewall.
-
-Example: ZONE=WorkFixed speed for the ethernet link. It is added as "speed" parameter in the ETHTOOL_OPTS variable.
 

 
masterMASTER, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, BRIDGE, BRIDGE_UUIDduplexETHTOOL_OPTS
  Reference to master connection. The variable used depends on the connection type and the value. In general, if the *_UUID variant is present, the variant without *_UUID is ignored. NetworkManager attempts to write both for compatibility with legacy tooling.Fixed duplex mode for the ethernet link. It is added as "duplex" parameter in the ETHOOL_OPTS variable.
 

 
slave-typeMASTER, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, DEVICETYPE, BRIDGE, BRIDGE_UUIDauto-negotiateETHTOOL_OPTS
  Slave type doesn't map directly to a variable, but it is recognized using different variables.  MASTER and MASTER_UUID for bonding, TEAM_MASTER, TEAM_MASTER_UUID and DEVICETYPE for teaming, BRIDGE and BRIDGE_UUID for bridging.
autoconnect-slavesAUTOCONNECT_SLAVES(+)
-missing variable means global defaultWhether slaves of this connection should be auto-connected when this connection is activated.Whether link speed and duplex autonegotiation is enabled. It is not saved only if disabled and no values are provided for the "speed" and "duplex" parameters (skips link configuration).
 

 
secondariesSECONDARY_UUIDS(+)
-mac-addressHWADDR
  UUID of VPN connections that should be activated together with this connection.Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.
 

 
gateway-ping-timeoutGATEWAY_PING_TIMEOUT(+)
-0If greater than zero, the IP connectivity will be checked by pinging the gateway and waiting for the specified timeout (in seconds).
-
-Example: GATEWAY_PING_TIMEOUT=5cloned-mac-addressMACADDR Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).
 

 
meteredCONNECTION_METERED(+)
+generate-mac-address-maskGENERATE_MAC_ADDRESS_MASK(+)
 
  Whether the device is metered
-
-Example: CONNECTION_METERED=yes
-
-Allowed values: yes,no,unknownthe MAC address mask for generating randomized and stable cloned-mac-address.
 

 
lldpLLDP(+)
+mac-address-blacklistHWADDR_BLACKLIST(+)
 missing variable means global defaultwhether LLDP is enabled for the connection
-
-Example: LLDP=no
+ It denies usage of the connection for any device whose address is listed.
 
-Allowed values: boolean value or 'rx'
 

 
auth-retriesAUTH_RETRIES(+)
-0Number of retries for authentication.mtuMTU MTU of the interface.
 

 
mdnsMDNS(+)
-missing variable means global defaultWhether or not mDNS is enabled for the connection
-
-Example: MDNS=yes
+s390-subchannelsSUBCHANNELS Subchannels for IBM S390 hosts.
 
-Allowed values: yes,no,resolve
 

 
llmnrLLMNR(+)
-missing variable means global defaultWhether or not LLMNR is enabled for the connection
+s390-nettypeNETTYPE Network type of the S390 host.
 
-Example: LLMNR=yes
+Example: NETTYPE=qeth
 
-Allowed values: yes,no,resolve
 

 
dns-over-tlsDNS_OVER_TLS(+)
-missing variable means global defaultWhether or not DNSOverTls is enabled for the connection
-
-Allowed values: yes,no,opportunistics390-optionsOPTIONS and PORTNAME, CTCPROTO, S390 device options. All options go to OPTIONS, except for "portname" and "ctcprot" that have their own variables.
 

 
mptcp-flagsMPTCP_FLAGS(+)
-missing variable means global defaultThe MPTCP flags that indicate whether MPTCP is enabled and which flags to use for the address endpoints.
-
-Example: MPTCP_FLAGS="signal,subflow"wake-on-lanETHTOOL_OPTS, ETHTOOL_WAKE_ON_LAN Wake on Lan mode for ethernet. The setting "ignore" is expressed with "ETHTOOL_WAKE_ON_LAN=ignore". Otherwise, the "ETHTOOL_OPTS" variable is set with the value "wol" and several of the characters "p|u|m|b|a|g|s|f|d" as explained in the ethtool manual page.
 

 
wait-device-timeoutDEVTIMEOUT(+)
-wake-on-lan-passwordETHTOOL_OPTS
  for initscripts compatibility, this variable must be a whole integer. If necessary, NetworkManager stores also a fractional component for the milliseconds.
-
-Example: DEVTIMEOUT=5
+Password for secure-on based Wake-on-Lan. It is added as "sopass" parameter in the ETHTOOL_OPTS variable.
 
-Allowed values: timeout in seconds.
 

 
mud-urlMUD_URLaccept-all-mac-addressesACCEPT_ALL_MAC_ADDRESSES
  MUD_URL to be sent by device (See RFC 8520).
-
-Example: https://yourdevice.example.com/model.json
-
-Allowed values: a valid URL that points to recommended policy for this device
wait-activation-delayWAIT_ACTIVATION_DELAY(+)
- Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.
-
-Example: WAIT_ACTIVATION_DELAY=5000
-
-Allowed values: delay in milliseconds.Enforce the interface to accept all the packets.
 

 
 

 

 

-
Table 18. dcb setting

-

+
Table 16. bond setting

+
@@ -1201,129 +1076,19 @@ Allowed values: delay in milliseconds.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
-
-
-
+Example: BONDING_OPTS="miimon=100 mode=broadcast"
+

 
 
 

 
Default
 Description
 
app-fcoe-flagsDCB_APP_FCOE_ENABLE, DCB_APP_FCOE_ADVERTISE, DCB_APP_FCOE_WILLINGnoFCOE flags.
-
-Example: DCB_APP_FCOE_ENABLE=yes DCB_APP_FCOE_ADVERTISE=yes
app-fcoe-priorityDCB_APP_FCOE_PRIORITY Priority of FCoE frames.
-
-Allowed values: 0 - 7
app-fcoe-modeDCB_APP_FCOE_MODEfabricFCoE controller mode.
-
-Allowed values: fabric, vn2vn
app-iscsi-flagsDCB_APP_ISCSI_ENABLE, DCB_APP_ISCSI_ADVERTISE, DCB_APP_ISCSI_WILLINGnoiSCSI flags.
app-iscsi-priorityDCB_APP_ISCSI_PRIORITY Priority of iSCSI frames.
-
-Allowed values: 0 - 7
app-fip-flagsDCB_APP_FIP_ENABLE, DCB_APP_FIP_ADVERTISE, DCB_APP_FIP_WILLINGnoFIP flags.
app-fip-priorityDCB_APP_FIP_PRIORITY Priority of FIP frames.
-
-Allowed values: 0 - 7
priority-flow-control-flagsDCB_PFC_ENABLE, DCB_PFC_ADVERTISE, DCB_PFC_WILLINGnoPriority flow control flags.
priority-flow-controlDCB_PFC_UP Priority flow control values. String of 8 "0" and "1", where "0". means "do not transmit priority pause", "1" means "transmit pause".
-
-Example: DCB_PFC_UP=01101110
priority-group-flagsDCB_PG_ENABLE, DCB_PG_ADVERTISE, DCB_PG_WILLINGnoPriority groups flags.
priority-group-idDCB_PG_ID Priority groups values. String of eight priorities (0 - 7) or "f" (unrestricted).
-
-Example: DCB_PG_ID=1205f173
priority-group-bandwidthDCB_PG_PCT Priority groups values. Eight bandwidths (in percent), separated with commas.
-
-Example: DCB_PG_PCT=10,5,10,15,10,10,10,30
priority-bandwidthDCB_PG_UPPCT Priority values. Eight bandwidths (in percent), separated with commas. The sum of the numbers must be 100.
-
-Example: DCB_PG_UPPCT=7,13,10,10,15,15,10,20
priority-strict-bandwidthDCB_PG_STRICT Priority values. String of eight "0" or "1", where "0" means "may not utilize all bandwidth", "1" means "may utilize all bandwidth".
-
-Example: DCB_PG_STRICT=01101110
priority-traffic-classDCB_PG_UP2TC
optionsBONDING_OPTS
  Priority values. String of eight traffic class values (0 - 7).
+Bonding options.
 
-Example: DCB_PG_UP2TC=01623701

 

 

-

-          All DCB related configuration is a NetworkManager extension. DCB=yes must be
-          used explicitly to enable DCB so that the rest of the DCB_* variables can apply.
-        

-

-
Table 19. ethtool setting

-

+

+
Table 17. bond-port setting

+
@@ -1336,12 +1101,19 @@ Example: DCB_PG_UP2TC=01623701
-
+
+
+
+
+
+

 
 
 

 
Default
 Description
 
queue-idBONDING_OPTS: queue-id=0Queue ID.
+
+Allowed values: 0 - 65535

 

 

 

-
Table 20. hostname setting

-

+
Table 18. bridge setting

+
@@ -1356,288 +1128,231 @@ Example: DCB_PG_UP2TC=01623701
-
-
+
-
-
+
+
-
-
-
-
+
+
+
+
+
+
+
+
+
+Allowed values: 0 - 32768
-
-
-
-
+
+
+
+Allowed values: 2 - 30
-
-
-
-
+
+
+
+Allowed values: 1 - 10
-
-

 
 
 

 
 
 
priorityHOSTNAME_PRIORITY(+)
+mac-addressBRIDGE_MACADDR(+)
 missing variable means global value or 100hostname priority
-
-Example: HOSTNAME_PRIORITY=50 MAC address of the bridge. Note that this requires a recent kernel support, originally introduced in 3.15 upstream kernel) BRIDGE_MACADDR for bridges is an NM extension.
 

 
from-dhcpHOSTNAME_FROM_DHCP(+)
-missing variable means global default or 1whether the system hostname can be determined from DHCP
+stpSTPnoSpan tree protocol participation.
priorityBRIDGING_OPTS: priority=32768STP priority.
 
-Example: HOSTNAME_FROM_DHCP=0,1
 

 
from-dhcpHOSTNAME_FROM_DNS_LOOKUP(+)
-missing variable means global default or 1whether the system hostname can be determined from reverse DNS lookup
+forward-delayDELAY15STP forwarding delay.
 
-Example: HOSTNAME_FROM_DNS_LOOKUP=0,1
 

 
only-best-deviceHOSTNAME_ONLY_FROM_DEFAULT(+)
-missing variable means global default or 1whether the hostname can be determined only from devices with the default route
+hello-timeBRIDGING_OPTS: hello_time=2STP hello time.
 
-Example: HOSTNAME_ONLY_FROM_DEFAULT=0,1
 

-

-

-
Table 21. infiniband setting

-

------
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+Allowed values: 6 - 40
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+Allowed values: 0 or 1
-
-
-
-
-
-
-






PropertyIfcfg-rh VariableDefaultDescription

 
mac-addressHWADDR IBoIP 20-byte hardware address of the device (in traditional hex-digits-and-colons notation). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.
+max-ageBRIDGING_OPTS: max_age=20STP maximum message age.
 
-Example: HWADDR=01:02:03:04:05:06:07:08:09:0A:01:02:03:04:05:06:07:08:09:11
 

 
mtuMTU MTU of the interface.ageing-timeBRIDGING_OPTS: ageing_time=300Ethernet MAC ageing time.
+
+Allowed values: 0 - 1000000
 

 
transport-modeCONNECTED_MODECONNECTED_MODE=noCONNECTED_MODE=yes for "connected" mode, CONNECTED_MODE=no for "datagram" modemulticast-snoopingBRIDGING_OPTS: multicast_snooping=1IGMP snooping support.
+
+Allowed values: 0 or 1
 

 
p-keyPKEY_ID (and PKEY=yes)PKEY=noInfiniBand P_Key. The value can be a hex number prefixed with "0x" or a decimal number. When PKEY_ID is specified, PHYSDEV and DEVICE also must be specified.
+vlan-filteringBRIDGING_OPTS: vlan_filtering=0VLAN filtering support.
 
-Example: PKEY=yes PKEY_ID=2 PHYSDEV=mlx4_ib0 DEVICE=mlx4_ib0.8002
 

 
parentPHYSDEV (PKEY=yes)PKEY=noInfiniBand parent device.
-
-Example: PHYSDEV=ib0

-

-

-
Table 22. ipv4 setting

-

------
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+Allowed values: 0 - 4094
-
-
+
+
-
-
-
-
-
-
-
+Example: BRIDGE_VLANS="1 pvid untagged,20,300-400 untagged"
-
-
+
+
-
+Example: BRIDGING_OPTS="group_address=01:80:C2:00:00:0A"
-
-
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+Example: BRIDGING_OPTS="vlan_protocol=802.1Q"
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+Example: BRIDGING_OPTS="multicast_last_member_count=4"
-
-
-
-
+
+
+
+Example: BRIDGING_OPTS="multicast_last_member_interval=200"
-
-
-
-
+
+
+
+Example: BRIDGING_OPTS="multicast_membership_interval=16000"
-
-
-
-
+
+
+
+Example: BRIDGING_OPTS="multicast_querier_interval=20000"
-
-
-
-
+
+
+
+Example: BRIDGING_OPTS="multicast_query_interval=22500"
-
-
-
-
+
+
+
+Example: BRIDGING_OPTS="multicast_query_response_interval=2000"
-
-
-
-
+
+
+
+Example: BRIDGING_OPTS="multicast_startup_query_count=4"
-
-
-
-
+
+
+
+Example: BRIDGING_OPTS="multicast_startup_query_interval=4000"






PropertyIfcfg-rh VariableDefaultDescription
methodBOOTPROTOnoneMethod used for IPv4 protocol configuration.
+vlan-default-pvidBRIDGING_OPTS: default_pvid=1default VLAN PVID.
 
-Allowed values: none, dhcp (bootp), static, ibft, autoip, shared
 

 
dnsDNS1, DNS2, ...vlansBRIDGE_VLANS
  List of DNS servers. Even if NetworkManager supports many DNS servers, initscripts and resolver only care about the first three, usually.
+List of VLANs on the bridge
 
-Example: DNS1=1.2.3.4 DNS2=10.0.0.254 DNS3=8.8.8.8
dns-searchDOMAIN List of DNS search domains.
 

 
addressesIPADDR, PREFIX (NETMASK), IPADDR1, PREFIX1 (NETMASK1), ...group-addressBRIDGING_OPTS: group_address=
  List of static IP addresses.
+STP group address.
 
-Example: IPADDR=10.5.5.23 PREFIX=24 IPADDR1=1.1.1.2 PREFIX1=16
 

 
gatewayGATEWAYvlan-protocolBRIDGING_OPTS: vlan_protocol=
  Gateway IP address.
+VLAN filtering protocol.
 
-Example: GATEWAY=10.5.5.1
routesADDRESS1, NETMASK1, GATEWAY1, METRIC1, OPTIONS1, ... List of static routes. They are not stored in ifcfg-* file, but in route-* file instead.
ignore-auto-routesPEERROUTES(+)
-yesPEERROUTES has the opposite meaning as 'ignore-auto-routes' property.
ignore-auto-dnsPEERDNSyesPEERDNS has the opposite meaning as 'ignore-auto-dns' property.
dhcp-send-hostnameDHCP_SEND_HOSTNAME(+)
-yesWhether DHCP_HOSTNAME should be sent to the DHCP server.
 

 
dhcp-hostnameDHCP_HOSTNAME Hostname to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used.vlan-stats-enabledBRIDGING_OPTS: vlan_stats_enabled=0
+
+
+Example: BRIDGING_OPTS="vlan_stats_enabled=1"
 

 
never-defaultDEFROUTE (GATEWAYDEV in /etc/sysconfig/network)yesDEFROUTE=no tells NetworkManager that this connection should not be assigned the default route. DEFROUTE has the opposite meaning as 'never-default' property.multicast-routerBRIDGING_OPTS: multicast_router=auto
+
+
+Example: BRIDGING_OPTS="multicast_router=enabled"
+
+Allowed values: auto, enabled, disabled
 

 
may-failIPV4_FAILURE_FATAL(+)
-noIPV4_FAILURE_FATAL has the opposite meaning as 'may-fail' property.multicast-query-use-ifaddrBRIDGING_OPTS: multicast_query_use_ifaddr=0
+
+
+Example: BRIDGING_OPTS="multicast_query-use_ifaddr=1"
 

 
route-metricIPV4_ROUTE_METRIC(+)
--1IPV4_ROUTE_METRIC is the default IPv4 metric for routes on this connection. If set to -1, a default metric based on the device type is used.multicast-querierBRIDGING_OPTS: multicast_querier=0
+
+
+Example: BRIDGING_OPTS="multicast_querier=1"
 

 
route-tableIPV4_ROUTE_TABLE(+)
-0IPV4_ROUTE_TABLE enables policy-routing and sets the default routing table.multicast-hash-maxBRIDGING_OPTS: multicast_hash_max=4096
+
+
+Example: BRIDGING_OPTS="multicast_hash_max=8192"
 

 
dns-optionsRES_OPTIONS(+)
- List of DNS options to be added to /etc/resolv.conf
+multicast-last-member-countBRIDGING_OPTS: multicast_last_member_count=2
+
 
-Example: RES_OPTIONS=ndots:2 timeout:3
 

 
dns-priorityIPV4_DNS_PRIORITY(+)
-0The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used.
+multicast-last-member-intervalBRIDGING_OPTS: multicast_last_member_interval=100
+
 
-Example: IPV4_DNS_PRIORITY=20
 

 
dhcp-client-idDHCP_CLIENT_ID(+)
- A string sent to the DHCP server to identify the local machine. A binary value can be specified using hex notation ('aa:bb:cc').
+multicast-membership-intervalBRIDGING_OPTS: multicast_membership_interval=26000
+
 
-Example: DHCP_CLIENT_ID=ax-srv-1; DHCP_CLIENT_ID=01:44:44:44:44:44:44
 

 
dad-timeoutACD_TIMEOUT(+), ARPING_WAITmissing variable means global default (config override or zero)Timeout (in milliseconds for ACD_TIMEOUT or in seconds for ARPING_WAIT) for address conflict detection before configuring IPv4 addresses. 0 turns off the ACD completely, -1 means default value.
+multicast-querier-intervalBRIDGING_OPTS: multicast_querier_interval=25500
+
 
-Example: ACD_TIMEOUT=2000 or ARPING_WAIT=2
 

 
dhcp-timeoutIPV4_DHCP_TIMEOUT(+)
- A timeout after which the DHCP transaction fails in case of no response.
+multicast-query-intervalBRIDGING_OPTS: multicast_query_interval=12500
+
 
-Example: IPV4_DHCP_TIMEOUT=10
 

 
dhcp-fqdnDHCP_FQDN FQDN to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used.
+multicast-query-response-intervalBRIDGING_OPTS: multicast_query_response_interval=1000
+
 
-Example: DHCP_FQDN=foo.bar.com
 

 
dhcp-vendor-class-identifierDHCP_VENDOR_CLASS_IDENTIFIER(+)
- The Vendor Class Identifier DHCP option (60).
+multicast-startup-query-countBRIDGING_OPTS: multicast_startup_query_count=2
+
 
-Example: DHCP_VENDOR_CLASS_IDENTIFIER=foo
 

 
link-localIPV4_LINK_LOCAL(+)
- Configure link-local IP address in interaction with method
+multicast-startup-query-intervalBRIDGING_OPTS: multicast_startup_query_interval=3125
+
 
-Example: IPV4_LINK_LOCAL=auto
 

 
 

 

 

-
Table 23. ipv6 setting

-

+
Table 19. bridge-port setting

+
@@ -1652,181 +1367,288 @@ Example: IPV4_LINK_LOCAL=auto
-
-
-
-
-
-
-
-
-
-
+
+
+
+
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

 
 
 

 
 
 
methodIPV6INIT, IPV6FORWARDING, IPV6_AUTOCONF, DHCPV6C, IPV6_DISABLEDIPV6INIT=yes; IPV6FORWARDING=no; IPV6_AUTOCONF=!IPV6FORWARDING, DHCPV6=noMethod used for IPv6 protocol configuration. ignore ~ IPV6INIT=no; auto ~ IPV6_AUTOCONF=yes; dhcp ~ IPV6_AUTOCONF=no and DHCPV6C=yes; disabled ~ IPV6_DISABLED=yes
dnsDNS1, DNS2, ... List of DNS servers. NetworkManager uses the variables both for IPv4 and IPv6.priorityBRIDGING_OPTS: priority=32STP priority.
+
+Allowed values: 0 - 63
 

 
dns-searchIPV6_DOMAIN(+)
+path-costBRIDGING_OPTS: path_cost=100STP cost.
+
+Allowed values: 1 - 65535
hairpin-modeBRIDGING_OPTS: hairpin_mode=yesHairpin mode of the bridge port.
vlansBRIDGE_PORT_VLANS List of VLANs on the bridge port
+
+Example: BRIDGE_PORT_VLANS="1 pvid untagged,20,300-400 untagged"

+

+

+
Table 20. connection setting

+

++++++
+
+
+
+
+
+
+
+
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
-
+
-
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
-
+Example: MULTI_CONNECT=3
-
-
+
+
-
+Example: ZONE=Work
-
-
-
-
+
+
+
+
-
-
-
-
+
+
+
+
-
-
+
-
-
+
+
-
-
+
-
-
+
+
-
-
+
-
+Example: GATEWAY_PING_TIMEOUT=5
-
-
+
-
+Example: CONNECTION_METERED=yes
+
+Allowed values: yes,no,unknown
-
-
+
-
-
+
+Allowed values: boolean value or 'rx'
-
-
-
-
+
+
+
+
+
+
+
+
+
+Allowed values: yes,no,resolve
-
-
-
-
+
+
+
+Example: LLMNR=yes
+
+Allowed values: yes,no,resolve
-
-
+
-
-
+
+Allowed values: yes,no,opportunistic
-
-
+
-
-
+
+Example: MPTCP_FLAGS="signal,subflow"
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+






PropertyIfcfg-rh VariableDefaultDescription
idNAME(+)
 
  List of DNS search domains.User friendly name for the connection profile.
 

 
addressesIPV6ADDR, IPV6ADDR_SECONDARIESuuidUUID(+)
+
  List of static IP addresses.
-
-Example: IPV6ADDR=ab12:9876::1 IPV6ADDR_SECONDARIES="ab12:9876::2 ab12:9876::3"UUID for the connection profile. When missing, NetworkManager creates the UUID itself (by hashing the filename).
 

 
gatewayIPV6_DEFAULTGWstable-idSTABLE_ID(+)
+
  Gateway IP address.
-
-Example: IPV6_DEFAULTGW=abbe::1Token to generate stable IDs.
 

 
routes(none)interface-nameDEVICE
  List of static routes. They are not stored in ifcfg-* file, but in route6-* file instead in the form of command line for 'ip route add'.Interface name of the device this profile is bound to. The variable can be left out when the profile should apply for more devices. Note that DEVICE can be required for some connection types.
 

 
ignore-auto-routesIPV6_PEERROUTES(+)
+typeTYPE (DEVICETYPE, DEVICE) Base type of the connection. DEVICETYPE is used for teaming connections.
+
+Example: TYPE=Ethernet; TYPE=Bond; TYPE=Bridge; DEVICETYPE=TeamPort
+
+Allowed values: Ethernet, Wireless, InfiniBand, Bridge, Bond, Vlan, Team, TeamPort
permissionsUSERS(+)
  Restrict to certain users the access to this connection, and allow the connection to be active only when at least one of the specified users is logged into an active session.
+
+Example: USERS="joe bob"
autoconnectONBOOT
 yesIPV6_PEERROUTES has the opposite meaning as 'ignore-auto-routes' property.Whether the connection should be autoconnected (not only while booting).
 

 
ignore-auto-dnsIPV6_PEERDNS(+)
+autoconnect-priorityAUTOCONNECT_PRIORITY(+)
 yesIPV6_PEERDNS has the opposite meaning as 'ignore-auto-dns' property.0Connection priority for automatic activation. Connections with higher numbers are preferred when selecting profiles for automatic activation.
+
+Example: AUTOCONNECT_PRIORITY=20
+
+Allowed values: -999 to 999
 

 
dhcp-hostnameDHCPV6_HOSTNAMEautoconnect-retriesAUTOCONNECT_RETRIES(+)
+
  Hostname to send the DHCP server.The number of times a connection should be autoactivated before giving up and switching to the next one.
+
+Example: AUTOCONNECT_RETRIES=1
+
+Allowed values: -1 (use global default), 0 (forever) or a positive value
 

 
dhcp-timeoutIPV6_DHCP_TIMEOUT(+)
+multi-connectMULTI_CONNECT(+)
 
  A timeout after which the DHCP transaction fails in case of no response.
+whether the profile can be active on multiple devices at a given moment. The values are numbers corresponding to #NMConnectionMultiConnect enum.
 
-Example: IPV6_DHCP_TIMEOUT=10
 

 
dhcp-hostname-flagsDHCPV6_HOSTNAME_FLAGSzoneZONE(+)
+
  flags for the DHCP hostname property
+Trust level of this connection. The string is usually used for a firewall.
 
-Example: DHCPV6_HOSTNAME_FLAGS=5
 

 
never-defaultIPV6_DEFROUTE(+), (and IPV6_DEFAULTGW, IPV6_DEFAULTDEV in /etc/sysconfig/network)IPV6_DEFROUTE=yes (when no variable specified)IPV6_DEFROUTE=no tells NetworkManager that this connection should not be assigned the default IPv6 route. IPV6_DEFROUTE has the opposite meaning as 'never-default' property.masterMASTER, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, BRIDGE, BRIDGE_UUID Reference to master connection. The variable used depends on the connection type and the value. In general, if the *_UUID variant is present, the variant without *_UUID is ignored. NetworkManager attempts to write both for compatibility with legacy tooling.
 

 
may-failIPV6_FAILURE_FATAL(+)
-noIPV6_FAILURE_FATAL has the opposite meaning as 'may-fail' property.slave-typeMASTER, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, DEVICETYPE, BRIDGE, BRIDGE_UUID Slave type doesn't map directly to a variable, but it is recognized using different variables.  MASTER and MASTER_UUID for bonding, TEAM_MASTER, TEAM_MASTER_UUID and DEVICETYPE for teaming, BRIDGE and BRIDGE_UUID for bridging.
 

 
route-metricIPV6_ROUTE_METRIC(+)
+autoconnect-slavesAUTOCONNECT_SLAVES(+)
 -1IPV6_ROUTE_METRIC is the default IPv6 metric for routes on this connection. If set to -1, a default metric based on the device type is used.missing variable means global defaultWhether slaves of this connection should be auto-connected when this connection is activated.
 

 
route-tableIPV6_ROUTE_TABLE(+)
+secondariesSECONDARY_UUIDS(+)
 0IPV6_ROUTE_TABLE enables policy-routing and sets the default routing table. UUID of VPN connections that should be activated together with this connection.
 

 
dns-priorityIPV6_DNS_PRIORITY(+)
+gateway-ping-timeoutGATEWAY_PING_TIMEOUT(+)
 
 0The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used.
+If greater than zero, the IP connectivity will be checked by pinging the gateway and waiting for the specified timeout (in seconds).
 
-Example: IPV6_DNS_PRIORITY=20
 

 
dns-optionsIPV6_RES_OPTIONS(+)
+meteredCONNECTION_METERED(+)
 
  List of DNS options to be added to /etc/resolv.conf
+Whether the device is metered
 
-Example: IPV6_RES_OPTIONS=ndots:2 timeout:3
 

 
ip6-privacyIPV6_PRIVACY, IPV6_PRIVACY_PREFER_PUBLIC_IP(+)
+lldpLLDP(+)
 noConfigure IPv6 Privacy Extensions for SLAAC (RFC4941).
+missing variable means global defaultwhether LLDP is enabled for the connection
 
-Example: IPV6_PRIVACY=rfc3041 IPV6_PRIVACY_PREFER_PUBLIC_IP=yes
+Example: LLDP=no
 
-Allowed values: IPV6_PRIVACY: no, yes (rfc3041 or rfc4941); IPV6_PRIVACY_PREFER_PUBLIC_IP: yes, no
 

 
addr-gen-modeIPV6_ADDR_GEN_MODE"default-or-eui64"Configure IPv6 Stable Privacy addressing for SLAAC (RFC7217).
+auth-retriesAUTH_RETRIES(+)
+0Number of retries for authentication.
mdnsMDNS(+)
+missing variable means global defaultWhether or not mDNS is enabled for the connection
 
-Example: IPV6_ADDR_GEN_MODE=stable-privacy
+Example: MDNS=yes
 
-Allowed values: IPV6_ADDR_GEN_MODE: default, default-or-eui64, eui64, stable-privacy
 

 
tokenIPV6_TOKEN The IPv6 tokenized interface identifier token
+llmnrLLMNR(+)
+missing variable means global defaultWhether or not LLMNR is enabled for the connection
 
-Example: IPV6_TOKEN=::53
 

 
dhcp-timeoutIPV6_RA_TIMEOUT(+)
+dns-over-tlsDNS_OVER_TLS(+)
  A timeout for waiting Router Advertisements in seconds.
+missing variable means global defaultWhether or not DNSOverTls is enabled for the connection
 
-Example: IPV6_RA_TIMEOUT=10
 

 
dhcp-duidDHCPV6_DUID(+)
+mptcp-flagsMPTCP_FLAGS(+)
  A string sent to the DHCPv6 server to identify the local machine. Apart from the special values "lease", "stable-llt", "stable-ll", "stable-uuid", "llt" and "ll" a binary value in hex format is expected. An hex string where each octet is separated by a colon is also accepted.
+missing variable means global defaultThe MPTCP flags that indicate whether MPTCP is enabled and which flags to use for the address endpoints.
 
-Example: DHCPV6_DUID=LL; DHCPV6_DUID=0301deadbeef0001; DHCPV6_DUID=03:01:de:ad:be:ef:00:01
wait-device-timeoutDEVTIMEOUT(+)
+ for initscripts compatibility, this variable must be a whole integer. If necessary, NetworkManager stores also a fractional component for the milliseconds.
+
+Example: DEVTIMEOUT=5
+
+Allowed values: timeout in seconds.
mud-urlMUD_URL MUD_URL to be sent by device (See RFC 8520).
+
+Example: https://yourdevice.example.com/model.json
+
+Allowed values: a valid URL that points to recommended policy for this device
wait-activation-delayWAIT_ACTIVATION_DELAY(+)
+ Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.
+
+Example: WAIT_ACTIVATION_DELAY=5000
+
+Allowed values: delay in milliseconds.
 

 
 

 

 

-
Table 24. match setting

-

+
Table 21. dcb setting

+
@@ -1839,19 +1661,129 @@ Example: DHCPV6_DUID=LL; DHCPV6_DUID=0301deadbeef0001; DHCPV6_DU
 
-
-
-
+
+
+
+
+
+
+
+
+
+
-
-
+Allowed values: 0 - 7
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

 
 
 

Default
 Description
 
pathMATCH_PATH
app-fcoe-flagsDCB_APP_FCOE_ENABLE, DCB_APP_FCOE_ADVERTISE, DCB_APP_FCOE_WILLINGnoFCOE flags.
+
+Example: DCB_APP_FCOE_ENABLE=yes DCB_APP_FCOE_ADVERTISE=yes
app-fcoe-priorityDCB_APP_FCOE_PRIORITY
  space-separated list of paths to match against the udev property ID_PATHS of devices
+Priority of FCoE frames.
 
-Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"
app-fcoe-modeDCB_APP_FCOE_MODEfabricFCoE controller mode.
+
+Allowed values: fabric, vn2vn
app-iscsi-flagsDCB_APP_ISCSI_ENABLE, DCB_APP_ISCSI_ADVERTISE, DCB_APP_ISCSI_WILLINGnoiSCSI flags.
app-iscsi-priorityDCB_APP_ISCSI_PRIORITY Priority of iSCSI frames.
+
+Allowed values: 0 - 7
app-fip-flagsDCB_APP_FIP_ENABLE, DCB_APP_FIP_ADVERTISE, DCB_APP_FIP_WILLINGnoFIP flags.
app-fip-priorityDCB_APP_FIP_PRIORITY Priority of FIP frames.
+
+Allowed values: 0 - 7
priority-flow-control-flagsDCB_PFC_ENABLE, DCB_PFC_ADVERTISE, DCB_PFC_WILLINGnoPriority flow control flags.
priority-flow-controlDCB_PFC_UP Priority flow control values. String of 8 "0" and "1", where "0". means "do not transmit priority pause", "1" means "transmit pause".
+
+Example: DCB_PFC_UP=01101110
priority-group-flagsDCB_PG_ENABLE, DCB_PG_ADVERTISE, DCB_PG_WILLINGnoPriority groups flags.
priority-group-idDCB_PG_ID Priority groups values. String of eight priorities (0 - 7) or "f" (unrestricted).
+
+Example: DCB_PG_ID=1205f173
priority-group-bandwidthDCB_PG_PCT Priority groups values. Eight bandwidths (in percent), separated with commas.
+
+Example: DCB_PG_PCT=10,5,10,15,10,10,10,30
priority-bandwidthDCB_PG_UPPCT Priority values. Eight bandwidths (in percent), separated with commas. The sum of the numbers must be 100.
+
+Example: DCB_PG_UPPCT=7,13,10,10,15,15,10,20
priority-strict-bandwidthDCB_PG_STRICT Priority values. String of eight "0" or "1", where "0" means "may not utilize all bandwidth", "1" means "may utilize all bandwidth".
+
+Example: DCB_PG_STRICT=01101110
priority-traffic-classDCB_PG_UP2TC Priority values. String of eight traffic class values (0 - 7).
+
+Example: DCB_PG_UP2TC=01623701

 

 

-

-
Table 25. ovs-bridge setting

-

+

+          All DCB related configuration is a NetworkManager extension. DCB=yes must be
+          used explicitly to enable DCB so that the rest of the DCB_* variables can apply.
+        

+

+
Table 22. ethtool setting

+
@@ -1868,8 +1800,8 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"

 
 
 

 

 

 

-
Table 26. ovs-dpdk setting

-

+
Table 23. hostname setting

+
@@ -1882,12 +1814,49 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

 
 
 

 
Default
 Description
 
priorityHOSTNAME_PRIORITY(+)
+missing variable means global value or 100hostname priority
+
+Example: HOSTNAME_PRIORITY=50
from-dhcpHOSTNAME_FROM_DHCP(+)
+missing variable means global default or 1whether the system hostname can be determined from DHCP
+
+Example: HOSTNAME_FROM_DHCP=0,1
from-dns-lookupHOSTNAME_FROM_DNS_LOOKUP(+)
+missing variable means global default or 1whether the system hostname can be determined from reverse DNS lookup
+
+Example: HOSTNAME_FROM_DNS_LOOKUP=0,1
only-best-deviceHOSTNAME_ONLY_FROM_DEFAULT(+)
+missing variable means global default or 1whether the hostname can be determined only from devices with the default route
+
+Example: HOSTNAME_ONLY_FROM_DEFAULT=0,1

 

 

 

-
Table 27. ovs-external-ids setting

-

+
Table 24. infiniband setting

+
@@ -1900,66 +1869,49 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

 
 
 

 
Default
 Description
 
mac-addressHWADDR IBoIP 20-byte hardware address of the device (in traditional hex-digits-and-colons notation). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.
+
+Example: HWADDR=01:02:03:04:05:06:07:08:09:0A:01:02:03:04:05:06:07:08:09:11
mtuMTU MTU of the interface.
transport-modeCONNECTED_MODECONNECTED_MODE=noCONNECTED_MODE=yes for "connected" mode, CONNECTED_MODE=no for "datagram" mode
p-keyPKEY_ID (and PKEY=yes)PKEY=noInfiniBand P_Key. The value can be a hex number prefixed with "0x" or a decimal number. When PKEY_ID is specified, PHYSDEV and DEVICE also must be specified.
+
+Example: PKEY=yes PKEY_ID=2 PHYSDEV=mlx4_ib0 DEVICE=mlx4_ib0.8002
parentPHYSDEV (PKEY=yes)PKEY=noInfiniBand parent device.
+
+Example: PHYSDEV=ib0

 

 

 

-
Table 28. ovs-interface setting

-

------
-
-
-
-
-
-
-
-






PropertyIfcfg-rh VariableDefaultDescription

-

-

-
Table 29. ovs-patch setting

-

------
-
-
-
-
-
-
-
-






PropertyIfcfg-rh VariableDefaultDescription

-

-

-
Table 30. ovs-port setting

-

------
-
-
-
-
-
-
-
-






PropertyIfcfg-rh VariableDefaultDescription

-

-

-
Table 31. proxy setting

-

+
Table 25. ipv4 setting

+
@@ -1975,126 +1927,192 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"
-
+
-
+Allowed values: none, dhcp (bootp), static, ibft, autoip, shared
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
+
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
-
+Example: RES_OPTIONS=ndots:2 timeout:3
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
-
+Example: DHCP_CLIENT_ID=ax-srv-1; DHCP_CLIENT_ID=01:44:44:44:44:44:44
-
-

 
 
 

 
 

 methodPROXY_METHOD(+)
-BOOTPROTO
 noneMethod for proxy configuration. For "auto", WPAD is used for proxy configuration, or set the PAC file via PAC_URL or PAC_SCRIPT.
+Method used for IPv4 protocol configuration.
 
-Allowed values: none, auto
 

 
browser-onlyBROWSER_ONLY(+)
+dnsDNS1, DNS2, ... List of DNS servers. Even if NetworkManager supports many DNS servers, initscripts and resolver only care about the first three, usually.
+
+Example: DNS1=1.2.3.4 DNS2=10.0.0.254 DNS3=8.8.8.8
dns-searchDOMAIN List of DNS search domains.
addressesIPADDR, PREFIX (NETMASK), IPADDR1, PREFIX1 (NETMASK1), ... List of static IP addresses.
+
+Example: IPADDR=10.5.5.23 PREFIX=24 IPADDR1=1.1.1.2 PREFIX1=16
gatewayGATEWAY Gateway IP address.
+
+Example: GATEWAY=10.5.5.1
routesADDRESS1, NETMASK1, GATEWAY1, METRIC1, OPTIONS1, ... List of static routes. They are not stored in ifcfg-* file, but in route-* file instead.
ignore-auto-routesPEERROUTES(+)
+yesPEERROUTES has the opposite meaning as 'ignore-auto-routes' property.
ignore-auto-dnsPEERDNSyesPEERDNS has the opposite meaning as 'ignore-auto-dns' property.
dhcp-send-hostnameDHCP_SEND_HOSTNAME(+)
+yesWhether DHCP_HOSTNAME should be sent to the DHCP server.
dhcp-hostnameDHCP_HOSTNAME Hostname to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used.
never-defaultDEFROUTE (GATEWAYDEV in /etc/sysconfig/network)yesDEFROUTE=no tells NetworkManager that this connection should not be assigned the default route. DEFROUTE has the opposite meaning as 'never-default' property.
may-failIPV4_FAILURE_FATAL(+)
 
 noWhether the proxy configuration is for browser only.IPV4_FAILURE_FATAL has the opposite meaning as 'may-fail' property.
 

 
pac-urlPAC_URL(+)
+route-metricIPV4_ROUTE_METRIC(+)
+-1IPV4_ROUTE_METRIC is the default IPv4 metric for routes on this connection. If set to -1, a default metric based on the device type is used.
route-tableIPV4_ROUTE_TABLE(+)
+0IPV4_ROUTE_TABLE enables policy-routing and sets the default routing table.
dns-optionsRES_OPTIONS(+)
 
  URL for PAC file.
+List of DNS options to be added to /etc/resolv.conf
 
-Example: PAC_URL=http://wpad.mycompany.com/wpad.dat
 

 
pac-scriptPAC_SCRIPT(+)
+dns-priorityIPV4_DNS_PRIORITY(+)
+0The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used.
+
+Example: IPV4_DNS_PRIORITY=20
auto-route-ext-gwIPV4_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.
dhcp-client-idDHCP_CLIENT_ID(+)
 
  The PAC script. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.
+A string sent to the DHCP server to identify the local machine. A binary value can be specified using hex notation ('aa:bb:cc').
 
-Example: PAC_SCRIPT="function FindProxyForURL (url, host) { return 'PROXY proxy.example.com:8080; DIRECT'; }"
 

-

-

-
Table 32. sriov setting

-

------
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
+Example: IPV4_DHCP_TIMEOUT=10
-
-
+
+
-
+Example: DHCP_HOSTNAME_FLAGS=5
-
-
-
-
+
+
+
+Example: DHCP_FQDN=foo.bar.com
-
-






PropertyIfcfg-rh VariableDefaultDescription

 
total-vfsSRIOV_TOTAL_VFS(+)
+dad-timeoutACD_TIMEOUT(+), ARPING_WAITmissing variable means global default (config override or zero)Timeout (in milliseconds for ACD_TIMEOUT or in seconds for ARPING_WAIT) for address conflict detection before configuring IPv4 addresses. 0 turns off the ACD completely, -1 means default value.
+
+Example: ACD_TIMEOUT=2000 or ARPING_WAIT=2
dhcp-timeoutIPV4_DHCP_TIMEOUT(+)
 
  The total number of virtual functions to create
+A timeout after which the DHCP transaction fails in case of no response.
 
-Example: SRIOV_TOTAL_VFS=16
 

 
vfsSRIOV_VF1(+), SRIOV_VF2(+), ...dhcp-hostname-flagsDHCP_HOSTNAME_FLAGS
  SR-IOV virtual function descriptors
+flags for the DHCP hostname and FQDN properties
 
-Example: SRIOV_VF10="mac=00:11:22:33:44:55", ...
 

 
autoprobe-driversSRIOV_AUTOPROBE_DRIVERS(+)
-missing variable means global defaultWhether to autoprobe virtual functions by a compatible driver
+dhcp-fqdnDHCP_FQDN FQDN to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used.
 
-Example: SRIOV_AUTOPROBE_DRIVERS=0,1
 

-

-

-
Table 33. tc setting

-

------
-
-
-
-
-
-
-
-
-
+
-
+Example: DHCP_VENDOR_CLASS_IDENTIFIER=foo
-
-
+
-
+Example: IPV4_LINK_LOCAL=auto






PropertyIfcfg-rh VariableDefaultDescription

 
qdiscsQDISC1(+), QDISC2(+), ..., TC_COMMIT(+)
+dhcp-vendor-class-identifierDHCP_VENDOR_CLASS_IDENTIFIER(+)
 
  Queueing disciplines to set on the interface. When no QDISC1, QDISC2, ..., FILTER1, FILTER2, ... keys are present, NetworkManager doesn't touch qdiscs and filters present on the interface, unless TC_COMMIT is set to 'yes'.
+The Vendor Class Identifier DHCP option (60).
 
-Example: QDISC1=ingress, QDISC2="root handle 1234: fq_codel"
 

 
qdiscsFILTER1(+), FILTER2(+), ..., TC_COMMIT(+)
+link-localIPV4_LINK_LOCAL(+)
 
  Traffic filters to set on the interface. When no QDISC1, QDISC2, ..., FILTER1, FILTER2, ... keys are present, NetworkManager doesn't touch qdiscs and filters present on the interface, unless TC_COMMIT is set to 'yes'.
+Configure link-local IP address in interaction with method
 
-Example: FILTER1="parent ffff: matchall action simple sdata Input", ...
 

 
 

 

 

-
Table 34. team-port setting

-

+
Table 26. ipv6 setting

+
@@ -2107,17 +2125,190 @@ Example: FILTER1="parent ffff: matchall action simple sdata Inpu
 
-
-
-
-
-
-
-

 
 
 

Default
 Description
 
configTEAM_PORT_CONFIG Team port configuration in JSON. See man teamd.conf for details.

+
+
+method
+IPV6INIT, IPV6FORWARDING, IPV6_AUTOCONF, DHCPV6C, IPV6_DISABLED
+IPV6INIT=yes; IPV6FORWARDING=no; IPV6_AUTOCONF=!IPV6FORWARDING, DHCPV6=no
+Method used for IPv6 protocol configuration. ignore ~ IPV6INIT=no; auto ~ IPV6_AUTOCONF=yes; dhcp ~ IPV6_AUTOCONF=no and DHCPV6C=yes; disabled ~ IPV6_DISABLED=yes
+
+
+dns
+DNS1, DNS2, ...
+ 
+List of DNS servers. NetworkManager uses the variables both for IPv4 and IPv6.
+
+
+dns-search
+IPV6_DOMAIN(+)
+
+ 
+List of DNS search domains.
+
+
+addresses
+IPV6ADDR, IPV6ADDR_SECONDARIES
+ 
+List of static IP addresses.
+
+Example: IPV6ADDR=ab12:9876::1 IPV6ADDR_SECONDARIES="ab12:9876::2 ab12:9876::3"
+
+
+gateway
+IPV6_DEFAULTGW
+ 
+Gateway IP address.
+
+Example: IPV6_DEFAULTGW=abbe::1
+
+
+routes
+(none)
+ 
+List of static routes. They are not stored in ifcfg-* file, but in route6-* file instead in the form of command line for 'ip route add'.
+
+
+ignore-auto-routes
+IPV6_PEERROUTES(+)
+
+yes
+IPV6_PEERROUTES has the opposite meaning as 'ignore-auto-routes' property.
+
+
+ignore-auto-dns
+IPV6_PEERDNS(+)
+
+yes
+IPV6_PEERDNS has the opposite meaning as 'ignore-auto-dns' property.
+
+
+dhcp-hostname
+DHCPV6_HOSTNAME
+ 
+Hostname to send the DHCP server.
+
+
+dhcp-timeout
+IPV6_DHCP_TIMEOUT(+)
+
+ 
+A timeout after which the DHCP transaction fails in case of no response.
+
+Example: IPV6_DHCP_TIMEOUT=10
+
+
+dhcp-hostname-flags
+DHCPV6_HOSTNAME_FLAGS
+ 
+flags for the DHCP hostname property
+
+Example: DHCPV6_HOSTNAME_FLAGS=5
+
+
+never-default
+IPV6_DEFROUTE(+), (and IPV6_DEFAULTGW, IPV6_DEFAULTDEV in /etc/sysconfig/network)
+IPV6_DEFROUTE=yes (when no variable specified)
+IPV6_DEFROUTE=no tells NetworkManager that this connection should not be assigned the default IPv6 route. IPV6_DEFROUTE has the opposite meaning as 'never-default' property.
+
+
+may-fail
+IPV6_FAILURE_FATAL(+)
+
+no
+IPV6_FAILURE_FATAL has the opposite meaning as 'may-fail' property.
+
+
+route-metric
+IPV6_ROUTE_METRIC(+)
+
+-1
+IPV6_ROUTE_METRIC is the default IPv6 metric for routes on this connection. If set to -1, a default metric based on the device type is used.
+
+
+route-table
+IPV6_ROUTE_TABLE(+)
+
+0
+IPV6_ROUTE_TABLE enables policy-routing and sets the default routing table.
+
+
+dns-priority
+IPV6_DNS_PRIORITY(+)
+
+0
+The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used.
+
+Example: IPV6_DNS_PRIORITY=20
+
+
+dns-options
+IPV6_RES_OPTIONS(+)
+
+ 
+List of DNS options to be added to /etc/resolv.conf
+
+Example: IPV6_RES_OPTIONS=ndots:2 timeout:3
+
+
+auto-route-ext-gw
+IPV6_AUTO_ROUTE_EXT_GW(+)
+
+yes
+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.
+
+
+ip6-privacy
+IPV6_PRIVACY, IPV6_PRIVACY_PREFER_PUBLIC_IP(+)
+
+no
+Configure IPv6 Privacy Extensions for SLAAC (RFC4941).
+
+Example: IPV6_PRIVACY=rfc3041 IPV6_PRIVACY_PREFER_PUBLIC_IP=yes
+
+Allowed values: IPV6_PRIVACY: no, yes (rfc3041 or rfc4941); IPV6_PRIVACY_PREFER_PUBLIC_IP: yes, no
+
+
+addr-gen-mode
+IPV6_ADDR_GEN_MODE
+"default-or-eui64"
+Configure IPv6 Stable Privacy addressing for SLAAC (RFC7217).
+
+Example: IPV6_ADDR_GEN_MODE=stable-privacy
+
+Allowed values: IPV6_ADDR_GEN_MODE: default, default-or-eui64, eui64, stable-privacy
+
+
+token
+IPV6_TOKEN
+ 
+The IPv6 tokenized interface identifier token
+
+Example: IPV6_TOKEN=::53
+
+
+ra-timeout
+IPV6_RA_TIMEOUT(+)
+
+ 
+A timeout for waiting Router Advertisements in seconds.
+
+Example: IPV6_RA_TIMEOUT=10
+
+
+dhcp-duid
+DHCPV6_DUID(+)
+
+ 
+A string sent to the DHCPv6 server to identify the local machine. Apart from the special values "lease", "stable-llt", "stable-ll", "stable-uuid", "llt" and "ll" a binary value in hex format is expected. An hex string where each octet is separated by a colon is also accepted.
+
+Example: DHCPV6_DUID=LL; DHCPV6_DUID=0301deadbeef0001; DHCPV6_DUID=03:01:de:ad:be:ef:00:01
+
+
+

 

 

-
Table 35. team setting

-

+
Table 27. loopback setting

+
@@ -2131,16 +2322,16 @@ Example: FILTER1="parent ffff: matchall action simple sdata Inpu
 
-
-
+
+
-
+

 
 
 

Description
 

 
configTEAM_CONFIGmtuMTU
  Team configuration in JSON. See man teamd.conf for details.MTU of the interface.
 

 

 

 

-
Table 36. user setting

-

+
Table 28. match setting

+
@@ -2154,18 +2345,18 @@ Example: FILTER1="parent ffff: matchall action simple sdata Inpu
 
-
-
+
+
-
+Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"

 
 
 

Description
 

 
dataNM_USER_*pathMATCH_PATH
  each key/value pair is stored as a separate variable with name composed by concatenating NM_USER_ with the encoded key. The key is encoded by substituting lowercase letters with uppercase and prepending uppercase letters with an underscore. A dot is encoded as a double underscore. Remaining characters are encoded as underscore followed by a 3 digit octal representation of the character.
+space-separated list of paths to match against the udev property ID_PATHS of devices
 
-Example: NM_USER_FOO__BAR=something
 

 

 

 

-
Table 37. veth setting

-

+
Table 29. ovs-bridge setting

+
@@ -2182,8 +2373,8 @@ Example: NM_USER_FOO__BAR=something

 
 
 

 

 

 

-
Table 38. vlan setting

-

+
Table 30. ovs-dpdk setting

+
@@ -2196,57 +2387,12 @@ Example: NM_USER_FOO__BAR=something
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+

 
 
 

 
Default
 Description
 
parentDEVICE or PHYSDEV Parent interface of the VLAN.
idVLAN_ID, DEVICE. VLAN identifier. If VLAN_ID is not set, it is attempted to be detected from the suffix of DEVICE=. Note that older versions of NetworkManager had a bug where they would prefer the detected ID from the DEVICE over VLAN_ID.
flagsGVRP, MVRP, VLAN_FLAGS VLAN flags.
-
-Allowed values: "yes or "no" for GVRP and MVRP; "LOOSE_BINDING" and "NO_REORDER_HDR" for VLAN_FLAGS
ingress-priority-mapVLAN_INGRESS_PRIORITY_MAP Ingress priority mapping.
-
-Example: VLAN_INGRESS_PRIORITY_MAP=4:2,3:5
egress-priority-mapVLAN_EGRESS_PRIORITY_MAP Egress priority mapping.
-
-Example: VLAN_EGRESS_PRIORITY_MAP=5:4,4:1,3:7
interface-namePHYSDEV and VLAN_ID, or DEVICE VLAN interface name. If all variables are set, parent device from PHYSDEV takes precedence over DEVICE, but VLAN id from DEVICE takes precedence over VLAN_ID.
-
-Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12

 

 

 

-
Table 39. vrf setting

-

+
Table 31. ovs-external-ids setting

+
@@ -2263,8 +2409,8 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12

 
 
 

 

 

 

-
Table 40. wifi-p2p setting

-

+
Table 32. ovs-interface setting

+
@@ -2281,8 +2427,8 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12

 
 
 

 

 

 

-
Table 41. 802-3-ethernet setting

-

+
Table 33. ovs-other-config setting

+
@@ -2295,115 +2441,12 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+

 
 
 

 
Default
 Description
 
port(none) The property is not saved by the plugin.
speedETHTOOL_OPTS Fixed speed for the ethernet link. It is added as "speed" parameter in the ETHTOOL_OPTS variable.
duplexETHTOOL_OPTS Fixed duplex mode for the ethernet link. It is added as "duplex" parameter in the ETHOOL_OPTS variable.
auto-negotiateETHTOOL_OPTS Whether link speed and duplex autonegotiation is enabled. It is not saved only if disabled and no values are provided for the "speed" and "duplex" parameters (skips link configuration).
mac-addressHWADDR Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.
cloned-mac-addressMACADDR Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).
generate-mac-address-maskGENERATE_MAC_ADDRESS_MASK(+)
- the MAC address mask for generating randomized and stable cloned-mac-address.
mac-address-blacklistHWADDR_BLACKLIST(+)
- It denies usage of the connection for any device whose address is listed.
-
-Example: HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55"
mtuMTU MTU of the interface.
s390-subchannelsSUBCHANNELS Subchannels for IBM S390 hosts.
-
-Example: SUBCHANNELS=0.0.b00a,0.0.b00b,0.0.b00c
s390-nettypeNETTYPE Network type of the S390 host.
-
-Example: NETTYPE=qeth
-
-Allowed values: "qeth", "lcs" or "ctc"
s390-optionsOPTIONS and PORTNAME, CTCPROTO, S390 device options. All options go to OPTIONS, except for "portname" and "ctcprot" that have their own variables.
wake-on-lanETHTOOL_OPTS, ETHTOOL_WAKE_ON_LAN Wake on Lan mode for ethernet. The setting "ignore" is expressed with "ETHTOOL_WAKE_ON_LAN=ignore". Otherwise, the "ETHTOOL_OPTS" variable is set with the value "wol" and several of the characters "p|u|m|b|a|g|s|f|d" as explained in the ethtool manual page.
wake-on-lan-passwordETHTOOL_OPTS Password for secure-on based Wake-on-Lan. It is added as "sopass" parameter in the ETHTOOL_OPTS variable.
-
-Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"
accept-all-mac-addressesACCEPT_ALL_MAC_ADDRESSES Enforce the interface to accept all the packets.

 

 

 

-
Table 42. wireguard setting

-

+
Table 34. ovs-patch setting

+
@@ -2420,8 +2463,26 @@ Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"

 
 
 

 

 

 

-
Table 43. 802-11-wireless-security setting

-

+
Table 35. ovs-port setting

+

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






PropertyIfcfg-rh VariableDefaultDescription

+

+

+
Table 36. proxy setting

+
@@ -2436,174 +2497,216 @@ Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
-
-
+
+Allowed values: none, auto
-
-
+
-
+
-
-
+
-
+Example: PAC_URL=http://wpad.mycompany.com/wpad.dat
-
-
+
-
+Example: PAC_SCRIPT="function FindProxyForURL (url, host) { return 'PROXY proxy.example.com:8080; DIRECT'; }"
+
+

 
 
 

 
 
 
key-mgmtKEY_MGMT(+)
- Key management method.
-
-Allowed values: none, ieee8021x, owe, wpa-psk, sae, wpa-eap, wpa-eap-suite-b-192
wep-tx-keyidxDEFAULTKEY1Index of active WEP key. Note that in ifcfg format the index starts counting at 1, while NetworkManager API otherwise is zero based.
-
-Allowed values: 1, 2, 3, 4
auth-algSECURITYMODE(+)
+methodPROXY_METHOD(+)
  Authentication algorithm for WEP.
+noneMethod for proxy configuration. For "auto", WPAD is used for proxy configuration, or set the PAC file via PAC_URL or PAC_SCRIPT.
 
-Allowed values: restricted, open, leap
 

 
protoWPA_ALLOW_WPA(+), WPA_ALLOW_WPA2(+)
+browser-onlyBROWSER_ONLY(+)
 
 noAllowed WPA protocols, WPA and WPA2 (RSN).
-
-Allowed values: yes, noWhether the proxy configuration is for browser only.
 

 
pairwiseCIPHER_PAIRWISE(+)
+pac-urlPAC_URL(+)
 
  Restrict pairwise encryption algorithms, specified as a space separated list.
+URL for PAC file.
 
-Allowed values: CCMP, TKIP
 

 
groupCIPHER_GROUP(+)
+pac-scriptPAC_SCRIPT(+)
 
  Restrict group/broadcast encryption algorithms, specified as a space separated list.
+The PAC script. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.
 
-Allowed values: CCMP, TKIP, WEP40, WEP104
 

+

+

+
Table 37. sriov setting

+

++++++
+
+
+
+
+
+
+
-
-
+
-
+Example: SRIOV_TOTAL_VFS=16
-
-
+
+
-
+
-
-
+
-
-
+
+
+
+






PropertyIfcfg-rh VariableDefaultDescription

 
pmfPMF(+)
+total-vfsSRIOV_TOTAL_VFS(+)
 
  Enables or disables PMF (802.11w)
-
-Example: PMF=required
+The total number of virtual functions to create
 
-Allowed values: default, disable, optional, required
 

 
leap-usernameIEEE_8021X_IDENTITY(+)
-vfsSRIOV_VF1(+), SRIOV_VF2(+), ...
  Login name for LEAP.SR-IOV virtual function descriptors
+
+Example: SRIOV_VF10="mac=00:11:22:33:44:55", ...
 

 
wep-key0KEY1, KEY_PASSPHRASE1(+)
+autoprobe-driversSRIOV_AUTOPROBE_DRIVERS(+)
  The first WEP key (used in most networks). See also DEFAULTKEY for key index.missing variable means global defaultWhether to autoprobe virtual functions by a compatible driver
+
+Example: SRIOV_AUTOPROBE_DRIVERS=0,1
 

+

+

+
Table 38. tc setting

+

++++++
+
+
+
+
+
+
+
-
-
+
-
+
-
-
+
-
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+






PropertyIfcfg-rh VariableDefaultDescription

 
wep-key1KEY2, KEY_PASSPHRASE2(+)
+qdiscsQDISC1(+), QDISC2(+), ..., TC_COMMIT(+)
 
  WEP key with index 1. See also DEFAULTKEY for key index.Queueing disciplines to set on the interface. When no QDISC1, QDISC2, ..., FILTER1, FILTER2, ... keys are present, NetworkManager doesn't touch qdiscs and filters present on the interface, unless TC_COMMIT is set to 'yes'.
+
+Example: QDISC1=ingress, QDISC2="root handle 1234: fq_codel"
 

 
wep-key2KEY3, KEY_PASSPHRASE3(+)
+tfiltersFILTER1(+), FILTER2(+), ..., TC_COMMIT(+)
 
  WEP key with index 2. See also DEFAULTKEY for key index.Traffic filters to set on the interface. When no QDISC1, QDISC2, ..., FILTER1, FILTER2, ... keys are present, NetworkManager doesn't touch qdiscs and filters present on the interface, unless TC_COMMIT is set to 'yes'.
+
+Example: FILTER1="parent ffff: matchall action simple sdata Input", ...
 
wep-key3KEY4, KEY_PASSPHRASE4(+)
- WEP key with index 3. See also DEFAULTKEY for key index.
wep-key-flagsWEP_KEY_FLAGS(+)
- Password flags for KEY<i>, KEY_PASSPHRASE<i> password. (see the section called “Secret flag types:” for _FLAGS values)
pskWPA_PSK Pre-Shared-Key for WPA networks.
psk-flagsWPA_PSK_FLAGS(+)
- Password flags for WPA_PSK_FLAGS. (see the section called “Secret flag types:” for _FLAGS values)
-
-Example: WPA_PSK_FLAGS=user
leap-passwordIEEE_8021X_PASSWORD(+)
- Password for LEAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent.
leap-password-flagsIEEE_8021X_PASSWORD_FLAGS(+)
- Password flags for IEEE_8021X_PASSWORD_FLAGS. (see the section called “Secret flag types:” for _FLAGS values)
wep-key-typeKEY<i> or KEY_PASSPHRASE<i>(+); KEY_TYPE(+)
-

+

+

+
Table 39. team setting

+

++++++
+
+
+
+
+
+
+
+
+
-
-
-
-
-
+
+
+






PropertyIfcfg-rh VariableDefaultDescription
configTEAM_CONFIG
  KEY is used for "key" type (10 or 26 hexadecimal characters, or 5 or 13 character string prefixed with "s:"). KEY_PASSPHRASE is used for WEP passphrases. KEY_TYPE specifies the key type and can be either 'key' or 'passphrase'. KEY_TYPE is redundant and can be omitted.
-
-Example: KEY1=s:ahoj, KEY1=0a1c45bc02, KEY_PASSPHRASE1=mysupersecretkey
wps-methodWPS_METHODTeam configuration in JSON. See man teamd.conf for details.

+

+

+
Table 40. team-port setting

+

++++++
+
+
+
+
+
+
+
+
+
-
-
-
-
-
+
+
+






PropertyIfcfg-rh VariableDefaultDescription
configTEAM_PORT_CONFIG
  Used to control the WPS methods to be used Valid values are "default", "auto", "disabled", "pin" and "pbc". If omitted, whatver the AP announces is used.
-
-Example: WPS_METHOD=disabled, WPS_METHOD="pin pbc"
filsFILS(+)
-Team port configuration in JSON. See man teamd.conf for details.

+

+

+
Table 41. user setting

+

++++++
+
+
+
+
+
+
+
+
+
-
-
-
+Example: NM_USER_FOO__BAR=something
+






PropertyIfcfg-rh VariableDefaultDescription
dataNM_USER_*
  Enables or disables FILS (802.11ai)
-
-Example: FILS=required
+each key/value pair is stored as a separate variable with name composed by concatenating NM_USER_ with the encoded key. The key is encoded by substituting lowercase letters with uppercase and prepending uppercase letters with an underscore. A dot is encoded as a double underscore. Remaining characters are encoded as underscore followed by a 3 digit octal representation of the character.
 
-Allowed values: default, disable, optional, required

 

 

 

-
Table 44. 802-11-wireless setting

-

+
Table 42. veth setting

+

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






PropertyIfcfg-rh VariableDefaultDescription

+

+

+
Table 43. vlan setting

+
@@ -2618,148 +2721,116 @@ Allowed values: default, disable, optional, required
-
-
-
-
-
-
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
+Allowed values: "yes or "no" for GVRP and MVRP; "LOOSE_BINDING" and "NO_REORDER_HDR" for VLAN_FLAGS
-
-
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
+Example: VLAN_PROTOCOL="802.1ad"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
-
+Example: VLAN_INGRESS_PRIORITY_MAP=4:2,3:5
-
-
+
+
-
+Example: VLAN_EGRESS_PRIORITY_MAP=5:4,4:1,3:7
-
-
+
+
-
-
-
-
-
-
-
+Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12

 
 
 

 
 
 
ssidESSID SSID of Wi-Fi network.
-
-Example: ESSID="Quick Net"
modeMODEparentDEVICE or PHYSDEV
  Wi-Fi network mode.
-
-Allowed values: Ad-Hoc, Managed (Auto)  [case insensitive]Parent interface of the VLAN.
 

 
bandBAND(+)
-idVLAN_ID, DEVICE.
  BAND alone is honored, but CHANNEL overrides BAND since it implies a band.
-
-Example: BAND=bg
-
-Allowed values: a, bgVLAN identifier. If VLAN_ID is not set, it is attempted to be detected from the suffix of DEVICE=. Note that older versions of NetworkManager had a bug where they would prefer the detected ID from the DEVICE over VLAN_ID.
 

 
channelCHANNELflagsGVRP, MVRP, VLAN_FLAGS
  Channel used for the Wi-Fi communication. Channels greater than 14 mean "a" band, otherwise the band is "bg".
+VLAN flags.
 
-Example: CHANNEL=6
 

 
bssidBSSID(+)
-protocolVLAN_PROTOCOL
  Restricts association only to a single AP.
+VLAN protocol.
 
-Example: BSSID=00:1E:BD:64:83:21
rate(none) This property is not handled by ifcfg-rh plugin.
tx-power(none) This property is not handled by ifcfg-rh plugin.
 

 
mac-addressHWADDR Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.
cloned-mac-addressMACADDR Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).
generate-mac-address-maskGENERATE_MAC_ADDRESS_MASK(+)
- the MAC address mask for generating randomized and stable cloned-mac-address.
mac-address-blacklistHWADDR_BLACKLIST(+)
- It denies usage of the connection for any device whose address is listed.
seen-bssids(none) This property is not handled by ifcfg-rh plugin.
mtuMTU MTU of the wireless interface.
hiddenSSID_HIDDEN(+)
- Whether the network hides the SSID.
powersavePOWERSAVE(+)
-ingress-priority-mapVLAN_INGRESS_PRIORITY_MAP
  Enables or disables Wi-Fi power saving.
-
-Example: POWERSAVE=enable
+Ingress priority mapping.
 
-Allowed values: default, ignore, enable, disable
 

 
mac-address-randomizationMAC_ADDRESS_RANDOMIZATION(+)
-egress-priority-mapVLAN_EGRESS_PRIORITY_MAP
  Enables or disables Wi-Fi MAC address randomization.
-
-Example: MAC_ADDRESS_RANDOMIZATION=always
+Egress priority mapping.
 
-Allowed values: default, never, always
 

 
security(none)interface-namePHYSDEV and VLAN_ID, or DEVICE
  This property is deprecated and not handled by ifcfg-rh-plugin.
ap-isolationAP_ISOLATION(+)
-missing variable means global defaultWhether AP isolation is enabled
+VLAN interface name. If all variables are set, parent device from PHYSDEV takes precedence over DEVICE, but VLAN id from DEVICE takes precedence over VLAN_ID.
 
-Allowed values: "yes", "no"
 

 
 

 

 

-
Table 45. wpan setting

+
Table 44. vrf setting

+

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






PropertyIfcfg-rh VariableDefaultDescription

+

+

+
Table 45. wifi-p2p setting

+

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






PropertyIfcfg-rh VariableDefaultDescription

+

+

+
Table 46. wireguard setting

+

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






PropertyIfcfg-rh VariableDefaultDescription

+

+

+
Table 47. wpan setting

 
diff --git a/docs/api/html/nm-settings-keyfile.html b/docs/api/html/nm-settings-keyfile.html
index 69bb333c..12b405b1 100644
--- a/docs/api/html/nm-settings-keyfile.html
+++ b/docs/api/html/nm-settings-keyfile.html
@@ -189,7 +189,93 @@ id=4
 

 
 

802-11-wireless-security  =  wifi-security

 

 

-
Table 1. bridge setting (section)

+
Table 1. 802-11-wireless setting (section)

+

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






PropertyKeyfile VariableFormatDescription
ssid string (or decimal-byte list - obsolete)SSID of Wi-Fi network.
+
+Example: ssid=Quick Net
mac-address usual hex-digits-and-colons notationMAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162).
cloned-mac-address usual hex-digits-and-colons notationCloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178).
mac-address-blacklist list of MACs (separated with semicolons)MAC address blacklist.
+
+Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78

+

+

+
Table 2. 802-3-ethernet setting (section)

+

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






PropertyKeyfile VariableFormatDescription
mac-address usual hex-digits-and-colons notationMAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162)
cloned-mac-address usual hex-digits-and-colons notationCloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178).
mac-address-blacklist list of MACs (separated with semicolons)MAC address blacklist.
+
+Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78

+

+

+
Table 3. bridge setting (section)

 
@@ -205,7 +291,7 @@ id=4
 
-
+

 
 

 

 mac-addressmac-address 
 usual hex-digits-and-colons notation
 MAC address in traditional hex-digits-and-colons notation, or semicolon separated list of 6 decimal bytes (obsolete)
 
@@ -214,7 +300,7 @@ Example: mac-address=00:22:68:12:79:A2 mac-address=0;34;104;18;1
 

 

 

-
Table 2. infiniband setting (section)

+
Table 4. infiniband setting (section)

 
@@ -230,7 +316,7 @@ Example: mac-address=00:22:68:12:79:A2 mac-address=0;34;104;18;1
 
-
+

 
 

 

 mac-addressmac-address 
 usual hex-digits-and-colons notation
 MAC address in traditional hex-digits-and-colons notation, or or semicolon separated list of 20 decimal bytes (obsolete)
 
@@ -239,7 +325,7 @@ Example: mac-address= 80:00:00:6d:fe:80:00:00:00:00:00:00:00:02:
 

 

 

-
Table 3. ipv4 setting (section)

+
Table 5. ipv4 setting (section)

 
@@ -256,7 +342,7 @@ Example: mac-address= 80:00:00:6d:fe:80:00:00:00:00:00:00:00:02:
 
-
+

 
 

 

 dnsdns 
 list of DNS IP addresses
 List of DNS servers.
 
@@ -290,7 +376,7 @@ Example: route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16
 

 

 

-
Table 4. ipv6 setting (section)

+
Table 6. ipv6 setting (section)

 
@@ -307,7 +393,7 @@ Example: route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16
-
+

 
 

 
 

 dnsdns 
 list of DNS IP addresses
 List of DNS servers.
 
@@ -341,7 +427,7 @@ Example: route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11
 

 

 

-
Table 5. serial setting (section)

+
Table 7. serial setting (section)

 
@@ -357,7 +443,7 @@ Example: route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11
 
-
+

 
 

 

 parityparity 
 'e', 'o', or 'n'
 The connection parity; even, odd, or none. Note that older versions of NetworkManager stored this as an integer: 69 ('E') for even, 111 ('o') for odd, or 110 ('n') for none.
 
@@ -366,7 +452,7 @@ Example: parity=n
 

 

 

-
Table 6. vpn setting (section)

+
Table 8. vpn setting (section)

 
@@ -401,7 +487,7 @@ Example: password=Popocatepetl

 
 

 

 

 

-
Table 7. wifi-p2p setting (section)

+
Table 9. wifi-p2p setting (section)

 
@@ -417,99 +503,13 @@ Example: password=Popocatepetl
-
+

 
 

 
 

 peerpeer 
 usual hex-digits-and-colons notation
 MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162).
 

 

 

 

-
Table 8. 802-3-ethernet setting (section)

-

------
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-






PropertyKeyfile VariableFormatDescription
mac-addressmac-addressusual hex-digits-and-colons notationMAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162)
cloned-mac-addresscloned-mac-addressusual hex-digits-and-colons notationCloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178).
mac-address-blacklistmac-address-blacklistlist of MACs (separated with semicolons)MAC address blacklist.
-
-Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78

-

-

-
Table 9. 802-11-wireless setting (section)

-

------
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-






PropertyKeyfile VariableFormatDescription
ssidssidstring (or decimal-byte list - obsolete)SSID of Wi-Fi network.
-
-Example: ssid=Quick Net
mac-addressmac-addressusual hex-digits-and-colons notationMAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162).
cloned-mac-addresscloned-mac-addressusual hex-digits-and-colons notationCloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178).
mac-address-blacklistmac-address-blacklistlist of MACs (separated with semicolons)MAC address blacklist.
-
-Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78

-

-

 
Table 10. wpan setting (section)

 
@@ -526,7 +526,7 @@ Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79
 
-
+
diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html
index e2f76d6a..2c7ef708 100644
--- a/docs/api/html/nm-settings-nmcli.html
+++ b/docs/api/html/nm-settings-nmcli.html
@@ -68,7 +68,7 @@
         

 
connection setting

-
 General Connection Profile Settings.

+
General Connection Profile Settings.

 

         Properties:
         

@@ -81,8 +81,8 @@
 

@@ -92,11 +92,11 @@
 
@@ -104,7 +104,7 @@
 
@@ -112,7 +112,7 @@
 
@@ -120,7 +120,7 @@
 
@@ -128,9 +128,9 @@
 
@@ -138,7 +138,7 @@
 
@@ -148,7 +148,7 @@
 
@@ -158,9 +158,9 @@
 
@@ -168,7 +168,7 @@
 
@@ -176,9 +176,9 @@
 
@@ -188,7 +188,7 @@
 
@@ -196,9 +196,9 @@
 
@@ -206,8 +206,8 @@
 
@@ -215,15 +215,15 @@
 
@@ -231,9 +231,9 @@
 
@@ -241,7 +241,7 @@
 
@@ -249,8 +249,8 @@
 
@@ -258,7 +258,7 @@
 
@@ -266,7 +266,7 @@
 
@@ -276,7 +276,7 @@
 
@@ -284,11 +284,11 @@
 
@@ -296,8 +296,8 @@
 
@@ -307,7 +307,7 @@
 
@@ -315,17 +315,17 @@
 
@@ -333,8 +333,8 @@
 
@@ -342,8 +342,8 @@
 
@@ -354,7 +354,7 @@
 

 
6lowpan setting

-
 6LoWPAN Settings.

+
6LoWPAN Settings.

 

         Properties:
         

@@ -368,7 +368,7 @@
 

@@ -378,7 +378,7 @@
 

 
802-1x setting

-
 IEEE 802.1x Authentication Settings.

+
IEEE 802.1x Authentication Settings.

 

         Properties:
         

@@ -391,7 +391,7 @@
 

@@ -399,7 +399,7 @@
 
@@ -407,7 +407,7 @@
 
@@ -415,9 +415,9 @@
 
@@ -425,7 +425,7 @@
 
@@ -433,7 +433,7 @@
 
@@ -441,8 +441,8 @@
 
@@ -450,8 +450,8 @@
 
@@ -459,7 +459,7 @@
 
@@ -467,7 +467,7 @@
 
@@ -475,7 +475,7 @@
 
@@ -483,7 +483,7 @@
 
@@ -491,7 +491,7 @@
 
@@ -499,7 +499,7 @@
 
@@ -507,7 +507,7 @@
 
@@ -515,7 +515,7 @@
 
@@ -523,7 +523,7 @@
 
@@ -531,7 +531,7 @@
 
@@ -539,7 +539,7 @@
 
@@ -547,7 +547,7 @@
 
@@ -555,7 +555,7 @@
 
@@ -563,7 +563,7 @@
 
@@ -571,7 +571,7 @@
 
@@ -579,7 +579,7 @@
 
@@ -587,7 +587,7 @@
 
@@ -595,7 +595,7 @@
 
@@ -603,7 +603,7 @@
 
@@ -611,9 +611,9 @@
 
@@ -621,7 +621,7 @@
 
@@ -629,7 +629,7 @@
 
@@ -637,8 +637,8 @@
 
@@ -646,8 +646,8 @@
 
@@ -655,7 +655,7 @@
 
@@ -663,7 +663,7 @@
 
@@ -671,7 +671,7 @@
 
@@ -679,7 +679,7 @@
 
@@ -687,8 +687,8 @@
 
@@ -696,7 +696,7 @@
 
@@ -704,7 +704,7 @@
 
@@ -712,7 +712,10 @@
 
@@ -720,7 +723,7 @@
 
@@ -728,7 +731,7 @@
 
@@ -736,9 +739,9 @@
 
@@ -746,7 +749,7 @@
 
@@ -754,7 +757,7 @@
 
@@ -762,7 +765,10 @@
 
@@ -770,7 +776,7 @@
 
@@ -781,7 +787,7 @@
 

 
adsl setting

-
 ADSL Settings.

+
ADSL Settings.

 

         Properties:
         

@@ -796,7 +802,7 @@
 

@@ -806,7 +812,7 @@
 
@@ -814,7 +820,7 @@
 
@@ -824,7 +830,7 @@
 
@@ -834,7 +840,7 @@
 
@@ -842,7 +848,7 @@
 
@@ -850,7 +856,7 @@
 
@@ -861,7 +867,7 @@
 

 
bluetooth setting

-
 Bluetooth Settings.

+
Bluetooth Settings.

 

         Properties:
         

@@ -876,7 +882,7 @@
 

@@ -886,7 +892,7 @@
 
@@ -897,7 +903,7 @@
 

 
bond setting

-
 Bonding Settings.

+
Bonding Settings.

 

         Properties:
         

@@ -909,7 +915,7 @@
 

@@ -919,7 +925,7 @@
 

 
bridge setting

-
 Bridging Settings.

+
Bridging Settings.

 

         Properties:
         

@@ -934,7 +940,7 @@
 

@@ -944,7 +950,7 @@
 
@@ -952,8 +958,8 @@
 
@@ -963,7 +969,7 @@
 
@@ -973,7 +979,7 @@
 
@@ -983,8 +989,11 @@
 
@@ -994,7 +1003,7 @@
 
@@ -1002,7 +1011,7 @@
 
@@ -1010,7 +1019,7 @@
 
@@ -1018,7 +1027,7 @@
 
@@ -1026,7 +1035,7 @@
 
@@ -1034,7 +1043,7 @@
 
@@ -1042,7 +1051,7 @@
 
@@ -1050,7 +1059,7 @@
 
@@ -1058,7 +1067,7 @@
 
@@ -1066,7 +1075,7 @@
 
@@ -1074,8 +1083,8 @@
 
@@ -1085,7 +1094,7 @@
 
@@ -1093,7 +1102,7 @@
 
@@ -1101,7 +1110,7 @@
 
@@ -1111,7 +1120,7 @@
 
@@ -1121,7 +1130,7 @@
 
@@ -1129,7 +1138,7 @@
 
@@ -1137,7 +1146,7 @@
 
@@ -1145,8 +1154,8 @@
 
@@ -1154,7 +1163,7 @@
 
@@ -1162,10 +1171,10 @@
 
@@ -1176,7 +1185,7 @@
 

 
bridge-port setting

-
 Bridge Port Settings.

+
Bridge Port Settings.

 

         Properties:
         

@@ -1191,7 +1200,7 @@
 

@@ -1201,7 +1210,7 @@
 
@@ -1211,7 +1220,7 @@
 
@@ -1219,10 +1228,10 @@
 
@@ -1233,7 +1242,7 @@
 

 
cdma setting

-
 CDMA-based Mobile Broadband Settings.

+
CDMA-based Mobile Broadband Settings.

 

         Properties:
         

@@ -1246,7 +1255,7 @@
 

@@ -1254,7 +1263,7 @@
 
@@ -1264,7 +1273,7 @@
 
@@ -1272,7 +1281,7 @@
 
@@ -1282,7 +1291,7 @@
 
@@ -1293,7 +1302,7 @@
 

 
dcb setting

-
 Data Center Bridging Settings.

+
Data Center Bridging Settings.

 

         Properties:
         

@@ -1306,7 +1315,7 @@
 

@@ -1314,8 +1323,8 @@
 
@@ -1323,7 +1332,7 @@
 
@@ -1331,7 +1340,7 @@
 
@@ -1339,7 +1348,7 @@
 
@@ -1347,7 +1356,7 @@
 
@@ -1355,7 +1364,7 @@
 
@@ -1363,7 +1372,7 @@
 
@@ -1371,7 +1380,7 @@
 
@@ -1379,7 +1388,7 @@
 
@@ -1387,7 +1396,7 @@
 
@@ -1395,7 +1404,7 @@
 
@@ -1403,7 +1412,7 @@
 
@@ -1411,7 +1420,7 @@
 
@@ -1419,7 +1428,7 @@
 
@@ -1430,7 +1439,7 @@
 

 
ethtool setting

-
 Ethtool Ethernet Settings.

+
Ethtool Ethernet Settings.

 

         Properties:
         

@@ -1794,7 +1803,7 @@
 

 

 
gsm setting

-
 GSM-based Mobile Broadband Settings.

+
GSM-based Mobile Broadband Settings.

 

         Properties:
         

@@ -1809,7 +1818,7 @@
 

@@ -1817,7 +1826,7 @@
 
@@ -1825,7 +1834,7 @@
 
@@ -1833,7 +1842,7 @@
 
@@ -1841,7 +1850,7 @@
 
@@ -1849,7 +1858,7 @@
 
@@ -1857,7 +1866,10 @@
 
@@ -1867,7 +1879,7 @@
 
@@ -1875,7 +1887,7 @@
 
@@ -1883,7 +1895,7 @@
 
@@ -1891,7 +1903,7 @@
 
@@ -1899,7 +1911,7 @@
 
@@ -1907,7 +1919,7 @@
 
@@ -1917,7 +1929,7 @@
 
@@ -1928,7 +1940,7 @@
 

 
infiniband setting

-
 Infiniband Settings.

+
Infiniband Settings.

 

         Properties:
         

@@ -1943,7 +1955,7 @@
 

@@ -1953,7 +1965,7 @@
 
@@ -1963,7 +1975,7 @@
 
@@ -1973,7 +1985,7 @@
 
@@ -1983,7 +1995,7 @@
 
@@ -1994,7 +2006,7 @@
 

 
ipv4 setting

-
 IPv4 Settings.

+
IPv4 Settings.

 

         Properties:
         

@@ -2009,16 +2021,25 @@
 

+
+
+
+
@@ -2026,12 +2047,12 @@
 
@@ -2039,7 +2060,7 @@
 
@@ -2047,7 +2068,7 @@
 
@@ -2055,9 +2076,9 @@
 
@@ -2065,7 +2086,7 @@
 
@@ -2073,9 +2094,9 @@
 
@@ -2083,7 +2104,7 @@
 
@@ -2091,8 +2112,8 @@
 
@@ -2100,7 +2121,7 @@
 
@@ -2108,7 +2129,8 @@
 
@@ -2116,11 +2138,11 @@
 
@@ -2128,14 +2150,14 @@
 
@@ -2143,9 +2165,9 @@
 
@@ -2155,9 +2177,9 @@
 
@@ -2165,7 +2187,7 @@
 
@@ -2173,7 +2195,7 @@
 
@@ -2181,8 +2203,8 @@
 
@@ -2190,7 +2212,7 @@
 
@@ -2198,11 +2220,11 @@
 
@@ -2210,7 +2232,7 @@
 
@@ -2218,10 +2240,10 @@
 
@@ -2229,7 +2251,7 @@
 
@@ -2237,10 +2259,10 @@
 
@@ -2249,14 +2271,14 @@
 
@@ -2341,19 +2379,28 @@ Example: priority 5 from 192.167.4.0/24 table 45
+
+
+
+
@@ -2361,7 +2408,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2369,9 +2416,9 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2379,7 +2426,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2387,7 +2434,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2395,8 +2442,8 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2404,7 +2451,8 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2412,11 +2460,11 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2424,14 +2472,14 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2439,9 +2487,9 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2451,9 +2499,9 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2461,7 +2509,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2469,7 +2517,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2477,10 +2525,10 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2488,7 +2536,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2496,11 +2544,11 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2508,7 +2556,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2516,7 +2564,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2524,8 +2572,8 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2533,10 +2581,10 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2544,7 +2592,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2552,10 +2600,10 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2564,13 +2612,13 @@ Example: priority 5 from 192.167.4.0/24 table 45
@@ -2634,7 +2682,7 @@ Example: priority 5 from 1:2:3::5/128 table 45

 
ip-tunnel setting

-
 IP Tunneling Settings.

+
IP Tunneling Settings.

 

         Properties:
         

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

@@ -2655,7 +2703,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2663,7 +2711,15 @@ Example: priority 5 from 1:2:3::5/128 table 45
+
+
+
+
@@ -2671,7 +2727,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2681,7 +2737,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2691,7 +2747,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2699,7 +2755,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2707,7 +2763,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2717,7 +2773,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2725,7 +2781,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2735,7 +2791,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2743,7 +2799,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2751,7 +2807,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2762,7 +2818,7 @@ Example: priority 5 from 1:2:3::5/128 table 45

 
macsec setting

-
 MACSec Settings.

+
MACSec Settings.

 

         Properties:
         

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

@@ -2787,7 +2843,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2795,7 +2851,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2805,7 +2861,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2815,7 +2871,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2825,7 +2881,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2835,7 +2891,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2843,7 +2899,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2851,7 +2907,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2862,7 +2918,7 @@ Example: priority 5 from 1:2:3::5/128 table 45

 
macvlan setting

-
 MAC VLAN Settings.

+
MAC VLAN Settings.

 

         Properties:
         

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

@@ -2887,7 +2943,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2895,7 +2951,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2905,7 +2961,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2916,7 +2972,7 @@ Example: priority 5 from 1:2:3::5/128 table 45

 
match setting

-
 Match settings.

+
Match settings.

 

         Properties:
         

@@ -2929,8 +2985,8 @@ Example: priority 5 from 1:2:3::5/128 table 45
 

@@ -2938,8 +2994,8 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2947,8 +3003,8 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2956,11 +3012,11 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2973,7 +3029,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
802-11-olpc-mesh setting

           Alias: olpc-mesh

-
 OLPC Wireless Mesh Settings.

+
OLPC Wireless Mesh Settings.

         Properties:
         

@@ -2988,7 +3044,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -2998,8 +3054,8 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -3009,7 +3065,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -3020,7 +3076,7 @@ Example: priority 5 from 1:2:3::5/128 table 45

 
ovs-bridge setting

-
 OvsBridge Link Settings.

+
OvsBridge Link Settings.

 

         Properties:
         

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

@@ -3041,7 +3097,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -3049,7 +3105,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -3057,7 +3113,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -3065,7 +3121,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
@@ -3076,7 +3132,7 @@ Example: priority 5 from 1:2:3::5/128 table 45

 
ovs-dpdk setting

-
 OvsDpdk Link Settings.

+
OvsDpdk Link Settings.

 

         Properties:
         

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

@@ -3097,7 +3153,23 @@ Example: priority 5 from 1:2:3::5/128 table 45
+
+
+
+
+
+
+
+
@@ -3108,7 +3180,7 @@ Example: priority 5 from 1:2:3::5/128 table 45

 
ovs-interface setting

-
 Open vSwitch Interface Settings.

+
Open vSwitch Interface Settings.

 

         Properties:
         

@@ -3117,20 +3189,30 @@ Example: priority 5 from 1:2:3::5/128 table 45
 

-
+
+
+
+
+
+
-
+
+

 

 

 mac-addressmac-address 
 usual hex-digits-and-colons notation
 MAC address in hex-digits-and-colons notation (e.g. 76:d8:9b:87:66:60:84:ee).
 

 

 
auth-retries

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

+
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

 		
 

             Alias: autoconnect

-
 Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.

-
 Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile.

-
 Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.

-
 If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined.

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

+
Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.

+
Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile.

+
Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.

+
If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined.

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

 

             Format: boolean

 

 
autoconnect-priority

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

+
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

 

 
autoconnect-retries

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

+
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

 

 
autoconnect-slaves

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

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

 

 
dns-over-tls

 
-
 Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.

-
 The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting.

-
 This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

+
Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.

+
The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting.

+
This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

 

             Format: int32

 

 
gateway-ping-timeout

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

+
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

 		
 

             Alias: con-name

-
 A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".

+
A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".

 

             Format: string

 		
 

             Alias: ifname

-
 The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings).

-
 For software devices this specifies the name of the created device.

-
 For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.

+
The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings).

+
For software devices this specifies the name of the created device.

+
For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.

 

             Format: string

 

 
lldp

 
-
 Whether LLDP is enabled for the connection.

+
Whether LLDP is enabled for the connection.

 

             Format: int32

 

 
llmnr

 
-
 Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.

-
 The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").

-
 This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

+
Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.

+
The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").

+
This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

 

             Format: int32

 		
 

             Alias: master

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

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

 

             Format: string

 

 
mdns

 
-
 Whether mDNS is enabled for the connection.

-
 The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").

-
 This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

+
Whether mDNS is enabled for the connection.

+
The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").

+
This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

 

             Format: int32

 

 
metered

 
-
 Whether the connection is metered.

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

+
Whether the connection is metered.

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

 

             Format: NMMetered (int32)

 

 
mptcp-flags

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

 

             Format: uint32

 

 
mud-url

 
-
 If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://".

-
 The special value "none" is allowed to indicate that no MUD URL is used.

-
 If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".

+
If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://".

+
The special value "none" is allowed to indicate that no MUD URL is used.

+
If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".

 

             Format: string

 

 
multi-connect

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

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

 

             Format: int32

 

 
permissions

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

+
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

 

 
read-only

 
-
 FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.

+
FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.

 

             Format: boolean

 

 
secondaries

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

+
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

 		
 

             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.

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

 

             Format: string

 

 
stable-id

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

-
 Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.

-
 The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.

-
 If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.

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

+
Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.

+
The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.

+
If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.

 

             Format: string

 

 
timestamp

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

+
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

 		
 

             Alias: type

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

+
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

 

 
uuid

 
-
 A universally unique identifier for the connection, for example generated with libuuid.  It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network.  For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes.

-
 The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").

+
A universally unique identifier for the connection, for example generated with libuuid.  It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network.  For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes.

+
The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").

 

-            Format: string

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

 		
 

 

 
wait-activation-delay

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

+
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

 

 
wait-device-timeout

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

+
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

 

 
zone

 
-
 The trust level of a the connection.  Free form case-insensitive string (for example "Home", "Work", "Public").  NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall.

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

+
The trust level of a the connection.  Free form case-insensitive string (for example "Home", "Work", "Public").  NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall.

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

 

             Format: string

 		
 
 

             Alias: dev

-
 If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.

+
If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.

 

             Format: string

 		
 

 
altsubject-matches

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

+
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

 

 
anonymous-identity

 
-
 Anonymous identity string for EAP authentication methods.  Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.

+
Anonymous identity string for EAP authentication methods.  Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.

 

             Format: string

 

 
auth-timeout

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

+
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

 

 
ca-cert

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

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

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

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

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

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

 

             Format: byte array

 

 
ca-cert-password

 
-
 The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.

+
The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.

 

             Format: string

 

 
ca-cert-password-flags

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

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

 

             Format: NMSettingSecretFlags (uint32)

 

 
ca-path

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

+
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 "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

 

 
client-cert

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

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

+
Contains the 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

 

 
client-cert-password

 
-
 The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.

+
The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.

 

             Format: string

 

 
client-cert-password-flags

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

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

 

             Format: NMSettingSecretFlags (uint32)

 

 
domain-match

 
-
 Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.

+
Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.

 

             Format: string

 

 
domain-suffix-match

 
-
 Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.

+
Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.

 

             Format: string

 

 
eap

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

+
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

 

 
identity

 
-
 Identity string for EAP authentication methods.  Often the user's user or login name.

+
Identity string for EAP authentication methods.  Often the user's user or login name.

 

             Format: string

 

 
optional

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

+
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

 

 
pac-file

 
-
 UTF-8 encoded file path containing PAC for EAP-FAST.

+
UTF-8 encoded file path containing PAC for EAP-FAST.

 

             Format: string

 

 
password

 
-
 UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.

+
UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.

 

             Format: string

 

 
password-flags

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

+
Flags indicating how to handle the "password" property.

 

             Format: NMSettingSecretFlags (uint32)

 

 
password-raw

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

+
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

 

 
password-raw-flags

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

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

 

             Format: NMSettingSecretFlags (uint32)

 

 
phase1-auth-flags

 
-
 Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly 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 settings. See the wpa_supplicant documentation for more details.

+
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

 

 
phase1-fast-provisioning

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

+
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

 

 
phase1-peaplabel

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

+
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

 

 
phase1-peapver

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

+
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

 

 
phase2-altsubject-matches

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

+
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

 

 
phase2-auth

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

+
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

 

 
phase2-autheap

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

+
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

 

 
phase2-ca-cert

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

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

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

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

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

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

 

             Format: byte array

 

 
phase2-ca-cert-password

 
-
 The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.

+
The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.

 

             Format: string

 

 
phase2-ca-cert-password-flags

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

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

 

             Format: NMSettingSecretFlags (uint32)

 

 
phase2-ca-path

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

+
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

 

 
phase2-client-cert

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

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

+
Contains the "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

 

 
phase2-client-cert-password

 
-
 The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.

+
The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.

 

             Format: string

 

 
phase2-client-cert-password-flags

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

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

 

             Format: NMSettingSecretFlags (uint32)

 

 
phase2-domain-match

 
-
 Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.

+
Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.

 

             Format: string

 

 
phase2-domain-suffix-match

 
-
 Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.

+
Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.

 

             Format: string

 

 
phase2-private-key

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

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

+
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

 

 
phase2-private-key-password

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

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

 

             Format: string

 

 
phase2-private-key-password-flags

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

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

 

             Format: NMSettingSecretFlags (uint32)

 

 
phase2-subject-match

 
-
 Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed.  This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match.

+
Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.

+

+            This property is deprecated since version 1.2.
+            Use "phase2-domain-suffix-match" instead.

 

             Format: string

 

 
pin

 
-
 PIN used for EAP authentication methods.

+
PIN used for EAP authentication methods.

 

             Format: string

 

 
pin-flags

 
-
 Flags indicating how to handle the "pin" property.

+
Flags indicating how to handle the "pin" property.

 

             Format: NMSettingSecretFlags (uint32)

 

 
private-key

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

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

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

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

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

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

 

             Format: byte array

 

 
private-key-password

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

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

 

             Format: string

 

 
private-key-password-flags

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

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

 

             Format: NMSettingSecretFlags (uint32)

 

 
subject-match

 
-
 Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed.  This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match.

+
Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.

+

+            This property is deprecated since version 1.2.
+            Use "phase2-domain-suffix-match" instead.

 

             Format: string

 

 
system-ca-certs

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

+
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

 		
 
 

             Alias: encapsulation

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

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

 

             Format: string

 		
 

             Alias: password

-
 Password used to authenticate with the ADSL service.

+
Password used to authenticate with the ADSL service.

 

             Format: string

 

 
password-flags

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

+
Flags indicating how to handle the "password" property.

 

             Format: NMSettingSecretFlags (uint32)

 		
 

             Alias: protocol

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

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

 

             Format: string

 		
 

             Alias: username

-
 Username used to authenticate with the ADSL service.

+
Username used to authenticate with the ADSL service.

 

             Format: string

 

 
vci

 
-
 VCI of ADSL connection

+
VCI of ADSL connection

 

             Format: uint32

 

 
vpi

 
-
 VPI of ADSL connection

+
VPI of ADSL connection

 

             Format: uint32

 		
 
 

             Alias: addr

-
 The Bluetooth address of the device.

+
The Bluetooth address of the device.

 

             Format: byte array

 		
 

             Alias: bt-type

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

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

 

             Format: string

 		
 

 
options

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

+
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

 		
 
 

             Alias: ageing-time

-
 The Ethernet MAC address aging time, in seconds.

+
The Ethernet MAC address aging time, in seconds.

 

             Format: uint32

 		
 

             Alias: forward-delay

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

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

 

             Format: uint32

 

 
group-address

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

+
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

 		
 

             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.

+
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

 		
 

             Alias: hello-time

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

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

 

             Format: uint32

 		
 

             Alias: mac

-
 If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set.

-
 If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1

+
If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set.

+
If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge.

+

+            This property is deprecated since version 1.12.
+            Use the "cloned-mac-address" property instead.

 

             Format: byte array

 		
 

             Alias: max-age

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

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

 

             Format: uint32

 

 
multicast-hash-max

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

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

 

             Format: uint32

 

 
multicast-last-member-count

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

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

 

             Format: uint32

 

 
multicast-last-member-interval

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

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

 

             Format: uint64

 

 
multicast-membership-interval

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

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

 

             Format: uint64

 

 
multicast-querier

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

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

 

             Format: boolean

 

 
multicast-querier-interval

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

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

 

             Format: uint64

 

 
multicast-query-interval

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

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

 

             Format: uint64

 

 
multicast-query-response-interval

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

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

 

             Format: uint64

 

 
multicast-query-use-ifaddr

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

+
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

 

 
multicast-router

 
-
 Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work.

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

+
Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work.

+
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

 		
 

             Alias: multicast-snooping

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

+
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

 

 
multicast-startup-query-count

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

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

 

             Format: uint32

 

 
multicast-startup-query-interval

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

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

 

             Format: uint64

 		
 

             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.

+
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

 		
 

             Alias: stp

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

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

 

             Format: boolean

 

 
vlan-default-pvid

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

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

 

             Format: uint32

 

 
vlan-filtering

 
-
 Control whether VLAN filtering is enabled on the bridge.

+
Control whether VLAN filtering is enabled on the bridge.

 

             Format: boolean

 

 
vlan-protocol

 
-
 If specified, the protocol used for VLAN filtering.

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

+
If specified, the protocol used for VLAN filtering.

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

 

             Format: string

 

 
vlan-stats-enabled

 
-
 Controls whether per-VLAN stats accounting is enabled.

+
Controls whether per-VLAN stats accounting is enabled.

 

             Format: boolean

 

 
vlans

 
-
 Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured  by the bridge.vlan-default-pvid property.

-
 In nmcli the VLAN list can be specified with the following syntax:

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

+
Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured  by the bridge.vlan-default-pvid property.

+
In nmcli the VLAN list can be specified with the following syntax:

+
$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

 		
 
 

             Alias: hairpin

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

+
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

 		
 

             Alias: path-cost

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

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

 

             Format: uint32

 		
 

             Alias: priority

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

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

 

             Format: uint32

 

 
vlans

 
-
 Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property.

-
 In nmcli the VLAN list can be specified with the following syntax:

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

+
Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property.

+
In nmcli the VLAN list can be specified with the following syntax:

+
$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

 		
 

 
mtu

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

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

 

             Format: uint32

 

 
number

 
-
 The number to dial to establish the connection to the CDMA-based mobile broadband network, if any.  If not specified, the default number (#777) is used when required.

+
The number to dial to establish the connection to the CDMA-based mobile broadband network, if any.  If not specified, the default number (#777) is used when required.

 

             Format: string

 		
 

             Alias: password

-
 The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.

+
The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.

 

             Format: string

 

 
password-flags

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

+
Flags indicating how to handle the "password" property.

 

             Format: NMSettingSecretFlags (uint32)

 		
 

             Alias: user

-
 The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.

+
The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.

 

             Format: string

 		
 

 
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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

 

             Format: NMSettingDcbFlags (uint32)

 

 
app-fcoe-mode

 
-
 The FCoE controller mode; either "fabric" or "vn2vn".

-
 Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".

+
The FCoE controller mode; either "fabric" or "vn2vn".

+
Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".

 

             Format: string

 

 
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 NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.

 

             Format: int32

 

 
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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

 

             Format: NMSettingDcbFlags (uint32)

 

 
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 NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.

 

             Format: int32

 

 
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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

 

             Format: NMSettingDcbFlags (uint32)

 

 
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 NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.

 

             Format: int32

 

 
priority-bandwidth

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

+
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

 

 
priority-flow-control

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

+
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

 

 
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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

 

             Format: NMSettingDcbFlags (uint32)

 

 
priority-group-bandwidth

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

+
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

 

 
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 NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

 

             Format: NMSettingDcbFlags (uint32)

 

 
priority-group-id

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

+
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

 

 
priority-strict-bandwidth

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

+
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

 

 
priority-traffic-class

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

+
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

 		
 
 

             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.

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

 

             Format: string

 

 
auto-config

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

+
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

 

 
device-id

 
-
 The device unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will only apply to the specified device.

+
The device unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will only apply to the specified device.

 

             Format: string

 

 
home-only

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

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

 

             Format: boolean

 

 
mtu

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

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

 

             Format: uint32

 

 
network-id

 
-
 The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration.  If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.

+
The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration.  If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.

 

             Format: string

 

 
number

 
-
 Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1

+
Legacy setting that used to help establishing PPP data sessions for GSM-based modems.

+

+            This property is deprecated since version 1.16.
+            User-provided values for this setting are no longer used.

 

             Format: string

 		
 

             Alias: password

-
 The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.

+
The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.

 

             Format: string

 

 
password-flags

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

+
Flags indicating how to handle the "password" property.

 

             Format: NMSettingSecretFlags (uint32)

 

 
pin

 
-
 If the SIM is locked with a PIN it must be unlocked before any other operations are requested.  Specify the PIN here to allow operation of the device.

+
If the SIM is locked with a PIN it must be unlocked before any other operations are requested.  Specify the PIN here to allow operation of the device.

 

             Format: string

 

 
pin-flags

 
-
 Flags indicating how to handle the "pin" property.

+
Flags indicating how to handle the "pin" property.

 

             Format: NMSettingSecretFlags (uint32)

 

 
sim-id

 
-
 The SIM card unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.

+
The SIM card unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.

 

             Format: string

 

 
sim-operator-id

 
-
 A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.

+
A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.

 

             Format: string

 		
 

             Alias: user

-
 The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.

+
The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.

 

             Format: string

 		
 
 

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

+
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

 		
 

             Alias: mtu

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

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

 

             Format: uint32

 		
 

             Alias: p-key

-
 The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.

+
The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.

 

             Format: int32

 		
 

             Alias: parent

-
 The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".

+
The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".

 

             Format: string

 		
 

             Alias: transport-mode

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

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

 

             Format: string

 		
 
 

             Alias: ip4

-
 Array of IP addresses.

+
Array of IP addresses.

 

             Format: a comma separated list of addresses

 		
 

 
auto-route-ext-gw

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

+

 
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.

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

 

             Format: int32

 

 
dhcp-client-id

 
-
 A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.

-
 The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links.

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

+
A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.

+
The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links.

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

 

             Format: string

 

 
dhcp-fqdn

 
-
 If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.

+
If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.

 

             Format: string

 

 
dhcp-hostname

 
-
 If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.

+
If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.

 

             Format: string

 

 
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.

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

 

             Format: uint32

 

 
dhcp-iaid

 
-
 A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.

+
A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.

 

             Format: string

 

 
dhcp-reject-servers

 
-
 Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.

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

+
Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.

+
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

 

 
dhcp-send-hostname

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

+
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

 

 
dhcp-timeout

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

-
 Set to 2147483647 (MAXINT32) for infinity.

+
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

 

 
dhcp-vendor-class-identifier

 
-
 The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.

+
The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.

 

             Format: string

 

 
dns

 
-
 Array of IP addresses of DNS servers.

+
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

 

 
dns-options

 
-
 Array of DNS options as described in man 5 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-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".

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

+
Array of DNS options as described in man 5 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-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".

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

 

             Format: array of string

 

 
dns-priority

 
-
 DNS servers priority.

-
 The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).

-
 Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.

-
 Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.

-
 Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.

-
 When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.

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

+
DNS servers priority.

+
The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).

+
Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.

+
Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.

+
Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.

+
When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.

+
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

 

 
dns-search

 
-
 List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.

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

+
List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.

+
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

 		
 

             Alias: gw4

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

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

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

+
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

 

 
ignore-auto-dns

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

+
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

 

 
ignore-auto-routes

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

+
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

 

 
link-local

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

+
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

 

 
may-fail

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

+
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

 

 
method

 
-
 IP configuration method.

-
 NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.

-
 In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.

-
 For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.

-
 For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.

+
IP configuration method.

+
NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.

+
In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.

+
For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.

+
For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.

 

             Format: string

 

 
never-default

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

+
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

 

 
required-timeout

 
-
 The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.

-
 This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.

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

+
The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.

+
This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.

+
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

 

 
route-metric

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

+
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

 

 
route-table

 
-
 Enable policy routing (source routing) and set the routing table used when adding routes.

-
 This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.

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

+
Enable policy routing (source routing) and set the routing table used when adding routes.

+
This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.

+
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

 
routes

 
 

-A list of IPv4 destination addresses, prefix length, optional IPv4
-next hop addresses, optional route metric, optional attribute. The valid syntax is:
-"ip[/prefix] [next-hop] [metric] [attribute=val]...[,ip[/prefix]...]".
-For example "192.0.2.0/24 10.1.1.1 77, 198.51.100.0/24".
+  A list of IPv4 destination addresses, prefix length, optional IPv4
+  next hop addresses, optional route metric, optional attribute. The valid syntax is:
+  "ip[/prefix] [next-hop] [metric] [attribute=val]...[,ip[/prefix]...]".
+  For example "192.0.2.0/24 10.1.1.1 77, 198.51.100.0/24".
 

 

-Various attributes are supported:
-

+  Various attributes are supported:
+  

 
    
 
  • "advmss" - an unsigned 32 bit integer.
    • 
 
  • "cwnd" - an unsigned 32 bit integer.
    • 
@@ -2269,17 +2291,33 @@ Various attributes are supported:
 
  • "lock-mtu" - a boolean value.
    • 
 
  • "lock-window" - a boolean value.
    • 
 
  • "mtu" - an unsigned 32 bit integer.
    • 
-
  • "onlink" - a boolean value.
    • 
+
  • "onlink" - a boolean value. The onlink flag
+       is ignored for IPv4 routes without a gateway. That also means,
+       with a positive "weight" the route cannot merge with ECMP routes
+       which are onlink and have a gateway.
+     
    • 
 
  • "quickack" - a boolean value.
    • 
 
  • "rto_min" - an unsigned 32 bit integer.
-The value is in milliseconds.
    • 
+     The value is in milliseconds.
    
 
  • "scope" - an unsigned 8 bit integer. IPv4 only.
    • 
 
  • "src" - an IPv4 address.
    • 
 
  • "table" - an unsigned 32 bit integer. The default depends on ipv4.route-table.
    • 
 
  • "tos" - an unsigned 8 bit integer. IPv4 only.
    • 
 
  • "type" - one of unicast, local, blackhole,
-unavailable, prohibit, throw.
-The default is unicast.
    • 
+       unavailable, prohibit, throw.
+       The default is unicast.
    
+
  • 
+
    "weight" - an unsigned 32 bit integer
+     ranging from 0 to 256. A non-zero weight indicates that the IPv4
+     route is an ECMP IPv4 route.  NetworkManager will automatically
+     merge compatible ECMP routes into multi-hop routes.  Setting to
+     zero or omitting the attribute configures single hop routes that
+     won't get merged. If the route finds no merge partner, it is
+     configured as single hop route.
    
+
    Note that in
+     NetworkManager, currently all nexthops of a ECMP route must share
+     the same "onlink" flag in order to be mergable.
    
+
    • 
 
  • "window" - an unsigned 32 bit integer.
    • 
 

 

@@ -2313,7 +2351,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
 

 

 
ipv6 setting

-
 IPv6 Settings.

+
IPv6 Settings.

 

         Properties:
         

@@ -2326,12 +2364,12 @@ Example: priority 5 from 192.167.4.0/24 table 45
 

 
addr-gen-mode

 
-
 Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. 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).

-
 If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced.

-
 The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced.

-
 The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively.

-
 For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions.

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

+
Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. 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).

+
If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced.

+
The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced.

+
The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively.

+
For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions.

+
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: int32

 		
 
 

             Alias: ip6

-
 Array of IP addresses.

+
Array of IP addresses.

 

             Format: a comma separated list of addresses

 		
 

 
auto-route-ext-gw

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

+

 
dhcp-duid

 
-
 A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option.

-
 The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id.

-
 The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk.

-
 The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt").

-
 When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.

+
A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option.

+
The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id.

+
The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk.

+
The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt").

+
When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.

 

             Format: string

 		
 

 
dhcp-hostname

 
-
 If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.

+
If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.

 

             Format: string

 		
 

 
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.

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

 

             Format: uint32

 		
 

 
dhcp-iaid

 
-
 A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.

+
A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.

 

             Format: string

 		
 

 
dhcp-send-hostname

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

+
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

 		
 

 
dhcp-timeout

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

-
 Set to 2147483647 (MAXINT32) for infinity.

+
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

 		
 

 
dns

 
-
 Array of IP addresses of DNS servers.

+
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

 		
 

 
dns-options

 
-
 Array of DNS options as described in man 5 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-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".

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

+
Array of DNS options as described in man 5 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-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".

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

 

             Format: array of string

 		
 

 
dns-priority

 
-
 DNS servers priority.

-
 The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).

-
 Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.

-
 Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.

-
 Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.

-
 When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.

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

+
DNS servers priority.

+
The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).

+
Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.

+
Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.

+
Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.

+
When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.

+
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

 		
 

 
dns-search

 
-
 List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.

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

+
List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.

+
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

 		
 
 

             Alias: gw6

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

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

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

+
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

 		
 

 
ignore-auto-dns

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

+
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

 		
 

 
ignore-auto-routes

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

+
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

 		
 

 
ip6-privacy

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

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

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

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

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

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

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

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

 		
 

 
may-fail

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

+
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

 		
 

 
method

 
-
 IP configuration method.

-
 NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.

-
 In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.

-
 For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.

-
 For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.

+
IP configuration method.

+
NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.

+
In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.

+
For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.

+
For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.

 

             Format: string

 		
 

 
mtu

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

+
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

 		
 

 
never-default

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

+
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

 		
 

 
ra-timeout

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

+
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

 		
 

 
required-timeout

 
-
 The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.

-
 This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.

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

+
The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.

+
This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.

+
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

 		
 

 
route-metric

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

+
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

 		
 

 
route-table

 
-
 Enable policy routing (source routing) and set the routing table used when adding routes.

-
 This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.

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

+
Enable policy routing (source routing) and set the routing table used when adding routes.

+
This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.

+
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

 		
 
routes

 
 

-A list of IPv6 destination addresses, prefix length, optional IPv6
-next hop addresses, optional route metric, optional attribute. The valid syntax is:
-"ip[/prefix] [next-hop] [metric] [attribute=val]...[,ip[/prefix]...]".
+  A list of IPv6 destination addresses, prefix length, optional IPv6
+  next hop addresses, optional route metric, optional attribute. The valid syntax is:
+  "ip[/prefix] [next-hop] [metric] [attribute=val]...[,ip[/prefix]...]".
 

 

-Various attributes are supported:
-

+  Various attributes are supported:
+  

 
    
 
  • "advmss" - an unsigned 32 bit integer.
    • 
 
  • "cwnd" - an unsigned 32 bit integer.
    • 
@@ -2587,12 +2635,12 @@ Various attributes are supported:
 
  • "onlink" - a boolean value.
    • 
 
  • "quickack" - a boolean value.
    • 
 
  • "rto_min" - an unsigned 32 bit integer.
-The value is in milliseconds.
    • 
+     The value is in milliseconds.
    
 
  • "src" - an IPv6 address.
    • 
 
  • "table" - an unsigned 32 bit integer. The default depends on ipv6.route-table.
    • 
 
  • "type" - one of unicast, local, blackhole,
-unavailable, prohibit, throw.
-The default is unicast.
    • 
+       unavailable, prohibit, throw.
+       The default is unicast.
    
 
  • "window" - an unsigned 32 bit integer.
    • 
 

 

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

 
token

 
-
 Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.

+
Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.

 

             Format: string

 		
 
 

 
encapsulation-limit

 
-
 How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.

+
How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.

 

             Format: uint32

 		
 

 
flags

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

 

             Format: uint32

 		
 

 
flow-label

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

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

+

+            Format: uint32

+
fwmark

+
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

 		
 

 
input-key

 
-
 The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.

+
The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.

 

             Format: string

 		
 
 

             Alias: local

-
 The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.

+
The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.

 

             Format: string

 		
 
 

             Alias: mode

-
 The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).

+
The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).

 

             Format: uint32

 		
 

 
mtu

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

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

 

             Format: uint32

 		
 

 
output-key

 
-
 The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.

+
The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.

 

             Format: string

 		
 
 

             Alias: dev

-
 If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface.

+
If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface.

 

             Format: string

 		
 

 
path-mtu-discovery

 
-
 Whether to enable Path MTU Discovery on this tunnel.

+
Whether to enable Path MTU Discovery on this tunnel.

 

             Format: boolean

 		
 
 

             Alias: remote

-
 The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.

+
The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.

 

             Format: string

 		
 

 
tos

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

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

 

             Format: uint32

 		
 

 
ttl

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

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

 

             Format: uint32

 		
 
 
 

             Alias: encrypt

-
 Whether the transmitted traffic must be encrypted.

+
Whether the transmitted traffic must be encrypted.

 

             Format: boolean

 		
 
 

             Alias: cak

-
 The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.

+
The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.

 

             Format: string

 		
 

 
mka-cak-flags

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

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

 

             Format: NMSettingSecretFlags (uint32)

 		
 
 

             Alias: ckn

-
 The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Must be a string of hexadecimal characters with a even length between 2 and 64.

+
The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Must be a string of hexadecimal characters with a even length between 2 and 64.

 

             Format: string

 		
 
 

             Alias: mode

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

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

 

             Format: int32

 		
 
 

             Alias: dev

-
 If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.

+
If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.

 

             Format: string

 		
 
 

             Alias: port

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

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

 

             Format: int32

 		
 

 
send-sci

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

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

 

             Format: boolean

 		
 

 
validation

 
-
 Specifies the validation mode for incoming frames.

+
Specifies the validation mode for incoming frames.

 

             Format: int32

 		
 
 
 

             Alias: mode

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

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

 

             Format: uint32

 		
 
 

             Alias: dev

-
 If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.

+
If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.

 

             Format: string

 		
 

 
promiscuous

 
-
 Whether the interface should be put in promiscuous mode.

+
Whether the interface should be put in promiscuous mode.

 

             Format: boolean

 		
 
 

             Alias: tap

-
 Whether the interface should be a MACVTAP.

+
Whether the interface should be a MACVTAP.

 

             Format: boolean

 		
 
 

 
driver

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

+
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

 		
 

 
interface-name

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

+
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

 		
 

 
kernel-command-line

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

+
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

 		
 

 
path

 
-
 A list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier.

-
 For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0".

-
 The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev").

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

+
A list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier.

+
For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0".

+
The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev").

+
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

 		
 
 
 
 
 

             Alias: channel

-
 Channel on which the mesh network to join is located.

+
Channel on which the mesh network to join is located.

 

             Format: uint32

 		
 
 

             Alias: dhcp-anycast

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

+
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

 		
 
 

             Alias: ssid

-
 SSID of the mesh network to join.

+
SSID of the mesh network to join.

 

             Format: byte array

 		
 
 

 
datapath-type

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

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

 

             Format: string

 		
 

 
fail-mode

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

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

 

             Format: string

 		
 

 
mcast-snooping-enable

 
-
 Enable or disable multicast snooping.

+
Enable or disable multicast snooping.

 

             Format: boolean

 		
 

 
rstp-enable

 
-
 Enable or disable RSTP.

+
Enable or disable RSTP.

 

             Format: boolean

 		
 

 
stp-enable

 
-
 Enable or disable STP.

+
Enable or disable STP.

 

             Format: boolean

 		
 
 

 
devargs

 
-
 Open vSwitch DPDK device arguments.

+
Open vSwitch DPDK device arguments.

 

             Format: string

 		
 

 
n-rxq

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

+
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

+
n-rxq-desc

+
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

+
n-txq-desc

+
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

 		
 
 

 
 
ofport-request

+
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

+

 
type

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

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

 

             Format: string

 

 

 

 

 

 
ovs-patch setting

-
 OvsPatch Link Settings.

+
OvsPatch Link Settings.

 

         Properties:
         

@@ -3142,7 +3224,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
peer

 
-
 Specifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer.

+
Specifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer.

 

             Format: string

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

 

 
ovs-port setting

-
 OvsPort Link Settings.

+
OvsPort Link Settings.

 

         Properties:
         

@@ -3165,7 +3247,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
bond-downdelay

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

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

 

             Format: uint32

 
@@ -3173,7 +3255,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
bond-mode

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

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

 

             Format: string

 
@@ -3181,7 +3263,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
bond-updelay

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

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

 

             Format: uint32

 
@@ -3189,7 +3271,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
lacp

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

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

 

             Format: string

 
@@ -3197,15 +3279,24 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
tag

 
-
 The VLAN tag in the range 0-4095.

+
The VLAN tag in the range 0-4095.

 

             Format: uint32

 
 
 
+
trunks

+
+
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

+
+
+
 
vlan-mode

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

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

 

             Format: string

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

 

 
ppp setting

-
 Point-to-Point Protocol Settings.

+
Point-to-Point Protocol Settings.

 

         Properties:
         

@@ -3229,7 +3320,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
baud

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

+
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

 
@@ -3237,7 +3328,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
crtscts

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

+
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

 
@@ -3245,7 +3336,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
lcp-echo-failure

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

+
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

 
@@ -3253,7 +3344,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
lcp-echo-interval

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

+
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

 
@@ -3261,7 +3352,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
mppe-stateful

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

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

 

             Format: boolean

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

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

+
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

 
@@ -3277,7 +3368,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
mtu

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

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

 

             Format: uint32

 
@@ -3285,7 +3376,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
no-vj-comp

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

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

 

             Format: boolean

 
@@ -3293,7 +3384,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
noauth

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

+
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

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

 
-
 If TRUE, BSD compression will not be requested.

+
If TRUE, BSD compression will not be requested.

 

             Format: boolean

 
@@ -3309,7 +3400,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
nodeflate

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

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

 

             Format: boolean

 
@@ -3317,7 +3408,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
refuse-chap

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

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

 

             Format: boolean

 
@@ -3325,7 +3416,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
refuse-eap

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

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

 

             Format: boolean

 
@@ -3333,7 +3424,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
refuse-mschap

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

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

 

             Format: boolean

 
@@ -3341,7 +3432,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
refuse-mschapv2

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

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

 

             Format: boolean

 
@@ -3349,7 +3440,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
refuse-pap

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

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

 

             Format: boolean

 
@@ -3357,7 +3448,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
require-mppe

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

+
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

 
@@ -3365,7 +3456,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
require-mppe-128

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

+
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

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

 

 
pppoe setting

-
 PPP-over-Ethernet Settings.

+
PPP-over-Ethernet Settings.

 

         Properties:
         

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

             Alias: parent

-
 If given, specifies the parent interface name on which this PPPoE connection should be created.  If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection.

+
If given, specifies the parent interface name on which this PPPoE connection should be created.  If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection.

 

             Format: string

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

             Alias: password

-
 Password used to authenticate with the PPPoE service.

+
Password used to authenticate with the PPPoE service.

 

             Format: string

 
@@ -3409,7 +3500,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
password-flags

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

+
Flags indicating how to handle the "password" property.

 

             Format: NMSettingSecretFlags (uint32)

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

             Alias: service

-
 If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service.  For most providers, this should be left blank.  It is only required if there are multiple access concentrators or a specific service is known to be required.

+
If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service.  For most providers, this should be left blank.  It is only required if there are multiple access concentrators or a specific service is known to be required.

 

             Format: string

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

             Alias: username

-
 Username used to authenticate with the PPPoE service.

+
Username used to authenticate with the PPPoE service.

 

             Format: string

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

 

 
proxy setting

-
 WWW Proxy Settings.

+
WWW Proxy Settings.

 

         Properties:
         

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

             Alias: browser-only

-
 Whether the proxy configuration is for browser only.

+
Whether the proxy configuration is for browser only.

 

             Format: boolean

 
@@ -3465,7 +3556,7 @@ 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 NM_SETTING_PROXY_METHOD_NONE (0)

 

             Format: int32

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

             Alias: pac-script

-
 PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.

+
PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.

 

             Format: string

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

             Alias: pac-url

-
 PAC URL for obtaining PAC file.

+
PAC URL for obtaining PAC file.

 

             Format: string

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

 

 
serial setting

-
 Serial Link Settings.

+
Serial Link Settings.

 

         Properties:
         

@@ -3509,7 +3600,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
baud

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

+
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

 
@@ -3517,7 +3608,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
bits

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

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

 

             Format: uint32

 
@@ -3525,7 +3616,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
parity

 
-
 Parity setting of the serial port.

+
Parity setting of the serial port.

 

             Format: NMSettingSerialParity (byte)

 
@@ -3533,7 +3624,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
send-delay

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

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

 

             Format: uint64

 
@@ -3541,7 +3632,7 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
stopbits

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

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

 

             Format: uint32

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

 

 
sriov setting

-
 SR-IOV settings.

+
SR-IOV settings.

 

         Properties:
         

@@ -3565,10 +3656,10 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
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).

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

 

             Format: NMTernary (int32)

 
@@ -3576,8 +3667,8 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
total-vfs

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

+
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

 
@@ -3585,16 +3676,16 @@ Example: priority 5 from 1:2:3::5/128 table 45
 
 
vfs

 
-
 Array of virtual function descriptors.

-
 Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF.

-
 When represented as string a VF is in the form:

-
 "INDEX [ATTR=VALUE[ ATTR=VALUE]...]".

-
 for example:

-
 "2 mac=00:11:22:33:44:55 spoof-check=true".

-
 Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans.

-
 The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form

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

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

+
Array of virtual function descriptors.

+
Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF.

+
When represented as string a VF is in the form:

+
"INDEX [ATTR=VALUE[ ATTR=VALUE]...]".

+
for example:

+
"2 mac=00:11:22:33:44:55 spoof-check=true".

+
Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans.

+
The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form

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

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

 

             Format: array of vardict

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

 

 
tc setting

-
 Linux Traffic Control Settings.

+
Linux Traffic Control Settings.

 

         Properties:
         

@@ -3623,7 +3714,7 @@ Array of TC queueing disciplines. qdisc is a basic block in the
 Linux traffic control subsystem
 

 

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

 
@@ -3634,39 +3725,39 @@ Each qdisc can be specified by the following attributes:
 
+        specifies the qdisc handle. A qdisc, which potentially can have children, gets
+        assigned a major number, called a 'handle', leaving the minor number namespace
+        available for classes. The handle is expressed as '10:'. It is customary to
+        explicitly assign a handle to qdiscs expected to have children.
+      

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

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

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

 


 
handle HANDLE

 

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

 

 

 
parent HANDLE

 

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

 

 

 
root

 

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

 

 

 
KIND

 

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

 

 
 

 

-Parameters for 'fq_codel':
+ Parameters for 'fq_codel':
 

 
@@ -3677,76 +3768,76 @@ Parameters for 'fq_codel':
 
+        the hard limit on the real queue size.  When this limit is
+        reached, incoming packets are dropped. Default is 10240 packets.
+      

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

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

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

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

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

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

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

 


 
limit U32

 

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

 

 

 
memory_limit U32

 

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

 

 

 
flows U32

 

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

 

 

 
target U32

 

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

 

 

 
interval U32

 

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

 

 

 
quantum U32

 

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

 

 

 
ecn BOOL

 

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

 

 

 
ce_threshold U32

 

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

 

 
 

 

-Parameters for 'sfq':
+ Parameters for 'sfq':
 

 
@@ -3757,57 +3848,57 @@ Parameters for 'sfq':
 
+   can be used to set a different hash table size, available
+   from kernel 2.6.39 onwards.  The specified divisor must be
+   a power of two and cannot be larger than 65536.
+   Default value: 1024.
+      

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

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

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

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

+   Default value is 127.
+      

 


 
divisor U32

 

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

 

 

 
limit U32

 

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

 

 

 
depth U32

 

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

 

 

 
perturb_period U32

 

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

 

 

 
quantum U32

 

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

 

 

 
flows U32

 

-Default value is 127.
-

 

 
 

 

-Parameters for 'tbf':
+ Parameters for 'tbf':
 

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

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

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

 


 
rate U64

 

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

 

 

 
burst U32

 
 

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

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

 

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

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

 

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

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

 		
 

 

 
limit U32

 

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

 

 

 
latency U32

 

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

 

 
 

@@ -3878,11 +3969,11 @@ the size of the bucket, the rate and possibly the peakrate
 
tfilters

 
 

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

 

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

 
@@ -3893,37 +3984,37 @@ Each tfilters can be specified by the following attributes:
 
+        specifies the tfilters handle. A filter is used by a classful qdisc to determine in which class
+        a packet will be enqueued. It is important to notice that filters reside within qdiscs. Therefore,
+        see qdiscs handle for detailed information.
+      

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

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

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

 


 
handle HANDLE

 

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

 

 

 
parent HANDLE

 

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

 

 

 
root

 

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

 

 

 
KIND

 

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

 

 
 

 

-Actions for 'mirred':
+ Actions for 'mirred':
 

 
@@ -3934,31 +4025,31 @@ Actions for 'mirred':
 
+        Define whether the packet should exit from the interface.
+      

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

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

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

 


 
egress bool

 

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

 

 

 
ingress bool

 

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

 

 

 
mirror bool

 

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

 

 

 
redirect bool

 

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

 

 
 

 

-Action for 'simple':
+ Action for 'simple':
 

 
@@ -3968,8 +4059,8 @@ Action for 'simple':
 
+    The actual string to print.
+      

 


 
sdata char[32]

 

-The actual string to print.
-

 

 

 

@@ -3982,7 +4073,7 @@ The actual string to print.
 

 

 
team setting

-
 Teaming Settings.

+
Teaming Settings.

 

         Properties:
         

@@ -3997,7 +4088,7 @@ The actual string to print.
 
 

             Alias: config

-
 The JSON configuration for the team network interface.  The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used.  See man teamd.conf for the format details.

+
The JSON configuration for the team network interface.  The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used.  See man teamd.conf for the format details.

 

             Format: string

 
@@ -4005,7 +4096,7 @@ The actual string to print.
 
 
link-watchers

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

+
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

 
@@ -4013,7 +4104,7 @@ The actual string to print.
 
 
mcast-rejoin-count

 
-
 Corresponds to the teamd mcast_rejoin.count.

+
Corresponds to the teamd mcast_rejoin.count.

 

             Format: int32

 
@@ -4021,7 +4112,7 @@ The actual string to print.
 
 
mcast-rejoin-interval

 
-
 Corresponds to the teamd mcast_rejoin.interval.

+
Corresponds to the teamd mcast_rejoin.interval.

 

             Format: int32

 
@@ -4029,7 +4120,7 @@ The actual string to print.
 
 
notify-peers-count

 
-
 Corresponds to the teamd notify_peers.count.

+
Corresponds to the teamd notify_peers.count.

 

             Format: int32

 
@@ -4037,7 +4128,7 @@ The actual string to print.
 
 
notify-peers-interval

 
-
 Corresponds to the teamd notify_peers.interval.

+
Corresponds to the teamd notify_peers.interval.

 

             Format: int32

 
@@ -4045,7 +4136,7 @@ The actual string to print.
 
 
runner

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

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

 

             Format: string

 
@@ -4053,7 +4144,7 @@ The actual string to print.
 
 
runner-active

 
-
 Corresponds to the teamd runner.active.

+
Corresponds to the teamd runner.active.

 

             Format: boolean

 
@@ -4061,7 +4152,7 @@ The actual string to print.
 
 
runner-agg-select-policy

 
-
 Corresponds to the teamd runner.agg_select_policy.

+
Corresponds to the teamd runner.agg_select_policy.

 

             Format: string

 
@@ -4069,7 +4160,7 @@ The actual string to print.
 
 
runner-fast-rate

 
-
 Corresponds to the teamd runner.fast_rate.

+
Corresponds to the teamd runner.fast_rate.

 

             Format: boolean

 
@@ -4077,7 +4168,7 @@ The actual string to print.
 
 
runner-hwaddr-policy

 
-
 Corresponds to the teamd runner.hwaddr_policy.

+
Corresponds to the teamd runner.hwaddr_policy.

 

             Format: string

 
@@ -4085,7 +4176,7 @@ The actual string to print.
 
 
runner-min-ports

 
-
 Corresponds to the teamd runner.min_ports.

+
Corresponds to the teamd runner.min_ports.

 

             Format: int32

 
@@ -4093,7 +4184,7 @@ The actual string to print.
 
 
runner-sys-prio

 
-
 Corresponds to the teamd runner.sys_prio.

+
Corresponds to the teamd runner.sys_prio.

 

             Format: int32

 
@@ -4101,7 +4192,7 @@ The actual string to print.
 
 
runner-tx-balancer

 
-
 Corresponds to the teamd runner.tx_balancer.name.

+
Corresponds to the teamd runner.tx_balancer.name.

 

             Format: string

 
@@ -4109,7 +4200,7 @@ The actual string to print.
 
 
runner-tx-balancer-interval

 
-
 Corresponds to the teamd runner.tx_balancer.interval.

+
Corresponds to the teamd runner.tx_balancer.interval.

 

             Format: int32

 
@@ -4117,7 +4208,7 @@ The actual string to print.
 
 
runner-tx-hash

 
-
 Corresponds to the teamd runner.tx_hash.

+
Corresponds to the teamd runner.tx_hash.

 

             Format: array of string

 
@@ -4128,7 +4219,7 @@ The actual string to print.
 

 

 
team-port setting

-
 Team Port Settings.

+
Team Port Settings.

 

         Properties:
         

@@ -4143,7 +4234,7 @@ The actual string to print.
 
 

             Alias: config

-
 The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.

+
The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.

 

             Format: string

 
@@ -4151,7 +4242,7 @@ The actual string to print.
 
 
lacp-key

 
-
 Corresponds to the teamd ports.PORTIFNAME.lacp_key.

+
Corresponds to the teamd ports.PORTIFNAME.lacp_key.

 

             Format: int32

 
@@ -4159,7 +4250,7 @@ The actual string to print.
 
 
lacp-prio

 
-
 Corresponds to the teamd ports.PORTIFNAME.lacp_prio.

+
Corresponds to the teamd ports.PORTIFNAME.lacp_prio.

 

             Format: int32

 
@@ -4167,7 +4258,7 @@ The actual string to print.
 
 
link-watchers

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

+
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

 
@@ -4175,7 +4266,7 @@ The actual string to print.
 
 
prio

 
-
 Corresponds to the teamd ports.PORTIFNAME.prio.

+
Corresponds to the teamd ports.PORTIFNAME.prio.

 

             Format: int32

 
@@ -4183,7 +4274,7 @@ The actual string to print.
 
 
queue-id

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

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

 

             Format: int32

 
@@ -4191,7 +4282,7 @@ The actual string to print.
 
 
sticky

 
-
 Corresponds to the teamd ports.PORTIFNAME.sticky.

+
Corresponds to the teamd ports.PORTIFNAME.sticky.

 

             Format: boolean

 
@@ -4202,7 +4293,7 @@ The actual string to print.
 

 

 
tun setting

-
 Tunnel Settings.

+
Tunnel Settings.

 

         Properties:
         

@@ -4217,7 +4308,7 @@ The actual string to print.
 
 

             Alias: group

-
 The group ID which will own the device. If set to NULL everyone will be able to use the device.

+
The group ID which will own the device. If set to NULL everyone will be able to use the device.

 

             Format: string

 
@@ -4227,7 +4318,7 @@ The actual string to print.
 
 

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

 

             Format: uint32

 
@@ -4237,7 +4328,7 @@ The actual string to print.
 
 

             Alias: multi-queue

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

+
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

 
@@ -4247,7 +4338,7 @@ The actual string to print.
 
 

             Alias: owner

-
 The user ID which will own the device. If set to NULL everyone will be able to use the device.

+
The user ID which will own the device. If set to NULL everyone will be able to use the device.

 

             Format: string

 
@@ -4257,7 +4348,7 @@ The actual string to print.
 
 

             Alias: pi

-
 If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.

+
If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.

 

             Format: boolean

 
@@ -4267,7 +4358,7 @@ The actual string to print.
 
 

             Alias: vnet-hdr

-
 If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.

+
If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.

 

             Format: boolean

 
@@ -4278,7 +4369,7 @@ The actual string to print.
 

 

 
vlan setting

-
 VLAN Settings.

+
VLAN Settings.

 

         Properties:
         

@@ -4293,7 +4384,7 @@ The actual string to print.
 
 

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

+
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

 
@@ -4303,8 +4394,8 @@ The actual string to print.
 
 

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

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

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

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

 
@@ -4314,7 +4405,7 @@ The actual string to print.
 
 

             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.

+
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

 
@@ -4324,7 +4415,7 @@ The actual string to print.
 
 

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

+
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

 
@@ -4334,7 +4425,16 @@ The actual string to print.
 
 

             Alias: dev

-
 If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.

+
If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.

+

+            Format: string

+
+
+
+
protocol

+
+
Specifies the VLAN protocol to use for encapsulation.

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

 

             Format: string

 
@@ -4345,7 +4445,7 @@ The actual string to print.
 

 

 
vpn setting

-
 VPN Settings.

+
VPN Settings.

 

         Properties:
         

@@ -4358,7 +4458,7 @@ The actual string to print.
 
 
data

 
-
 Dictionary of key/value pairs of VPN plugin specific data.  Both keys and values must be strings.

+
Dictionary of key/value pairs of VPN plugin specific data.  Both keys and values must be strings.

 

             Format: dict of string to string

 
@@ -4366,7 +4466,7 @@ The actual string to print.
 
 
persistent

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

+
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

 
@@ -4374,7 +4474,7 @@ The actual string to print.
 
 
secrets

 
-
 Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys.  Both keys and values must be strings.

+
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

 
@@ -4384,7 +4484,7 @@ The actual string to print.
 
 

             Alias: vpn-type

-
 D-Bus service name of the VPN plugin that this setting uses to connect to its network.  i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.

+
D-Bus service name of the VPN plugin that this setting uses to connect to its network.  i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.

 

             Format: string

 
@@ -4392,7 +4492,7 @@ The actual string to print.
 
 
timeout

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

+
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

 
@@ -4402,7 +4502,7 @@ The actual string to print.
 
 

             Alias: user

-
 If the VPN connection requires a user name for authentication, that name should be provided here.  If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty.  If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.

+
If the VPN connection requires a user name for authentication, that name should be provided here.  If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty.  If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.

 

             Format: string

 
@@ -4413,7 +4513,7 @@ The actual string to print.
 

 

 
vrf setting

-
 VRF settings.

+
VRF settings.

 

         Properties:
         

@@ -4427,7 +4527,7 @@ The actual string to print.
 
 

             Alias: table

-
 The routing table for this VRF.

+
The routing table for this VRF.

 

             Format: uint32

 
@@ -4437,7 +4537,7 @@ The actual string to print.
 

 

 
vxlan setting

-
 VXLAN Settings.

+
VXLAN Settings.

 

         Properties:
         

@@ -4450,7 +4550,7 @@ The actual string to print.
 
 
ageing

 
-
 Specifies the lifetime in seconds of FDB entries learnt by the kernel.

+
Specifies the lifetime in seconds of FDB entries learnt by the kernel.

 

             Format: uint32

 
@@ -4460,7 +4560,7 @@ The actual string to print.
 
 

             Alias: destination-port

-
 Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.

+
Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.

 

             Format: uint32

 
@@ -4470,7 +4570,7 @@ The actual string to print.
 
 

             Alias: id

-
 Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.

+
Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.

 

             Format: uint32

 
@@ -4478,7 +4578,7 @@ The actual string to print.
 
 
l2-miss

 
-
 Specifies whether netlink LL ADDR miss notifications are generated.

+
Specifies whether netlink LL ADDR miss notifications are generated.

 

             Format: boolean

 
@@ -4486,7 +4586,7 @@ The actual string to print.
 
 
l3-miss

 
-
 Specifies whether netlink IP ADDR miss notifications are generated.

+
Specifies whether netlink IP ADDR miss notifications are generated.

 

             Format: boolean

 
@@ -4494,7 +4594,7 @@ The actual string to print.
 
 
learning

 
-
 Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.

+
Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.

 

             Format: boolean

 
@@ -4502,7 +4602,7 @@ The actual string to print.
 
 
limit

 
-
 Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.

+
Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.

 

             Format: uint32

 
@@ -4512,7 +4612,7 @@ The actual string to print.
 
 

             Alias: local

-
 If given, specifies the source IP address to use in outgoing packets.

+
If given, specifies the source IP address to use in outgoing packets.

 

             Format: string

 
@@ -4522,7 +4622,7 @@ The actual string to print.
 
 

             Alias: dev

-
 If given, specifies the parent interface name or parent connection UUID.

+
If given, specifies the parent interface name or parent connection UUID.

 

             Format: string

 
@@ -4530,7 +4630,7 @@ The actual string to print.
 
 
proxy

 
-
 Specifies whether ARP proxy is turned on.

+
Specifies whether ARP proxy is turned on.

 

             Format: boolean

 
@@ -4540,7 +4640,7 @@ The actual string to print.
 
 

             Alias: remote

-
 Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.

+
Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.

 

             Format: string

 
@@ -4548,7 +4648,7 @@ The actual string to print.
 
 
rsc

 
-
 Specifies whether route short circuit is turned on.

+
Specifies whether route short circuit is turned on.

 

             Format: boolean

 
@@ -4558,7 +4658,7 @@ The actual string to print.
 
 

             Alias: source-port-max

-
 Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.

+
Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.

 

             Format: uint32

 
@@ -4568,7 +4668,7 @@ The actual string to print.
 
 

             Alias: source-port-min

-
 Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.

+
Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.

 

             Format: uint32

 
@@ -4576,7 +4676,7 @@ The actual string to print.
 
 
tos

 
-
 Specifies the TOS value to use in outgoing packets.

+
Specifies the TOS value to use in outgoing packets.

 

             Format: uint32

 
@@ -4584,7 +4684,7 @@ The actual string to print.
 
 
ttl

 
-
 Specifies the time-to-live value to use in outgoing packets.

+
Specifies the time-to-live value to use in outgoing packets.

 

             Format: uint32

 
@@ -4595,7 +4695,7 @@ The actual string to print.
 

 

 
wifi-p2p setting

-
 Wi-Fi P2P Settings.

+
Wi-Fi P2P Settings.

 

         Properties:
         

@@ -4610,7 +4710,7 @@ The actual string to print.
 
 

             Alias: peer

-
 The P2P device that should be connected to. Currently, this is the only way to create or join a group.

+
The P2P device that should be connected to. Currently, this is the only way to create or join a group.

 

             Format: string

 
@@ -4618,8 +4718,8 @@ The actual string to print.
 
 
wfd-ies

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

+
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

 
@@ -4627,8 +4727,8 @@ The actual string to print.
 
 
wps-method

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

+
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

 
@@ -4639,7 +4739,7 @@ The actual string to print.
 

 

 
wimax setting

-
 WiMax Settings.

+
WiMax Settings.

 

         Properties:
         

@@ -4654,7 +4754,10 @@ The actual string to print.
 
 

             Alias: mac

-
 If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing). Deprecated: 1

+
If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing).

+

+            This property is deprecated since version 1.2.
+            WiMAX is no longer supported.

 

             Format: byte array

 
@@ -4664,7 +4767,10 @@ The actual string to print.
 
 

             Alias: nsp

-
 Network Service Provider (NSP) name of the WiMAX network this connection should use. Deprecated: 1

+
Network Service Provider (NSP) name of the WiMAX network this connection should use.

+

+            This property is deprecated since version 1.2.
+            WiMAX is no longer supported.

 

             Format: string

 
@@ -4677,7 +4783,7 @@ The actual string to print.
 
802-3-ethernet setting

 

           Alias: ethernet

-
 Wired Ethernet Settings.

+
Wired Ethernet Settings.

 

         Properties:
         

@@ -4690,7 +4796,7 @@ The actual string to print.
 
 
accept-all-mac-addresses

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

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

 
@@ -4698,7 +4804,7 @@ The actual string to print.
 
 
auto-negotiate

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

+
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

 
@@ -4708,10 +4814,10 @@ The actual string to print.
 
 

             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 if the device has one (otherwise this is treated as "preserve"). "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.

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

+
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 if the device has one (otherwise this is treated as "preserve"). "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.

+
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

 
@@ -4719,7 +4825,7 @@ The actual string to print.
 
 
duplex

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

+
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

 
@@ -4727,11 +4833,11 @@ The actual string to print.
 
 
generate-mac-address-mask

 
-
 With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.

-
 If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.

-
 If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.

-
 If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.

-
 If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.

+
With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.

+
If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.

+
If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.

+
If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.

+
If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.

 

             Format: string

 
@@ -4741,7 +4847,7 @@ The actual string to print.
 
 

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

+
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

 
@@ -4749,7 +4855,7 @@ The actual string to print.
 
 
mac-address-blacklist

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

+
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

 
@@ -4759,7 +4865,7 @@ The actual string to print.
 
 

             Alias: mtu

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

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

 

             Format: uint32

 
@@ -4767,7 +4873,7 @@ The actual string to print.
 
 
port

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

+
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

 
@@ -4775,7 +4881,7 @@ The actual string to print.
 
 
s390-nettype

 
-
 s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.

+
s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.

 

             Format: string

 
@@ -4783,8 +4889,8 @@ The actual string to print.
 
 
s390-options

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

-
 Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.

+
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

 
@@ -4792,7 +4898,7 @@ The actual string to print.
 
 
s390-subchannels

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

+
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

 
@@ -4800,7 +4906,7 @@ The actual string to print.
 
 
speed

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

+
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

 
@@ -4808,7 +4914,7 @@ The actual string to print.
 
 
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 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).

 

             Format: uint32

 
@@ -4816,7 +4922,7 @@ The actual string to print.
 
 
wake-on-lan-password

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

+
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

 
@@ -4827,7 +4933,7 @@ The actual string to print.
 

 

 
wireguard setting

-
 WireGuard Settings.

+
WireGuard Settings.

 

         Properties:
         

@@ -4840,8 +4946,8 @@ The actual string to print.
 
 
fwmark

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

+
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

 
@@ -4849,9 +4955,9 @@ The actual string to print.
 
 
ip4-auto-default-route

 
-
 Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing".

-
 Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route.

-
 Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips. 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.

+
Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing".

+
Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route.

+
Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips. 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)

 
@@ -4859,7 +4965,7 @@ The actual string to print.
 
 
ip6-auto-default-route

 
-
 Like ip4-auto-default-route, but for the IPv6 default route.

+
Like ip4-auto-default-route, but for the IPv6 default route.

 

             Format: NMTernary (int32)

 
@@ -4867,7 +4973,7 @@ The actual string to print.
 
 
listen-port

 
-
 The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.

+
The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.

 

             Format: uint32

 
@@ -4875,8 +4981,8 @@ The actual string to print.
 
 
mtu

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

+
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

 
@@ -4884,8 +4990,8 @@ The actual string to print.
 
 
peer-routes

 
-
 Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively.

-
 Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.

+
Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively.

+
Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.

 

             Format: boolean

 
@@ -4893,7 +4999,7 @@ The actual string to print.
 
 
private-key

 
-
 The 256 bit private-key in base64 encoding.

+
The 256 bit private-key in base64 encoding.

 

             Format: string

 
@@ -4901,7 +5007,7 @@ The actual string to print.
 
 
private-key-flags

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

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

 

             Format: NMSettingSecretFlags (uint32)

 
@@ -4914,7 +5020,7 @@ The actual string to print.
 
802-11-wireless setting

 

           Alias: wifi

-
 Wi-Fi Settings.

+
Wi-Fi Settings.

 

         Properties:
         

@@ -4927,10 +5033,10 @@ The actual string to print.
 
 
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 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).

 

             Format: NMTernary (int32)

 
@@ -4938,7 +5044,7 @@ The actual string to print.
 
 
band

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

+
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

 
@@ -4946,8 +5052,8 @@ The actual string to print.
 
 
bssid

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

+
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

 
@@ -4955,7 +5061,7 @@ The actual string to print.
 
 
channel

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

+
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

 
@@ -4965,10 +5071,10 @@ The actual string to print.
 
 

             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.

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

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

+
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

 
@@ -4976,11 +5082,11 @@ The actual string to print.
 
 
generate-mac-address-mask

 
-
 With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.

-
 If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.

-
 If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.

-
 If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.

-
 If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.

+
With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.

+
If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.

+
If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.

+
If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.

+
If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.

 

             Format: string

 
@@ -4988,10 +5094,10 @@ The actual string to print.
 
 
hidden

 
-
 If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode.

-
 In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID.  However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution.

-
 In AP mode, the created network does not broadcast its SSID.

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

+
If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode.

+
In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID.  However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution.

+
In AP mode, the created network does not broadcast its SSID.

+
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

 
@@ -5001,7 +5107,7 @@ The actual string to print.
 
 

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

+
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

 
@@ -5009,7 +5115,7 @@ The actual string to print.
 
 
mac-address-blacklist

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

+
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

 
@@ -5017,7 +5123,10 @@ The actual string to print.
 
 
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). This property is deprecated for 'cloned-mac-address'. Deprecated: 1

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

+

+            This property is deprecated since version 1.4.
+            Use the "cloned-mac-address" property instead.

 

             Format: uint32

 
@@ -5027,7 +5136,7 @@ The actual string to print.
 
 

             Alias: mode

-
 Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.

+
Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.

 

             Format: string

 
@@ -5037,7 +5146,7 @@ The actual string to print.
 
 

             Alias: mtu

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

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

 

             Format: uint32

 
@@ -5045,7 +5154,7 @@ The actual string to print.
 
 
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 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.

 

             Format: uint32

 
@@ -5053,7 +5162,7 @@ The actual string to print.
 
 
rate

 
-
 If non-zero, directs the device to only use the specified bitrate for communication with the access point.  Units are in Kb/s, ie 5500 = 5.5 Mbit/s.  This property is highly driver dependent and not all devices support setting a static bitrate.

+
If non-zero, directs the device to only use the specified bitrate for communication with the access point.  Units are in Kb/s, ie 5500 = 5.5 Mbit/s.  This property is highly driver dependent and not all devices support setting a static bitrate.

 

             Format: uint32

 
@@ -5061,7 +5170,7 @@ The actual string to print.
 
 
seen-bssids

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

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

 

             Format: array of string

 
@@ -5071,7 +5180,7 @@ The actual string to print.
 
 

             Alias: ssid

-
 SSID of the Wi-Fi network. Must be specified.

+
SSID of the Wi-Fi network. Must be specified.

 

             Format: byte array

 
@@ -5079,7 +5188,7 @@ The actual string to print.
 
 
tx-power

 
-
 If non-zero, directs the device to use the specified transmit power. Units are dBm.  This property is highly driver dependent and not all devices support setting a static transmit power.

+
If non-zero, directs the device to use the specified transmit power. Units are dBm.  This property is highly driver dependent and not all devices support setting a static transmit power.

 

             Format: uint32

 
@@ -5087,7 +5196,7 @@ The actual string to print.
 
 
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 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).

 

             Format: uint32

 
@@ -5100,7 +5209,7 @@ The actual string to print.
 
802-11-wireless-security setting

 

           Alias: wifi-sec

-
 Wi-Fi Security Settings.

+
Wi-Fi Security Settings.

 

         Properties:
         

@@ -5113,7 +5222,7 @@ The actual string to print.
 
 
auth-alg

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

+
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

 
@@ -5121,7 +5230,7 @@ The actual string to print.
 
 
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 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.

 

             Format: int32

 
@@ -5129,7 +5238,7 @@ The actual string to print.
 
 
group

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

+
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

 
@@ -5137,8 +5246,8 @@ The actual string to print.
 
 
key-mgmt

 
-
 Key management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only).

-
 This property must be set for any Wi-Fi connection that uses security.

+
Key management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only).

+
This property must be set for any Wi-Fi connection that uses security.

 

             Format: string

 
@@ -5146,7 +5255,7 @@ The actual string to print.
 
 
leap-password

 
-
 The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").

+
The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").

 

             Format: string

 
@@ -5154,7 +5263,7 @@ The actual string to print.
 
 
leap-password-flags

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

+
Flags indicating how to handle the "leap-password" property.

 

             Format: NMSettingSecretFlags (uint32)

 
@@ -5162,7 +5271,7 @@ The actual string to print.
 
 
leap-username

 
-
 The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").

+
The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").

 

             Format: string

 
@@ -5170,7 +5279,7 @@ The actual string to print.
 
 
pairwise

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

+
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

 
@@ -5178,7 +5287,7 @@ The actual string to print.
 
 
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 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.

 

             Format: int32

 
@@ -5186,7 +5295,7 @@ The actual string to print.
 
 
proto

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

+
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

 
@@ -5194,7 +5303,7 @@ The actual string to print.
 
 
psk

 
-
 Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.

+
Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.

 

             Format: string

 
@@ -5202,7 +5311,7 @@ The actual string to print.
 
 
psk-flags

 
-
 Flags indicating how to handle the "psk" property.

+
Flags indicating how to handle the "psk" property.

 

             Format: NMSettingSecretFlags (uint32)

 
@@ -5210,7 +5319,7 @@ The actual string to print.
 
 
wep-key-flags

 
-
 Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.

+
Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.

 

             Format: NMSettingSecretFlags (uint32)

 
@@ -5218,7 +5327,7 @@ The actual string to print.
 
 
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 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.

 

             Format: NMWepKeyType (uint32)

 
@@ -5226,7 +5335,7 @@ The actual string to print.
 
 
wep-key0

 
-
 Index 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.

+
Index 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.

 

             Format: string

 
@@ -5234,7 +5343,7 @@ The actual string to print.
 
 
wep-key1

 
-
 Index 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.

+
Index 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.

 

             Format: string

 
@@ -5242,7 +5351,7 @@ The actual string to print.
 
 
wep-key2

 
-
 Index 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.

+
Index 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.

 

             Format: string

 
@@ -5250,7 +5359,7 @@ The actual string to print.
 
 
wep-key3

 
-
 Index 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.

+
Index 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.

 

             Format: string

 
@@ -5258,7 +5367,7 @@ The actual string to print.
 
 
wep-tx-keyidx

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

+
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

 
@@ -5266,9 +5375,9 @@ The actual string to print.
 
 
wps-method

 
-
 Flags indicating which mode of WPS is to be used if any.

-
 There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities.

-
 WPS can be disabled by setting this property to a value of 1.

+
Flags indicating which mode of WPS is to be used if any.

+
There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities.

+
WPS can be disabled by setting this property to a value of 1.

 

             Format: uint32

 
@@ -5279,7 +5388,7 @@ The actual string to print.
 

 

 
wpan setting

-
 IEEE 802.15.4 (WPAN) MAC Settings.

+
IEEE 802.15.4 (WPAN) MAC Settings.

 

         Properties:
         

@@ -5294,7 +5403,7 @@ The actual string to print.
 
 

             Alias: channel

-
 IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".

+
IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".

 

             Format: int32

 
@@ -5304,7 +5413,7 @@ The actual string to print.
 
 

             Alias: mac

-
 If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.

+
If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.

 

             Format: string

 
@@ -5314,7 +5423,7 @@ The actual string to print.
 
 

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

+
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

 
@@ -5324,7 +5433,7 @@ The actual string to print.
 
 

             Alias: pan-id

-
 IEEE 802.15.4 Personal Area Network (PAN) identifier.

+
IEEE 802.15.4 Personal Area Network (PAN) identifier.

 

             Format: uint32

 
@@ -5334,7 +5443,7 @@ The actual string to print.
 
 

             Alias: short-addr

-
 Short IEEE 802.15.4 address to be used within a restricted environment.

+
Short IEEE 802.15.4 address to be used within a restricted environment.

 

             Format: uint32

 
@@ -5345,7 +5454,7 @@ The actual string to print.
 

 

 
bond-port setting

-
 Bond Port Settings.

+
Bond Port Settings.

 

         Properties:
         

@@ -5359,7 +5468,7 @@ The actual string to print.
 
 

             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.

+
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

 
@@ -5369,7 +5478,7 @@ The actual string to print.
 

 

 
hostname setting

-
 Hostname settings.

+
Hostname settings.

 

         Properties:
         

@@ -5382,8 +5491,8 @@ The actual string to print.
 
 
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).

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

 

             Format: NMTernary (int32)

 
@@ -5391,8 +5500,8 @@ The actual string to print.
 
 
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).

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

 

             Format: NMTernary (int32)

 
@@ -5400,9 +5509,9 @@ The actual string to print.
 
 
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 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).

 

             Format: NMTernary (int32)

 
@@ -5410,9 +5519,9 @@ The actual string to print.
 
 
priority

 
-
 The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority.

-
 If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100.

-
 Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.

+
The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority.

+
If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100.

+
Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.

 

             Format: int32

 
@@ -5422,8 +5531,32 @@ The actual string to print.
 

 

 

-
veth setting

-
 Veth Settings.

+
loopback setting

+
Loopback Link Settings.

+

+        Properties:
+        

+

++++
+
+
+
+
+




mtu

+

+            Alias: mtu

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

+

+            Format: uint32

+

+

+

+

+
veth setting

+
Veth Settings.

 

         Properties:
         

@@ -5437,7 +5570,7 @@ The actual string to print.
 
 

             Alias: peer

-
 This property specifies the peer interface name of the veth. This property is mandatory.

+
This property specifies the peer interface name of the veth. This property is mandatory.

 

             Format: string

 
diff --git a/docs/api/html/nmcli.html b/docs/api/html/nmcli.html
index 526f1ee6..8443d500 100644
--- a/docs/api/html/nmcli.html
+++ b/docs/api/html/nmcli.html
@@ -1595,6 +1595,39 @@
 
Provides a default value for the internationalization variables that are
           unset or null.

 
+
+
NO_COLOR

+
Default to not producing colored and paged output. The
+          --colors option, if used, takes precedence.

+
+
+
PAGER

+
+
Filter to pipe the output through if it doesn't fit on a screen.
+          Can be a file name of an executable or a shell command. Empty string to
+          disable the functionality.

+
Note that the pager command is expected to handle wide characters
+          and ANSI escape sequences for changing colors (unless they're disabled).
+          nmcli sets up the environment variables
+          LESS and LESSCHARSET appropriately for the
+          less(1)
+          pager, other pagers may or may not need extra configuration.

+
If unspecified,
+          pager(1),
+          less(1)
+          and more(1)
+          will be tried (in that order).

+
+
+
+
TERM

+
+
Terminal type. If dumb, nmcli
+          will not use a pager or produce ANSI escape sequences for coloring.

+
Terminal types other than dumb are assumed to
+          support ASCII escape sequences for setting the output color.

+
+
 
 

 

diff --git a/docs/api/html/ref-dbus-devices.html b/docs/api/html/ref-dbus-devices.html
index 7d732909..ffff3da4 100644
--- a/docs/api/html/ref-dbus-devices.html
+++ b/docs/api/html/ref-dbus-devices.html
@@ -54,6 +54,9 @@
 org.freedesktop.NetworkManager.Device.Infiniband — Infiniband Device.
 
 

+org.freedesktop.NetworkManager.Device.Loopback — Loopback Device.
+

+

 org.freedesktop.NetworkManager.Device.Lowpan — 6LoWPAN Device.
 

 

diff --git a/docs/api/html/ref-settings.html b/docs/api/html/ref-settings.html
index f35354f9..f0cec0d7 100644
--- a/docs/api/html/ref-settings.html
+++ b/docs/api/html/ref-settings.html
@@ -28,160 +28,166 @@
 
Configuration Settings

 

 

-connection —  General Connection Profile Settings
+connection — General Connection Profile Settings
 

 

-6lowpan —  6LoWPAN Settings
+6lowpan — 6LoWPAN Settings
 

 

-802-1x —  IEEE 802.1x Authentication Settings
+802-1x — IEEE 802.1x Authentication Settings
 

 

-adsl —  ADSL Settings
+adsl — ADSL Settings
 

 

-bluetooth —  Bluetooth Settings
+bluetooth — Bluetooth Settings
 

 

-bond —  Bonding Settings
+bond — Bonding Settings
 

 

-bridge —  Bridging Settings
+bridge — Bridging Settings
 

 

-bridge-port —  Bridge Port Settings
+bridge-port — Bridge Port Settings
 

 

-cdma —  CDMA-based Mobile Broadband Settings
+cdma — CDMA-based Mobile Broadband Settings
 

 

-dcb —  Data Center Bridging Settings
+dcb — Data Center Bridging Settings
 

 

-dummy —  Dummy Link Settings
+dummy — Dummy Link Settings
 

 

-ethtool —  Ethtool Ethernet Settings
+ethtool — Ethtool Ethernet Settings
 

 

-generic —  Generic Link Settings
+generic — Generic Link Settings
 

 

-gsm —  GSM-based Mobile Broadband Settings
+gsm — GSM-based Mobile Broadband Settings
 

 

-infiniband —  Infiniband Settings
+infiniband — Infiniband Settings
 

 

-ipv4 —  IPv4 Settings
+ipv4 — IPv4 Settings
 

 

-ipv6 —  IPv6 Settings
+ipv6 — IPv6 Settings
 

 

-ip-tunnel —  IP Tunneling Settings
+ip-tunnel — IP Tunneling Settings
 

 

-macsec —  MACSec Settings
+macsec — MACSec Settings
 

 

-macvlan —  MAC VLAN Settings
+macvlan — MAC VLAN Settings
 

 

-match —  Match settings
+match — Match settings
 

 

-802-11-olpc-mesh —  OLPC Wireless Mesh Settings
+802-11-olpc-mesh — OLPC Wireless Mesh Settings
 

 

-ovs-bridge —  OvsBridge Link Settings
+ovs-bridge — OvsBridge Link Settings
 

 

-ovs-dpdk —  OvsDpdk Link Settings
+ovs-dpdk — OvsDpdk Link Settings
 

 

-ovs-interface —  Open vSwitch Interface Settings
+ovs-interface — Open vSwitch Interface Settings
 

 

-ovs-patch —  OvsPatch Link Settings
+ovs-patch — OvsPatch Link Settings
 

 

-ovs-port —  OvsPort Link Settings
+ovs-port — OvsPort Link Settings
 

 

-ppp —  Point-to-Point Protocol Settings
+ppp — Point-to-Point Protocol Settings
 

 

-pppoe —  PPP-over-Ethernet Settings
+pppoe — PPP-over-Ethernet Settings
 

 

-proxy —  WWW Proxy Settings
+proxy — WWW Proxy Settings
 

 

-serial —  Serial Link Settings
+serial — Serial Link Settings
 

 

-sriov —  SR-IOV settings
+sriov — SR-IOV settings
 

 

-tc —  Linux Traffic Control Settings
+tc — Linux Traffic Control Settings
 

 

-team —  Teaming Settings
+team — Teaming Settings
 

 

-team-port —  Team Port Settings
+team-port — Team Port Settings
 

 

-tun —  Tunnel Settings
+tun — Tunnel Settings
 

 

-user —  General User Profile Settings
+user — General User Profile Settings
 

 

-vlan —  VLAN Settings
+vlan — VLAN Settings
 

 

-vpn —  VPN Settings
+vpn — VPN Settings
 

 

-vrf —  VRF settings
+vrf — VRF settings
 

 

-vxlan —  VXLAN Settings
+vxlan — VXLAN Settings
 

 

-wifi-p2p —  Wi-Fi P2P Settings
+wifi-p2p — Wi-Fi P2P Settings
 

 

-wimax —  WiMax Settings
+wimax — WiMax Settings
 

 

-802-3-ethernet —  Wired Ethernet Settings
+802-3-ethernet — Wired Ethernet Settings
 

 

-wireguard —  WireGuard Settings
+wireguard — WireGuard Settings
 

 

-802-11-wireless —  Wi-Fi Settings
+802-11-wireless — Wi-Fi Settings
 

 

-802-11-wireless-security —  Wi-Fi Security Settings
+802-11-wireless-security — Wi-Fi Security Settings
 

 

-wpan —  IEEE 802.15.4 (WPAN) MAC Settings
+wpan — IEEE 802.15.4 (WPAN) MAC Settings
 

 

-bond-port —  Bond Port Settings
+bond-port — Bond Port Settings
 

 

-hostname —  Hostname settings
+hostname — Hostname settings
 

 

-ovs-external-ids —  OVS External IDs Settings
+loopback — Loopback Link Settings
 

 

-veth —  Veth Settings
+ovs-external-ids — OVS External IDs Settings
+

+

+ovs-other-config — OVS Other Config Settings
+

+

+veth — Veth Settings
 

 

 
Secret flag types

diff --git a/docs/api/html/settings-6lowpan.html b/docs/api/html/settings-6lowpan.html
index a185cc5f..1d692e4d 100644
--- a/docs/api/html/settings-6lowpan.html
+++ b/docs/api/html/settings-6lowpan.html
@@ -29,7 +29,7 @@
 

 
 
6lowpan

-
6lowpan —  6LoWPAN Settings

+
6lowpan — 6LoWPAN Settings

 		
 
 

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

-
Table 47. 

+
Table 49. 

 
diff --git a/docs/api/html/settings-802-11-olpc-mesh.html b/docs/api/html/settings-802-11-olpc-mesh.html
index 86a6c492..031ccb05 100644
--- a/docs/api/html/settings-802-11-olpc-mesh.html
+++ b/docs/api/html/settings-802-11-olpc-mesh.html
@@ -29,7 +29,7 @@
 

 
 


 
 
802-11-olpc-mesh

-
802-11-olpc-mesh —  OLPC Wireless Mesh Settings

+
802-11-olpc-mesh — OLPC Wireless Mesh Settings

 		
 
 

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

-
Table 67. 

+
Table 69. 

 
diff --git a/docs/api/html/settings-802-11-wireless-security.html b/docs/api/html/settings-802-11-wireless-security.html
index 7f6d2474..83f4300e 100644
--- a/docs/api/html/settings-802-11-wireless-security.html
+++ b/docs/api/html/settings-802-11-wireless-security.html
@@ -29,7 +29,7 @@
 

 
 


 
 
802-11-wireless-security

-
802-11-wireless-security —  Wi-Fi Security Settings

+
802-11-wireless-security — Wi-Fi Security Settings

 		
 
 

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

-
Table 92. 

+
Table 94. 

 
diff --git a/docs/api/html/settings-802-11-wireless.html b/docs/api/html/settings-802-11-wireless.html
index 00372730..24700c54 100644
--- a/docs/api/html/settings-802-11-wireless.html
+++ b/docs/api/html/settings-802-11-wireless.html
@@ -29,7 +29,7 @@
 

 
 


 
 
802-11-wireless

-
802-11-wireless —  Wi-Fi Settings

+
802-11-wireless — Wi-Fi Settings

 		
 
 

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

-
Table 91. 

+
Table 93. 

 
diff --git a/docs/api/html/settings-802-1x.html b/docs/api/html/settings-802-1x.html
index 97827e6a..4ad4158d 100644
--- a/docs/api/html/settings-802-1x.html
+++ b/docs/api/html/settings-802-1x.html
@@ -29,7 +29,7 @@
 

 
 


 
 
802-1x

-
802-1x —  IEEE 802.1x Authentication Settings

+
802-1x — IEEE 802.1x Authentication Settings

 		
 
 

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

-
Table 48. 

+
Table 50. 

 
diff --git a/docs/api/html/settings-802-3-ethernet.html b/docs/api/html/settings-802-3-ethernet.html
index b3132cf3..b232048e 100644
--- a/docs/api/html/settings-802-3-ethernet.html
+++ b/docs/api/html/settings-802-3-ethernet.html
@@ -29,7 +29,7 @@
 

 
 


 
 
802-3-ethernet

-
802-3-ethernet —  Wired Ethernet Settings

+
802-3-ethernet — Wired Ethernet Settings

 		
 
 

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

-
Table 89. 

+
Table 91. 

 
diff --git a/docs/api/html/settings-adsl.html b/docs/api/html/settings-adsl.html
index 9c9cd333..ab01cb14 100644
--- a/docs/api/html/settings-adsl.html
+++ b/docs/api/html/settings-adsl.html
@@ -29,7 +29,7 @@
 

 
 


 
 
adsl

-
adsl —  ADSL Settings

+
adsl — ADSL Settings

 		
 
 

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

-
Table 49. 

+
Table 51. 

 
diff --git a/docs/api/html/settings-bluetooth.html b/docs/api/html/settings-bluetooth.html
index 6af4a0ee..cc035095 100644
--- a/docs/api/html/settings-bluetooth.html
+++ b/docs/api/html/settings-bluetooth.html
@@ -29,7 +29,7 @@
 

 
 


 
 
bluetooth

-
bluetooth —  Bluetooth Settings

+
bluetooth — Bluetooth Settings

 		
 
 

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

-
Table 50. 

+
Table 52. 

 
diff --git a/docs/api/html/settings-bond-port.html b/docs/api/html/settings-bond-port.html
index dc63034a..6daf9a3d 100644
--- a/docs/api/html/settings-bond-port.html
+++ b/docs/api/html/settings-bond-port.html
@@ -29,7 +29,7 @@
 

 
 


 
 
bond-port

-
bond-port —  Bond Port Settings

+
bond-port — Bond Port Settings

 		
 
 

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

-
Table 94. 

+
Table 96. 

 
diff --git a/docs/api/html/settings-bond.html b/docs/api/html/settings-bond.html
index 81b21536..21d2ff0f 100644
--- a/docs/api/html/settings-bond.html
+++ b/docs/api/html/settings-bond.html
@@ -29,7 +29,7 @@
 

 
 


 
 
bond

-
bond —  Bonding Settings

+
bond — Bonding Settings

 		
 
 

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

-
Table 51. 

+
Table 53. 

 
diff --git a/docs/api/html/settings-bridge-port.html b/docs/api/html/settings-bridge-port.html
index 7ab80feb..05b27bc4 100644
--- a/docs/api/html/settings-bridge-port.html
+++ b/docs/api/html/settings-bridge-port.html
@@ -29,7 +29,7 @@
 

 
 


 
 
bridge-port

-
bridge-port —  Bridge Port Settings

+
bridge-port — Bridge Port Settings

 		
 
 

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

-
Table 53. 

+
Table 55. 

 
diff --git a/docs/api/html/settings-bridge.html b/docs/api/html/settings-bridge.html
index b47077e9..27f4d555 100644
--- a/docs/api/html/settings-bridge.html
+++ b/docs/api/html/settings-bridge.html
@@ -29,7 +29,7 @@
 

 
 


 
 
bridge

-
bridge —  Bridging Settings

+
bridge — Bridging Settings

 		
 
 

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

-
Table 52. 

+
Table 54. 

 
diff --git a/docs/api/html/settings-cdma.html b/docs/api/html/settings-cdma.html
index c718232d..c579ce75 100644
--- a/docs/api/html/settings-cdma.html
+++ b/docs/api/html/settings-cdma.html
@@ -29,7 +29,7 @@
 

 
 


 
 
cdma

-
cdma —  CDMA-based Mobile Broadband Settings

+
cdma — CDMA-based Mobile Broadband Settings

 		
 
 

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

-
Table 54. 

+
Table 56. 

 
diff --git a/docs/api/html/settings-connection.html b/docs/api/html/settings-connection.html
index fd66ad01..47eb2f12 100644
--- a/docs/api/html/settings-connection.html
+++ b/docs/api/html/settings-connection.html
@@ -29,7 +29,7 @@
 

 
 


 
 
connection

-
connection —  General Connection Profile Settings

+
connection — General Connection Profile Settings

 		
 
 

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

-
Table 46. 

+
Table 48. 

 
diff --git a/docs/api/html/settings-dcb.html b/docs/api/html/settings-dcb.html
index f99db147..acaaf982 100644
--- a/docs/api/html/settings-dcb.html
+++ b/docs/api/html/settings-dcb.html
@@ -29,7 +29,7 @@
 

 
 


 
 
dcb

-
dcb —  Data Center Bridging Settings

+
dcb — Data Center Bridging Settings

 		
 
 

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

-
Table 55. 

+
Table 57. 

 
diff --git a/docs/api/html/settings-dummy.html b/docs/api/html/settings-dummy.html
index efdb69b3..f2929aab 100644
--- a/docs/api/html/settings-dummy.html
+++ b/docs/api/html/settings-dummy.html
@@ -29,7 +29,7 @@
 

 
 


 
 
dummy

-
dummy —  Dummy Link Settings

+
dummy — Dummy Link Settings

 		
 
 

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

-
Table 56. 

+
Table 58. 

 
diff --git a/docs/api/html/settings-ethtool.html b/docs/api/html/settings-ethtool.html
index 8f7d443b..35273827 100644
--- a/docs/api/html/settings-ethtool.html
+++ b/docs/api/html/settings-ethtool.html
@@ -29,7 +29,7 @@
 

 
 


 
 
ethtool

-
ethtool —  Ethtool Ethernet Settings

+
ethtool — Ethtool Ethernet Settings

 		
 
 

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

-
Table 57. 

+
Table 59. 

 
diff --git a/docs/api/html/settings-generic.html b/docs/api/html/settings-generic.html
index efe5a89a..23ef5e04 100644
--- a/docs/api/html/settings-generic.html
+++ b/docs/api/html/settings-generic.html
@@ -29,7 +29,7 @@
 

 
 


 
 
generic

-
generic —  Generic Link Settings

+
generic — Generic Link Settings

 		
 
 

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

-
Table 58. 

+
Table 60. 

 
diff --git a/docs/api/html/settings-gsm.html b/docs/api/html/settings-gsm.html
index 2834c46d..0f57507e 100644
--- a/docs/api/html/settings-gsm.html
+++ b/docs/api/html/settings-gsm.html
@@ -29,7 +29,7 @@
 

 
 


 
 
gsm

-
gsm —  GSM-based Mobile Broadband Settings

+
gsm — GSM-based Mobile Broadband Settings

 		
 
 

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

-
Table 59. 

+
Table 61. 

 
diff --git a/docs/api/html/settings-hostname.html b/docs/api/html/settings-hostname.html
index d6110465..d12fcfba 100644
--- a/docs/api/html/settings-hostname.html
+++ b/docs/api/html/settings-hostname.html
@@ -7,7 +7,7 @@
 
-
+
@@ -22,14 +22,14 @@
 
-
+

 
 

 
 
 
 
 
Home
 Up
 PrevNextNext
 

 

 

 

 
 
hostname

-
hostname —  Hostname settings

+
hostname — Hostname settings

 		
 
 

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

-
Table 95. 

+
Table 97. 

 
diff --git a/docs/api/html/settings-infiniband.html b/docs/api/html/settings-infiniband.html
index 317a26a5..6b509038 100644
--- a/docs/api/html/settings-infiniband.html
+++ b/docs/api/html/settings-infiniband.html
@@ -29,7 +29,7 @@
 

 
 


 
 
infiniband

-
infiniband —  Infiniband Settings

+
infiniband — Infiniband Settings

 		
 
 

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

-
Table 60. 

+
Table 62. 

 
diff --git a/docs/api/html/settings-ip-tunnel.html b/docs/api/html/settings-ip-tunnel.html
index cd464bac..4f35a153 100644
--- a/docs/api/html/settings-ip-tunnel.html
+++ b/docs/api/html/settings-ip-tunnel.html
@@ -29,7 +29,7 @@
 

 
 


 
 
ip-tunnel

-
ip-tunnel —  IP Tunneling Settings

+
ip-tunnel — IP Tunneling Settings

 		
 
 

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

-
Table 63. 

+
Table 65. 

 
@@ -72,6 +72,12 @@
 
+
+
+
+
+
+
diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html
index a933d551..4de460ed 100644
--- a/docs/api/html/settings-ipv4.html
+++ b/docs/api/html/settings-ipv4.html
@@ -29,7 +29,7 @@
 

 
 

 
 

 
fwmark
uint32
0
 

 
input-key

 
string

 

 
 
ipv4

-
ipv4 —  IPv4 Settings

+
ipv4 — IPv4 Settings

 		
 
 

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

-
Table 61. 

+
Table 63. 

 
@@ -66,6 +66,12 @@
 
+
+
+
+
+
+
@@ -132,6 +138,12 @@
 
+
+
+
+
+
+
@@ -221,6 +233,12 @@
 
+
+
+
+
+
+

 
 

 
 

 
auto-route-ext-gw
NMTernary (int32)
 

 
dad-timeout

 
int32

 
-1
 
 

 
dns-data
array of strings
 

 
dns-options

 
array of string

 

  
 
routing-rules
array of 'a{sv}'
 

 
 

 

diff --git a/docs/api/html/settings-ipv6.html b/docs/api/html/settings-ipv6.html
index b5ce52e6..ed0f3010 100644
--- a/docs/api/html/settings-ipv6.html
+++ b/docs/api/html/settings-ipv6.html
@@ -29,7 +29,7 @@
 

 
 
ipv6

-
ipv6 —  IPv6 Settings

+
ipv6 — IPv6 Settings

 		
 
 

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

-
Table 62. 

+
Table 64. 

 
@@ -72,6 +72,12 @@
 
+
+
+
+
+
+
@@ -126,6 +132,12 @@
 
+
+
+
+
+
+
@@ -228,6 +240,12 @@
 
+
+
+
+
+
+
diff --git a/docs/api/html/settings-loopback.html b/docs/api/html/settings-loopback.html
new file mode 100644
index 00000000..05caf07c
--- /dev/null
+++ b/docs/api/html/settings-loopback.html
@@ -0,0 +1,69 @@
+
+
+
+
+loopback: NetworkManager Reference Manual
+
+
+
+
+
+
+
+
+
+

 
 

 
 

 
auto-route-ext-gw
NMTernary (int32)
 

 
dad-timeout

 
int32

 
-1
 
 

 
dns-data
array of strings
 

 
dns-options

 
array of string

 
 
 

 
routing-rules
array of 'a{sv}'
 

 
token

 
string

 

+
+
+
+
+
+
+

+

+

+
+
+

+
loopback

+
loopback — Loopback Link Settings

+

+

+

+            Properties
+        

+

+
Table 98. 

+

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






Key NameValue TypeDefault ValueValue Description
mtu
uint32
0
 

+

+


+

+

+

+
Generated by GTK-Doc V1.33.1

+
+
\ No newline at end of file
diff --git a/docs/api/html/settings-macsec.html b/docs/api/html/settings-macsec.html
index 72e103d0..6b19558f 100644
--- a/docs/api/html/settings-macsec.html
+++ b/docs/api/html/settings-macsec.html
@@ -29,7 +29,7 @@
 

 
 
macsec

-
macsec —  MACSec Settings

+
macsec — MACSec Settings

 		
 
 

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

-
Table 64. 

+
Table 66. 

 
diff --git a/docs/api/html/settings-macvlan.html b/docs/api/html/settings-macvlan.html
index aec99676..645bee54 100644
--- a/docs/api/html/settings-macvlan.html
+++ b/docs/api/html/settings-macvlan.html
@@ -29,7 +29,7 @@
 

 
 


 
 
macvlan

-
macvlan —  MAC VLAN Settings

+
macvlan — MAC VLAN Settings

 		
 
 

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

-
Table 65. 

+
Table 67. 

 
diff --git a/docs/api/html/settings-match.html b/docs/api/html/settings-match.html
index 2c483f94..916d91ef 100644
--- a/docs/api/html/settings-match.html
+++ b/docs/api/html/settings-match.html
@@ -29,7 +29,7 @@
 

 
 


 
 
match

-
match —  Match settings

+
match — Match settings

 		
 
 

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

-
Table 66. 

+
Table 68. 

 
diff --git a/docs/api/html/settings-ovs-bridge.html b/docs/api/html/settings-ovs-bridge.html
index 6977650b..24b481f6 100644
--- a/docs/api/html/settings-ovs-bridge.html
+++ b/docs/api/html/settings-ovs-bridge.html
@@ -29,7 +29,7 @@
 

 
 


 
 
ovs-bridge

-
ovs-bridge —  OvsBridge Link Settings

+
ovs-bridge — OvsBridge Link Settings

 		
 
 

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

-
Table 68. 

+
Table 70. 

 
diff --git a/docs/api/html/settings-ovs-dpdk.html b/docs/api/html/settings-ovs-dpdk.html
index 959b44c1..bbd4d878 100644
--- a/docs/api/html/settings-ovs-dpdk.html
+++ b/docs/api/html/settings-ovs-dpdk.html
@@ -29,7 +29,7 @@
 

 
 


 
 
ovs-dpdk

-
ovs-dpdk —  OvsDpdk Link Settings

+
ovs-dpdk — OvsDpdk Link Settings

 		
 
 

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

-
Table 69. 

+
Table 71. 

 
@@ -65,6 +65,18 @@
 
+
+
+
+
+
+
+
+
+
+
+
+

 
 

0

  
 
n-rxq-desc
uint32
0
 
n-txq-desc
uint32
0
 

 
 

 

diff --git a/docs/api/html/settings-ovs-external-ids.html b/docs/api/html/settings-ovs-external-ids.html
index 21de0dc0..c41f7ba5 100644
--- a/docs/api/html/settings-ovs-external-ids.html
+++ b/docs/api/html/settings-ovs-external-ids.html
@@ -6,8 +6,8 @@
 
 
 
-
-
+
+
 
 
 
@@ -21,24 +21,24 @@
 
 Home
 Up
-Prev
-Next
+Prev
+Next
 
 

 

 

 
 
ovs-external-ids

-
ovs-external-ids —  OVS External IDs Settings

+
ovs-external-ids — OVS External IDs Settings

 		
 
 

 

-

+

             Properties
         

 

-
Table 96. 

+
Table 99. 

 
diff --git a/docs/api/html/settings-ovs-interface.html b/docs/api/html/settings-ovs-interface.html
index 22dc57f7..c1dabd02 100644
--- a/docs/api/html/settings-ovs-interface.html
+++ b/docs/api/html/settings-ovs-interface.html
@@ -29,7 +29,7 @@
 

 
 


 
 
ovs-interface

-
ovs-interface —  Open vSwitch Interface Settings

+
ovs-interface — Open vSwitch Interface Settings

 		
 
 

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

-
Table 70. 

+
Table 72. 

 
@@ -52,12 +52,20 @@
 
-
+
+
+
+
+
+
+
+
-
+
+

 
 

Default Value
 Value Description
 
ofport-request
uint32
0
 

 
type

 
string

 

  

 

 

 


diff --git a/docs/api/html/settings-ovs-other-config.html b/docs/api/html/settings-ovs-other-config.html
new file mode 100644
index 00000000..5b3c728e
--- /dev/null
+++ b/docs/api/html/settings-ovs-other-config.html
@@ -0,0 +1,69 @@
+
+
+
+
+ovs-other-config: NetworkManager Reference Manual
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

+

+

+
+
+

+
ovs-other-config

+
ovs-other-config — OVS Other Config Settings

+

+

+

+            Properties
+        

+

+
Table 100. 

+

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






Key NameValue TypeDefault ValueValue Description
data
dict of string to string
{}
 

+

+


+

+

+

+
Generated by GTK-Doc V1.33.1

+
+
\ No newline at end of file
diff --git a/docs/api/html/settings-ovs-patch.html b/docs/api/html/settings-ovs-patch.html
index f5e5990f..1abb2211 100644
--- a/docs/api/html/settings-ovs-patch.html
+++ b/docs/api/html/settings-ovs-patch.html
@@ -29,7 +29,7 @@
 

 
 
ovs-patch

-
ovs-patch —  OvsPatch Link Settings

+
ovs-patch — OvsPatch Link Settings

 		
 
 

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

-
Table 71. 

+
Table 73. 

 
diff --git a/docs/api/html/settings-ovs-port.html b/docs/api/html/settings-ovs-port.html
index 736c7923..35f828c5 100644
--- a/docs/api/html/settings-ovs-port.html
+++ b/docs/api/html/settings-ovs-port.html
@@ -29,7 +29,7 @@
 

 
 


 
 
ovs-port

-
ovs-port —  OvsPort Link Settings

+
ovs-port — OvsPort Link Settings

 		
 
 

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

-
Table 72. 

+
Table 74. 

 
@@ -84,6 +84,12 @@
 
+
+
+
+
+
+
diff --git a/docs/api/html/settings-ppp.html b/docs/api/html/settings-ppp.html
index 62f673d9..baf53247 100644
--- a/docs/api/html/settings-ppp.html
+++ b/docs/api/html/settings-ppp.html
@@ -29,7 +29,7 @@
 

 
 

 
 

 
trunks
array of vardict
 

 
vlan-mode

 
string

 

 
 
ppp

-
ppp —  Point-to-Point Protocol Settings

+
ppp — Point-to-Point Protocol Settings

 		
 
 

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

-
Table 73. 

+
Table 75. 

 
diff --git a/docs/api/html/settings-pppoe.html b/docs/api/html/settings-pppoe.html
index 8d36c318..5cfac707 100644
--- a/docs/api/html/settings-pppoe.html
+++ b/docs/api/html/settings-pppoe.html
@@ -29,7 +29,7 @@
 

 
 


 
 
pppoe

-
pppoe —  PPP-over-Ethernet Settings

+
pppoe — PPP-over-Ethernet Settings

 		
 
 

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

-
Table 74. 

+
Table 76. 

 
diff --git a/docs/api/html/settings-proxy.html b/docs/api/html/settings-proxy.html
index d49e6fbd..5a28d81a 100644
--- a/docs/api/html/settings-proxy.html
+++ b/docs/api/html/settings-proxy.html
@@ -29,7 +29,7 @@
 

 
 


 
 
proxy

-
proxy —  WWW Proxy Settings

+
proxy — WWW Proxy Settings

 		
 
 

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

-
Table 75. 

+
Table 77. 

 
diff --git a/docs/api/html/settings-serial.html b/docs/api/html/settings-serial.html
index 9112980b..70dfcbc3 100644
--- a/docs/api/html/settings-serial.html
+++ b/docs/api/html/settings-serial.html
@@ -29,7 +29,7 @@
 

 
 


 
 
serial

-
serial —  Serial Link Settings

+
serial — Serial Link Settings

 		
 
 

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

-
Table 76. 

+
Table 78. 

 
diff --git a/docs/api/html/settings-sriov.html b/docs/api/html/settings-sriov.html
index 9000defc..62f7e68a 100644
--- a/docs/api/html/settings-sriov.html
+++ b/docs/api/html/settings-sriov.html
@@ -29,7 +29,7 @@
 

 
 


 
 
sriov

-
sriov —  SR-IOV settings

+
sriov — SR-IOV settings

 		
 
 

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

-
Table 77. 

+
Table 79. 

 
diff --git a/docs/api/html/settings-tc.html b/docs/api/html/settings-tc.html
index dc1b3765..d83d148a 100644
--- a/docs/api/html/settings-tc.html
+++ b/docs/api/html/settings-tc.html
@@ -29,7 +29,7 @@
 

 
 


 
 
tc

-
tc —  Linux Traffic Control Settings

+
tc — Linux Traffic Control Settings

 		
 
 

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

-
Table 78. 

+
Table 80. 

 
diff --git a/docs/api/html/settings-team-port.html b/docs/api/html/settings-team-port.html
index c8d05d09..333d7677 100644
--- a/docs/api/html/settings-team-port.html
+++ b/docs/api/html/settings-team-port.html
@@ -29,7 +29,7 @@
 

 
 


 
 
team-port

-
team-port —  Team Port Settings

+
team-port — Team Port Settings

 		
 
 

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

-
Table 80. 

+
Table 82. 

 
diff --git a/docs/api/html/settings-team.html b/docs/api/html/settings-team.html
index 2a572ac5..640185f6 100644
--- a/docs/api/html/settings-team.html
+++ b/docs/api/html/settings-team.html
@@ -29,7 +29,7 @@
 

 
 


 
 
team

-
team —  Teaming Settings

+
team — Teaming Settings

 		
 
 

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

-
Table 79. 

+
Table 81. 

 
diff --git a/docs/api/html/settings-tun.html b/docs/api/html/settings-tun.html
index 10fdbfb8..3691e124 100644
--- a/docs/api/html/settings-tun.html
+++ b/docs/api/html/settings-tun.html
@@ -29,7 +29,7 @@
 

 
 


 
 
tun

-
tun —  Tunnel Settings

+
tun — Tunnel Settings

 		
 
 

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

-
Table 81. 

+
Table 83. 

 
diff --git a/docs/api/html/settings-user.html b/docs/api/html/settings-user.html
index 66a8248d..8ce10de8 100644
--- a/docs/api/html/settings-user.html
+++ b/docs/api/html/settings-user.html
@@ -29,7 +29,7 @@
 

 
 


 
 
user

-
user —  General User Profile Settings

+
user — General User Profile Settings

 		
 
 

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

-
Table 82. 

+
Table 84. 

 
diff --git a/docs/api/html/settings-veth.html b/docs/api/html/settings-veth.html
index 4a8a8213..d045edae 100644
--- a/docs/api/html/settings-veth.html
+++ b/docs/api/html/settings-veth.html
@@ -6,7 +6,7 @@
 
-
+
@@ -21,7 +21,7 @@
 
-
+

 
 

 
 
 
 
 
 
Home
 UpPrevPrev
 Next
 

 

@@ -29,16 +29,16 @@
 

 
 
veth

-
veth —  Veth Settings

+
veth — Veth Settings

 		
 
 

 

-

+

             Properties
         

 

-
Table 97. 

+
Table 101. 

 
diff --git a/docs/api/html/settings-vlan.html b/docs/api/html/settings-vlan.html
index 2f10e0c2..5a310346 100644
--- a/docs/api/html/settings-vlan.html
+++ b/docs/api/html/settings-vlan.html
@@ -29,7 +29,7 @@
 

 
 


 
 
vlan

-
vlan —  VLAN Settings

+
vlan — VLAN Settings

 		
 
 

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

-
Table 83. 

+
Table 85. 

 
@@ -89,6 +89,12 @@
 
+
+
+
+
+
+

 
 


  
 
protocol
string
 

 
 

 

diff --git a/docs/api/html/settings-vpn.html b/docs/api/html/settings-vpn.html
index cdd8c3ad..bb452283 100644
--- a/docs/api/html/settings-vpn.html
+++ b/docs/api/html/settings-vpn.html
@@ -29,7 +29,7 @@
 

 
 
vpn

-
vpn —  VPN Settings

+
vpn — VPN Settings

 		
 
 

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

-
Table 84. 

+
Table 86. 

 
diff --git a/docs/api/html/settings-vrf.html b/docs/api/html/settings-vrf.html
index f0472049..e23ce0bc 100644
--- a/docs/api/html/settings-vrf.html
+++ b/docs/api/html/settings-vrf.html
@@ -29,7 +29,7 @@
 

 
 


 
 
vrf

-
vrf —  VRF settings

+
vrf — VRF settings

 		
 
 

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

-
Table 85. 

+
Table 87. 

 
diff --git a/docs/api/html/settings-vxlan.html b/docs/api/html/settings-vxlan.html
index c099f710..c00e3c0d 100644
--- a/docs/api/html/settings-vxlan.html
+++ b/docs/api/html/settings-vxlan.html
@@ -29,7 +29,7 @@
 

 
 


 
 
vxlan

-
vxlan —  VXLAN Settings

+
vxlan — VXLAN Settings

 		
 
 

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

-
Table 86. 

+
Table 88. 

 
diff --git a/docs/api/html/settings-wifi-p2p.html b/docs/api/html/settings-wifi-p2p.html
index cae67981..566e1109 100644
--- a/docs/api/html/settings-wifi-p2p.html
+++ b/docs/api/html/settings-wifi-p2p.html
@@ -29,7 +29,7 @@
 

 
 


 
 
wifi-p2p

-
wifi-p2p —  Wi-Fi P2P Settings

+
wifi-p2p — Wi-Fi P2P Settings

 		
 
 

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

-
Table 87. 

+
Table 89. 

 
diff --git a/docs/api/html/settings-wimax.html b/docs/api/html/settings-wimax.html
index d4748205..770a44a8 100644
--- a/docs/api/html/settings-wimax.html
+++ b/docs/api/html/settings-wimax.html
@@ -29,7 +29,7 @@
 

 
 


 
 
wimax

-
wimax —  WiMax Settings

+
wimax — WiMax Settings

 		
 
 

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

-
Table 88. 

+
Table 90. 

 
diff --git a/docs/api/html/settings-wireguard.html b/docs/api/html/settings-wireguard.html
index 88dc36c2..c5c3fe23 100644
--- a/docs/api/html/settings-wireguard.html
+++ b/docs/api/html/settings-wireguard.html
@@ -29,7 +29,7 @@
 

 
 


 
 
wireguard

-
wireguard —  WireGuard Settings

+
wireguard — WireGuard Settings

 		
 
 

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

-
Table 90. 

+
Table 92. 

 
diff --git a/docs/api/html/settings-wpan.html b/docs/api/html/settings-wpan.html
index 83aeb13f..f6560737 100644
--- a/docs/api/html/settings-wpan.html
+++ b/docs/api/html/settings-wpan.html
@@ -29,7 +29,7 @@
 

 
 


 
 
wpan

-
wpan —  IEEE 802.15.4 (WPAN) MAC Settings

+
wpan — IEEE 802.15.4 (WPAN) MAC Settings

 		
 
 

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

-
Table 93. 

+
Table 95. 

 
diff --git a/docs/api/html/spec.html b/docs/api/html/spec.html
index 8de008d9..a4ec537b 100644
--- a/docs/api/html/spec.html
+++ b/docs/api/html/spec.html
@@ -78,6 +78,9 @@
 org.freedesktop.NetworkManager.Device.Infiniband — Infiniband Device.

+org.freedesktop.NetworkManager.Device.Loopback — Loopback Device.
+

+

 org.freedesktop.NetworkManager.Device.Lowpan — 6LoWPAN Device.
 

-- 
cgit 1.3.0-6-gf8a5