From 70e18d99b8e3e77bb37e218d7ac582130156f8ef Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 25 Jan 2024 09:46:18 +0100 Subject: New upstream version 1.45.90 --- CONTRIBUTING.md | 68 +- Makefile.am | 43 +- Makefile.in | 180 +- NEWS | 35 +- README.md | 80 +- configure | 376 +- configure.ac | 19 +- data/NetworkManager-dispatcher.service.in | 1 + ...rkManager-wait-online-systemd-pre200.service.in | 15 - data/meson.build | 7 +- docs/api/Makefile.am | 1 + docs/api/Makefile.in | 4 +- ...-org.freedesktop.NetworkManager.AccessPoint.xml | 11 + ...s-org.freedesktop.NetworkManager.Device.Hsr.xml | 83 + ...us-org.freedesktop.NetworkManager.IP4Config.xml | 16 +- ...us-org.freedesktop.NetworkManager.IP6Config.xml | 9 +- docs/api/html/NetworkManager-dispatcher.html | 15 +- docs/api/html/NetworkManager.conf.html | 23 +- docs/api/html/NetworkManager.devhelp2 | 14 +- docs/api/html/NetworkManager.html | 40 +- docs/api/html/ch01.html | 3 + ...org.freedesktop.NetworkManager.AccessPoint.html | 11 + ....freedesktop.NetworkManager.Device.Generic.html | 4 +- ...-org.freedesktop.NetworkManager.Device.Hsr.html | 113 + ...freedesktop.NetworkManager.Device.IPTunnel.html | 6 +- ...eedesktop.NetworkManager.Device.Infiniband.html | 2 +- ...g.freedesktop.NetworkManager.Device.Lowpan.html | 2 +- ...g.freedesktop.NetworkManager.Device.Macsec.html | 2 +- ....freedesktop.NetworkManager.Device.Macvlan.html | 2 +- ...rg.freedesktop.NetworkManager.Device.Modem.html | 2 +- ...freedesktop.NetworkManager.Device.OlpcMesh.html | 2 +- ...reedesktop.NetworkManager.Device.OvsBridge.html | 2 +- ....freedesktop.NetworkManager.Device.OvsPort.html | 2 +- ...org.freedesktop.NetworkManager.Device.Team.html | 2 +- ...-org.freedesktop.NetworkManager.Device.Tun.html | 2 +- ...org.freedesktop.NetworkManager.Device.Veth.html | 2 +- ...org.freedesktop.NetworkManager.Device.Vlan.html | 2 +- ...-org.freedesktop.NetworkManager.Device.Vrf.html | 2 +- ...rg.freedesktop.NetworkManager.Device.Vxlan.html | 2 +- ....freedesktop.NetworkManager.Device.WifiP2P.html | 4 +- ...reedesktop.NetworkManager.Device.WireGuard.html | 2 +- ...rg.freedesktop.NetworkManager.Device.Wired.html | 2 +- ...freedesktop.NetworkManager.Device.Wireless.html | 4 +- ...org.freedesktop.NetworkManager.Device.Wpan.html | 2 +- ...s-org.freedesktop.NetworkManager.IP4Config.html | 20 +- ...s-org.freedesktop.NetworkManager.IP6Config.html | 11 +- docs/api/html/index.html | 20 +- docs/api/html/ix01.html | 354 +- docs/api/html/license.html | 11 +- docs/api/html/nm-dbus-types.html | 34 +- docs/api/html/nm-openvswitch.html | 4 +- docs/api/html/nm-settings-dbus.html | 191 +- docs/api/html/nm-settings-ifcfg-rh.html | 56 +- docs/api/html/nm-settings-keyfile.html | 67 +- docs/api/html/nm-settings-nmcli.html | 2009 +++- docs/api/html/nmcli-examples.html | 4 +- docs/api/html/ref-dbus-devices.html | 3 + docs/api/html/ref-settings.html | 3 + docs/api/html/settings-6lowpan.html | 2 +- docs/api/html/settings-802-11-olpc-mesh.html | 2 +- .../html/settings-802-11-wireless-security.html | 8 +- docs/api/html/settings-802-11-wireless.html | 16 +- docs/api/html/settings-802-1x.html | 2 +- docs/api/html/settings-802-3-ethernet.html | 4 +- docs/api/html/settings-adsl.html | 2 +- docs/api/html/settings-bluetooth.html | 2 +- docs/api/html/settings-bond-port.html | 2 +- docs/api/html/settings-bond.html | 2 +- docs/api/html/settings-bridge-port.html | 2 +- docs/api/html/settings-bridge.html | 2 +- docs/api/html/settings-cdma.html | 2 +- docs/api/html/settings-connection.html | 24 +- docs/api/html/settings-dcb.html | 18 +- docs/api/html/settings-dummy.html | 2 +- docs/api/html/settings-ethtool.html | 2 +- docs/api/html/settings-generic.html | 2 +- docs/api/html/settings-gsm.html | 6 +- docs/api/html/settings-hostname.html | 16 +- docs/api/html/settings-hsr.html | 89 + docs/api/html/settings-infiniband.html | 2 +- docs/api/html/settings-ip-tunnel.html | 8 +- docs/api/html/settings-ipv4.html | 22 +- docs/api/html/settings-ipv6.html | 20 +- docs/api/html/settings-link.html | 8 +- docs/api/html/settings-loopback.html | 4 +- docs/api/html/settings-macsec.html | 2 +- docs/api/html/settings-macvlan.html | 2 +- docs/api/html/settings-match.html | 2 +- docs/api/html/settings-ovs-bridge.html | 2 +- docs/api/html/settings-ovs-dpdk.html | 2 +- docs/api/html/settings-ovs-external-ids.html | 4 +- docs/api/html/settings-ovs-interface.html | 2 +- docs/api/html/settings-ovs-other-config.html | 4 +- docs/api/html/settings-ovs-patch.html | 2 +- docs/api/html/settings-ovs-port.html | 2 +- docs/api/html/settings-ppp.html | 2 +- docs/api/html/settings-pppoe.html | 2 +- docs/api/html/settings-proxy.html | 4 +- docs/api/html/settings-serial.html | 2 +- docs/api/html/settings-sriov.html | 8 +- docs/api/html/settings-tc.html | 2 +- docs/api/html/settings-team-port.html | 2 +- docs/api/html/settings-team.html | 2 +- docs/api/html/settings-tun.html | 4 +- docs/api/html/settings-user.html | 2 +- docs/api/html/settings-veth.html | 4 +- docs/api/html/settings-vlan.html | 4 +- docs/api/html/settings-vpn.html | 2 +- docs/api/html/settings-vrf.html | 2 +- docs/api/html/settings-vxlan.html | 2 +- docs/api/html/settings-wifi-p2p.html | 2 +- docs/api/html/settings-wimax.html | 2 +- docs/api/html/settings-wireguard.html | 2 +- docs/api/html/settings-wpan.html | 2 +- docs/api/html/spec.html | 3 + docs/api/network-manager-docs.xml | 20 +- docs/api/settings-spec.xml | 102 +- docs/api/version.xml | 2 +- docs/libnm/Makefile.am | 1 - docs/libnm/Makefile.in | 4 - docs/libnm/html/NMAccessPoint.html | 60 + docs/libnm/html/NMClient.html | 24 +- docs/libnm/html/NMDevice.html | 1 + docs/libnm/html/NMDeviceGeneric.html | 4 +- docs/libnm/html/NMDeviceHsr.html | 398 + docs/libnm/html/NMDeviceIPTunnel.html | 61 + docs/libnm/html/NMDeviceInfiniband.html | 4 +- docs/libnm/html/NMSettingConnection.html | 100 + docs/libnm/html/NMSettingEthtool.html | 74 + docs/libnm/html/NMSettingHostname.html | 4 +- docs/libnm/html/NMSettingHsr.html | 274 + docs/libnm/html/NMSettingIPConfig.html | 22 + docs/libnm/html/NMSettingInfiniband.html | 4 +- docs/libnm/html/NMSettingMatch.html | 4 + docs/libnm/html/NMSettingWired.html | 1 + docs/libnm/html/NMSettingWireless.html | 1 + docs/libnm/html/api-index-full.html | 228 + docs/libnm/html/ch03.html | 3 + docs/libnm/html/ch04.html | 3 + docs/libnm/html/index.html | 20 +- docs/libnm/html/libnm-nm-dbus-interface.html | 26 +- docs/libnm/html/libnm-nm-ethtool-utils.html | 50 + docs/libnm/html/libnm-nm-utils.html | 50 +- docs/libnm/html/libnm-nm-version-macros.html | 14 +- docs/libnm/html/libnm-nm-version.html | 32 + docs/libnm/html/libnm.devhelp2 | 62 +- docs/libnm/html/license.html | 10 +- docs/libnm/html/object-tree.html | 2 + docs/libnm/html/usage.html | 2 +- docs/libnm/libnm-docs.xml | 20 +- docs/libnm/libnm-sections.txt | 71 + docs/libnm/libnm.types | 2 + docs/libnm/meson.build | 5 +- docs/libnm/version.xml | 2 +- examples/python/gi/gmaincontext.py | 4 +- examples/python/gi/nm-add-connection2.py | 1 - examples/python/gi/nm-up-many.py | 10 - examples/python/gi/nm-update2.py | 1 - examples/python/gi/nm-wg-set | 2 - examples/python/gi/ovs-external-ids.py | 9 - introspection/meson.build | 1 + .../org.freedesktop.NetworkManager.AccessPoint.xml | 7 + .../org.freedesktop.NetworkManager.Device.Hsr.xml | 51 + .../org.freedesktop.NetworkManager.IP4Config.xml | 16 +- .../org.freedesktop.NetworkManager.IP6Config.xml | 9 +- m4/attributes.m4 | 4 +- m4/vapigen.m4 | 3 +- man/NetworkManager-dispatcher.8 | 15 +- man/NetworkManager-dispatcher.xml | 28 +- man/NetworkManager-wait-online.service.8 | 4 +- man/NetworkManager-wait-online.service.xml | 13 +- man/NetworkManager.8 | 39 +- man/NetworkManager.conf.5 | 27 +- man/NetworkManager.conf.xml | 41 +- man/NetworkManager.xml | 51 +- man/meson.build | 21 +- man/nm-cloud-setup.8 | 6 +- man/nm-cloud-setup.xml | 13 +- man/nm-initrd-generator.8 | 6 +- man/nm-initrd-generator.xml | 13 +- man/nm-online.1 | 6 +- man/nm-online.xml | 13 +- man/nm-openvswitch.7 | 10 +- man/nm-openvswitch.xml | 17 +- man/nm-settings-dbus.5 | 196 +- man/nm-settings-dbus.xml | 100 +- man/nm-settings-ifcfg-rh.5 | 66 +- man/nm-settings-ifcfg-rh.xml | 12 +- man/nm-settings-ifcfg-rh.xsl | 4 +- man/nm-settings-keyfile.5 | 71 +- man/nm-settings-keyfile.xml | 47 +- man/nm-settings-keyfile.xsl | 37 +- man/nm-settings-nmcli.5 | 1657 +++- man/nm-settings-nmcli.xml | 1303 ++- man/nm-settings-nmcli.xsl | 10 + man/nmcli-examples.7 | 10 +- man/nmcli-examples.xml | 17 +- man/nmcli.1 | 6 +- man/nmcli.xml | 13 +- man/nmtui.1 | 6 +- man/nmtui.xml | 13 +- meson.build | 15 +- po/NetworkManager.pot | 3724 ++++---- po/POTFILES.in | 4 +- po/as.gmo | Bin 111982 -> 111650 bytes po/bn_IN.gmo | Bin 114327 -> 113946 bytes po/ca.gmo | Bin 164078 -> 163821 bytes po/de.gmo | Bin 296483 -> 278680 bytes po/el.gmo | Bin 99395 -> 99248 bytes po/es.gmo | Bin 303631 -> 285727 bytes po/fr.gmo | Bin 366518 -> 348513 bytes po/gd.gmo | Bin 16373 -> 16260 bytes po/hi.gmo | Bin 105958 -> 105604 bytes po/hr.gmo | Bin 342310 -> 318634 bytes po/hu.gmo | Bin 249744 -> 249481 bytes po/id.gmo | Bin 315841 -> 298705 bytes po/id.po | 2 +- po/it.gmo | Bin 312545 -> 294819 bytes po/ja.gmo | Bin 391487 -> 372090 bytes po/kn.gmo | Bin 123601 -> 123227 bytes po/ko.gmo | Bin 376266 -> 354599 bytes po/mr.gmo | Bin 108522 -> 108181 bytes po/pl.gmo | Bin 209480 -> 209230 bytes po/pt_BR.gmo | Bin 332270 -> 314729 bytes po/ro.gmo | Bin 109161 -> 109044 bytes po/ru.gmo | Bin 631658 -> 638646 bytes po/ru.po | 3496 +++---- po/sv.gmo | Bin 260319 -> 468670 bytes po/sv.po | 9614 +++++++++++--------- po/ta.gmo | Bin 159070 -> 158693 bytes po/te.gmo | Bin 118645 -> 118300 bytes po/tr.gmo | Bin 115211 -> 114972 bytes po/uk.gmo | Bin 621694 -> 641348 bytes po/uk.po | 4309 ++++----- po/zh_CN.gmo | Bin 351667 -> 327109 bytes po/zh_CN.po | 2 +- po/zh_TW.gmo | Bin 281026 -> 264820 bytes src/contrib/nm-vpn-editor-plugin-call.h | 2 +- src/core/NetworkManagerUtils.c | 35 +- src/core/devices/adsl/nm-device-adsl.c | 6 +- src/core/devices/bluetooth/nm-device-bt.c | 6 +- src/core/devices/nm-device-6lowpan.c | 6 +- src/core/devices/nm-device-bond.c | 25 +- src/core/devices/nm-device-bridge.c | 195 +- src/core/devices/nm-device-dummy.c | 8 +- src/core/devices/nm-device-ethernet.c | 42 +- src/core/devices/nm-device-factory.c | 1 + src/core/devices/nm-device-generic.c | 6 +- src/core/devices/nm-device-hsr.c | 287 + src/core/devices/nm-device-hsr.h | 31 + src/core/devices/nm-device-infiniband.c | 12 +- src/core/devices/nm-device-tun.c | 8 +- src/core/devices/nm-device-vlan.c | 12 +- src/core/devices/nm-device-vxlan.c | 6 +- src/core/devices/nm-device-wireguard.c | 4 +- src/core/devices/nm-device-wpan.c | 8 +- src/core/devices/nm-device.c | 535 +- src/core/devices/ovs/nm-device-ovs-bridge.c | 6 +- src/core/devices/ovs/nm-device-ovs-interface.c | 340 +- src/core/devices/ovs/nm-device-ovs-port.c | 6 +- src/core/devices/team/nm-device-team.c | 22 +- src/core/devices/wifi/nm-device-iwd-p2p.c | 6 +- src/core/devices/wifi/nm-device-olpc-mesh.c | 6 +- src/core/devices/wifi/nm-device-wifi-p2p.c | 89 +- src/core/devices/wifi/nm-device-wifi.c | 35 +- src/core/devices/wifi/nm-iwd-manager.c | 9 +- src/core/devices/wifi/nm-wifi-ap.c | 41 + src/core/devices/wifi/nm-wifi-ap.h | 3 + src/core/devices/wifi/nm-wifi-common.c | 11 +- src/core/dhcp/nm-dhcp-client.c | 2 +- src/core/dhcp/nm-dhcp-client.h | 3 + src/core/dhcp/nm-dhcp-dhclient-utils.c | 12 +- src/core/dhcp/nm-dhcp-dhclient-utils.h | 1 + src/core/dhcp/nm-dhcp-dhclient.c | 125 +- src/core/dhcp/nm-dhcp-dhcpcd.c | 2 +- src/core/dhcp/nm-dhcp-helper.c | 4 +- src/core/dhcp/nm-dhcp-nettools.c | 40 +- src/core/dhcp/tests/test-dhcp-dhclient.c | 100 +- src/core/dns/nm-dns-manager.c | 42 +- src/core/dns/nm-dns-manager.h | 2 + src/core/dnsmasq/nm-dnsmasq-utils.c | 4 +- src/core/main-utils.c | 5 +- src/core/meson.build | 1 + src/core/ndisc/nm-fake-ndisc.c | 2 +- src/core/ndisc/nm-lndp-ndisc.c | 2 +- src/core/ndisc/nm-ndisc.c | 4 +- src/core/nm-act-request.c | 13 +- src/core/nm-active-connection.c | 11 +- src/core/nm-active-connection.h | 3 +- src/core/nm-auth-utils.c | 11 +- src/core/nm-config-data.c | 4 +- src/core/nm-config.c | 8 +- src/core/nm-connectivity.c | 17 +- src/core/nm-core-utils.c | 196 +- src/core/nm-core-utils.h | 7 + src/core/nm-dbus-manager.c | 4 +- src/core/nm-dbus-utils.c | 12 + src/core/nm-dbus-utils.h | 59 +- src/core/nm-dispatcher.c | 51 +- src/core/nm-dispatcher.h | 3 + src/core/nm-ip-config.c | 121 +- src/core/nm-ip-config.h | 5 +- src/core/nm-l3-config-data.c | 62 +- src/core/nm-l3-config-data.h | 2 + src/core/nm-l3-ipv4ll.c | 68 +- src/core/nm-l3cfg.c | 442 +- src/core/nm-l3cfg.h | 4 +- src/core/nm-manager.c | 69 +- src/core/nm-netns.c | 35 +- src/core/nm-policy.c | 12 +- src/core/nm-rfkill-manager.c | 25 +- src/core/nm-rfkill-manager.h | 7 - src/core/nm-types.h | 2 +- src/core/platform/nm-fake-platform.c | 8 + src/core/platform/tests/test-common.h | 2 +- src/core/platform/tests/test-link.c | 41 +- src/core/platform/tests/test-platform-general.c | 2 +- src/core/settings/nm-settings.c | 2 +- .../plugins/ifcfg-rh/nms-ifcfg-rh-reader.c | 10 +- .../plugins/ifcfg-rh/nms-ifcfg-rh-writer.c | 43 +- .../plugins/ifcfg-rh/tests/test-ifcfg-rh.c | 19 +- .../plugins/keyfile/tests/test-keyfile-settings.c | 10 +- src/core/supplicant/nm-supplicant-interface.c | 15 +- .../supplicant/nm-supplicant-settings-verify.c | 2 +- src/core/supplicant/nm-supplicant-types.h | 8 +- src/core/tests/test-core-with-expect.c | 2 +- src/core/tests/test-core.c | 56 +- src/core/tests/test-l3cfg.c | 2 +- src/core/vpn/nm-vpn-connection.c | 3 +- src/libnm-base/nm-base.h | 34 +- src/libnm-base/nm-config-base.h | 1 - src/libnm-base/nm-ethtool-base.c | 31 +- src/libnm-base/nm-ethtool-utils-base.h | 7 + src/libnm-client-impl/libnm.ver | 22 + src/libnm-client-impl/meson.build | 117 +- src/libnm-client-impl/nm-access-point.c | 39 + src/libnm-client-impl/nm-client.c | 1 + src/libnm-client-impl/nm-dbus-helpers.h | 2 +- src/libnm-client-impl/nm-device-hsr.c | 279 + src/libnm-client-impl/nm-device-ip-tunnel.c | 39 + src/libnm-client-impl/nm-device.c | 3 + src/libnm-client-impl/nm-dhcp4-config.h | 2 +- src/libnm-client-impl/nm-dhcp6-config.h | 2 +- src/libnm-client-impl/nm-dns-manager.h | 2 +- src/libnm-client-impl/nm-ip-config.c | 2 +- src/libnm-client-impl/nm-ip4-config.h | 2 +- src/libnm-client-impl/nm-ip6-config.h | 2 +- src/libnm-client-impl/nm-libnm-utils.c | 48 +- src/libnm-client-impl/nm-libnm-utils.h | 46 +- src/libnm-client-impl/nm-object-private.h | 2 +- .../nm-remote-connection-private.h | 2 +- src/libnm-client-impl/tests/test-gir.py | 2 +- src/libnm-client-impl/tests/test-libnm.c | 4 + src/libnm-client-public/NetworkManager.h | 2 + src/libnm-client-public/meson.build | 1 + src/libnm-client-public/nm-access-point.h | 4 + src/libnm-client-public/nm-autoptr.h | 2 + src/libnm-client-public/nm-device-hsr.h | 56 + src/libnm-client-public/nm-device-ip-tunnel.h | 3 + src/libnm-client-public/nm-ethtool-utils.h | 7 + src/libnm-core-aux-extern/nm-dispatcher-api.h | 1 + src/libnm-core-aux-intern/nm-auth-subject.c | 6 +- src/libnm-core-aux-intern/nm-common-macros.h | 29 +- .../gen-metadata-nm-settings-libnm-core.xml.in | 50 + src/libnm-core-impl/meson.build | 2 +- src/libnm-core-impl/nm-connection-private.h | 2 +- src/libnm-core-impl/nm-connection.c | 75 +- src/libnm-core-impl/nm-keyfile.c | 11 +- src/libnm-core-impl/nm-meta-setting-base-impl.c | 9 + src/libnm-core-impl/nm-property-compare.c | 136 - src/libnm-core-impl/nm-property-compare.h | 16 - src/libnm-core-impl/nm-setting-6lowpan.c | 16 +- src/libnm-core-impl/nm-setting-8021x.c | 118 +- src/libnm-core-impl/nm-setting-adsl.c | 24 +- src/libnm-core-impl/nm-setting-bluetooth.c | 15 +- src/libnm-core-impl/nm-setting-bond-port.c | 4 +- src/libnm-core-impl/nm-setting-bond.c | 12 +- src/libnm-core-impl/nm-setting-bridge-port.c | 16 +- src/libnm-core-impl/nm-setting-bridge.c | 8 +- src/libnm-core-impl/nm-setting-cdma.c | 21 +- src/libnm-core-impl/nm-setting-connection.c | 470 +- src/libnm-core-impl/nm-setting-dcb.c | 16 +- src/libnm-core-impl/nm-setting-dummy.c | 3 - src/libnm-core-impl/nm-setting-ethtool.c | 31 + src/libnm-core-impl/nm-setting-generic.c | 12 - src/libnm-core-impl/nm-setting-gsm.c | 47 +- src/libnm-core-impl/nm-setting-hsr.c | 266 + src/libnm-core-impl/nm-setting-infiniband.c | 18 +- src/libnm-core-impl/nm-setting-ip-config.c | 423 +- src/libnm-core-impl/nm-setting-ip-tunnel.c | 27 +- src/libnm-core-impl/nm-setting-ip4-config.c | 116 +- src/libnm-core-impl/nm-setting-ip6-config.c | 85 +- src/libnm-core-impl/nm-setting-loopback.c | 8 +- src/libnm-core-impl/nm-setting-macsec.c | 25 +- src/libnm-core-impl/nm-setting-macvlan.c | 15 +- src/libnm-core-impl/nm-setting-match.c | 118 +- src/libnm-core-impl/nm-setting-olpc-mesh.c | 12 +- src/libnm-core-impl/nm-setting-ovs-bridge.c | 8 +- src/libnm-core-impl/nm-setting-ovs-dpdk.c | 3 +- src/libnm-core-impl/nm-setting-ovs-interface.c | 11 +- src/libnm-core-impl/nm-setting-ovs-patch.c | 3 +- src/libnm-core-impl/nm-setting-ovs-port.c | 19 +- src/libnm-core-impl/nm-setting-ppp.c | 13 +- src/libnm-core-impl/nm-setting-pppoe.c | 24 +- src/libnm-core-impl/nm-setting-private.h | 349 +- src/libnm-core-impl/nm-setting-proxy.c | 17 +- src/libnm-core-impl/nm-setting-serial.c | 12 +- src/libnm-core-impl/nm-setting-team-port.c | 16 +- src/libnm-core-impl/nm-setting-team.c | 15 +- src/libnm-core-impl/nm-setting-tun.c | 19 +- src/libnm-core-impl/nm-setting-veth.c | 3 +- src/libnm-core-impl/nm-setting-vlan.c | 44 +- src/libnm-core-impl/nm-setting-vpn.c | 19 +- src/libnm-core-impl/nm-setting-vxlan.c | 21 +- src/libnm-core-impl/nm-setting-wifi-p2p.c | 3 +- src/libnm-core-impl/nm-setting-wimax.c | 15 +- src/libnm-core-impl/nm-setting-wired.c | 60 +- src/libnm-core-impl/nm-setting-wireguard.c | 7 +- src/libnm-core-impl/nm-setting-wireless-security.c | 75 +- src/libnm-core-impl/nm-setting-wireless.c | 161 +- src/libnm-core-impl/nm-setting-wpan.c | 12 +- src/libnm-core-impl/nm-setting.c | 360 +- src/libnm-core-impl/nm-simple-connection.c | 3 - src/libnm-core-impl/nm-team-utils.c | 12 +- src/libnm-core-impl/nm-team-utils.h | 5 +- src/libnm-core-impl/nm-utils-private.h | 2 +- src/libnm-core-impl/nm-utils.c | 886 +- src/libnm-core-impl/nm-vpn-editor-plugin.c | 2 +- src/libnm-core-impl/nm-vpn-plugin-info.c | 12 +- src/libnm-core-impl/tests/meson.build | 1 - src/libnm-core-impl/tests/test-compare.c | 231 - src/libnm-core-impl/tests/test-general.c | 330 +- src/libnm-core-impl/tests/test-setting.c | 250 +- src/libnm-core-intern/nm-core-internal.h | 98 +- src/libnm-core-intern/nm-keyfile-internal.h | 2 +- src/libnm-core-intern/nm-keyfile-utils.h | 2 +- src/libnm-core-intern/nm-meta-setting-base-impl.h | 1 + src/libnm-core-public/meson.build | 3 +- src/libnm-core-public/nm-core-types.h | 1 + src/libnm-core-public/nm-dbus-interface.h | 7 +- src/libnm-core-public/nm-dbus-types.xml | 12 +- src/libnm-core-public/nm-setting-connection.h | 16 +- src/libnm-core-public/nm-setting-ethtool.h | 6 + src/libnm-core-public/nm-setting-hsr.h | 49 + src/libnm-core-public/nm-setting-ip-config.h | 3 + src/libnm-core-public/nm-utils.h | 17 +- src/libnm-core-public/nm-version-macros.h | 5 +- src/libnm-core-public/nm-version-macros.h.in | 1 + src/libnm-core-public/nm-version.h | 14 + src/libnm-glib-aux/nm-dedup-multi.h | 2 +- src/libnm-glib-aux/nm-enum-utils.c | 129 +- src/libnm-glib-aux/nm-enum-utils.h | 12 + src/libnm-glib-aux/nm-errno.c | 23 +- src/libnm-glib-aux/nm-glib.h | 380 +- src/libnm-glib-aux/nm-hash-utils.h | 29 +- src/libnm-glib-aux/nm-macros-internal.h | 26 +- src/libnm-glib-aux/nm-shared-utils.c | 304 +- src/libnm-glib-aux/nm-shared-utils.h | 367 +- src/libnm-glib-aux/nm-test-utils.h | 39 +- src/libnm-glib-aux/tests/test-shared-general.c | 286 +- src/libnm-lldp/nm-lldp-rx.c | 2 +- src/libnm-platform/nm-linux-platform.c | 148 +- src/libnm-platform/nm-platform-utils.c | 128 +- src/libnm-platform/nm-platform-utils.h | 8 + src/libnm-platform/nm-platform.c | 376 +- src/libnm-platform/nm-platform.h | 110 +- src/libnm-platform/nmp-base.h | 16 +- src/libnm-platform/nmp-object.c | 12 + src/libnm-platform/nmp-object.h | 8 + src/libnm-platform/nmp-plobj.c | 4 +- src/libnm-platform/nmp-plobj.h | 2 +- src/libnm-platform/wifi/nm-wifi-utils-nl80211.c | 113 +- src/libnm-platform/wifi/nm-wifi-utils-private.h | 5 - src/libnm-platform/wifi/nm-wifi-utils-wext.c | 16 +- src/libnm-platform/wifi/nm-wifi-utils.c | 22 - src/libnm-platform/wifi/nm-wifi-utils.h | 6 - src/libnm-std-aux/nm-linux-compat.h | 1 - src/libnm-std-aux/nm-std-aux.h | 107 +- src/libnm-std-aux/nm-std-utils.c | 40 + src/libnm-std-aux/nm-std-utils.h | 2 + .../src/libsystemd-network/sd-dhcp6-client.c | 4 +- .../sd-adapt-shared/nm-sd-adapt-shared.h | 5 - src/libnmc-base/qrcodegen.h | 2 +- src/libnmc-setting/meson.build | 15 +- src/libnmc-setting/nm-meta-setting-base-impl.c | 9 + src/libnmc-setting/nm-meta-setting-base-impl.h | 1 + src/libnmc-setting/nm-meta-setting-desc.c | 675 +- src/libnmc-setting/nm-meta-setting-desc.h | 41 +- src/libnmc-setting/settings-docs.h | 72 +- src/libnmc-setting/settings-docs.h.in | 72 +- src/libnmt-newt/nmt-newt-button-box.c | 4 +- src/libnmt-newt/nmt-newt-form.c | 4 +- src/libnmt-newt/nmt-newt-section.c | 2 +- src/libnmt-newt/nmt-newt-textbox.c | 2 +- src/libnmt-newt/nmt-newt-utils.c | 4 +- src/linux-headers/nl80211-vnd-intel.h | 106 - src/n-acd/src/n-acd-private.h | 1 + src/n-acd/src/n-acd-probe.c | 3 +- src/n-dhcp4/src/n-dhcp4-c-connection.c | 14 +- src/n-dhcp4/src/n-dhcp4-client.c | 2 +- src/nm-cloud-setup/nm-cloud-setup.service.in | 10 +- src/nm-daemon-helper/nm-daemon-helper.c | 7 +- src/nm-dispatcher/nm-dispatcher-utils.c | 8 +- src/nm-initrd-generator/nmi-cmdline-reader.c | 10 +- .../tests/test-cmdline-reader.c | 28 +- src/nm-online/nm-online.c | 2 +- src/nmcli/common.c | 2 +- src/nmcli/connections.c | 168 +- src/nmcli/devices.c | 58 +- src/nmcli/gen-metadata-nm-settings-nmcli.c | 520 +- src/nmcli/gen-metadata-nm-settings-nmcli.xml.in | 2046 +++-- src/nmcli/general.c | 84 +- src/nmcli/settings.c | 2 +- src/nmcli/utils.c | 5 +- src/nmcli/utils.h | 1 + src/nmtui/nm-editor-utils.c | 4 +- src/nmtui/nmt-8021x-fields.c | 2 +- src/nmtui/nmt-address-list.c | 2 +- src/nmtui/nmt-connect-connection-list.c | 2 +- src/nmtui/nmt-editor-grid.c | 8 +- src/nmtui/nmt-editor.c | 2 +- src/nmtui/nmt-mac-entry.c | 8 +- src/nmtui/nmt-mac-entry.h | 3 +- src/nmtui/nmt-page-bond.c | 2 +- src/nmtui/nmt-page-ethernet.c | 2 +- src/nmtui/nmt-page-vlan.c | 2 +- src/nmtui/nmt-page-wifi.c | 2 +- src/nmtui/nmt-port-list.c | 2 +- src/nmtui/nmt-route-table.c | 4 +- src/nmtui/nmtui-connect.c | 4 +- src/nmtui/nmtui-edit.c | 4 +- .../test-client.check-on-disk/test_002.expected | 48 +- .../test-client.check-on-disk/test_003.expected | 1374 +-- .../test-client.check-on-disk/test_004.expected | 4885 +++++----- .../test_daemon_not_running.expected | 10 + src/tests/client/test-client.py | 118 +- tools/generate-docs-nm-property-infos.py | 133 +- tools/generate-docs-nm-settings-docs-gir.py | 41 +- tools/generate-docs-nm-settings-docs-merge.py | 4 +- tools/run-nm-test.sh | 8 +- tools/test-cloud-meta-mock.py | 2 - tools/test-networkmanager-service.py | 17 +- valgrind.suppressions | 10 + vapi/NM-1.0.metadata | 2 + 544 files changed, 33986 insertions(+), 20656 deletions(-) delete mode 100644 data/NetworkManager-wait-online-systemd-pre200.service.in create mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml create mode 100644 docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Hsr.html create mode 100644 docs/api/html/settings-hsr.html create mode 100644 docs/libnm/html/NMDeviceHsr.html create mode 100644 docs/libnm/html/NMSettingHsr.html create mode 100644 introspection/org.freedesktop.NetworkManager.Device.Hsr.xml create mode 100644 src/core/devices/nm-device-hsr.c create mode 100644 src/core/devices/nm-device-hsr.h create mode 100644 src/libnm-client-impl/nm-device-hsr.c create mode 100644 src/libnm-client-public/nm-device-hsr.h delete mode 100644 src/libnm-core-impl/nm-property-compare.c delete mode 100644 src/libnm-core-impl/nm-property-compare.h create mode 100644 src/libnm-core-impl/nm-setting-hsr.c delete mode 100644 src/libnm-core-impl/tests/test-compare.c create mode 100644 src/libnm-core-public/nm-setting-hsr.h delete mode 100644 src/linux-headers/nl80211-vnd-intel.h create mode 100644 src/tests/client/test-client.check-on-disk/test_daemon_not_running.expected diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4896fef9..c9da4fd7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -9,13 +9,62 @@ Check out website https://networkmanager.dev and our [GNOME page](https://wiki.g The release tarballs can be found at [download.gnome.org](https://download.gnome.org/sources/NetworkManager/). -Our mailing list is networkmanager@lists.freedesktop.org ([archive](https://lists.freedesktop.org/archives/networkmanager/), -[old-archive](https://mail.gnome.org/archives/networkmanager-list/)). +Find our available communication channels at https://networkmanager.dev/community/. -Find us on IRC channel `#nm` on Libera.Chat. -Report issues and send patches via [gitlab.freedesktop.org](https://gitlab.freedesktop.org/NetworkManager/NetworkManager/) -or our mailing list. +Report issues +------------- + +Report issues or feature requests in our [Gitlab's issue tracker](https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues) +or our maling list. + +For bug reports usually NetworkManager's logs will be needed to understand the +problem. Attach the full logs to the issue. For WiFi related issues, attach also +the logs from wpa_supplicant, or iwd if you are using it (i.e. +`journalctl -u NetworkManager -u wpa_supplicant`). + +To get more useful logs, increase the log level as explained in +["logging SECTION" in NetworkManager.conf](https://networkmanager.dev/docs/api/latest/NetworkManager.conf.html). + +Logfiles contain no passwords and little sensitive information, but please +check before posting the file online. The script [anonymize-logs.py](contrib/scripts/anonymize-logs.py) +can do some basic data anonymization but makes a bit harder to analyze the logs +and you still need to review them. You can also personally hand over the logfile +to a NM developer to treat it confidential. + + +Contribute +---------- + +Send patches to our repository at [gitlab.freedesktop.org](https://gitlab.freedesktop.org/NetworkManager/NetworkManager/). +If you are willing to contribute, please read these guidelines first: + +- Find bugs or features to work on in our [Gitlab's issue tracker](https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues). + +- Work on any issue you want, but please put a comment to indicate that you are + willing to work on it so others don't do the same work in parallel, or to + check whether anyone is already doing so. + +- Issues marked as `help-wanted` are those where the NetworkManager developers + are explicitly asking for contributors' help, probably due to lack of capacity + to work on it. + +- Issues marked as `good-first-issue` indicate that they are probably quite + simple fixes, well suited for first time contributors. + +- Contributions for features or bugs not reported in the issue tracker are also + welcome, but if they require a high amount of work, it is always better to + open an issue explaining what you intend to do first. That way, you won't + waste your valuable time if your idea doesn't fit well into the project or a + different approach would be desirable. + +- Reference related issues in your Merge Request description, and if the issue + gets resolved with it, indicate it with a line `Resolves: https://issue-url`. + Please use full URLs because they are clickable both from the web UI and from + the terminal. + +- Read the rest of this document to learn about the code style, code + organization, tests and other useful stuff. Documentation @@ -49,7 +98,7 @@ Coding Style The formatting is automated using [clang-format](https://clang.llvm.org/docs/ClangFormat.html). Run `./contrib/scripts/nm-code-format.sh -i` ([[1]](contrib/scripts/nm-code-format.sh)) to reformat -the code or run `clang-format` directly. +the code or run `clang-format` directly. Pass `--help` for the list of options. As the generated format depends on the version of clang-format, you need to use the correct clang-format version. That is basically the version that our [gitlab-ci @@ -58,6 +107,7 @@ for the "check-tree" test. This is the version from a recent Fedora installation You may also run `./contrib/scripts/nm-code-format-container.sh` which uses a Fedora container with podman and the correct version of clang-format. +This accepts the same arguments as `./contrib/scripts/nm-code-format.sh`. You are welcome to not bother and open a merge request with wrong formatting, but note that we then will automatically adjust your contribution before @@ -217,6 +267,7 @@ Code Structure `./tools`- tools for generating the intermediate files or merging the file. + Cscope/ctags --------------------------- @@ -419,6 +470,7 @@ To resync our local notes use: ``` $ git fetch origin refs/notes/bugs:refs/notes/bugs -f ``` -### Testing NetworkManager with nm-in-container script. -See [the readme](tools/nm-in-container/README.md) for details. +### Testing NetworkManager with nm-in-container or nm-in-vm scripts. + +See [the readme](tools/nm-guest-data/README.md) for details. diff --git a/Makefile.am b/Makefile.am index 1e091996..4a4ea616 100644 --- a/Makefile.am +++ b/Makefile.am @@ -649,7 +649,6 @@ src_libnm_platform_libnm_platform_la_SOURCES = \ \ src/linux-headers/ethtool.h \ src/linux-headers/mptcp.h \ - src/linux-headers/nl80211-vnd-intel.h \ src/linux-headers/nl802154.h \ \ src/nm-compat-headers/linux/if_addr.h \ @@ -1022,6 +1021,8 @@ introspection_sources = \ introspection/org.freedesktop.NetworkManager.Device.Dummy.h \ introspection/org.freedesktop.NetworkManager.Device.Generic.c \ introspection/org.freedesktop.NetworkManager.Device.Generic.h \ + introspection/org.freedesktop.NetworkManager.Device.Hsr.c \ + introspection/org.freedesktop.NetworkManager.Device.Hsr.h \ introspection/org.freedesktop.NetworkManager.Device.IPTunnel.c \ introspection/org.freedesktop.NetworkManager.Device.IPTunnel.h \ introspection/org.freedesktop.NetworkManager.Device.Infiniband.c \ @@ -1113,6 +1114,7 @@ DBUS_INTERFACE_DOCS = \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Dummy.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Generic.xml \ + docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Loopback.xml \ @@ -1182,6 +1184,7 @@ dbusinterfaces_DATA = \ introspection/org.freedesktop.NetworkManager.Device.Bridge.xml \ introspection/org.freedesktop.NetworkManager.Device.Dummy.xml \ introspection/org.freedesktop.NetworkManager.Device.Generic.xml \ + introspection/org.freedesktop.NetworkManager.Device.Hsr.xml \ introspection/org.freedesktop.NetworkManager.Device.IPTunnel.xml \ introspection/org.freedesktop.NetworkManager.Device.Infiniband.xml \ introspection/org.freedesktop.NetworkManager.Device.Loopback.xml \ @@ -1261,6 +1264,7 @@ src_libnm_core_impl_lib_h_pub_real = \ src/libnm-core-public/nm-setting-generic.h \ src/libnm-core-public/nm-setting-gsm.h \ src/libnm-core-public/nm-setting-hostname.h \ + src/libnm-core-public/nm-setting-hsr.h \ src/libnm-core-public/nm-setting-infiniband.h \ src/libnm-core-public/nm-setting-ip-config.h \ src/libnm-core-public/nm-setting-ip-tunnel.h \ @@ -1316,7 +1320,6 @@ src_libnm_core_public_mkenums_h = \ src_libnm_core_impl_lib_h_priv = \ src/libnm-core-impl/nm-connection-private.h \ src/libnm-core-impl/nm-default-libnm-core.h \ - src/libnm-core-impl/nm-property-compare.h \ src/libnm-core-impl/nm-setting-private.h \ src/libnm-core-impl/nm-team-utils.h \ src/libnm-core-impl/nm-utils-private.h \ @@ -1343,6 +1346,7 @@ src_libnm_core_impl_lib_c_settings_real = \ src/libnm-core-impl/nm-setting-generic.c \ src/libnm-core-impl/nm-setting-gsm.c \ src/libnm-core-impl/nm-setting-hostname.c \ + src/libnm-core-impl/nm-setting-hsr.c \ src/libnm-core-impl/nm-setting-infiniband.c \ src/libnm-core-impl/nm-setting-ip-config.c \ src/libnm-core-impl/nm-setting-ip-tunnel.c \ @@ -1391,7 +1395,6 @@ src_libnm_core_impl_lib_c_real = \ src/libnm-core-impl/nm-keyfile-utils.c \ src/libnm-core-impl/nm-keyfile.c \ src/libnm-core-impl/nm-meta-setting-base-impl.c \ - src/libnm-core-impl/nm-property-compare.c \ src/libnm-core-impl/nm-setting.c \ src/libnm-core-impl/nm-simple-connection.c \ src/libnm-core-impl/nm-team-utils.c \ @@ -1597,7 +1600,6 @@ EXTRA_DIST += \ ############################################################################### check_programs += \ - src/libnm-core-impl/tests/test-compare \ src/libnm-core-impl/tests/test-crypto \ src/libnm-core-impl/tests/test-general \ src/libnm-core-impl/tests/test-keyfile \ @@ -1626,7 +1628,6 @@ src_libnm_core_impl_tests_cppflags = \ $(SANITIZER_EXEC_CFLAGS) \ $(NULL) -src_libnm_core_impl_tests_test_compare_CPPFLAGS = $(src_libnm_core_impl_tests_cppflags) src_libnm_core_impl_tests_test_crypto_CPPFLAGS = $(src_libnm_core_impl_tests_cppflags) src_libnm_core_impl_tests_test_general_CPPFLAGS = $(src_libnm_core_impl_tests_cppflags) src_libnm_core_impl_tests_test_keyfile_CPPFLAGS = $(src_libnm_core_impl_tests_cppflags) @@ -1663,7 +1664,6 @@ src_libnm_core_impl_tests_ldflags = \ $(SANITIZER_EXEC_LDFLAGS) \ $(NULL) -src_libnm_core_impl_tests_test_compare_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_crypto_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_general_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_keyfile_LDADD = $(src_libnm_core_impl_tests_ldadd) @@ -1671,7 +1671,6 @@ src_libnm_core_impl_tests_test_secrets_LDADD = $(src_libnm_core_impl_tests_ldadd src_libnm_core_impl_tests_test_setting_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_settings_defaults_LDADD = $(src_libnm_core_impl_tests_ldadd) -src_libnm_core_impl_tests_test_compare_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) src_libnm_core_impl_tests_test_crypto_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) src_libnm_core_impl_tests_test_general_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) src_libnm_core_impl_tests_test_keyfile_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) @@ -1679,7 +1678,6 @@ src_libnm_core_impl_tests_test_secrets_LDFLAGS = $(src_libnm_core_impl_tests_ldf src_libnm_core_impl_tests_test_setting_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) src_libnm_core_impl_tests_test_settings_defaults_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) -$(src_libnm_core_impl_tests_test_compare_OBJECTS): $(src_libnm_core_public_mkenums_h) $(src_libnm_core_impl_tests_test_crypto_OBJECTS): $(src_libnm_core_public_mkenums_h) $(src_libnm_core_impl_tests_test_general_OBJECTS): $(src_libnm_core_public_mkenums_h) $(src_libnm_core_impl_tests_test_keyfile_OBJECTS): $(src_libnm_core_public_mkenums_h) @@ -1742,6 +1740,7 @@ libnm_lib_h_pub_real = \ src/libnm-client-public/nm-device-dummy.h \ src/libnm-client-public/nm-device-ethernet.h \ src/libnm-client-public/nm-device-generic.h \ + src/libnm-client-public/nm-device-hsr.h \ src/libnm-client-public/nm-device-infiniband.h \ src/libnm-client-public/nm-device-ip-tunnel.h \ src/libnm-client-public/nm-device-loopback.h \ @@ -1813,6 +1812,7 @@ libnm_lib_c_real = \ src/libnm-client-impl/nm-device-dummy.c \ src/libnm-client-impl/nm-device-ethernet.c \ src/libnm-client-impl/nm-device-generic.c \ + src/libnm-client-impl/nm-device-hsr.c \ src/libnm-client-impl/nm-device-infiniband.c \ src/libnm-client-impl/nm-device-ip-tunnel.c \ src/libnm-client-impl/nm-device-loopback.c \ @@ -2042,7 +2042,10 @@ libnm_noinst_data = \ src/libnm-client-impl/nm-property-infos-ifcfg-rh.xml \ src/libnm-client-impl/nm-property-infos-keyfile.xml \ src/libnm-client-impl/nm-property-infos-nmcli.xml \ - src/libnm-client-impl/nm-settings-docs-gir.xml \ + src/libnm-client-impl/nm-settings-docs-gir-dbus.xml \ + src/libnm-client-impl/nm-settings-docs-gir-ifcfg-rh.xml \ + src/libnm-client-impl/nm-settings-docs-gir-keyfile.xml \ + src/libnm-client-impl/nm-settings-docs-gir-nmcli.xml \ src/libnmc-setting/settings-docs-input.xml \ $(NULL) @@ -2088,7 +2091,7 @@ endif libnm_docs_sources = $(src_libnm_core_impl_lib_c_settings_real) -src/libnm-client-impl/nm-property-infos-%.xml: tools/generate-docs-nm-property-infos.py src/libnm-core-impl/libnm-core-impl.la $(libnm_docs_sources) +src/libnm-client-impl/nm-property-infos-%.xml: tools/generate-docs-nm-property-infos.py src/libnm-core-impl/libnm-core-impl.la src/libnm-client-impl/NM-1.0.gir $(libnm_docs_sources) $(AM_V_GEN) \ "$(PYTHON)" \ $(srcdir)/tools/generate-docs-nm-property-infos.py \ @@ -2096,7 +2099,7 @@ src/libnm-client-impl/nm-property-infos-%.xml: tools/generate-docs-nm-property-i $@ \ $(wordlist 3,1000,$^) -src/libnm-client-impl/nm-settings-docs-gir.xml: tools/generate-docs-nm-settings-docs-gir.py src/libnm-client-impl/NM-1.0.gir src/libnm-client-impl/NM-1.0.typelib src/libnm-client-impl/libnm.la $(libnm_docs_sources) +src/libnm-client-impl/nm-settings-docs-gir-%.xml: tools/generate-docs-nm-settings-docs-gir.py src/libnm-client-impl/NM-1.0.gir src/libnm-client-impl/NM-1.0.typelib src/libnm-client-impl/libnm.la $(libnm_docs_sources) $(AM_V_GEN) \ export GI_TYPELIB_PATH=$(abs_builddir)/src/libnm-client-impl$${GI_TYPELIB_PATH:+:$$GI_TYPELIB_PATH}; \ export LD_LIBRARY_PATH=$(abs_builddir)/src/libnm-client-impl/.libs$${LD_LIBRARY_PATH:+:$$LD_LIBRARY_PATH}; \ @@ -2104,9 +2107,10 @@ src/libnm-client-impl/nm-settings-docs-gir.xml: tools/generate-docs-nm-settings- "$(PYTHON)" \ $(srcdir)/tools/generate-docs-nm-settings-docs-gir.py \ --gir $(builddir)/src/libnm-client-impl/NM-1.0.gir \ - --output $@ + --output $@ \ + --target $(patsubst nm-settings-docs-gir-%.xml,%,$(notdir $@)) -man/nm-settings-docs-nmcli.xml: src/nmcli/gen-metadata-nm-settings-nmcli.xml src/libnm-client-impl/nm-property-infos-nmcli.xml src/libnm-client-impl/nm-settings-docs-gir.xml tools/generate-docs-nm-settings-docs-merge.py man/common.ent +man/nm-settings-docs-nmcli.xml: src/nmcli/gen-metadata-nm-settings-nmcli.xml src/libnm-client-impl/nm-property-infos-nmcli.xml src/libnm-client-impl/nm-settings-docs-gir-nmcli.xml tools/generate-docs-nm-settings-docs-merge.py man/common.ent $(AM_V_GEN) \ "$(PYTHON)" \ "$(srcdir)/tools/generate-docs-nm-settings-docs-merge.py" \ @@ -2115,10 +2119,10 @@ man/nm-settings-docs-nmcli.xml: src/nmcli/gen-metadata-nm-settings-nmcli.xml src "$<" \ $(wordlist 1,3,$^) -src/libnmc-setting/settings-docs-input.xml: src/libnm-client-impl/nm-property-infos-nmcli.xml src/libnm-client-impl/nm-settings-docs-gir.xml tools/generate-docs-nm-settings-docs-merge.py +src/libnmc-setting/settings-docs-input.xml: src/libnm-client-impl/nm-property-infos-nmcli.xml src/libnm-client-impl/nm-settings-docs-gir-nmcli.xml tools/generate-docs-nm-settings-docs-merge.py $(AM_V_GEN) "$(PYTHON)" $(srcdir)/tools/generate-docs-nm-settings-docs-merge.py $@ $(wordlist 1,2,$^) -man/nm-settings-docs-%.xml: src/libnm-client-impl/nm-property-infos-%.xml src/libnm-client-impl/nm-settings-docs-gir.xml tools/generate-docs-nm-settings-docs-merge.py man/common.ent +man/nm-settings-docs-%.xml: src/libnm-client-impl/nm-property-infos-%.xml src/libnm-client-impl/nm-settings-docs-gir-%.xml tools/generate-docs-nm-settings-docs-merge.py man/common.ent $(AM_V_GEN) "$(PYTHON)" $(srcdir)/tools/generate-docs-nm-settings-docs-merge.py $@ $(wordlist 1,2,$^) @@ -2653,6 +2657,8 @@ src_core_libNetworkManager_la_SOURCES = \ src/core/devices/nm-device-dummy.h \ src/core/devices/nm-device-ethernet.c \ src/core/devices/nm-device-ethernet.h \ + src/core/devices/nm-device-hsr.c \ + src/core/devices/nm-device-hsr.h \ src/core/devices/nm-device-infiniband.c \ src/core/devices/nm-device-infiniband.h \ src/core/devices/nm-device-ip-tunnel.c \ @@ -5523,6 +5529,7 @@ EXTRA_DIST += \ src/tests/client/test-client.check-on-disk/test_004.expected \ src/tests/client/test-client.check-on-disk/test_offline.expected \ src/tests/client/test-client.check-on-disk/test_version_warn.expected \ + src/tests/client/test-client.check-on-disk/test_daemon_not_running.expected \ \ src/tests/client/meson.build \ $(NULL) @@ -5550,13 +5557,8 @@ systemdsystemunit_DATA += \ data/NetworkManager.service: $(srcdir)/data/NetworkManager.service.in $(AM_V_GEN) $(data_edit) $< >$@ -if HAVE_SYSTEMD_200 data/NetworkManager-wait-online.service: $(srcdir)/data/NetworkManager-wait-online.service.in $(AM_V_GEN) $(data_edit) $< >$@ -else -data/NetworkManager-wait-online.service: $(srcdir)/data/NetworkManager-wait-online-systemd-pre200.service.in - $(AM_V_GEN) $(data_edit) $< >$@ -endif data/NetworkManager-dispatcher.service: $(srcdir)/data/NetworkManager-dispatcher.service.in $(AM_V_GEN) $(data_edit) $< >$@ @@ -5590,7 +5592,6 @@ EXTRA_DIST += \ data/85-nm-unmanaged.rules \ data/90-nm-thunderbolt.rules \ data/NetworkManager-dispatcher.service.in \ - data/NetworkManager-wait-online-systemd-pre200.service.in \ data/NetworkManager-wait-online.service.in \ data/NetworkManager.service.in \ data/nm-priv-helper.service.in \ diff --git a/Makefile.in b/Makefile.in index f1c5c856..6dc18a27 100644 --- a/Makefile.in +++ b/Makefile.in @@ -441,9 +441,7 @@ am__EXEEXT_4 = src/libnm-client-impl/tests/test-nm-client$(EXEEXT) \ am__EXEEXT_11 = src/libnm-platform/tests/test-nm-platform$(EXEEXT) \ src/libnm-client-aux-extern/tests/test-libnm-client-aux$(EXEEXT) \ src/libnm-glib-aux/tests/test-shared-general$(EXEEXT) \ - $(am__EXEEXT_3) \ - src/libnm-core-impl/tests/test-compare$(EXEEXT) \ - src/libnm-core-impl/tests/test-crypto$(EXEEXT) \ + $(am__EXEEXT_3) src/libnm-core-impl/tests/test-crypto$(EXEEXT) \ src/libnm-core-impl/tests/test-general$(EXEEXT) \ src/libnm-core-impl/tests/test-keyfile$(EXEEXT) \ src/libnm-core-impl/tests/test-secrets$(EXEEXT) \ @@ -650,6 +648,7 @@ am__objects_1 = introspection/libnmdbus_la-org.freedesktop.NetworkManager.Access introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Bridge.lo \ introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Dummy.lo \ introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Generic.lo \ + introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.lo \ introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.lo \ introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Infiniband.lo \ introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Loopback.lo \ @@ -940,6 +939,7 @@ am_src_core_libNetworkManager_la_OBJECTS = \ src/core/devices/libNetworkManager_la-nm-device-bridge.lo \ src/core/devices/libNetworkManager_la-nm-device-dummy.lo \ src/core/devices/libNetworkManager_la-nm-device-ethernet.lo \ + src/core/devices/libNetworkManager_la-nm-device-hsr.lo \ src/core/devices/libNetworkManager_la-nm-device-infiniband.lo \ src/core/devices/libNetworkManager_la-nm-device-ip-tunnel.lo \ src/core/devices/libNetworkManager_la-nm-device-loopback.lo \ @@ -1189,6 +1189,7 @@ am__objects_5 = \ src/libnm-client-impl/libnm_client_impl_la-nm-device-dummy.lo \ src/libnm-client-impl/libnm_client_impl_la-nm-device-ethernet.lo \ src/libnm-client-impl/libnm_client_impl_la-nm-device-generic.lo \ + src/libnm-client-impl/libnm_client_impl_la-nm-device-hsr.lo \ src/libnm-client-impl/libnm_client_impl_la-nm-device-infiniband.lo \ src/libnm-client-impl/libnm_client_impl_la-nm-device-ip-tunnel.lo \ src/libnm-client-impl/libnm_client_impl_la-nm-device-loopback.lo \ @@ -1294,6 +1295,7 @@ am__objects_8 = \ src/libnm-core-impl/libnm_core_impl_la-nm-setting-generic.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-setting-gsm.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-setting-hostname.lo \ + src/libnm-core-impl/libnm_core_impl_la-nm-setting-hsr.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-setting-infiniband.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-setting-ip-config.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-setting-ip-tunnel.lo \ @@ -1340,7 +1342,6 @@ am__objects_9 = $(am__objects_8) \ src/libnm-core-impl/libnm_core_impl_la-nm-keyfile-utils.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-keyfile.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-meta-setting-base-impl.lo \ - src/libnm-core-impl/libnm_core_impl_la-nm-property-compare.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-setting.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-simple-connection.lo \ src/libnm-core-impl/libnm_core_impl_la-nm-team-utils.lo \ @@ -1476,7 +1477,6 @@ src_libnm_platform_libnm_platform_la_DEPENDENCIES = \ $(am__DEPENDENCIES_1) am__src_libnm_platform_libnm_platform_la_SOURCES_DIST = \ src/linux-headers/ethtool.h src/linux-headers/mptcp.h \ - src/linux-headers/nl80211-vnd-intel.h \ src/linux-headers/nl802154.h \ src/nm-compat-headers/linux/if_addr.h \ src/libnm-platform/nm-linux-platform.c \ @@ -2207,10 +2207,10 @@ src_libnm_core_impl_gen_metadata_nm_settings_libnm_core_LINK = \ $(LIBTOOLFLAGS) --mode=link $(CCLD) $(AM_CFLAGS) $(CFLAGS) \ $(src_libnm_core_impl_gen_metadata_nm_settings_libnm_core_LDFLAGS) \ $(LDFLAGS) -o $@ -src_libnm_core_impl_tests_test_compare_SOURCES = \ - src/libnm-core-impl/tests/test-compare.c -src_libnm_core_impl_tests_test_compare_OBJECTS = \ - src/libnm-core-impl/tests/test_compare-test-compare.$(OBJEXT) +src_libnm_core_impl_tests_test_crypto_SOURCES = \ + src/libnm-core-impl/tests/test-crypto.c +src_libnm_core_impl_tests_test_crypto_OBJECTS = \ + src/libnm-core-impl/tests/test_crypto-test-crypto.$(OBJEXT) am__DEPENDENCIES_6 = \ src/libnm-core-aux-extern/libnm-core-aux-extern.la \ src/libnm-core-impl/libnm-core-impl.la \ @@ -2222,17 +2222,6 @@ am__DEPENDENCIES_6 = \ src/libnm-glib-aux/libnm-glib-aux.la \ src/libnm-std-aux/libnm-std-aux.la \ src/c-siphash/libc-siphash.la $(am__DEPENDENCIES_1) -src_libnm_core_impl_tests_test_compare_DEPENDENCIES = \ - $(am__DEPENDENCIES_6) -src_libnm_core_impl_tests_test_compare_LINK = $(LIBTOOL) $(AM_V_lt) \ - --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=link \ - $(CCLD) $(AM_CFLAGS) $(CFLAGS) \ - $(src_libnm_core_impl_tests_test_compare_LDFLAGS) $(LDFLAGS) \ - -o $@ -src_libnm_core_impl_tests_test_crypto_SOURCES = \ - src/libnm-core-impl/tests/test-crypto.c -src_libnm_core_impl_tests_test_crypto_OBJECTS = \ - src/libnm-core-impl/tests/test_crypto-test-crypto.$(OBJEXT) src_libnm_core_impl_tests_test_crypto_DEPENDENCIES = \ $(am__DEPENDENCIES_6) src_libnm_core_impl_tests_test_crypto_LINK = $(LIBTOOL) $(AM_V_lt) \ @@ -2757,6 +2746,7 @@ am__depfiles_remade = examples/C/glib/$(DEPDIR)/add_connection_gdbus-add-connect introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Bridge.Plo \ introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Dummy.Plo \ introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Generic.Plo \ + introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.Plo \ introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.Plo \ introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Infiniband.Plo \ introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Loopback.Plo \ @@ -2845,6 +2835,7 @@ am__depfiles_remade = examples/C/glib/$(DEPDIR)/add_connection_gdbus-add-connect src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-ethernet.Plo \ src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-factory.Plo \ src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-generic.Plo \ + src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-hsr.Plo \ src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-infiniband.Plo \ src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-ip-tunnel.Plo \ src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-loopback.Plo \ @@ -3003,6 +2994,7 @@ am__depfiles_remade = examples/C/glib/$(DEPDIR)/add_connection_gdbus-add-connect src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-dummy.Plo \ src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-ethernet.Plo \ src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-generic.Plo \ + src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-hsr.Plo \ src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-infiniband.Plo \ src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-ip-tunnel.Plo \ src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-loopback.Plo \ @@ -3058,7 +3050,6 @@ am__depfiles_remade = examples/C/glib/$(DEPDIR)/add_connection_gdbus-add-connect src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-keyfile-utils.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-keyfile.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-meta-setting-base-impl.Plo \ - src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-property-compare.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-6lowpan.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-8021x.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-adsl.Plo \ @@ -3075,6 +3066,7 @@ am__depfiles_remade = examples/C/glib/$(DEPDIR)/add_connection_gdbus-add-connect src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-generic.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-gsm.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hostname.Plo \ + src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hsr.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-infiniband.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-ip-config.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-ip-tunnel.Plo \ @@ -3121,7 +3113,6 @@ am__depfiles_remade = examples/C/glib/$(DEPDIR)/add_connection_gdbus-add-connect src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-utils.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-vpn-editor-plugin.Plo \ src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-vpn-plugin-info.Plo \ - src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Po \ src/libnm-core-impl/tests/$(DEPDIR)/test_crypto-test-crypto.Po \ src/libnm-core-impl/tests/$(DEPDIR)/test_general-nm-core-tests-enum-types.Po \ src/libnm-core-impl/tests/$(DEPDIR)/test_general-test-general.Po \ @@ -3498,7 +3489,6 @@ SOURCES = $(src_libnmt_newt_libnmt_newt_a_SOURCES) \ src/libnm-client-impl/tests/test-remote-settings-client.c \ src/libnm-client-impl/tests/test-secret-agent.c \ $(src_libnm_core_impl_gen_metadata_nm_settings_libnm_core_SOURCES) \ - src/libnm-core-impl/tests/test-compare.c \ src/libnm-core-impl/tests/test-crypto.c \ $(src_libnm_core_impl_tests_test_general_SOURCES) \ $(nodist_src_libnm_core_impl_tests_test_general_SOURCES) \ @@ -3627,7 +3617,6 @@ DIST_SOURCES = $(am__src_libnmt_newt_libnmt_newt_a_SOURCES_DIST) \ src/libnm-client-impl/tests/test-remote-settings-client.c \ src/libnm-client-impl/tests/test-secret-agent.c \ $(src_libnm_core_impl_gen_metadata_nm_settings_libnm_core_SOURCES) \ - src/libnm-core-impl/tests/test-compare.c \ src/libnm-core-impl/tests/test-crypto.c \ $(src_libnm_core_impl_tests_test_general_SOURCES) \ src/libnm-core-impl/tests/test-keyfile.c \ @@ -3949,7 +3938,6 @@ ACLOCAL = @ACLOCAL@ AMTAR = @AMTAR@ AM_CFLAGS = @AM_CFLAGS@ AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ -AM_TESTS_FD_REDIRECT = @AM_TESTS_FD_REDIRECT@ AR = @AR@ AUTOCONF = @AUTOCONF@ AUTOHEADER = @AUTOHEADER@ @@ -4138,8 +4126,6 @@ SELINUX_LIBS = @SELINUX_LIBS@ SET_MAKE = @SET_MAKE@ SHELL = @SHELL@ STRIP = @STRIP@ -SYSTEMD_200_CFLAGS = @SYSTEMD_200_CFLAGS@ -SYSTEMD_200_LIBS = @SYSTEMD_200_LIBS@ SYSTEMD_INHIBIT_CFLAGS = @SYSTEMD_INHIBIT_CFLAGS@ SYSTEMD_INHIBIT_LIBS = @SYSTEMD_INHIBIT_LIBS@ SYSTEMD_JOURNAL_CFLAGS = @SYSTEMD_JOURNAL_CFLAGS@ @@ -5011,10 +4997,10 @@ EXTRA_DIST = src/c-stdaux/src/c-stdaux-generic.h \ src/tests/client/test-client.check-on-disk/test_004.expected \ src/tests/client/test-client.check-on-disk/test_offline.expected \ src/tests/client/test-client.check-on-disk/test_version_warn.expected \ + src/tests/client/test-client.check-on-disk/test_daemon_not_running.expected \ src/tests/client/meson.build $(NULL) data/84-nm-drivers.rules \ data/85-nm-unmanaged.rules data/90-nm-thunderbolt.rules \ data/NetworkManager-dispatcher.service.in \ - data/NetworkManager-wait-online-systemd-pre200.service.in \ data/NetworkManager-wait-online.service.in \ data/NetworkManager.service.in data/nm-priv-helper.service.in \ data/meson.build data/nm-shared.xml data/server.conf.in \ @@ -5172,7 +5158,6 @@ man_pages_autogen = man/nm-settings-dbus.5 man/nm-settings-keyfile.5 \ check_programs = src/libnm-platform/tests/test-nm-platform \ src/libnm-client-aux-extern/tests/test-libnm-client-aux \ src/libnm-glib-aux/tests/test-shared-general $(am__append_6) \ - src/libnm-core-impl/tests/test-compare \ src/libnm-core-impl/tests/test-crypto \ src/libnm-core-impl/tests/test-general \ src/libnm-core-impl/tests/test-keyfile \ @@ -5666,7 +5651,6 @@ src_libnm_platform_libnm_platform_la_CPPFLAGS = \ src_libnm_platform_libnm_platform_la_SOURCES = \ src/linux-headers/ethtool.h src/linux-headers/mptcp.h \ - src/linux-headers/nl80211-vnd-intel.h \ src/linux-headers/nl802154.h \ src/nm-compat-headers/linux/if_addr.h \ src/libnm-platform/nm-linux-platform.c \ @@ -5942,6 +5926,8 @@ introspection_sources = \ introspection/org.freedesktop.NetworkManager.Device.Dummy.h \ introspection/org.freedesktop.NetworkManager.Device.Generic.c \ introspection/org.freedesktop.NetworkManager.Device.Generic.h \ + introspection/org.freedesktop.NetworkManager.Device.Hsr.c \ + introspection/org.freedesktop.NetworkManager.Device.Hsr.h \ introspection/org.freedesktop.NetworkManager.Device.IPTunnel.c \ introspection/org.freedesktop.NetworkManager.Device.IPTunnel.h \ introspection/org.freedesktop.NetworkManager.Device.Infiniband.c \ @@ -6032,6 +6018,7 @@ DBUS_INTERFACE_DOCS = \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Dummy.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Generic.xml \ + docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml \ docs/api/dbus-org.freedesktop.NetworkManager.Device.Loopback.xml \ @@ -6085,6 +6072,7 @@ dbusinterfaces_DATA = \ introspection/org.freedesktop.NetworkManager.Device.Bridge.xml \ introspection/org.freedesktop.NetworkManager.Device.Dummy.xml \ introspection/org.freedesktop.NetworkManager.Device.Generic.xml \ + introspection/org.freedesktop.NetworkManager.Device.Hsr.xml \ introspection/org.freedesktop.NetworkManager.Device.IPTunnel.xml \ introspection/org.freedesktop.NetworkManager.Device.Infiniband.xml \ introspection/org.freedesktop.NetworkManager.Device.Loopback.xml \ @@ -6149,6 +6137,7 @@ src_libnm_core_impl_lib_h_pub_real = \ src/libnm-core-public/nm-setting-generic.h \ src/libnm-core-public/nm-setting-gsm.h \ src/libnm-core-public/nm-setting-hostname.h \ + src/libnm-core-public/nm-setting-hsr.h \ src/libnm-core-public/nm-setting-infiniband.h \ src/libnm-core-public/nm-setting-ip-config.h \ src/libnm-core-public/nm-setting-ip-tunnel.h \ @@ -6206,7 +6195,6 @@ src_libnm_core_public_mkenums_h = \ src_libnm_core_impl_lib_h_priv = \ src/libnm-core-impl/nm-connection-private.h \ src/libnm-core-impl/nm-default-libnm-core.h \ - src/libnm-core-impl/nm-property-compare.h \ src/libnm-core-impl/nm-setting-private.h \ src/libnm-core-impl/nm-team-utils.h \ src/libnm-core-impl/nm-utils-private.h \ @@ -6234,6 +6222,7 @@ src_libnm_core_impl_lib_c_settings_real = \ src/libnm-core-impl/nm-setting-generic.c \ src/libnm-core-impl/nm-setting-gsm.c \ src/libnm-core-impl/nm-setting-hostname.c \ + src/libnm-core-impl/nm-setting-hsr.c \ src/libnm-core-impl/nm-setting-infiniband.c \ src/libnm-core-impl/nm-setting-ip-config.c \ src/libnm-core-impl/nm-setting-ip-tunnel.c \ @@ -6283,7 +6272,6 @@ src_libnm_core_impl_lib_c_real = \ src/libnm-core-impl/nm-keyfile-utils.c \ src/libnm-core-impl/nm-keyfile.c \ src/libnm-core-impl/nm-meta-setting-base-impl.c \ - src/libnm-core-impl/nm-property-compare.c \ src/libnm-core-impl/nm-setting.c \ src/libnm-core-impl/nm-simple-connection.c \ src/libnm-core-impl/nm-team-utils.c \ @@ -6406,7 +6394,6 @@ src_libnm_core_impl_tests_cppflags = \ $(SANITIZER_EXEC_CFLAGS) \ $(NULL) -src_libnm_core_impl_tests_test_compare_CPPFLAGS = $(src_libnm_core_impl_tests_cppflags) src_libnm_core_impl_tests_test_crypto_CPPFLAGS = $(src_libnm_core_impl_tests_cppflags) src_libnm_core_impl_tests_test_general_CPPFLAGS = $(src_libnm_core_impl_tests_cppflags) src_libnm_core_impl_tests_test_keyfile_CPPFLAGS = $(src_libnm_core_impl_tests_cppflags) @@ -6442,14 +6429,12 @@ src_libnm_core_impl_tests_ldflags = \ $(SANITIZER_EXEC_LDFLAGS) \ $(NULL) -src_libnm_core_impl_tests_test_compare_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_crypto_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_general_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_keyfile_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_secrets_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_setting_LDADD = $(src_libnm_core_impl_tests_ldadd) src_libnm_core_impl_tests_test_settings_defaults_LDADD = $(src_libnm_core_impl_tests_ldadd) -src_libnm_core_impl_tests_test_compare_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) src_libnm_core_impl_tests_test_crypto_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) src_libnm_core_impl_tests_test_general_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) src_libnm_core_impl_tests_test_keyfile_LDFLAGS = $(src_libnm_core_impl_tests_ldflags) @@ -6474,6 +6459,7 @@ libnm_lib_h_pub_real = \ src/libnm-client-public/nm-device-dummy.h \ src/libnm-client-public/nm-device-ethernet.h \ src/libnm-client-public/nm-device-generic.h \ + src/libnm-client-public/nm-device-hsr.h \ src/libnm-client-public/nm-device-infiniband.h \ src/libnm-client-public/nm-device-ip-tunnel.h \ src/libnm-client-public/nm-device-loopback.h \ @@ -6548,6 +6534,7 @@ libnm_lib_c_real = \ src/libnm-client-impl/nm-device-dummy.c \ src/libnm-client-impl/nm-device-ethernet.c \ src/libnm-client-impl/nm-device-generic.c \ + src/libnm-client-impl/nm-device-hsr.c \ src/libnm-client-impl/nm-device-infiniband.c \ src/libnm-client-impl/nm-device-ip-tunnel.c \ src/libnm-client-impl/nm-device-loopback.c \ @@ -6717,7 +6704,10 @@ libnm_noinst_data = \ src/libnm-client-impl/nm-property-infos-ifcfg-rh.xml \ src/libnm-client-impl/nm-property-infos-keyfile.xml \ src/libnm-client-impl/nm-property-infos-nmcli.xml \ - src/libnm-client-impl/nm-settings-docs-gir.xml \ + src/libnm-client-impl/nm-settings-docs-gir-dbus.xml \ + src/libnm-client-impl/nm-settings-docs-gir-ifcfg-rh.xml \ + src/libnm-client-impl/nm-settings-docs-gir-keyfile.xml \ + src/libnm-client-impl/nm-settings-docs-gir-nmcli.xml \ src/libnmc-setting/settings-docs-input.xml \ $(NULL) @@ -7169,6 +7159,8 @@ src_core_libNetworkManager_la_SOURCES = \ src/core/devices/nm-device-dummy.h \ src/core/devices/nm-device-ethernet.c \ src/core/devices/nm-device-ethernet.h \ + src/core/devices/nm-device-hsr.c \ + src/core/devices/nm-device-hsr.h \ src/core/devices/nm-device-infiniband.c \ src/core/devices/nm-device-infiniband.h \ src/core/devices/nm-device-ip-tunnel.c \ @@ -9259,6 +9251,9 @@ introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Dummy.lo: \ introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Generic.lo: \ introspection/$(am__dirstamp) \ introspection/$(DEPDIR)/$(am__dirstamp) +introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.lo: \ + introspection/$(am__dirstamp) \ + introspection/$(DEPDIR)/$(am__dirstamp) introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.lo: \ introspection/$(am__dirstamp) \ introspection/$(DEPDIR)/$(am__dirstamp) @@ -9623,6 +9618,9 @@ src/core/devices/libNetworkManager_la-nm-device-dummy.lo: \ src/core/devices/libNetworkManager_la-nm-device-ethernet.lo: \ src/core/devices/$(am__dirstamp) \ src/core/devices/$(DEPDIR)/$(am__dirstamp) +src/core/devices/libNetworkManager_la-nm-device-hsr.lo: \ + src/core/devices/$(am__dirstamp) \ + src/core/devices/$(DEPDIR)/$(am__dirstamp) src/core/devices/libNetworkManager_la-nm-device-infiniband.lo: \ src/core/devices/$(am__dirstamp) \ src/core/devices/$(DEPDIR)/$(am__dirstamp) @@ -10092,6 +10090,9 @@ src/libnm-client-impl/libnm_client_impl_la-nm-device-ethernet.lo: \ src/libnm-client-impl/libnm_client_impl_la-nm-device-generic.lo: \ src/libnm-client-impl/$(am__dirstamp) \ src/libnm-client-impl/$(DEPDIR)/$(am__dirstamp) +src/libnm-client-impl/libnm_client_impl_la-nm-device-hsr.lo: \ + src/libnm-client-impl/$(am__dirstamp) \ + src/libnm-client-impl/$(DEPDIR)/$(am__dirstamp) src/libnm-client-impl/libnm_client_impl_la-nm-device-infiniband.lo: \ src/libnm-client-impl/$(am__dirstamp) \ src/libnm-client-impl/$(DEPDIR)/$(am__dirstamp) @@ -10314,6 +10315,9 @@ src/libnm-core-impl/libnm_core_impl_la-nm-setting-gsm.lo: \ src/libnm-core-impl/libnm_core_impl_la-nm-setting-hostname.lo: \ src/libnm-core-impl/$(am__dirstamp) \ src/libnm-core-impl/$(DEPDIR)/$(am__dirstamp) +src/libnm-core-impl/libnm_core_impl_la-nm-setting-hsr.lo: \ + src/libnm-core-impl/$(am__dirstamp) \ + src/libnm-core-impl/$(DEPDIR)/$(am__dirstamp) src/libnm-core-impl/libnm_core_impl_la-nm-setting-infiniband.lo: \ src/libnm-core-impl/$(am__dirstamp) \ src/libnm-core-impl/$(DEPDIR)/$(am__dirstamp) @@ -10449,9 +10453,6 @@ src/libnm-core-impl/libnm_core_impl_la-nm-keyfile.lo: \ src/libnm-core-impl/libnm_core_impl_la-nm-meta-setting-base-impl.lo: \ src/libnm-core-impl/$(am__dirstamp) \ src/libnm-core-impl/$(DEPDIR)/$(am__dirstamp) -src/libnm-core-impl/libnm_core_impl_la-nm-property-compare.lo: \ - src/libnm-core-impl/$(am__dirstamp) \ - src/libnm-core-impl/$(DEPDIR)/$(am__dirstamp) src/libnm-core-impl/libnm_core_impl_la-nm-setting.lo: \ src/libnm-core-impl/$(am__dirstamp) \ src/libnm-core-impl/$(DEPDIR)/$(am__dirstamp) @@ -11573,13 +11574,6 @@ src/libnm-core-impl/tests/$(am__dirstamp): src/libnm-core-impl/tests/$(DEPDIR)/$(am__dirstamp): @$(MKDIR_P) src/libnm-core-impl/tests/$(DEPDIR) @: > src/libnm-core-impl/tests/$(DEPDIR)/$(am__dirstamp) -src/libnm-core-impl/tests/test_compare-test-compare.$(OBJEXT): \ - src/libnm-core-impl/tests/$(am__dirstamp) \ - src/libnm-core-impl/tests/$(DEPDIR)/$(am__dirstamp) - -src/libnm-core-impl/tests/test-compare$(EXEEXT): $(src_libnm_core_impl_tests_test_compare_OBJECTS) $(src_libnm_core_impl_tests_test_compare_DEPENDENCIES) $(EXTRA_src_libnm_core_impl_tests_test_compare_DEPENDENCIES) src/libnm-core-impl/tests/$(am__dirstamp) - @rm -f src/libnm-core-impl/tests/test-compare$(EXEEXT) - $(AM_V_CCLD)$(src_libnm_core_impl_tests_test_compare_LINK) $(src_libnm_core_impl_tests_test_compare_OBJECTS) $(src_libnm_core_impl_tests_test_compare_LDADD) $(LIBS) src/libnm-core-impl/tests/test_crypto-test-crypto.$(OBJEXT): \ src/libnm-core-impl/tests/$(am__dirstamp) \ src/libnm-core-impl/tests/$(DEPDIR)/$(am__dirstamp) @@ -12145,6 +12139,7 @@ distclean-compile: @AMDEP_TRUE@@am__include@ @am__quote@introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Bridge.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Dummy.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Generic.Plo@am__quote@ # am--include-marker +@AMDEP_TRUE@@am__include@ @am__quote@introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Infiniband.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Loopback.Plo@am__quote@ # am--include-marker @@ -12233,6 +12228,7 @@ distclean-compile: @AMDEP_TRUE@@am__include@ @am__quote@src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-ethernet.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-factory.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-generic.Plo@am__quote@ # am--include-marker +@AMDEP_TRUE@@am__include@ @am__quote@src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-hsr.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-infiniband.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-ip-tunnel.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-loopback.Plo@am__quote@ # am--include-marker @@ -12391,6 +12387,7 @@ distclean-compile: @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-dummy.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-ethernet.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-generic.Plo@am__quote@ # am--include-marker +@AMDEP_TRUE@@am__include@ @am__quote@src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-hsr.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-infiniband.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-ip-tunnel.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-loopback.Plo@am__quote@ # am--include-marker @@ -12446,7 +12443,6 @@ distclean-compile: @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-keyfile-utils.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-keyfile.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-meta-setting-base-impl.Plo@am__quote@ # am--include-marker -@AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-property-compare.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-6lowpan.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-8021x.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-adsl.Plo@am__quote@ # am--include-marker @@ -12463,6 +12459,7 @@ distclean-compile: @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-generic.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-gsm.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hostname.Plo@am__quote@ # am--include-marker +@AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hsr.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-infiniband.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-ip-config.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-ip-tunnel.Plo@am__quote@ # am--include-marker @@ -12509,7 +12506,6 @@ distclean-compile: @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-utils.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-vpn-editor-plugin.Plo@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-vpn-plugin-info.Plo@am__quote@ # am--include-marker -@AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Po@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/tests/$(DEPDIR)/test_crypto-test-crypto.Po@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/tests/$(DEPDIR)/test_general-nm-core-tests-enum-types.Po@am__quote@ # am--include-marker @AMDEP_TRUE@@am__include@ @am__quote@src/libnm-core-impl/tests/$(DEPDIR)/test_general-test-general.Po@am__quote@ # am--include-marker @@ -13235,6 +13231,13 @@ introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Generic.lo: int @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(introspection_libnmdbus_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Generic.lo `test -f 'introspection/org.freedesktop.NetworkManager.Device.Generic.c' || echo '$(srcdir)/'`introspection/org.freedesktop.NetworkManager.Device.Generic.c +introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.lo: introspection/org.freedesktop.NetworkManager.Device.Hsr.c +@am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(introspection_libnmdbus_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.lo -MD -MP -MF introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.Tpo -c -o introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.lo `test -f 'introspection/org.freedesktop.NetworkManager.Device.Hsr.c' || echo '$(srcdir)/'`introspection/org.freedesktop.NetworkManager.Device.Hsr.c +@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.Tpo introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.Plo +@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='introspection/org.freedesktop.NetworkManager.Device.Hsr.c' object='introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.lo' libtool=yes @AMDEPBACKSLASH@ +@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ +@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(introspection_libnmdbus_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.lo `test -f 'introspection/org.freedesktop.NetworkManager.Device.Hsr.c' || echo '$(srcdir)/'`introspection/org.freedesktop.NetworkManager.Device.Hsr.c + introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.lo: introspection/org.freedesktop.NetworkManager.Device.IPTunnel.c @am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(introspection_libnmdbus_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.lo -MD -MP -MF introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.Tpo -c -o introspection/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.lo `test -f 'introspection/org.freedesktop.NetworkManager.Device.IPTunnel.c' || echo '$(srcdir)/'`introspection/org.freedesktop.NetworkManager.Device.IPTunnel.c @am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.Tpo introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.Plo @@ -13823,6 +13826,13 @@ src/core/devices/libNetworkManager_la-nm-device-ethernet.lo: src/core/devices/nm @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_core_libNetworkManager_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/core/devices/libNetworkManager_la-nm-device-ethernet.lo `test -f 'src/core/devices/nm-device-ethernet.c' || echo '$(srcdir)/'`src/core/devices/nm-device-ethernet.c +src/core/devices/libNetworkManager_la-nm-device-hsr.lo: src/core/devices/nm-device-hsr.c +@am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_core_libNetworkManager_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/core/devices/libNetworkManager_la-nm-device-hsr.lo -MD -MP -MF src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-hsr.Tpo -c -o src/core/devices/libNetworkManager_la-nm-device-hsr.lo `test -f 'src/core/devices/nm-device-hsr.c' || echo '$(srcdir)/'`src/core/devices/nm-device-hsr.c +@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-hsr.Tpo src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-hsr.Plo +@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='src/core/devices/nm-device-hsr.c' object='src/core/devices/libNetworkManager_la-nm-device-hsr.lo' libtool=yes @AMDEPBACKSLASH@ +@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ +@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_core_libNetworkManager_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/core/devices/libNetworkManager_la-nm-device-hsr.lo `test -f 'src/core/devices/nm-device-hsr.c' || echo '$(srcdir)/'`src/core/devices/nm-device-hsr.c + src/core/devices/libNetworkManager_la-nm-device-infiniband.lo: src/core/devices/nm-device-infiniband.c @am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_core_libNetworkManager_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/core/devices/libNetworkManager_la-nm-device-infiniband.lo -MD -MP -MF src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-infiniband.Tpo -c -o src/core/devices/libNetworkManager_la-nm-device-infiniband.lo `test -f 'src/core/devices/nm-device-infiniband.c' || echo '$(srcdir)/'`src/core/devices/nm-device-infiniband.c @am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-infiniband.Tpo src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-infiniband.Plo @@ -14691,6 +14701,13 @@ src/libnm-client-impl/libnm_client_impl_la-nm-device-generic.lo: src/libnm-clien @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_client_impl_libnm_client_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/libnm-client-impl/libnm_client_impl_la-nm-device-generic.lo `test -f 'src/libnm-client-impl/nm-device-generic.c' || echo '$(srcdir)/'`src/libnm-client-impl/nm-device-generic.c +src/libnm-client-impl/libnm_client_impl_la-nm-device-hsr.lo: src/libnm-client-impl/nm-device-hsr.c +@am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_client_impl_libnm_client_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/libnm-client-impl/libnm_client_impl_la-nm-device-hsr.lo -MD -MP -MF src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-hsr.Tpo -c -o src/libnm-client-impl/libnm_client_impl_la-nm-device-hsr.lo `test -f 'src/libnm-client-impl/nm-device-hsr.c' || echo '$(srcdir)/'`src/libnm-client-impl/nm-device-hsr.c +@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-hsr.Tpo src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-hsr.Plo +@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='src/libnm-client-impl/nm-device-hsr.c' object='src/libnm-client-impl/libnm_client_impl_la-nm-device-hsr.lo' libtool=yes @AMDEPBACKSLASH@ +@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ +@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_client_impl_libnm_client_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/libnm-client-impl/libnm_client_impl_la-nm-device-hsr.lo `test -f 'src/libnm-client-impl/nm-device-hsr.c' || echo '$(srcdir)/'`src/libnm-client-impl/nm-device-hsr.c + src/libnm-client-impl/libnm_client_impl_la-nm-device-infiniband.lo: src/libnm-client-impl/nm-device-infiniband.c @am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_client_impl_libnm_client_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/libnm-client-impl/libnm_client_impl_la-nm-device-infiniband.lo -MD -MP -MF src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-infiniband.Tpo -c -o src/libnm-client-impl/libnm_client_impl_la-nm-device-infiniband.lo `test -f 'src/libnm-client-impl/nm-device-infiniband.c' || echo '$(srcdir)/'`src/libnm-client-impl/nm-device-infiniband.c @am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-infiniband.Tpo src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-infiniband.Plo @@ -15104,6 +15121,13 @@ src/libnm-core-impl/libnm_core_impl_la-nm-setting-hostname.lo: src/libnm-core-im @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_libnm_core_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/libnm-core-impl/libnm_core_impl_la-nm-setting-hostname.lo `test -f 'src/libnm-core-impl/nm-setting-hostname.c' || echo '$(srcdir)/'`src/libnm-core-impl/nm-setting-hostname.c +src/libnm-core-impl/libnm_core_impl_la-nm-setting-hsr.lo: src/libnm-core-impl/nm-setting-hsr.c +@am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_libnm_core_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/libnm-core-impl/libnm_core_impl_la-nm-setting-hsr.lo -MD -MP -MF src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hsr.Tpo -c -o src/libnm-core-impl/libnm_core_impl_la-nm-setting-hsr.lo `test -f 'src/libnm-core-impl/nm-setting-hsr.c' || echo '$(srcdir)/'`src/libnm-core-impl/nm-setting-hsr.c +@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hsr.Tpo src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hsr.Plo +@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='src/libnm-core-impl/nm-setting-hsr.c' object='src/libnm-core-impl/libnm_core_impl_la-nm-setting-hsr.lo' libtool=yes @AMDEPBACKSLASH@ +@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ +@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_libnm_core_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/libnm-core-impl/libnm_core_impl_la-nm-setting-hsr.lo `test -f 'src/libnm-core-impl/nm-setting-hsr.c' || echo '$(srcdir)/'`src/libnm-core-impl/nm-setting-hsr.c + src/libnm-core-impl/libnm_core_impl_la-nm-setting-infiniband.lo: src/libnm-core-impl/nm-setting-infiniband.c @am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_libnm_core_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/libnm-core-impl/libnm_core_impl_la-nm-setting-infiniband.lo -MD -MP -MF src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-infiniband.Tpo -c -o src/libnm-core-impl/libnm_core_impl_la-nm-setting-infiniband.lo `test -f 'src/libnm-core-impl/nm-setting-infiniband.c' || echo '$(srcdir)/'`src/libnm-core-impl/nm-setting-infiniband.c @am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-infiniband.Tpo src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-infiniband.Plo @@ -15419,13 +15443,6 @@ src/libnm-core-impl/libnm_core_impl_la-nm-meta-setting-base-impl.lo: src/libnm-c @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_libnm_core_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/libnm-core-impl/libnm_core_impl_la-nm-meta-setting-base-impl.lo `test -f 'src/libnm-core-impl/nm-meta-setting-base-impl.c' || echo '$(srcdir)/'`src/libnm-core-impl/nm-meta-setting-base-impl.c -src/libnm-core-impl/libnm_core_impl_la-nm-property-compare.lo: src/libnm-core-impl/nm-property-compare.c -@am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_libnm_core_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/libnm-core-impl/libnm_core_impl_la-nm-property-compare.lo -MD -MP -MF src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-property-compare.Tpo -c -o src/libnm-core-impl/libnm_core_impl_la-nm-property-compare.lo `test -f 'src/libnm-core-impl/nm-property-compare.c' || echo '$(srcdir)/'`src/libnm-core-impl/nm-property-compare.c -@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-property-compare.Tpo src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-property-compare.Plo -@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='src/libnm-core-impl/nm-property-compare.c' object='src/libnm-core-impl/libnm_core_impl_la-nm-property-compare.lo' libtool=yes @AMDEPBACKSLASH@ -@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ -@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_libnm_core_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/libnm-core-impl/libnm_core_impl_la-nm-property-compare.lo `test -f 'src/libnm-core-impl/nm-property-compare.c' || echo '$(srcdir)/'`src/libnm-core-impl/nm-property-compare.c - src/libnm-core-impl/libnm_core_impl_la-nm-setting.lo: src/libnm-core-impl/nm-setting.c @am__fastdepCC_TRUE@ $(AM_V_CC)$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_libnm_core_impl_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/libnm-core-impl/libnm_core_impl_la-nm-setting.lo -MD -MP -MF src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting.Tpo -c -o src/libnm-core-impl/libnm_core_impl_la-nm-setting.lo `test -f 'src/libnm-core-impl/nm-setting.c' || echo '$(srcdir)/'`src/libnm-core-impl/nm-setting.c @am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting.Tpo src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting.Plo @@ -17099,20 +17116,6 @@ src/libnm-core-impl/gen_metadata_nm_settings_libnm_core-gen-metadata-nm-settings @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_gen_metadata_nm_settings_libnm_core_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/libnm-core-impl/gen_metadata_nm_settings_libnm_core-gen-metadata-nm-settings-libnm-core.obj `if test -f 'src/libnm-core-impl/gen-metadata-nm-settings-libnm-core.c'; then $(CYGPATH_W) 'src/libnm-core-impl/gen-metadata-nm-settings-libnm-core.c'; else $(CYGPATH_W) '$(srcdir)/src/libnm-core-impl/gen-metadata-nm-settings-libnm-core.c'; fi` -src/libnm-core-impl/tests/test_compare-test-compare.o: src/libnm-core-impl/tests/test-compare.c -@am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_tests_test_compare_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/libnm-core-impl/tests/test_compare-test-compare.o -MD -MP -MF src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Tpo -c -o src/libnm-core-impl/tests/test_compare-test-compare.o `test -f 'src/libnm-core-impl/tests/test-compare.c' || echo '$(srcdir)/'`src/libnm-core-impl/tests/test-compare.c -@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Tpo src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Po -@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='src/libnm-core-impl/tests/test-compare.c' object='src/libnm-core-impl/tests/test_compare-test-compare.o' libtool=no @AMDEPBACKSLASH@ -@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ -@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_tests_test_compare_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/libnm-core-impl/tests/test_compare-test-compare.o `test -f 'src/libnm-core-impl/tests/test-compare.c' || echo '$(srcdir)/'`src/libnm-core-impl/tests/test-compare.c - -src/libnm-core-impl/tests/test_compare-test-compare.obj: src/libnm-core-impl/tests/test-compare.c -@am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_tests_test_compare_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/libnm-core-impl/tests/test_compare-test-compare.obj -MD -MP -MF src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Tpo -c -o src/libnm-core-impl/tests/test_compare-test-compare.obj `if test -f 'src/libnm-core-impl/tests/test-compare.c'; then $(CYGPATH_W) 'src/libnm-core-impl/tests/test-compare.c'; else $(CYGPATH_W) '$(srcdir)/src/libnm-core-impl/tests/test-compare.c'; fi` -@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Tpo src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Po -@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='src/libnm-core-impl/tests/test-compare.c' object='src/libnm-core-impl/tests/test_compare-test-compare.obj' libtool=no @AMDEPBACKSLASH@ -@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ -@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_tests_test_compare_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o src/libnm-core-impl/tests/test_compare-test-compare.obj `if test -f 'src/libnm-core-impl/tests/test-compare.c'; then $(CYGPATH_W) 'src/libnm-core-impl/tests/test-compare.c'; else $(CYGPATH_W) '$(srcdir)/src/libnm-core-impl/tests/test-compare.c'; fi` - src/libnm-core-impl/tests/test_crypto-test-crypto.o: src/libnm-core-impl/tests/test-crypto.c @am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(src_libnm_core_impl_tests_test_crypto_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT src/libnm-core-impl/tests/test_crypto-test-crypto.o -MD -MP -MF src/libnm-core-impl/tests/$(DEPDIR)/test_crypto-test-crypto.Tpo -c -o src/libnm-core-impl/tests/test_crypto-test-crypto.o `test -f 'src/libnm-core-impl/tests/test-crypto.c' || echo '$(srcdir)/'`src/libnm-core-impl/tests/test-crypto.c @am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) src/libnm-core-impl/tests/$(DEPDIR)/test_crypto-test-crypto.Tpo src/libnm-core-impl/tests/$(DEPDIR)/test_crypto-test-crypto.Po @@ -19198,13 +19201,6 @@ src/libnm-glib-aux/tests/test-json-aux.log: src/libnm-glib-aux/tests/test-json-a --log-file $$b.log --trs-file $$b.trs \ $(am__common_driver_flags) $(AM_LOG_DRIVER_FLAGS) $(LOG_DRIVER_FLAGS) -- $(LOG_COMPILE) \ "$$tst" $(AM_TESTS_FD_REDIRECT) -src/libnm-core-impl/tests/test-compare.log: src/libnm-core-impl/tests/test-compare$(EXEEXT) - @p='src/libnm-core-impl/tests/test-compare$(EXEEXT)'; \ - b='src/libnm-core-impl/tests/test-compare'; \ - $(am__check_pre) $(LOG_DRIVER) --test-name "$$f" \ - --log-file $$b.log --trs-file $$b.trs \ - $(am__common_driver_flags) $(AM_LOG_DRIVER_FLAGS) $(LOG_DRIVER_FLAGS) -- $(LOG_COMPILE) \ - "$$tst" $(AM_TESTS_FD_REDIRECT) src/libnm-core-impl/tests/test-crypto.log: src/libnm-core-impl/tests/test-crypto$(EXEEXT) @p='src/libnm-core-impl/tests/test-crypto$(EXEEXT)'; \ b='src/libnm-core-impl/tests/test-crypto'; \ @@ -20030,6 +20026,7 @@ distclean: distclean-recursive -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Bridge.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Dummy.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Generic.Plo + -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Infiniband.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Loopback.Plo @@ -20118,6 +20115,7 @@ distclean: distclean-recursive -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-ethernet.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-factory.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-generic.Plo + -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-hsr.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-infiniband.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-ip-tunnel.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-loopback.Plo @@ -20276,6 +20274,7 @@ distclean: distclean-recursive -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-dummy.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-ethernet.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-generic.Plo + -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-hsr.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-infiniband.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-ip-tunnel.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-loopback.Plo @@ -20331,7 +20330,6 @@ distclean: distclean-recursive -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-keyfile-utils.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-keyfile.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-meta-setting-base-impl.Plo - -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-property-compare.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-6lowpan.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-8021x.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-adsl.Plo @@ -20348,6 +20346,7 @@ distclean: distclean-recursive -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-generic.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-gsm.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hostname.Plo + -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hsr.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-infiniband.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-ip-config.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-ip-tunnel.Plo @@ -20394,7 +20393,6 @@ distclean: distclean-recursive -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-utils.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-vpn-editor-plugin.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-vpn-plugin-info.Plo - -rm -f src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Po -rm -f src/libnm-core-impl/tests/$(DEPDIR)/test_crypto-test-crypto.Po -rm -f src/libnm-core-impl/tests/$(DEPDIR)/test_general-nm-core-tests-enum-types.Po -rm -f src/libnm-core-impl/tests/$(DEPDIR)/test_general-test-general.Po @@ -20711,6 +20709,7 @@ maintainer-clean: maintainer-clean-recursive -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Bridge.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Dummy.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Generic.Plo + -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Hsr.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.IPTunnel.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Infiniband.Plo -rm -f introspection/$(DEPDIR)/libnmdbus_la-org.freedesktop.NetworkManager.Device.Loopback.Plo @@ -20799,6 +20798,7 @@ maintainer-clean: maintainer-clean-recursive -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-ethernet.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-factory.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-generic.Plo + -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-hsr.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-infiniband.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-ip-tunnel.Plo -rm -f src/core/devices/$(DEPDIR)/libNetworkManager_la-nm-device-loopback.Plo @@ -20957,6 +20957,7 @@ maintainer-clean: maintainer-clean-recursive -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-dummy.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-ethernet.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-generic.Plo + -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-hsr.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-infiniband.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-ip-tunnel.Plo -rm -f src/libnm-client-impl/$(DEPDIR)/libnm_client_impl_la-nm-device-loopback.Plo @@ -21012,7 +21013,6 @@ maintainer-clean: maintainer-clean-recursive -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-keyfile-utils.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-keyfile.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-meta-setting-base-impl.Plo - -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-property-compare.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-6lowpan.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-8021x.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-adsl.Plo @@ -21029,6 +21029,7 @@ maintainer-clean: maintainer-clean-recursive -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-generic.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-gsm.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hostname.Plo + -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-hsr.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-infiniband.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-ip-config.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-setting-ip-tunnel.Plo @@ -21075,7 +21076,6 @@ maintainer-clean: maintainer-clean-recursive -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-utils.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-vpn-editor-plugin.Plo -rm -f src/libnm-core-impl/$(DEPDIR)/libnm_core_impl_la-nm-vpn-plugin-info.Plo - -rm -f src/libnm-core-impl/tests/$(DEPDIR)/test_compare-test-compare.Po -rm -f src/libnm-core-impl/tests/$(DEPDIR)/test_crypto-test-crypto.Po -rm -f src/libnm-core-impl/tests/$(DEPDIR)/test_general-nm-core-tests-enum-types.Po -rm -f src/libnm-core-impl/tests/$(DEPDIR)/test_general-test-general.Po @@ -21574,7 +21574,6 @@ src/libnm-core-impl/tests/nm-core-tests-enum-types.c.stamp: src/libnm-core-impl/ $(src_libnm_core_impl_tests_test_general_OBJECTS): src/libnm-core-impl/tests/nm-core-tests-enum-types.h -$(src_libnm_core_impl_tests_test_compare_OBJECTS): $(src_libnm_core_public_mkenums_h) $(src_libnm_core_impl_tests_test_crypto_OBJECTS): $(src_libnm_core_public_mkenums_h) $(src_libnm_core_impl_tests_test_general_OBJECTS): $(src_libnm_core_public_mkenums_h) $(src_libnm_core_impl_tests_test_keyfile_OBJECTS): $(src_libnm_core_public_mkenums_h) @@ -21624,7 +21623,7 @@ src/libnm-client-impl/libnm.typelib: src/libnm-client-impl/libnm.gir @BUILD_DOCS_FALSE@ $(AM_V_GEN) cp $^ $@ @BUILD_DOCS_FALSE@check-local-gen-metadata-nm-settings-libnm-core: -src/libnm-client-impl/nm-property-infos-%.xml: tools/generate-docs-nm-property-infos.py src/libnm-core-impl/libnm-core-impl.la $(libnm_docs_sources) +src/libnm-client-impl/nm-property-infos-%.xml: tools/generate-docs-nm-property-infos.py src/libnm-core-impl/libnm-core-impl.la src/libnm-client-impl/NM-1.0.gir $(libnm_docs_sources) $(AM_V_GEN) \ "$(PYTHON)" \ $(srcdir)/tools/generate-docs-nm-property-infos.py \ @@ -21632,7 +21631,7 @@ src/libnm-client-impl/nm-property-infos-%.xml: tools/generate-docs-nm-property-i $@ \ $(wordlist 3,1000,$^) -src/libnm-client-impl/nm-settings-docs-gir.xml: tools/generate-docs-nm-settings-docs-gir.py src/libnm-client-impl/NM-1.0.gir src/libnm-client-impl/NM-1.0.typelib src/libnm-client-impl/libnm.la $(libnm_docs_sources) +src/libnm-client-impl/nm-settings-docs-gir-%.xml: tools/generate-docs-nm-settings-docs-gir.py src/libnm-client-impl/NM-1.0.gir src/libnm-client-impl/NM-1.0.typelib src/libnm-client-impl/libnm.la $(libnm_docs_sources) $(AM_V_GEN) \ export GI_TYPELIB_PATH=$(abs_builddir)/src/libnm-client-impl$${GI_TYPELIB_PATH:+:$$GI_TYPELIB_PATH}; \ export LD_LIBRARY_PATH=$(abs_builddir)/src/libnm-client-impl/.libs$${LD_LIBRARY_PATH:+:$$LD_LIBRARY_PATH}; \ @@ -21640,9 +21639,10 @@ src/libnm-client-impl/nm-settings-docs-gir.xml: tools/generate-docs-nm-settings- "$(PYTHON)" \ $(srcdir)/tools/generate-docs-nm-settings-docs-gir.py \ --gir $(builddir)/src/libnm-client-impl/NM-1.0.gir \ - --output $@ + --output $@ \ + --target $(patsubst nm-settings-docs-gir-%.xml,%,$(notdir $@)) -man/nm-settings-docs-nmcli.xml: src/nmcli/gen-metadata-nm-settings-nmcli.xml src/libnm-client-impl/nm-property-infos-nmcli.xml src/libnm-client-impl/nm-settings-docs-gir.xml tools/generate-docs-nm-settings-docs-merge.py man/common.ent +man/nm-settings-docs-nmcli.xml: src/nmcli/gen-metadata-nm-settings-nmcli.xml src/libnm-client-impl/nm-property-infos-nmcli.xml src/libnm-client-impl/nm-settings-docs-gir-nmcli.xml tools/generate-docs-nm-settings-docs-merge.py man/common.ent $(AM_V_GEN) \ "$(PYTHON)" \ "$(srcdir)/tools/generate-docs-nm-settings-docs-merge.py" \ @@ -21651,10 +21651,10 @@ man/nm-settings-docs-nmcli.xml: src/nmcli/gen-metadata-nm-settings-nmcli.xml src "$<" \ $(wordlist 1,3,$^) -src/libnmc-setting/settings-docs-input.xml: src/libnm-client-impl/nm-property-infos-nmcli.xml src/libnm-client-impl/nm-settings-docs-gir.xml tools/generate-docs-nm-settings-docs-merge.py +src/libnmc-setting/settings-docs-input.xml: src/libnm-client-impl/nm-property-infos-nmcli.xml src/libnm-client-impl/nm-settings-docs-gir-nmcli.xml tools/generate-docs-nm-settings-docs-merge.py $(AM_V_GEN) "$(PYTHON)" $(srcdir)/tools/generate-docs-nm-settings-docs-merge.py $@ $(wordlist 1,2,$^) -man/nm-settings-docs-%.xml: src/libnm-client-impl/nm-property-infos-%.xml src/libnm-client-impl/nm-settings-docs-gir.xml tools/generate-docs-nm-settings-docs-merge.py man/common.ent +man/nm-settings-docs-%.xml: src/libnm-client-impl/nm-property-infos-%.xml src/libnm-client-impl/nm-settings-docs-gir-%.xml tools/generate-docs-nm-settings-docs-merge.py man/common.ent $(AM_V_GEN) "$(PYTHON)" $(srcdir)/tools/generate-docs-nm-settings-docs-merge.py $@ $(wordlist 1,2,$^) check-local-libnm-gir: $(builddir)/src/libnm-client-impl/NM-1.0.gir @@ -21951,10 +21951,8 @@ check-local-gitlab-ci: @HAVE_SYSTEMD_TRUE@data/NetworkManager.service: $(srcdir)/data/NetworkManager.service.in @HAVE_SYSTEMD_TRUE@ $(AM_V_GEN) $(data_edit) $< >$@ -@HAVE_SYSTEMD_200_TRUE@@HAVE_SYSTEMD_TRUE@data/NetworkManager-wait-online.service: $(srcdir)/data/NetworkManager-wait-online.service.in -@HAVE_SYSTEMD_200_TRUE@@HAVE_SYSTEMD_TRUE@ $(AM_V_GEN) $(data_edit) $< >$@ -@HAVE_SYSTEMD_200_FALSE@@HAVE_SYSTEMD_TRUE@data/NetworkManager-wait-online.service: $(srcdir)/data/NetworkManager-wait-online-systemd-pre200.service.in -@HAVE_SYSTEMD_200_FALSE@@HAVE_SYSTEMD_TRUE@ $(AM_V_GEN) $(data_edit) $< >$@ +@HAVE_SYSTEMD_TRUE@data/NetworkManager-wait-online.service: $(srcdir)/data/NetworkManager-wait-online.service.in +@HAVE_SYSTEMD_TRUE@ $(AM_V_GEN) $(data_edit) $< >$@ @HAVE_SYSTEMD_TRUE@data/NetworkManager-dispatcher.service: $(srcdir)/data/NetworkManager-dispatcher.service.in @HAVE_SYSTEMD_TRUE@ $(AM_V_GEN) $(data_edit) $< >$@ diff --git a/NEWS b/NEWS index a529d6fe..7fd1d5fe 100644 --- a/NEWS +++ b/NEWS @@ -1,15 +1,28 @@ -=============================================== -NetworkManager-1.44.2 -Overview of changes since NetworkManager-1.44.0 -=============================================== +============================================= +NetworkManager-1.46 +Overview of changes since NetworkManager-1.44 +============================================= -* Better log IPv4 Address Conflict Detection (ACD) conflicts -* Remove the upper limit of 65535 for PIDs read from the PID file -* Allow missing default gateway with oFono -* Honor the CLICOLOR_FORCE environment variable -* Fix generating connection with IPv6 method disabled vs ignored -* Fix possible segmentation fault when doing a checkpoint rollback -* Documentation improvements +* Support dynamic value "${NETWORK_SSID}" for connection.stable-id to generate + the stable ID based on the Wi-Fi's SSID. +* Support new value "wifi.cloned-mac-address=stable-ssid" for randomizing the + MAC address based on the Wi-Fi network. +* Change internal ABI of NMSetting types and NMSimpleConnection. The layout of + these structs was already hidden from public headers since 1.34 and this change + should not be noticeable. +* Honor udev property ID_NET_AUTO_LINK_LOCAL_ONLY=1 for enabling + link local addresses on default wired connection. +* Honor udev property ID_NET_MANAGED_BY to only manage an interface + when set to "org.freedesktop.NetworkManager". +* D-Bus methods StartFind() and StopFind() on interface + "org.freedesktop.NetworkManager.Device.WifiP2P" now require the + "org.freedesktop.NetworkManager.wifi.scan" Polkit permission. +* Drop build support with Python2. Python3 is now required. +* nmcli: limit number of printed addresses/routes in `nmcli` overview to 10. +* Limit number of exported IP addresses/routes on D-Bus to 100 to reduce + performance cost. Also, D-Bus updates for addresses/routes are now rate + limited to 3 per second. +* cloud-setup: enable more sandboxing options in systemd service file. ============================================= NetworkManager-1.44 diff --git a/README.md b/README.md index 1676c2d6..7eed9c9f 100644 --- a/README.md +++ b/README.md @@ -1,9 +1,5 @@ -****************** -NetworkManager core daemon has moved to gitlab.freedesktop.org! - -git clone https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git -****************** - +NetworkManager +============== Networking that Just Works -------------------------- @@ -31,7 +27,8 @@ network. NetworkManager will _never_ activate a connection that is not in this list, or that the user has not directed NetworkManager to connect to. -How it works: +How it works +------------ The NetworkManager daemon runs as a privileged service (since it must access and control hardware), but provides a D-Bus interface on the system bus to @@ -56,7 +53,34 @@ link-local addresses. Most communication with these daemons occurs, again, via D-Bus. +How to use it +------------- + +Install NetworkManager with your distribution's package manager. + +As NetworkManager is actually a daemon that runs in the background, you need to +use one of the many existing client programs to interact with it. + +Terminal clients: +- `nmcli`: advanced command line client that gives you full control over all the + aspects of NetworkManager, developed as part of the NetworkManager project. +- `nmtui`: text-based user interface (TUI) client. Also for the terminal, but + interactive and more user friendly, also part of the NetworkManager project. +- [`nmstate`][1]: declarative network API and command line tool that uses + NetworkManager as backend. +- Ansible: use the [network-role][2] in your playbooks + +GUI clients +- `nm-connection-editor` and `nm-applet`: basic GUI interfaces developed by + the NetworkManager project. +- GNOME shell: interacts with NetworkManager via its default settings panel + `gnome-control-center` +- KDE Plasma: interacts with NetworkManager via its default settings panel + and `plasma-nm` + + Why doesn't my network Just Work? +--------------------------------- Driver problems are the #1 cause of why NetworkManager sometimes fails to connect to wireless networks. Often, the driver simply doesn't behave in a @@ -86,3 +110,45 @@ distribution directs syslog's 'daemon' facility output, as enormously. See the logging section of file contrib/fedora/rpm/NetworkManager.conf for how to enable debug logging in NetworkManager. + + +Documentation +------------- + +Updated documentation can be found at https://networkmanager.dev/docs + +Users can consult the man pages. Most relevant pages for normal users are: +- NetworkManager daemon: [`NetworkManager (8)`][3], [`NetworkManager.conf (5)`][4] +- nmcli: [`nmcli (1)`][5], [`nmcli-examples (5)`][6], [`nm-settings-nmcli (5)`][7] +- nmtui: [`nmtui (1)`][8] + + +Get in touch +------------ + +To connect with the community, get help or get involved see the available +communication channels at https://networkmanager.dev/community/ + +Report bugs or feature request in our [issue tracker](https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues). +See [Report issues](https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/main/CONTRIBUTING.md?ref_type=heads#report-issues) +for details about how to do it. + +To get involved, see [CONTRIBUTING.md](CONTRIBUTING.md) + + +License +------- + +NetworkManager is free software under GPL-2.0-or-later and LGPL-2.1-or-later. +See [CONTRIBUTING.md#legal](CONTRIBUTING.md#legal) and +[RELICENSE.md](RELICENSE.md) for details. + + +[1]: https://nmstate.io/ +[2]: https://linux-system-roles.github.io/network/ +[3]: https://networkmanager.dev/docs/api/latest/NetworkManager.html +[4]: https://networkmanager.dev/docs/api/latest/NetworkManager.conf.html +[5]: https://networkmanager.dev/docs/api/latest/nmcli.html +[6]: https://networkmanager.dev/docs/api/latest/nmcli-examples.html +[7]: https://networkmanager.dev/docs/api/latest/nm-settings-nmcli.html +[8]: https://networkmanager.dev/docs/api/latest/nmtui.html diff --git a/configure b/configure index 59b623df..a368ca8f 100755 --- a/configure +++ b/configure @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.71 for NetworkManager 1.44.2. +# Generated by GNU Autoconf 2.71 for NetworkManager 1.45.90. # # Report bugs to . # @@ -622,8 +622,8 @@ MAKEFLAGS= # Identity of this package. PACKAGE_NAME='NetworkManager' PACKAGE_TARNAME='NetworkManager' -PACKAGE_VERSION='1.44.2' -PACKAGE_STRING='NetworkManager 1.44.2' +PACKAGE_VERSION='1.45.90' +PACKAGE_STRING='NetworkManager 1.45.90' PACKAGE_BUGREPORT='http://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager' PACKAGE_URL='' @@ -825,10 +825,6 @@ SYSTEMD_JOURNAL_LIBS SYSTEMD_JOURNAL_CFLAGS LIBSYSTEMD_LIBS LIBSYSTEMD_CFLAGS -HAVE_SYSTEMD_200_FALSE -HAVE_SYSTEMD_200_TRUE -SYSTEMD_200_LIBS -SYSTEMD_200_CFLAGS systemdsystemunitdir HAVE_SYSTEMD_FALSE HAVE_SYSTEMD_TRUE @@ -852,7 +848,6 @@ INTROSPECTION_GIRDIR INTROSPECTION_GENERATE INTROSPECTION_COMPILER INTROSPECTION_SCANNER -AM_TESTS_FD_REDIRECT LOG_DRIVER GLIB_LIBS GLIB_CFLAGS @@ -1158,8 +1153,6 @@ LIBUDEV_CFLAGS LIBUDEV_LIBS QT_CFLAGS QT_LIBS -SYSTEMD_200_CFLAGS -SYSTEMD_200_LIBS LIBSYSTEMD_CFLAGS LIBSYSTEMD_LIBS SYSTEMD_JOURNAL_CFLAGS @@ -1749,7 +1742,7 @@ if test "$ac_init_help" = "long"; then # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures NetworkManager 1.44.2 to adapt to many kinds of systems. +\`configure' configures NetworkManager 1.45.90 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1821,7 +1814,7 @@ fi if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of NetworkManager 1.44.2:";; + short | recursive ) echo "Configuration of NetworkManager 1.45.90:";; esac cat <<\_ACEOF @@ -2036,10 +2029,6 @@ Some influential environment variables: linker flags for LIBUDEV, overriding pkg-config QT_CFLAGS C compiler flags for QT, overriding pkg-config QT_LIBS linker flags for QT, overriding pkg-config - SYSTEMD_200_CFLAGS - C compiler flags for SYSTEMD_200, overriding pkg-config - SYSTEMD_200_LIBS - linker flags for SYSTEMD_200, overriding pkg-config LIBSYSTEMD_CFLAGS C compiler flags for LIBSYSTEMD, overriding pkg-config LIBSYSTEMD_LIBS @@ -2181,7 +2170,7 @@ fi test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -NetworkManager configure 1.44.2 +NetworkManager configure 1.45.90 generated by GNU Autoconf 2.71 Copyright (C) 2021 Free Software Foundation, Inc. @@ -2902,7 +2891,7 @@ cat >config.log <<_ACEOF This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by NetworkManager $as_me 1.44.2, which was +It was created by NetworkManager $as_me 1.45.90, which was generated by GNU Autoconf 2.71. Invocation command line was $ $0$ac_configure_args_raw @@ -4398,7 +4387,7 @@ fi # Define the identity of the package. PACKAGE='NetworkManager' - VERSION='1.44.2' + VERSION='1.45.90' printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h @@ -4436,47 +4425,16 @@ AMTAR='$${TAR-tar}' # We'll loop over all known methods to create a tar archive until one works. -_am_tools='gnutar plaintar pax cpio none' - -# The POSIX 1988 'ustar' format is defined with fixed-size fields. - # There is notably a 21 bits limit for the UID and the GID. In fact, - # the 'pax' utility can hang on bigger UID/GID (see automake bug#8343 - # and bug#13588). - am_max_uid=2097151 # 2^21 - 1 - am_max_gid=$am_max_uid - # The $UID and $GID variables are not portable, so we need to resort - # to the POSIX-mandated id(1) utility. Errors in the 'id' calls - # below are definitely unexpected, so allow the users to see them - # (that is, avoid stderr redirection). - am_uid=`id -u || echo unknown` - am_gid=`id -g || echo unknown` - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking whether UID '$am_uid' is supported by ustar format" >&5 -printf %s "checking whether UID '$am_uid' is supported by ustar format... " >&6; } - if test $am_uid -le $am_max_uid; then - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5 -printf "%s\n" "yes" >&6; } - else - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5 -printf "%s\n" "no" >&6; } - _am_tools=none - fi - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking whether GID '$am_gid' is supported by ustar format" >&5 -printf %s "checking whether GID '$am_gid' is supported by ustar format... " >&6; } - if test $am_gid -le $am_max_gid; then - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5 -printf "%s\n" "yes" >&6; } - else - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5 -printf "%s\n" "no" >&6; } - _am_tools=none - fi +_am_tools='gnutar pax cpio none' + + - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking how to create a ustar tar archive" >&5 -printf %s "checking how to create a ustar tar archive... " >&6; } + { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking how to create a pax tar archive" >&5 +printf %s "checking how to create a pax tar archive... " >&6; } # Go ahead even if we have the value already cached. We do so because we # need to set the values for the 'am__tar' and 'am__untar' variables. - _am_tools=${am_cv_prog_tar_ustar-$_am_tools} + _am_tools=${am_cv_prog_tar_pax-$_am_tools} for _am_tool in $_am_tools; do case $_am_tool in @@ -4488,8 +4446,8 @@ printf %s "checking how to create a ustar tar archive... " >&6; } echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && break done - am__tar="$_am_tar --format=ustar -chf - "'"$$tardir"' - am__tar_="$_am_tar --format=ustar -chf - "'"$tardir"' + am__tar="$_am_tar --format=posix -chf - "'"$$tardir"' + am__tar_="$_am_tar --format=posix -chf - "'"$tardir"' am__untar="$_am_tar -xf -" ;; plaintar) @@ -4501,14 +4459,14 @@ printf %s "checking how to create a ustar tar archive... " >&6; } am__untar='tar xf -' ;; pax) - am__tar='pax -L -x ustar -w "$$tardir"' - am__tar_='pax -L -x ustar -w "$tardir"' + am__tar='pax -L -x pax -w "$$tardir"' + am__tar_='pax -L -x pax -w "$tardir"' am__untar='pax -r' ;; cpio) - am__tar='find "$$tardir" -print | cpio -o -H ustar -L' - am__tar_='find "$tardir" -print | cpio -o -H ustar -L' - am__untar='cpio -i -H ustar -d' + am__tar='find "$$tardir" -print | cpio -o -H pax -L' + am__tar_='find "$tardir" -print | cpio -o -H pax -L' + am__untar='cpio -i -H pax -d' ;; none) am__tar=false @@ -4519,7 +4477,7 @@ printf %s "checking how to create a ustar tar archive... " >&6; } # If the value was cached, stop now. We just wanted to have am__tar # and am__untar set. - test -n "${am_cv_prog_tar_ustar}" && break + test -n "${am_cv_prog_tar_pax}" && break # tar/untar a dummy directory, and stop if the command works. rm -rf conftest.dir @@ -4547,15 +4505,15 @@ printf %s "checking how to create a ustar tar archive... " >&6; } done rm -rf conftest.dir - if test ${am_cv_prog_tar_ustar+y} + if test ${am_cv_prog_tar_pax+y} then : printf %s "(cached) " >&6 else $as_nop - am_cv_prog_tar_ustar=$_am_tool + am_cv_prog_tar_pax=$_am_tool fi - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_prog_tar_ustar" >&5 -printf "%s\n" "$am_cv_prog_tar_ustar" >&6; } + { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $am_cv_prog_tar_pax" >&5 +printf "%s\n" "$am_cv_prog_tar_pax" >&6; } @@ -19337,9 +19295,9 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu NM_MAJOR_VERSION=1 -NM_MINOR_VERSION=44 -NM_MICRO_VERSION=2 -NM_VERSION=1.44.2 +NM_MINOR_VERSION=45 +NM_MICRO_VERSION=90 +NM_VERSION=1.45.90 @@ -19347,7 +19305,7 @@ NM_VERSION=1.44.2 -NM_GIT_SHA=8bee6ef894a27ffc8a464df3b32b03e811e1a15d +NM_GIT_SHA=ee21ca8743e28f1c10933f3829f43a1d3b7ea2d8 if test """" != "no-config-h" ; then @@ -23274,167 +23232,12 @@ if test -n "$GLIB_CFLAGS"; then pkg_cv_GLIB_CFLAGS="$GLIB_CFLAGS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gio-unix-2.0 >= 2.37.6 gmodule-2.0\""; } >&5 - ($PKG_CONFIG --exists --print-errors "gio-unix-2.0 >= 2.37.6 gmodule-2.0") 2>&5 - ac_status=$? - printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 - test $ac_status = 0; }; then - pkg_cv_GLIB_CFLAGS=`$PKG_CONFIG --cflags "gio-unix-2.0 >= 2.37.6 gmodule-2.0" 2>/dev/null` - test "x$?" != "x0" && pkg_failed=yes -else - pkg_failed=yes -fi - else - pkg_failed=untried -fi -if test -n "$GLIB_LIBS"; then - pkg_cv_GLIB_LIBS="$GLIB_LIBS" - elif test -n "$PKG_CONFIG"; then - if test -n "$PKG_CONFIG" && \ - { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gio-unix-2.0 >= 2.37.6 gmodule-2.0\""; } >&5 - ($PKG_CONFIG --exists --print-errors "gio-unix-2.0 >= 2.37.6 gmodule-2.0") 2>&5 - ac_status=$? - printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 - test $ac_status = 0; }; then - pkg_cv_GLIB_LIBS=`$PKG_CONFIG --libs "gio-unix-2.0 >= 2.37.6 gmodule-2.0" 2>/dev/null` - test "x$?" != "x0" && pkg_failed=yes -else - pkg_failed=yes -fi - else - pkg_failed=untried -fi - - - -if test $pkg_failed = yes; then - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5 -printf "%s\n" "no" >&6; } - -if $PKG_CONFIG --atleast-pkgconfig-version 0.20; then - _pkg_short_errors_supported=yes -else - _pkg_short_errors_supported=no -fi - if test $_pkg_short_errors_supported = yes; then - GLIB_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "gio-unix-2.0 >= 2.37.6 gmodule-2.0" 2>&1` - else - GLIB_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "gio-unix-2.0 >= 2.37.6 gmodule-2.0" 2>&1` - fi - # Put the nasty error message in config.log where it belongs - echo "$GLIB_PKG_ERRORS" >&5 - - -pkg_failed=no -{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for GLIB" >&5 -printf %s "checking for GLIB... " >&6; } - -if test -n "$GLIB_CFLAGS"; then - pkg_cv_GLIB_CFLAGS="$GLIB_CFLAGS" - elif test -n "$PKG_CONFIG"; then - if test -n "$PKG_CONFIG" && \ - { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gio-unix-2.0 >= 2.40 gmodule-2.0\""; } >&5 - ($PKG_CONFIG --exists --print-errors "gio-unix-2.0 >= 2.40 gmodule-2.0") 2>&5 - ac_status=$? - printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 - test $ac_status = 0; }; then - pkg_cv_GLIB_CFLAGS=`$PKG_CONFIG --cflags "gio-unix-2.0 >= 2.40 gmodule-2.0" 2>/dev/null` - test "x$?" != "x0" && pkg_failed=yes -else - pkg_failed=yes -fi - else - pkg_failed=untried -fi -if test -n "$GLIB_LIBS"; then - pkg_cv_GLIB_LIBS="$GLIB_LIBS" - elif test -n "$PKG_CONFIG"; then - if test -n "$PKG_CONFIG" && \ - { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gio-unix-2.0 >= 2.40 gmodule-2.0\""; } >&5 - ($PKG_CONFIG --exists --print-errors "gio-unix-2.0 >= 2.40 gmodule-2.0") 2>&5 - ac_status=$? - printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 - test $ac_status = 0; }; then - pkg_cv_GLIB_LIBS=`$PKG_CONFIG --libs "gio-unix-2.0 >= 2.40 gmodule-2.0" 2>/dev/null` - test "x$?" != "x0" && pkg_failed=yes -else - pkg_failed=yes -fi - else - pkg_failed=untried -fi - - - -if test $pkg_failed = yes; then - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5 -printf "%s\n" "no" >&6; } - -if $PKG_CONFIG --atleast-pkgconfig-version 0.20; then - _pkg_short_errors_supported=yes -else - _pkg_short_errors_supported=no -fi - if test $_pkg_short_errors_supported = yes; then - GLIB_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "gio-unix-2.0 >= 2.40 gmodule-2.0" 2>&1` - else - GLIB_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "gio-unix-2.0 >= 2.40 gmodule-2.0" 2>&1` - fi - # Put the nasty error message in config.log where it belongs - echo "$GLIB_PKG_ERRORS" >&5 - - as_fn_error $? "Package requirements (gio-unix-2.0 >= 2.40 gmodule-2.0) were not met: - -$GLIB_PKG_ERRORS - -Consider adjusting the PKG_CONFIG_PATH environment variable if you -installed software in a non-standard prefix. - -Alternatively, you may set the environment variables GLIB_CFLAGS -and GLIB_LIBS to avoid the need to call pkg-config. -See the pkg-config man page for more details." "$LINENO" 5 -elif test $pkg_failed = untried; then - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5 -printf "%s\n" "no" >&6; } - { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 -printf "%s\n" "$as_me: error: in \`$ac_pwd':" >&2;} -as_fn_error $? "The pkg-config script could not be found or is too old. Make sure it -is in your PATH or set the PKG_CONFIG environment variable to the full -path to pkg-config. - -Alternatively, you may set the environment variables GLIB_CFLAGS -and GLIB_LIBS to avoid the need to call pkg-config. -See the pkg-config man page for more details. - -To get pkg-config, see . -See \`config.log' for more details" "$LINENO" 5; } -else - GLIB_CFLAGS=$pkg_cv_GLIB_CFLAGS - GLIB_LIBS=$pkg_cv_GLIB_LIBS - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5 -printf "%s\n" "yes" >&6; } - -fi - LOG_DRIVER='$(top_srcdir)/build-aux/test-driver' - -elif test $pkg_failed = untried; then - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5 -printf "%s\n" "no" >&6; } - -pkg_failed=no -{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for GLIB" >&5 -printf %s "checking for GLIB... " >&6; } - -if test -n "$GLIB_CFLAGS"; then - pkg_cv_GLIB_CFLAGS="$GLIB_CFLAGS" - elif test -n "$PKG_CONFIG"; then - if test -n "$PKG_CONFIG" && \ - { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gio-unix-2.0 >= 2.40 gmodule-2.0\""; } >&5 - ($PKG_CONFIG --exists --print-errors "gio-unix-2.0 >= 2.40 gmodule-2.0") 2>&5 + { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gio-unix-2.0 >= 2.42 gmodule-2.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "gio-unix-2.0 >= 2.42 gmodule-2.0") 2>&5 ac_status=$? printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_GLIB_CFLAGS=`$PKG_CONFIG --cflags "gio-unix-2.0 >= 2.40 gmodule-2.0" 2>/dev/null` + pkg_cv_GLIB_CFLAGS=`$PKG_CONFIG --cflags "gio-unix-2.0 >= 2.42 gmodule-2.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -23446,12 +23249,12 @@ if test -n "$GLIB_LIBS"; then pkg_cv_GLIB_LIBS="$GLIB_LIBS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gio-unix-2.0 >= 2.40 gmodule-2.0\""; } >&5 - ($PKG_CONFIG --exists --print-errors "gio-unix-2.0 >= 2.40 gmodule-2.0") 2>&5 + { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gio-unix-2.0 >= 2.42 gmodule-2.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "gio-unix-2.0 >= 2.42 gmodule-2.0") 2>&5 ac_status=$? printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_GLIB_LIBS=`$PKG_CONFIG --libs "gio-unix-2.0 >= 2.40 gmodule-2.0" 2>/dev/null` + pkg_cv_GLIB_LIBS=`$PKG_CONFIG --libs "gio-unix-2.0 >= 2.42 gmodule-2.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -23472,14 +23275,14 @@ else _pkg_short_errors_supported=no fi if test $_pkg_short_errors_supported = yes; then - GLIB_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "gio-unix-2.0 >= 2.40 gmodule-2.0" 2>&1` + GLIB_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "gio-unix-2.0 >= 2.42 gmodule-2.0" 2>&1` else - GLIB_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "gio-unix-2.0 >= 2.40 gmodule-2.0" 2>&1` + GLIB_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "gio-unix-2.0 >= 2.42 gmodule-2.0" 2>&1` fi # Put the nasty error message in config.log where it belongs echo "$GLIB_PKG_ERRORS" >&5 - as_fn_error $? "Package requirements (gio-unix-2.0 >= 2.40 gmodule-2.0) were not met: + as_fn_error $? "Package requirements (gio-unix-2.0 >= 2.42 gmodule-2.0) were not met: $GLIB_PKG_ERRORS @@ -23511,20 +23314,11 @@ else printf "%s\n" "yes" >&6; } fi - LOG_DRIVER='$(top_srcdir)/build-aux/test-driver' -else - GLIB_CFLAGS=$pkg_cv_GLIB_CFLAGS - GLIB_LIBS=$pkg_cv_GLIB_LIBS - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5 -printf "%s\n" "yes" >&6; } - LOG_DRIVER='$(top_srcdir)/build-aux/tap-driver.sh' +LOG_DRIVER='$(top_srcdir)/build-aux/test-driver' - AM_TESTS_FD_REDIRECT='--tap' -fi - -GLIB_CFLAGS="$GLIB_CFLAGS -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_40 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_40" +GLIB_CFLAGS="$GLIB_CFLAGS -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_42 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_42" @@ -23906,86 +23700,6 @@ if test "$with_systemdsystemunitdir" != no; then fi - -pkg_failed=no -{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for SYSTEMD_200" >&5 -printf %s "checking for SYSTEMD_200... " >&6; } - -if test -n "$SYSTEMD_200_CFLAGS"; then - pkg_cv_SYSTEMD_200_CFLAGS="$SYSTEMD_200_CFLAGS" - elif test -n "$PKG_CONFIG"; then - if test -n "$PKG_CONFIG" && \ - { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"systemd >= 200\""; } >&5 - ($PKG_CONFIG --exists --print-errors "systemd >= 200") 2>&5 - ac_status=$? - printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 - test $ac_status = 0; }; then - pkg_cv_SYSTEMD_200_CFLAGS=`$PKG_CONFIG --cflags "systemd >= 200" 2>/dev/null` - test "x$?" != "x0" && pkg_failed=yes -else - pkg_failed=yes -fi - else - pkg_failed=untried -fi -if test -n "$SYSTEMD_200_LIBS"; then - pkg_cv_SYSTEMD_200_LIBS="$SYSTEMD_200_LIBS" - elif test -n "$PKG_CONFIG"; then - if test -n "$PKG_CONFIG" && \ - { { printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"systemd >= 200\""; } >&5 - ($PKG_CONFIG --exists --print-errors "systemd >= 200") 2>&5 - ac_status=$? - printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 - test $ac_status = 0; }; then - pkg_cv_SYSTEMD_200_LIBS=`$PKG_CONFIG --libs "systemd >= 200" 2>/dev/null` - test "x$?" != "x0" && pkg_failed=yes -else - pkg_failed=yes -fi - else - pkg_failed=untried -fi - - - -if test $pkg_failed = yes; then - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5 -printf "%s\n" "no" >&6; } - -if $PKG_CONFIG --atleast-pkgconfig-version 0.20; then - _pkg_short_errors_supported=yes -else - _pkg_short_errors_supported=no -fi - if test $_pkg_short_errors_supported = yes; then - SYSTEMD_200_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "systemd >= 200" 2>&1` - else - SYSTEMD_200_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "systemd >= 200" 2>&1` - fi - # Put the nasty error message in config.log where it belongs - echo "$SYSTEMD_200_PKG_ERRORS" >&5 - - have_systemd_200=no -elif test $pkg_failed = untried; then - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5 -printf "%s\n" "no" >&6; } - have_systemd_200=no -else - SYSTEMD_200_CFLAGS=$pkg_cv_SYSTEMD_200_CFLAGS - SYSTEMD_200_LIBS=$pkg_cv_SYSTEMD_200_LIBS - { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5 -printf "%s\n" "yes" >&6; } - have_systemd_200=yes -fi - if test "${have_systemd_200}" = "yes"; then - HAVE_SYSTEMD_200_TRUE= - HAVE_SYSTEMD_200_FALSE='#' -else - HAVE_SYSTEMD_200_TRUE='#' - HAVE_SYSTEMD_200_FALSE= -fi - - # Hostname persist mode # Check whether --with-hostname-persist was given. @@ -32425,10 +32139,6 @@ if test -z "${HAVE_SYSTEMD_TRUE}" && test -z "${HAVE_SYSTEMD_FALSE}"; then as_fn_error $? "conditional \"HAVE_SYSTEMD\" was never defined. Usually this means the macro was only invoked conditionally." "$LINENO" 5 fi -if test -z "${HAVE_SYSTEMD_200_TRUE}" && test -z "${HAVE_SYSTEMD_200_FALSE}"; then - as_fn_error $? "conditional \"HAVE_SYSTEMD_200\" was never defined. -Usually this means the macro was only invoked conditionally." "$LINENO" 5 -fi if test -z "${WITH_EBPF_TRUE}" && test -z "${WITH_EBPF_FALSE}"; then as_fn_error $? "conditional \"WITH_EBPF\" was never defined. Usually this means the macro was only invoked conditionally." "$LINENO" 5 @@ -32931,7 +32641,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by NetworkManager $as_me 1.44.2, which was +This file was extended by NetworkManager $as_me 1.45.90, which was generated by GNU Autoconf 2.71. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -32999,7 +32709,7 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_config='$ac_cs_config_escaped' ac_cs_version="\\ -NetworkManager config.status 1.44.2 +NetworkManager config.status 1.45.90 configured by $0, generated by GNU Autoconf 2.71, with options \\"\$ac_cs_config\\" diff --git a/configure.ac b/configure.ac index 6bb296c2..275e87e1 100644 --- a/configure.ac +++ b/configure.ac @@ -7,8 +7,8 @@ dnl - add corresponding NM_VERSION_x_y_z macros in dnl "shared/nm-version-macros.h.in" dnl - update number in meson.build m4_define([nm_major_version], [1]) -m4_define([nm_minor_version], [44]) -m4_define([nm_micro_version], [2]) +m4_define([nm_minor_version], [45]) +m4_define([nm_micro_version], [90]) m4_define([nm_version], [nm_major_version.nm_minor_version.nm_micro_version]) @@ -21,7 +21,7 @@ AC_CONFIG_MACRO_DIR([m4]) AC_CONFIG_AUX_DIR([build-aux]) AC_REQUIRE_AUX_FILE([tap-driver.sh]) -AM_INIT_AUTOMAKE(1.12 foreign tar-ustar no-dist-gzip dist-xz -Wno-portability) dnl NB: Do not [quote] this parameter. +AM_INIT_AUTOMAKE(1.12 foreign tar-pax no-dist-gzip dist-xz -Wno-portability) dnl NB: Do not [quote] this parameter. AM_MAINTAINER_MODE([enable]) AM_SILENT_RULES([yes]) @@ -273,13 +273,11 @@ AC_SEARCH_LIBS([dlopen], [dl dld], [test "$ac_cv_search_dlopen" = "none required" || AC_SUBST([DL_LIBS], "$ac_cv_search_dlopen"]), []) -PKG_CHECK_MODULES(GLIB, [gio-unix-2.0 >= 2.37.6 gmodule-2.0], - [AC_SUBST(LOG_DRIVER, '$(top_srcdir)/build-aux/tap-driver.sh') - AC_SUBST(AM_TESTS_FD_REDIRECT, '--tap')], - [PKG_CHECK_MODULES(GLIB, gio-unix-2.0 >= 2.40 gmodule-2.0) - AC_SUBST(LOG_DRIVER, '$(top_srcdir)/build-aux/test-driver')]) +PKG_CHECK_MODULES(GLIB, [gio-unix-2.0 >= 2.42 gmodule-2.0]) -GLIB_CFLAGS="$GLIB_CFLAGS -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_40 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_40" +AC_SUBST(LOG_DRIVER, '$(top_srcdir)/build-aux/test-driver') + +GLIB_CFLAGS="$GLIB_CFLAGS -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_42 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_42" AC_SUBST(GLIB_CFLAGS) AC_SUBST(GLIB_LIBS) @@ -334,9 +332,6 @@ if test "$with_systemdsystemunitdir" != no; then AC_SUBST([systemdsystemunitdir], [$with_systemdsystemunitdir]) fi -PKG_CHECK_MODULES(SYSTEMD_200, [systemd >= 200], [have_systemd_200=yes], [have_systemd_200=no]) -AM_CONDITIONAL(HAVE_SYSTEMD_200, test "${have_systemd_200}" = "yes") - # Hostname persist mode AC_ARG_WITH(hostname-persist, AS_HELP_STRING([--with-hostname-persist=default|suse|gentoo|slackware], diff --git a/data/NetworkManager-dispatcher.service.in b/data/NetworkManager-dispatcher.service.in index 1a45f353..7861807d 100644 --- a/data/NetworkManager-dispatcher.service.in +++ b/data/NetworkManager-dispatcher.service.in @@ -1,5 +1,6 @@ [Unit] Description=Network Manager Script Dispatcher Service +Documentation=man:NetworkManager-dispatcher.service(8) [Service] Type=dbus diff --git a/data/NetworkManager-wait-online-systemd-pre200.service.in b/data/NetworkManager-wait-online-systemd-pre200.service.in deleted file mode 100644 index 55e4508c..00000000 --- a/data/NetworkManager-wait-online-systemd-pre200.service.in +++ /dev/null @@ -1,15 +0,0 @@ -[Unit] -Description=Network Manager Wait Online -Documentation=man:nm-online(1) -Requisite=NetworkManager.service -After=NetworkManager.service -Wants=network.target -Before=network.target - -[Service] -Type=oneshot -ExecStart=@bindir@/nm-online -s -q --timeout=30 -RemainAfterExit=yes - -[Install] -WantedBy=network.target diff --git a/data/meson.build b/data/meson.build index d617025a..79c88ed7 100644 --- a/data/meson.build +++ b/data/meson.build @@ -12,14 +12,9 @@ if install_systemdunitdir 'NetworkManager-dispatcher.service.in', 'NetworkManager.service.in', 'nm-priv-helper.service.in', + 'NetworkManager-wait-online.service.in', ] - if have_systemd_200 - services += ['NetworkManager-wait-online.service.in'] - else - services += ['NetworkManager-wait-online-systemd-pre200.service.in'] - endif - foreach service: services configure_file( input: service, diff --git a/docs/api/Makefile.am b/docs/api/Makefile.am index 4bdce0e0..069fd639 100644 --- a/docs/api/Makefile.am +++ b/docs/api/Makefile.am @@ -39,6 +39,7 @@ content_files = \ dbus-org.freedesktop.NetworkManager.Device.Bridge.xml \ dbus-org.freedesktop.NetworkManager.Device.Dummy.xml \ dbus-org.freedesktop.NetworkManager.Device.Generic.xml \ + dbus-org.freedesktop.NetworkManager.Device.Hsr.xml \ dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml \ dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml \ dbus-org.freedesktop.NetworkManager.Device.Loopback.xml \ diff --git a/docs/api/Makefile.in b/docs/api/Makefile.in index a5f236f5..6475054c 100644 --- a/docs/api/Makefile.in +++ b/docs/api/Makefile.in @@ -167,7 +167,6 @@ ACLOCAL = @ACLOCAL@ AMTAR = @AMTAR@ AM_CFLAGS = @AM_CFLAGS@ AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ -AM_TESTS_FD_REDIRECT = @AM_TESTS_FD_REDIRECT@ AR = @AR@ AUTOCONF = @AUTOCONF@ AUTOHEADER = @AUTOHEADER@ @@ -356,8 +355,6 @@ SELINUX_LIBS = @SELINUX_LIBS@ SET_MAKE = @SET_MAKE@ SHELL = @SHELL@ STRIP = @STRIP@ -SYSTEMD_200_CFLAGS = @SYSTEMD_200_CFLAGS@ -SYSTEMD_200_LIBS = @SYSTEMD_200_LIBS@ SYSTEMD_INHIBIT_CFLAGS = @SYSTEMD_INHIBIT_CFLAGS@ SYSTEMD_INHIBIT_LIBS = @SYSTEMD_INHIBIT_LIBS@ SYSTEMD_JOURNAL_CFLAGS = @SYSTEMD_JOURNAL_CFLAGS@ @@ -489,6 +486,7 @@ content_files = $(GENERATED_FILES) \ dbus-org.freedesktop.NetworkManager.Device.Bridge.xml \ dbus-org.freedesktop.NetworkManager.Device.Dummy.xml \ dbus-org.freedesktop.NetworkManager.Device.Generic.xml \ + dbus-org.freedesktop.NetworkManager.Device.Hsr.xml \ dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml \ dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml \ dbus-org.freedesktop.NetworkManager.Device.Loopback.xml \ diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.AccessPoint.xml b/docs/api/dbus-org.freedesktop.NetworkManager.AccessPoint.xml index c649b74a..1fb52f5a 100644 --- a/docs/api/dbus-org.freedesktop.NetworkManager.AccessPoint.xml +++ b/docs/api/dbus-org.freedesktop.NetworkManager.AccessPoint.xml @@ -16,6 +16,7 @@ HwAddress readable s Mode readable u MaxBitrate readable u +Bandwidth readable u Strength readable y LastSeen readable i @@ -119,6 +120,16 @@ The maximum bitrate this access point is capable of, in kilobits/second (Kb/s). + + The "Bandwidth" property + org.freedesktop.NetworkManager.AccessPoint:Bandwidth + +Bandwidth readable u + + +The bandwidth announced by the access point in MHz. + + The "Strength" property org.freedesktop.NetworkManager.AccessPoint:Strength diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml new file mode 100644 index 00000000..8376dcd6 --- /dev/null +++ b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml @@ -0,0 +1,83 @@ + + + + org.freedesktop.NetworkManager.Device.Hsr + org.freedesktop.NetworkManager.Device.Hsr + org.freedesktop.NetworkManager.Device.Hsr HSR Device. + Properties + +Port1 readable o +Port2 readable o +SupervisionAddress readable s +MulticastSpec readable y +Prp readable b + + + + Description + + + + + + Property Details + + The "Port1" property + org.freedesktop.NetworkManager.Device.Hsr:Port1 + +Port1 readable o + + +The device's port1 device. + +Since 1.46 + + + The "Port2" property + org.freedesktop.NetworkManager.Device.Hsr:Port2 + +Port2 readable o + + +The device's port2 device. + +Since 1.46 + + + The "SupervisionAddress" property + org.freedesktop.NetworkManager.Device.Hsr:SupervisionAddress + +SupervisionAddress readable s + + +The supervision MAC address. + +Since 1.46 + + + The "MulticastSpec" property + org.freedesktop.NetworkManager.Device.Hsr:MulticastSpec + +MulticastSpec readable y + + +The last byte of the supervision address. + +Since 1.46 + + + The "Prp" property + org.freedesktop.NetworkManager.Device.Hsr:Prp + +Prp readable b + + +Whether the PRP protocol is used or not. + +Since 1.46 + + + + diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.IP4Config.xml b/docs/api/dbus-org.freedesktop.NetworkManager.IP4Config.xml index 94a9ec44..c14e5c41 100644 --- a/docs/api/dbus-org.freedesktop.NetworkManager.IP4Config.xml +++ b/docs/api/dbus-org.freedesktop.NetworkManager.IP4Config.xml @@ -40,7 +40,9 @@ Addresses readable aau Array of arrays of IPv4 address/prefix/gateway. All 3 elements of each array are in network byte order. Essentially: [(addr, prefix, gateway), -(addr, prefix, gateway), ...] Deprecated: use AddressData and Gateway +(addr, prefix, gateway), ...]. + +DEPRECATED: use AddressData and Gateway @@ -76,7 +78,9 @@ Arrays of IPv4 route/prefix/next-hop/metric. All 4 elements of each tuple are in network byte order. 'route' and 'next hop' are IPv4 addresses, while prefix and metric are simple unsigned integers. Essentially: [(route, prefix, next-hop, metric), (route, prefix, next-hop, metric), -...] Deprecated: use RouteData +...]. + +DEPRECATED: use RouteData @@ -98,7 +102,9 @@ address string) and "prefix" (a uint). Some routes may include "next-hop" Nameservers readable au -The nameservers in use. Deprecated: use NameserverData +The nameservers in use. + +DEPRECATED: use NameserverData @@ -162,7 +168,9 @@ WinsServers readable au The Windows Internet Name Service servers associated with the connection. -Each address is in network byte order. Deprecated: use WinsServerData +Each address is in network byte order. + +DEPRECATED: use WinsServerData diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.IP6Config.xml b/docs/api/dbus-org.freedesktop.NetworkManager.IP6Config.xml index 00074df2..55da5265 100644 --- a/docs/api/dbus-org.freedesktop.NetworkManager.IP6Config.xml +++ b/docs/api/dbus-org.freedesktop.NetworkManager.IP6Config.xml @@ -35,8 +35,9 @@ Addresses readable a(ayuay) -Array of tuples of IPv6 address/prefix/gateway. Deprecated: use -AddressData and Gateway. +Array of tuples of IPv6 address/prefix/gateway. + +DEPRECATED: use AddressData and Gateway. @@ -68,7 +69,9 @@ The gateway in use. Routes readable a(ayuayu) -Tuples of IPv6 route/prefix/next-hop/metric. Deprecated: use RouteData +Tuples of IPv6 route/prefix/next-hop/metric. + +DEPRECATED: use RouteData. diff --git a/docs/api/html/NetworkManager-dispatcher.html b/docs/api/html/NetworkManager-dispatcher.html index 88ed3634..b8ef62c3 100644 --- a/docs/api/html/NetworkManager-dispatcher.html +++ b/docs/api/html/NetworkManager-dispatcher.html @@ -51,8 +51,9 @@ device an operation just happened on, and second the action. For device actions, the interface is the name of the kernel interface suitable for IP configuration. Thus it is either VPN_IP_IFACE, DEVICE_IP_IFACE, or DEVICE_IFACE, as applicable. - For the hostname action the device name is always "none" - and for connectivity-change it is empty. + For the hostname action the device name is always + "none". For connectivity-change and + dns-change it is empty.

The actions are:

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

+ + + +

dns-change

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

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

-

slaves-order

-

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

- -

firewall-backend

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

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

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

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

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

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

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

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

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

NM_UNMANAGED

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

- + + +

ID_NET_MANAGED_BY

+

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

+ + +

NM_AUTO_DEFAULT_LINK_LOCAL_ONLY

+

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

+ + +

ID_NET_AUTO_LINK_LOCAL_ONLY

+

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

+ + +

ID_NET_DHCP_BROADCAST

+

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

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

The "Bandwidth" property

+
+Bandwidth  readable   u
+
+

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

+
+
+

The "Strength" property

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

 

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

+

+

+
+
+

+
org.freedesktop.NetworkManager.Device.Hsr

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

+

+

+
Properties

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

+

+

+
Description

+

+

+

+

+

+

+
Property Details

+

+
The "Port1" property

+
+Port1  readable   o
+

+

+The device's port1 device.
+

+
Since 1.46

+

+

+

+
The "Port2" property

+
+Port2  readable   o
+

+

+The device's port2 device.
+

+
Since 1.46

+

+

+

+
The "SupervisionAddress" property

+
+SupervisionAddress  readable   s
+

+

+The supervision MAC address.
+

+
Since 1.46

+

+

+

+
The "MulticastSpec" property

+
+MulticastSpec  readable   y
+

+

+The last byte of the supervision address.
+

+
Since 1.46

+

+

+

+
The "Prp" property

+
+Prp  readable   b
+

+

+Whether the PRP protocol is used or not.
+

+
Since 1.46

+

+

+

+

+
Generated by GTK-Doc V1.33.1

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

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

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

 
 HwAddress      readable   s
 Companion      readable   o
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html
index 571a45e6..ad89fdce 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Slaves  readable   ao
 

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html
index 4dcf9283..a220330d 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

 
 Slaves  readable   ao
 

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html
index 8340f542..56feac4c 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html
@@ -33,7 +33,7 @@
 
 

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

 
 Peer  readable   o
 

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

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

 
 Table  readable   u
 

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

 

-
Properties

+
Properties

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

 

 

-
Signals

+
Signals

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

 

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

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

 

 

-
Signals

+
Signals

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

 

 

-
Properties

+
Properties

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

 

-
Properties

+
Properties

 
 HwAddress  readable   s
 

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

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

+

+DEPRECATED: use AddressData and Gateway
 

 

 

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

+

+DEPRECATED: use RouteData
 

 

 

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

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

+

+DEPRECATED: use NameserverData

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

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

+

+DEPRECATED: use WinsServerData

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

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

+

+DEPRECATED: use AddressData and Gateway.

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

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

+

+DEPRECATED: use RouteData.

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

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

-


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

-

+ Foundation by visiting their Web site.

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

I

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

W

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

Z

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

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

-


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

-

+ General Public License along with this program.

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

NM_DEVICE_TYPE_HSR

+

+ + +

= 33

+

+ + +

A HSR/PRP device. Since: 1.46.

+

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

NM_WIFI_DEVICE_CAP_FREQ_6GHZ

+

+ + +

= 0x00000800

+

+ + +

device supports 6GHz frequencies. Since: 1.46.

+

+ +  + + +

NM_WIFI_DEVICE_CAP_MESH

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

enum NMMetered

-

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

+

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

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

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

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

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

-

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

+

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

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

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

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

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

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

link setting

+

hsr setting

+

HSR/PRP Settings.

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

link setting

Link settings.

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

loopback setting

+

loopback setting

Loopback Link Settings.

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

ovs-external-ids setting

+

ovs-external-ids setting

OVS External IDs Settings.

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

ovs-other-config setting

+

ovs-other-config setting

OVS Other Config Settings.

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

veth setting

+

veth setting

Veth Settings.

diff --git a/docs/api/html/nm-settings-ifcfg-rh.html b/docs/api/html/nm-settings-ifcfg-rh.html index 187e6a08..890e4643 100644 --- a/docs/api/html/nm-settings-ifcfg-rh.html +++ b/docs/api/html/nm-settings-ifcfg-rh.html @@ -32,7 +32,7 @@

Description

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

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

-

Table 23. infiniband setting

+

Table 23. hsr setting

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

Table 24. infiniband setting

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

-

Table 24. ipv4 setting

+

Table 25. ipv4 setting

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

-

Table 25. ipv6 setting

+

Table 26. ipv6 setting

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

-

Table 26. match setting

+

Table 27. match setting

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

-

Table 27. ovs-external-ids setting

+

Table 28. ovs-external-ids setting

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

-

Table 28. ovs-other-config setting

+

Table 29. ovs-other-config setting

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

-

Table 29. proxy setting

+

Table 30. proxy setting

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

-

Table 30. sriov setting

+

Table 31. sriov setting

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

-

Table 31. tc setting

+

Table 32. tc setting

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

-

Table 32. team setting

+

Table 33. team setting

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

-

Table 33. team-port setting

+

Table 34. team-port setting

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

-

Table 34. user setting

+

Table 35. user setting

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

-

Table 35. vlan setting

+

Table 36. vlan setting

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

See Also

-

nm-settings(5), +

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

Description

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

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

File Format

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

+

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

+

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

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

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

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

See Also

-

nm-settings(5), +

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

The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection.

Currently, this only applies to 802-1x authentication.

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

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

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

Format: boolean

+

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

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

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

- Format: int32

+ Format: integer

+

+ Valid values: -999 - 999

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

The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

+

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

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

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

- Format: NMSettingConnectionAutoconnectSlaves (int32)

+ Format: choice (NMSettingConnectionAutoconnectSlaves)

+

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

+ + + +

connection.controller

+ +

+ Alias: controller

+

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

+

+ Format: string

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

The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting.

This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

- Format: int32

+ Format: choice (NMSettingConnectionDnsOverTls)

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 600

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

Whether LLDP is enabled for the connection.

- Format: int32

+ Format: choice (NMSettingConnectionLldp)

+

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

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

The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").

This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

- Format: int32

+ Format: choice (NMSettingConnectionLlmnr)

+

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

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

Alias: master

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

+

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

Format: string

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

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

This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

- Format: int32

+ Format: choice (NMSettingConnectionMdns)

+

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

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

Whether the connection is metered.

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

- Format: NMMetered (int32)

+ Format: ternary

+

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

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

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

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

- Format: uint32

+ Format: flags (NMMptcpFlags)

+

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

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

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

- Format: int32

+ Format: choice (NMConnectionMultiConnect)

+

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

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

An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah".

At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.

- Format: array of string

+ Format: list of strings

+ + + +

connection.port-type

+ +

+ Alias: port-type

+

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

+

+ Format: string

+

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

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

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

- Format: array of string

+ Format: list of strings

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

Alias: slave-type

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

+

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

Format: string

+

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

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

This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.

The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used to derive the DHCP client identifier with ipv4.dhcp-client-id=stable, the DHCPv6 DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid] and the DHCP IAID with ipv4.iaid=stable and ipv6.iaid=stable.

Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.

-

The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.

+

The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-SSID, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. "${NETWORK_SSID}" uses the SSID for Wi-Fi networks and falls back to "${CONNECTION}" on other networks. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.

If the value is unset, a global connection default is consulted. If the value is still unset, the default is "default${CONNECTION}" go generate an ID unique per connection profile.

Format: string

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

The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.

NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).

- Format: uint64

+ Format: read only

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

Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).

Format: string

+

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

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

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

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

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

+ Format: string

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

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

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

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

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

Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed.

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

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

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

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

- Format: array of string

+ Format: list of strings

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

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

- Format: int32

+ Format: integer

+

+ Valid values: 0 - 2147483647

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

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

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

- Format: byte array

+ Format: filesystem path

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

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

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

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

- Format: byte array

+ Format: filesystem path

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

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

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

- Format: array of string

+ Format: list of strings

+

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

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

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

Format: boolean

+

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

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

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

- Format: byte array

+ Format: bytes

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

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

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

- Format: uint32

+ Format: flags (NMSetting8021xAuthFlags)

+

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

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

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

Format: string

+

+ Valid values: 0, 1, 2, 3

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

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

Format: string

+

+ Valid values: 0, 1

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

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

Format: string

+

+ Valid values: 0, 1

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

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

- Format: array of string

+ Format: list of strings

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

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

Format: string

+

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

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

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

Format: string

+

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

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

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

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

- Format: byte array

+ Format: filesystem path

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

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

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

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

- Format: string

+ Format: filesystem path

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

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

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

- Format: byte array

+ Format: filesystem path

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

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

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

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

- Format: byte array

+ Format: filesystem path

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

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

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

Flags indicating how to handle the "pin" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

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

- Format: byte array

+ Format: filesystem path

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

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

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

Format: boolean

+

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

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

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

Format: string

+

+ Valid values: vcmux, llc

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

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

Format: string

+

+ Valid values: pppoa, pppoe, ipoatm

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

VCI of ADSL connection

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65536

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

VPI of ADSL connection

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65536

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

The Bluetooth address of the device.

- Format: byte array

+ Format: MAC address

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

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

Format: string

+

+ Valid values: dun, panu, nap

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

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

- Format: dict of string to string

+ Format: list of key/value options

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

The Ethernet MAC address aging time, in seconds.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 1000000

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 30

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

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

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

- Format: byte array

+ Format: MAC address

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 10

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

- Format: byte array

+ Format: MAC address

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 40

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 1 - 4294967295

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

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

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

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

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

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

Format: boolean

+

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

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

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

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

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

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

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

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

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

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

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

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

Format: boolean

+

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

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

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

Format: string

+

+ Valid values: auto, disabled, enabled

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

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

Format: boolean

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

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

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

Format: boolean

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4094

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

Control whether VLAN filtering is enabled on the bridge.

Format: boolean

+

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

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

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

Format: string

+

+ Valid values: 802.1Q, 802.1ad

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

Controls whether per-VLAN stats accounting is enabled.

Format: boolean

+

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

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

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

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

- Format: array of vardict

+ Format: list of bridge.vlans objects

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

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

Format: boolean

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 63

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

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

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

- Format: array of vardict

+ Format: list of bridge-port.vlans objects

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

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

- Format: uint32

+ Format: integer

+

+ Special values: auto

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

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

dcb.app-fcoe-flags

-

Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

+

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

+

+ Format: flags (NMSettingDcbFlags)

- Format: NMSettingDcbFlags (uint32)

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

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

Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".

Format: string

+

+ Valid values: fabric, vn2vn

dcb.app-fcoe-priority

-

The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.

+

The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the "enable" (0x1) flag.

+

+ Format: integer

- Format: int32

+ Valid values: -1 - 7

+

+ Special values: unset (-1)

dcb.app-fip-flags

-

Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

+

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

+

+ Format: flags (NMSettingDcbFlags)

- Format: NMSettingDcbFlags (uint32)

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

dcb.app-fip-priority

-

The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.

+

The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the "enable" (0x1) flag.

+

+ Format: integer

+

+ Valid values: -1 - 7

- Format: int32

+ Special values: unset (-1)

dcb.app-iscsi-flags

-

Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

+

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

- Format: NMSettingDcbFlags (uint32)

+ Format: flags (NMSettingDcbFlags)

+

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

dcb.app-iscsi-priority

-

The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.

+

The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the "enable" (0x1) flag.

+

+ Format: integer

- Format: int32

+ Valid values: -1 - 7

+

+ Special values: unset (-1)

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

An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents.

- Format: array of uint32

+ Format: list of integers

+

+ Valid values: 0 - 100

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

An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.

- Format: array of uint32

+ Format: list of booleans

+

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

dcb.priority-flow-control-flags

-

Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

+

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

+

+ Format: flags (NMSettingDcbFlags)

- Format: NMSettingDcbFlags (uint32)

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

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

An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents.

- Format: array of uint32

+ Format: list of integers

+

+ Valid values: 0 - 100

dcb.priority-group-flags

-

Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).

+

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

+

+ Format: flags (NMSettingDcbFlags)

- Format: NMSettingDcbFlags (uint32)

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

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

An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.

- Format: array of uint32

+ Format: list of integers

+

+ Valid values: 0 - 7, 15

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

An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.

- Format: array of uint32

+ Format: list of booleans

+

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

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

An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.

- Format: array of uint32

+ Format: list of integers

+

+ Valid values: 0 - 7

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

ethtool.channels-combined

+ +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + + +

ethtool.channels-other

+ +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + + +

ethtool.channels-rx

+ +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + + +

ethtool.channels-tx

+ +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + +

ethtool.coalesce-adaptive-rx

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-adaptive-tx

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-pkt-rate-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-pkt-rate-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-frames

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-frames-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-frames-irq

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-frames-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-usecs

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-usecs-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-usecs-irq

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-rx-usecs-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-sample-interval

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-stats-block-usecs

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-frames

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-frames-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-frames-irq

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-frames-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-usecs

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-usecs-high

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-usecs-irq

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.coalesce-tx-usecs-low

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+ + + +

ethtool.eee-enabled

+ +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-esp-hw-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

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

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-fcoe-mtu

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-gro

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-gso

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-highdma

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-hw-tc-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-l2-fwd-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-loopback

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-lro

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-macsec-hw-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-ntuple

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-all

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-fcs

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-gro-hw

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-gro-list

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-udp-gro-forwarding

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-udp_tunnel-port-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-vlan-filter

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rx-vlan-stag-filter

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

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

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rxhash

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-rxvlan

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-sg

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tls-hw-record

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tls-hw-rx-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tls-hw-tx-offload

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tso

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-fcoe-crc

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-ip-generic

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-ipv4

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-ipv6

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-checksum-sctp

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-esp-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-fcoe-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gre-csum-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gre-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gso-list

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gso-partial

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-gso-robust

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-ipxip4-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-ipxip6-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-nocache-copy

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-scatter-gather

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-scatter-gather-fraglist

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-sctp-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tcp-ecn-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tcp-mangleid-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tcp-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tcp6-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-tunnel-remcsum-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-udp-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-udp_tnl-csum-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-tx-udp_tnl-segmentation

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

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

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.feature-txvlan

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.pause-autoneg

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.pause-rx

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.pause-tx

- + +

+ Format: ternary

+

+ Valid values: on, off, ignore

+

ethtool.ring-rx

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.ring-rx-jumbo

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.ring-rx-mini

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

ethtool.ring-tx

- + +

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

Alias: apn

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

+

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

Format: string

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Special values: auto

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

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

Flags indicating how to handle the "pin" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

- Format: byte array

+ Format: Infiniband MAC address

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

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

- Format: uint32

+ Format: integer

+

+ Special values: auto

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

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

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

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 65535

+

+ Special values: default (-1)

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

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

Format: string

+

+ Valid values: datagram, connected

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

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

- Format: a comma separated list of addresses

+ Format: list of ipv4.addresses objects

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

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

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

- Format: NMTernary (int32)

+ Format: ternary

+

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

ipv4.dad-timeout

-

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

-

The property is currently implemented only for IPv4.

+

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

+

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

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 30000

+

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

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

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

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

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

-

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

+

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

+

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

Format: string

+

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

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

ipv4.dhcp-hostname-flags

Flags for the DHCP hostname and FQDN.

-

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

-

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

+

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

+

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

+

+ Format: flags (NMDhcpHostnameFlags)

- Format: uint32

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

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

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

This property is currently not implemented for DHCPv6.

- Format: array of string

+ Format: list of IPv4 addresses

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

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

Format: boolean

+

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

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

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

Set to 2147483647 (MAXINT32) for infinity.

- Format: int32

+ Format: integer

+

+ Valid values: 0 - 2147483647

+

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

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

Array of IP addresses of DNS servers.

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

- Format: array of uint32

+ Format: list of IPv4 addresses

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

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

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

- Format: a comma separated list of DNS options

+ Format: list of strings

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

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

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

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

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

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

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

- Format: array of string

+ Format: list of strings

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

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

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

- Format: string

+ Format: IPv4 address

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

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

- Format: int32

+ Format: choice (NMSettingIP4LinkLocal)

+

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

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

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

Format: boolean

+

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

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

Format: string

+

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

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

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

Format: boolean

+

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

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

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

- Format: NMTernary (int32)

+ Format: ternary

+

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

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

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

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

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

+

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

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

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

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

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

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

- Format: a comma separated list of routes

+ Format: list of ipv4.routes objects

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

- Format: a comma separated list of routing rules

+ Format: list of ipv4.routing-rules objects

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

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

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

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

+ Format: choice (NMSettingIP6ConfigAddrGenMode)

+

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

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

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

- Format: a comma separated list of addresses

+ Format: list of ipv6.addresses objects

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

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

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

- Format: NMTernary (int32)

+ Format: ternary

+

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

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

ipv6.dhcp-hostname-flags

Flags for the DHCP hostname and FQDN.

-

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

-

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

+

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

+

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

+

+ Format: flags (NMDhcpHostnameFlags)

- Format: uint32

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

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

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

Format: boolean

+

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

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

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

Set to 2147483647 (MAXINT32) for infinity.

- Format: int32

+ Format: integer

+

+ Valid values: 0 - 2147483647

+

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

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

Array of IP addresses of DNS servers.

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

- Format: array of byte array

+ Format: list of IPv6 addresses

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

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

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

- Format: a comma separated list of DNS options

+ Format: list of strings

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

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

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

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

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

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

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

- Format: array of string

+ Format: list of strings

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

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

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

- Format: string

+ Format: IPv6 address

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

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

- Format: NMSettingIP6ConfigPrivacy (int32)

+ Format: choice (NMSettingIP6ConfigPrivacy)

+

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

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

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

Format: boolean

+

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

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

Format: string

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Special values: auto

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

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

Format: boolean

+

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

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

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

Set to 2147483647 (MAXINT32) for infinity.

- Format: int32

+ Format: integer

+

+ Valid values: 0 - 2147483647

+

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

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

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

- Format: NMTernary (int32)

+ Format: ternary

+

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

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

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

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

- Format: int32

+ Format: integer

+

+ Valid values: -1 - 2147483647

+

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

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

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

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

+

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

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

- Format: a comma separated list of routes

+ Format: list of ipv6.routes objects

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

- Format: a comma separated list of routing rules

+ Format: list of ipv6.routing-rules objects

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

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

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

- Format: uint32

+ Format: flags (NMIPTunnelFlags)

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 1048575

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

- Format: uint32

+ Format: choice (NMIPTunnelMode)

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Special values: auto

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

Whether to enable Path MTU Discovery on this tunnel.

Format: boolean

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

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

Whether the transmitted traffic must be encrypted.

Format: boolean

+

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

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

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

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

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

- Format: int32

+ Format: choice (NMSettingMacsecMode)

+

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

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

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

- Format: int32

+ Format: integer

+

+ Valid values: 1 - 65534

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

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

Format: boolean

+

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

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

Specifies the validation mode for incoming frames.

- Format: int32

+ Format: choice (NMSettingMacsecValidation)

+

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

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

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

- Format: uint32

+ Format: choice (NMSettingMacvlanMode)

+

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

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

Whether the interface should be put in promiscuous mode.

Format: boolean

+

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

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

Whether the interface should be a MACVTAP.

Format: boolean

+

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

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

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

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

- Format: array of string

+ Format: list of strings

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

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

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

- Format: array of string

+ Format: list of strings

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

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

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

- Format: array of string

+ Format: list of strings

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

Each element of the list is a shell wildcard pattern.

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

- Format: array of string

+ Format: list of strings

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

Channel on which the mesh network to join is located.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

This is currently only implemented by dhclient DHCP plugin.

- Format: byte array

+ Format: MAC address

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

SSID of the mesh network to join.

- Format: byte array

+ Format: string

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

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

Format: string

+

+ Valid values: system, netdev

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

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

Format: string

+

+ Valid values: secure, standalone

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

Enable or disable multicast snooping.

Format: boolean

+

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

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

Enable or disable RSTP.

Format: boolean

+

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

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

Enable or disable STP.

Format: boolean

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4096

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4096

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65279

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

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

Format: string

+

+ Valid values: internal, system, patch, dpdk

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

Format: string

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

Format: string

+

+ Valid values: active, off, passive

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

The VLAN tag in the range 0-4095.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4095

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

A list of VLAN ranges that this port trunks.

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

- Format: array of vardict

+ Format: list of ovs-port.trunks objects

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

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

Format: string

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

Format: boolean

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

Format: boolean

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 16384

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

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

- Format: uint32

+ Format: integer

+

+ Special values: auto

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

If TRUE, BSD compression will not be requested.

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

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

Format: boolean

+

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

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

Flags indicating how to handle the "password" property.

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

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

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

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

Whether the proxy configuration is for browser only.

Format: boolean

+

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

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

Alias: method

-

Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)

+

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

- Format: int32

+ Format: choice (NMSettingProxyMethod)

+

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

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 5 - 8

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

Parity setting of the serial port.

- Format: NMSettingSerialParity (byte)

+ Format: choice (NMSettingSerialParity)

+

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

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

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

- Format: uint64

+ Format: integer

+

+ Valid values: 0 - 18446744073709551615

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

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

- Format: uint32

+ Format: integer

+

+ Valid values: 1 - 2

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

sriov.autoprobe-drivers

Whether to autoprobe virtual functions by a compatible driver.

-

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

-

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

-

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

+

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

+

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

+

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

- Format: NMTernary (int32)

+ Format: ternary

+

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

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

The total number of virtual functions to create.

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

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

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

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

- Format: array of vardict

+ Format: list of sriov.vfs objects

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

- Format: GPtrArray(NMTCQdisc)

+ Format: list of tc.qdiscs objects

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

- Format: GPtrArray(NMTCTfilter)

+ Format: list of tc.tfilters objects

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

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

- Format: array of vardict

+ Format: list of team.link-watchers objects

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

Corresponds to the teamd mcast_rejoin.count.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

Corresponds to the teamd mcast_rejoin.interval.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

Corresponds to the teamd notify_peers.count.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

Corresponds to the teamd notify_peers.interval.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

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

Format: string

+

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

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

Corresponds to the teamd runner.active.

Format: boolean

+

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

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

Corresponds to the teamd runner.agg_select_policy.

Format: string

+

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

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

Corresponds to the teamd runner.fast_rate.

Format: boolean

+

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

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

Corresponds to the teamd runner.hwaddr_policy.

Format: string

+

+ Valid values: same_all, by_active, only_active

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

Corresponds to the teamd runner.min_ports.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

Corresponds to the teamd runner.sys_prio.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

Corresponds to the teamd runner.tx_balancer.name.

Format: string

+

+ Valid values: basic

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

Corresponds to the teamd runner.tx_balancer.interval.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

Corresponds to the teamd runner.tx_hash.

- Format: array of string

+ Format: list of strings

+

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

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

Corresponds to the teamd ports.PORTIFNAME.lacp_key.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

Corresponds to the teamd ports.PORTIFNAME.lacp_prio.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

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

- Format: array of vardict

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

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

Corresponds to the teamd ports.PORTIFNAME.prio.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

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

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+

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

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

Corresponds to the teamd ports.PORTIFNAME.sticky.

Format: boolean

+

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

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

Alias: mode

-

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

+

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

- Format: uint32

+ Format: choice (NMSettingTunMode)

+

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

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

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

Format: boolean

+

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

@@ -4465,6 +5402,8 @@ Linux traffic control subsystem

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

Format: boolean

+

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

@@ -4475,6 +5414,8 @@ Linux traffic control subsystem

If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.

Format: boolean

+

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

@@ -4500,7 +5441,7 @@ Linux traffic control subsystem Alias: egress

For outgoing packets, a list of mappings from Linux SKB priorities to 802.1p priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".

- Format: array of string

+ Format: list of vlan.egress-priority-map objects

@@ -4508,10 +5449,12 @@ Linux traffic control subsystem

Alias: flags

-

One or more flags which control the behavior and features of the VLAN interface. Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol).

+

One or more flags which control the behavior and features of the VLAN interface. Flags include "reorder-headers" (0x1) (reordering of output packet headers), "gvrp" (0x2) (use of the GVRP protocol), and "loose-binding" (0x4) (loose binding of the interface to its master device's operating state). "mvrp" (0x8) (use of the MVRP protocol).

The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.

- Format: NMVlanFlags (uint32)

+ Format: flags (NMVlanFlags)

+

+ Valid values: reorder-headers (0x1), gvrp (0x2), loose-binding (0x4), mvrp (0x8)

@@ -4521,7 +5464,9 @@ Linux traffic control subsystem Alias: id

The VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4095

@@ -4531,7 +5476,7 @@ Linux traffic control subsystem Alias: ingress

For incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".

- Format: array of string

+ Format: list of vlan.ingress-priority-map objects

@@ -4551,6 +5496,8 @@ Linux traffic control subsystem

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

Format: string

+

+ Valid values: 802.1Q, 802.1ad

@@ -4574,7 +5521,7 @@ Linux traffic control subsystem

Dictionary of key/value pairs of VPN plugin specific data. Both keys and values must be strings.

- Format: dict of string to string

+ Format: list of key/value options

@@ -4583,6 +5530,8 @@ Linux traffic control subsystem

If the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.

Format: boolean

+

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

@@ -4590,7 +5539,7 @@ Linux traffic control subsystem

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

- Format: dict of string to string

+ Format: list of key/value options

@@ -4608,7 +5557,9 @@ Linux traffic control subsystem

Timeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -4643,7 +5594,9 @@ Linux traffic control subsystem Alias: table

The routing table for this VRF.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -4666,7 +5619,9 @@ Linux traffic control subsystem

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -4676,7 +5631,9 @@ Linux traffic control subsystem Alias: destination-port

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -4686,7 +5643,9 @@ Linux traffic control subsystem Alias: id

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 16777215

@@ -4695,6 +5654,8 @@ Linux traffic control subsystem

Specifies whether netlink LL ADDR miss notifications are generated.

Format: boolean

+

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

@@ -4703,6 +5664,8 @@ Linux traffic control subsystem

Specifies whether netlink IP ADDR miss notifications are generated.

Format: boolean

+

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

@@ -4711,6 +5674,8 @@ Linux traffic control subsystem

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

Format: boolean

+

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

@@ -4718,7 +5683,9 @@ Linux traffic control subsystem

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -4747,6 +5714,8 @@ Linux traffic control subsystem

Specifies whether ARP proxy is turned on.

Format: boolean

+

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

@@ -4765,6 +5734,8 @@ Linux traffic control subsystem

Specifies whether route short circuit is turned on.

Format: boolean

+

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

@@ -4774,7 +5745,9 @@ Linux traffic control subsystem Alias: source-port-max

Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -4784,7 +5757,9 @@ Linux traffic control subsystem Alias: source-port-min

Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -4792,7 +5767,9 @@ Linux traffic control subsystem

Specifies the TOS value to use in outgoing packets.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

@@ -4800,7 +5777,9 @@ Linux traffic control subsystem

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

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 255

@@ -4826,7 +5805,7 @@ Linux traffic control subsystem Alias: peer

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

- Format: string

+ Format: MAC address

@@ -4835,7 +5814,7 @@ Linux traffic control subsystem

The Wi-Fi Display (WFD) Information Elements (IEs) to set.

Wi-Fi Display requires a protocol specific information element to be set in certain Wi-Fi frames. These can be specified here for the purpose of establishing a connection. This setting is only useful when implementing a Wi-Fi Display client.

- Format: byte array

+ Format: bytes

@@ -4844,7 +5823,9 @@ Linux traffic control subsystem

Flags indicating which mode of WPS is to be used.

There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.

- Format: uint32

+ Format: flags (NMSettingWirelessSecurityWpsMethod)

+

+ Valid values: default (0x0), disabled (0x1), auto (0x2), pbc (0x4), pin (0x8)

@@ -4873,7 +5854,7 @@ Linux traffic control subsystem This property is deprecated since version 1.2. WiMAX is no longer supported.

- Format: byte array

+ Format: string

@@ -4886,7 +5867,7 @@ Linux traffic control subsystem This property is deprecated since version 1.2. WiMAX is no longer supported.

- Format: string

+ Format: MAC address

@@ -4912,7 +5893,9 @@ Linux traffic control subsystem

When TRUE, setup the interface to accept packets for all MAC addresses. This is enabling the kernel interface flag IFF_PROMISC. When FALSE, the interface will only accept the packets with the interface destination mac address or broadcast.

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -4921,6 +5904,8 @@ Linux traffic control subsystem

When TRUE, enforce auto-negotiation of speed and duplex mode. If "speed" and "duplex" properties are both specified, only that single mode will be advertised and accepted during the link auto-negotiation process: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. When FALSE, "speed" and "duplex" properties should be both set or link configuration will be skipped.

Format: boolean

+

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

@@ -4933,7 +5918,9 @@ Linux traffic control subsystem

If unspecified, the value can be overwritten via global defaults, see manual of NetworkManager.conf. If still unspecified, it defaults to "preserve" (older versions of NetworkManager may use a different default value).

On D-Bus, this field is expressed as "assigned-mac-address" or the deprecated "cloned-mac-address".

- Format: byte array

+ Format: MAC address

+

+ Special values: preserve, permanent, random, stable

@@ -4942,6 +5929,8 @@ Linux traffic control subsystem

When a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.

Format: string

+

+ Valid values: half, full

@@ -4963,7 +5952,7 @@ Linux traffic control subsystem Alias: mac

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

- Format: byte array

+ Format: MAC address

@@ -4971,7 +5960,7 @@ Linux traffic control subsystem

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

- Format: array of string

+ Format: list of MAC addresses

@@ -4981,7 +5970,9 @@ Linux traffic control subsystem Alias: mtu

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

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -4989,7 +5980,7 @@ Linux traffic control subsystem

Specific port type to use if the device supports multiple attachment methods. One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.

- Format: string

+ Format: read only

@@ -4998,6 +5989,8 @@ Linux traffic control subsystem

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

Format: string

+

+ Valid values: qeth, lcs, ctc

@@ -5006,7 +5999,7 @@ Linux traffic control subsystem

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

Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.

- Format: dict of string to string

+ Format: list of key/value options

@@ -5014,7 +6007,7 @@ Linux traffic control subsystem

Identifies specific subchannels that this network device uses for communication with z/VM or s390 host. Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels. The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.

- Format: array of string

+ Format: list of 802-3-ethernet.s390-subchannels objects

@@ -5022,15 +6015,19 @@ Linux traffic control subsystem

When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

802-3-ethernet.wake-on-lan

-

The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).

+

The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of "phy" (0x2), "unicast" (0x4), "multicast" (0x8), "broadcast" (0x10), "arp" (0x20), "magic" (0x40) or the special values "default" (0x1) (to use global settings) and "ignore" (0x8000) (to disable management of Wake-on-LAN in NetworkManager).

+

+ Format: flags (NMSettingWiredWakeOnLan)

- Format: uint32

+ Valid values: phy (0x2), unicast (0x4), multicast (0x8), broadcast (0x10), arp (0x20), magic (0x40), default (0x1), ignore (0x8000)

@@ -5038,7 +6035,7 @@ Linux traffic control subsystem

If specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address. If NULL, no password will be required.

- Format: string

+ Format: MAC address

@@ -5063,7 +6060,9 @@ Linux traffic control subsystem

The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise, it is a 32-bit fwmark for outgoing packets.

Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -5073,7 +6072,9 @@ Linux traffic control subsystem

Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route.

Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips. Since this automatism only makes sense if you also have a peer with an /0 allowed-ips, it is usually not necessary to enable this explicitly. However, you can disable it if you want to configure your own routing and rules.

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -5081,7 +6082,9 @@ Linux traffic control subsystem

Like ip4-auto-default-route, but for the IPv6 default route.

- Format: NMTernary (int32)

+ Format: ternary

+

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

@@ -5089,7 +6092,9 @@ Linux traffic control subsystem

The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -5098,7 +6103,9 @@ Linux traffic control subsystem

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.

If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, this does not take into account the current routes at the time of activation.

- Format: uint32

+ Format: integer

+

+ Special values: auto

@@ -5108,6 +6115,8 @@ Linux traffic control subsystem

Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.

Format: boolean

+

+ Valid values: true/yes/on, false/no/off

@@ -5123,10 +6132,9 @@ Linux traffic control subsystem

Flags indicating how to handle the "private-key" property.

- See the section called “Secret flag types:” for flag values. -

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -5150,12 +6158,14 @@ Linux traffic control subsystem

802-11-wireless.ap-isolation

-

Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode.

-

If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.

-

If set to NM_TERNARY_FALSE (0), devices can talk to each other.

-

When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).

+

Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from "default" (-1) only when the interface is configured in AP mode.

+

If set to "true" (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.

+

If set to "false" (0), devices can talk to each other.

+

When set to "default" (-1), the global default is used; in case the global default is unspecified it is assumed to be "false" (0).

- Format: NMTernary (int32)

+ Format: ternary

+

+ Valid values: true/yes/on, false/no/off, default/unknown

@@ -5164,6 +6174,8 @@ Linux traffic control subsystem

802.11 frequency band of the network. One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11. This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible. This setting depends on specific driver capability and may not work with all drivers.

Format: string

+

+ Valid values: a, bg

@@ -5172,7 +6184,7 @@ Linux traffic control subsystem

If specified, directs the device to only associate with the given access point. This capability is highly driver dependent and not supported by all devices. Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future.

Locking a client profile to a certain BSSID will prevent roaming and also disable background scanning. That can be useful, if there is only one access point for the SSID.

- Format: byte array

+ Format: MAC address

@@ -5180,7 +6192,9 @@ Linux traffic control subsystem

Wireless channel to use for the Wi-Fi connection. The device will only join (or create for Ad-Hoc networks) a Wi-Fi network on the specified channel. Because channel numbers overlap between bands, this property also requires the "band" property to be set.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 4294967295

@@ -5189,11 +6203,13 @@ Linux traffic control subsystem

Alias: cloned-mac

If specified, request that the device use this MAC address instead. This is known as MAC cloning or spoofing.

-

Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random" and "stable" are supported. "preserve" means not to touch the MAC address on activation. "permanent" means to use the permanent hardware address of the device. "random" creates a random MAC address on each connect. "stable" creates a hashed MAC address based on connection.stable-id and a machine dependent key.

+

Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random", "stable" and "stable-ssid" are supported. "preserve" means not to touch the MAC address on activation. "permanent" means to use the permanent hardware address of the device. "random" creates a random MAC address on each connect. "stable" creates a hashed MAC address based on connection.stable-id and a machine dependent key. "stable-ssid" creates a hashed MAC address based on the SSID, the same as setting the stable-id to "${NETWORK_SSID}".

If unspecified, the value can be overwritten via global defaults, see manual of NetworkManager.conf. If still unspecified, it defaults to "preserve" (older versions of NetworkManager may use a different default value).

On D-Bus, this field is expressed as "assigned-mac-address" or the deprecated "cloned-mac-address".

- Format: byte array

+ Format: MAC address

+

+ Special values: preserve, permanent, random, stable, stable-ssid

@@ -5217,6 +6233,8 @@ Linux traffic control subsystem

Note that marking the network as hidden may be a privacy issue for you (in infrastructure mode) or client stations (in AP mode), as the explicit probe-scans are distinctly recognizable on the air.

Format: boolean

+

+ Valid values: true/yes/on, false/no/off

@@ -5226,7 +6244,7 @@ Linux traffic control subsystem Alias: mac

If specified, this connection will only apply to the Wi-Fi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).

- Format: byte array

+ Format: MAC address

@@ -5234,18 +6252,20 @@ Linux traffic control subsystem

A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").

- Format: array of string

+ Format: list of MAC addresses

802-11-wireless.mac-address-randomization

-

One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address).

+

One of "default" (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), "never" (1) (never randomize the MAC address), or "always" (2) (always randomize the MAC address).

This property is deprecated since version 1.4. Use the "cloned-mac-address" property instead.

- Format: uint32

+ Format: choice (NMSettingMacRandomization)

+

+ Valid values: default (0), never (1), always (2)

@@ -5256,6 +6276,8 @@ Linux traffic control subsystem

Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap". If blank, infrastructure is assumed.

Format: string

+

+ Valid values: infrastructure, adhoc, ap, mesh

@@ -5265,15 +6287,19 @@ Linux traffic control subsystem Alias: mtu

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.

- Format: uint32

+ Format: integer

+

+ Special values: auto

802-11-wireless.powersave

-

One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.

+

One of "disable" (2) (disable Wi-Fi power saving), "enable" (3) (enable Wi-Fi power saving), "ignore" (1) (don't touch currently configure setting) or "default" (0) (use the globally configured value). All other values are reserved.

- Format: uint32

+ Format: choice (NMSettingWirelessPowersave)

+

+ Valid values: default (0), ignore (1), disable (2), enable (3)

@@ -5282,7 +6308,7 @@ Linux traffic control subsystem

A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network. NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.

This is not a regular property that the user would configure. Instead, NetworkManager automatically sets the seen BSSIDs and tracks them internally in "/var/lib/NetworkManager/seen-bssids" file.

- Format: array of string

+ Format: read only

@@ -5292,15 +6318,17 @@ Linux traffic control subsystem Alias: ssid

SSID of the Wi-Fi network. Must be specified.

- Format: byte array

+ Format: string

802-11-wireless.wake-on-wlan

-

The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).

+

The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of "any" (0x2), "disconnect" (0x4), "magic" (0x8), "gtk-rekey-failure" (0x10), "eap-identity-request" (0x20), "4way-handshake" (0x40), "rfkill-release" (0x80), "tcp" (0x100) or the special values "default" (0x1) (to use global settings) and "ignore" (0x8000) (to disable management of Wake-on-LAN in NetworkManager).

- Format: uint32

+ Format: flags (NMSettingWirelessWakeOnWLan)

+

+ Valid values: any (0x2), disconnect (0x4), magic (0x8), gtk-rekey-failure (0x10), eap-identity-request (0x20), 4way-handshake (0x40), rfkill-release (0x80), tcp (0x100), all (0x1fe), default (0x1), ignore (0x8000)

@@ -5327,14 +6355,18 @@ Linux traffic control subsystem

When WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here. One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP. When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.

Format: string

+

+ Valid values: open, shared, leap

802-11-wireless-security.fils

-

Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.

+

Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of "default" (0) (use global default value), "disable" (1) (disable FILS), "optional" (2) (enable FILS if the supplicant and the access point support it) or "required" (3) (enable FILS and fail if not supported). When set to "default" (0) and no global default is set, FILS will be optionally enabled.

- Format: int32

+ Format: choice (NMSettingWirelessSecurityFils)

+

+ Valid values: default (0), disable (1), optional (2), required (3)

@@ -5342,7 +6374,9 @@ Linux traffic control subsystem

A list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".

- Format: array of string

+ Format: list of strings

+

+ Valid values: wep40, wep104, tkip, ccmp

@@ -5352,6 +6386,8 @@ Linux traffic control subsystem

This property must be set for any Wi-Fi connection that uses security.

Format: string

+

+ Valid values: none, ieee8021x, wpa-psk, wpa-eap, wpa-eap-suite-b-192, sae, owe

@@ -5367,10 +6403,9 @@ Linux traffic control subsystem

Flags indicating how to handle the "leap-password" property.

- See the section called “Secret flag types:” for flag values. -

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -5386,15 +6421,19 @@ Linux traffic control subsystem

A list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "tkip" or "ccmp".

- Format: array of string

+ Format: list of strings

+

+ Valid values: tkip, ccmp

802-11-wireless-security.pmf

-

Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.

+

Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of "default" (0) (use global default value), "disable" (1) (disable PMF), "optional" (2) (enable PMF if the supplicant and the access point support it) or "required" (3) (enable PMF and fail if not supported). When set to "default" (0) and no global default is set, PMF will be optionally enabled.

+

+ Format: choice (NMSettingWirelessSecurityPmf)

- Format: int32

+ Valid values: default (0), disable (1), optional (2), required (3)

@@ -5402,7 +6441,9 @@ Linux traffic control subsystem

List of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN). If not specified, both WPA and RSN connections are allowed.

- Format: array of string

+ Format: list of strings

+

+ Valid values: wpa, rsn

@@ -5418,10 +6459,9 @@ Linux traffic control subsystem

Flags indicating how to handle the "psk" property.

- See the section called “Secret flag types:” for flag values. -

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

@@ -5429,18 +6469,19 @@ Linux traffic control subsystem

Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.

- See the section called “Secret flag types:” for flag values. -

+ Format: flags (NMSettingSecretFlags)

- Format: NMSettingSecretFlags (uint32)

+ Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)

802-11-wireless-security.wep-key-type

-

Controls the interpretation of WEP keys. Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.

+

Controls the interpretation of WEP keys. Allowed values are "key" (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or "passphrase" (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.

+

+ Format: choice (NMWepKeyType)

- Format: NMWepKeyType (uint32)

+ Valid values: unknown (0), key (1), passphrase (2)

@@ -5480,7 +6521,9 @@ Linux traffic control subsystem

When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here. Valid values are 0 (default key) through 3. Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 3

@@ -5490,7 +6533,9 @@ Linux traffic control subsystem

There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities.

WPS can be disabled by setting this property to a value of 1.

- Format: uint32

+ Format: flags (NMSettingWirelessSecurityWpsMethod)

+

+ Valid values: default (0x0), disabled (0x1), auto (0x2), pbc (0x4), pin (0x8)

@@ -5516,7 +6561,11 @@ Linux traffic control subsystem Alias: channel

IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".

- Format: int32

+ Format: integer

+

+ Valid values: -32768 - 32767

+

+ Special values: default (-1)

@@ -5526,7 +6575,7 @@ Linux traffic control subsystem Alias: mac

If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.

- Format: string

+ Format: WPAN MAC address

@@ -5536,7 +6585,11 @@ Linux traffic control subsystem Alias: page

IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".

- Format: int32

+ Format: integer

+

+ Valid values: -32768 - 32767

+

+ Special values: default (-1)

@@ -5546,7 +6599,11 @@ Linux traffic control subsystem Alias: pan-id

IEEE 802.15.4 Personal Area Network (PAN) identifier.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

+

+ Special values: unset (0xffff)

@@ -5556,7 +6613,11 @@ Linux traffic control subsystem Alias: short-addr

Short IEEE 802.15.4 address to be used within a restricted environment.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

+

+ Special values: unset (0xffff)

@@ -5582,7 +6643,9 @@ Linux traffic control subsystem Alias: prio

The port priority for bond active port re-selection during failover. A higher number means a higher priority in selection. The primary port has the highest priority. This option is only compatible with active-backup, balance-tlb and balance-alb modes.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

@@ -5592,7 +6655,9 @@ Linux traffic control subsystem Alias: queue-id

The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.

- Format: uint32

+ Format: integer

+

+ Valid values: 0 - 65535

@@ -5615,28 +6680,34 @@ Linux traffic control subsystem

hostname.from-dhcp

Whether the system hostname can be determined from DHCP on this connection.

-

When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).

+

When set to "default" (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be "true" (1).

+

+ Format: ternary

- Format: NMTernary (int32)

+ Valid values: true/yes/on, false/no/off, default/unknown

hostname.from-dns-lookup

Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.

-

When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).

+

When set to "default" (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be "true" (1).

- Format: NMTernary (int32)

+ Format: ternary

+

+ Valid values: true/yes/on, false/no/off, default/unknown

hostname.only-from-default

-

If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).

-

If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route.

-

When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).

+

If set to "true" (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).

+

If set to "false" (0), the hostname can be set from this device even if it doesn't have the default route.

+

When set to "default" (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be "false" (0).

+

+ Format: ternary

- Format: NMTernary (int32)

+ Valid values: true/yes/on, false/no/off, default/unknown

@@ -5646,7 +6717,67 @@ Linux traffic control subsystem

If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100.

Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.

- Format: int32

+ Format: integer

+

+ Valid values: -2147483648 - 2147483647

+ + + + + +
+
+

hsr setting

+

HSR/PRP Settings.

+

+ Properties: +

+
++++ + + + + + + + + + + + + + + + + @@ -5654,7 +6785,7 @@ Linux traffic control subsystem
-

link setting

+

link setting

Link settings.

Properties: @@ -5670,7 +6801,11 @@ Linux traffic control subsystem

@@ -5678,7 +6813,11 @@ Linux traffic control subsystem @@ -5686,7 +6825,11 @@ Linux traffic control subsystem @@ -5694,7 +6837,11 @@ Linux traffic control subsystem @@ -5702,7 +6849,7 @@ Linux traffic control subsystem
-

loopback setting

+

loopback setting

Loopback Link Settings.

Properties: @@ -5719,14 +6866,16 @@ Linux traffic control subsystem Alias: mtu

If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.

- Format: uint32

+ Format: integer

+

+ Special values: auto

hsr.multicast-spec

 +

+ Alias: multicast-spec

+

The last byte of supervision address.

+

+ Format: integer

+

+ Valid values: 0 - 255

+

hsr.port1

 +

+ Alias: port1

+

The port1 interface name of the HSR. This property is mandatory.

+

+ Format: string

+

hsr.port2

 +

+ Alias: port2

+

The port2 interface name of the HSR. This property is mandatory.

+

+ Format: string

+

hsr.prp

 +

The protocol used by the interface, whether it is PRP or HSR.

+

+ Format: boolean

+

+ Valid values: true/yes/on, false/no/off

The maximum size of a packet built by the Generic Receive Offload stack for this device. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

+

+ Special values: default (-1)

The maximum segments of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

+

+ Special values: default (-1)

The maximum size of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

+

+ Special values: default (-1)

The size of the transmit queue for the device, in number of packets. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.

- Format: int64

+ Format: integer

+

+ Valid values: -1 - 4294967295

+

+ Special values: default (-1)
-

veth setting

+

veth setting

Veth Settings.

Properties: diff --git a/docs/api/html/nmcli-examples.html b/docs/api/html/nmcli-examples.html index 0a832ab7..fdbed744 100644 --- a/docs/api/html/nmcli-examples.html +++ b/docs/api/html/nmcli-examples.html @@ -187,7 +187,7 @@ B,DISPATCH This command activates a VPN connection profile enabling nmcli to interact with the user ('--ask'): this will allow nmcli to prompt for the VPN password on the command line when the password-flags are set to '0x02' ('always ask', see - nm-settings(5) + nm-settings-nmcli(5) ). This is particularly useful for OTP based VPNs, as the user needs to be prompted for the password each time the connection is activated. @@ -697,7 +697,7 @@ Type "Yes" to commit the changes: Yesnmcli(1), NetworkManager(8), NetworkManager.conf(5), - nm-settings(5), + nm-settings-nmcli(5), nm-online(1), nm-applet(1), nm-connection-editor(1) diff --git a/docs/api/html/ref-dbus-devices.html b/docs/api/html/ref-dbus-devices.html index ffff3da4..91027634 100644 --- a/docs/api/html/ref-dbus-devices.html +++ b/docs/api/html/ref-dbus-devices.html @@ -48,6 +48,9 @@ org.freedesktop.NetworkManager.Device.Generic — Unrecognized Device.

+org.freedesktop.NetworkManager.Device.Hsr — HSR Device. +
+
org.freedesktop.NetworkManager.Device.IPTunnel — IP Tunneling Device.
diff --git a/docs/api/html/ref-settings.html b/docs/api/html/ref-settings.html index 1beceeb8..ce26570f 100644 --- a/docs/api/html/ref-settings.html +++ b/docs/api/html/ref-settings.html @@ -178,6 +178,9 @@ hostname — Hostname settings
+hsr — HSR/PRP Settings +
+
link — Link settings
diff --git a/docs/api/html/settings-6lowpan.html b/docs/api/html/settings-6lowpan.html index 0f6ffd16..867de0e9 100644 --- a/docs/api/html/settings-6lowpan.html +++ b/docs/api/html/settings-6lowpan.html @@ -38,7 +38,7 @@ Properties
-

Table 37. 

+

Table 38. 

diff --git a/docs/api/html/settings-802-11-olpc-mesh.html b/docs/api/html/settings-802-11-olpc-mesh.html index f67b9882..8ac352c8 100644 --- a/docs/api/html/settings-802-11-olpc-mesh.html +++ b/docs/api/html/settings-802-11-olpc-mesh.html @@ -38,7 +38,7 @@ Properties
-

Table 57. 

+

Table 58. 

diff --git a/docs/api/html/settings-802-11-wireless-security.html b/docs/api/html/settings-802-11-wireless-security.html index c6eded77..dedb108d 100644 --- a/docs/api/html/settings-802-11-wireless-security.html +++ b/docs/api/html/settings-802-11-wireless-security.html @@ -38,7 +38,7 @@ Properties
-

Table 82. 

+

Table 83. 

@@ -63,7 +63,7 @@ - + @@ -107,7 +107,7 @@ This property must be set for any Wi-Fi connection that uses security. - + @@ -137,7 +137,7 @@ This property must be set for any Wi-Fi connection that uses security. - + diff --git a/docs/api/html/settings-802-11-wireless.html b/docs/api/html/settings-802-11-wireless.html index 3589a25c..0d402d10 100644 --- a/docs/api/html/settings-802-11-wireless.html +++ b/docs/api/html/settings-802-11-wireless.html @@ -38,7 +38,7 @@ Properties
-

Table 81. 

+

Table 82. 

fils
 
int32
 
0
Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of 0 (default) (use global default value), 1 (disable) (disable FILS), 2 (optional) (enable FILS if the supplicant and the access point support it) or 3 (required) (enable FILS and fail if not supported). When set to 0 (default) and no global default is set, FILS will be optionally enabled. 
group
 
pmf
 
int32
 
0
Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of 0 (default) (use global default value), 1 (disable) (disable PMF), 2 (optional) (enable PMF if the supplicant and the access point support it) or 3 (required) (enable PMF and fail if not supported). When set to 0 (default) and no global default is set, PMF will be optionally enabled. 
proto
 
wep-key-type
 
NMWepKeyType (uint32)
 
Controls the interpretation of WEP keys.  Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.Controls the interpretation of WEP keys.  Allowed values are 1 (key), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or 2 (passphrase), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.
 

 

 
wep-key0

 
@@ -57,13 +57,13 @@
 
-
+When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 0 (false).
@@ -139,7 +139,7 @@ Note that marking the network as hidden may be a privacy issue for you (in infra
 
-
+
@@ -157,7 +157,7 @@ Note that marking the network as hidden may be a privacy issue for you (in infra
 
-
+
@@ -195,7 +195,7 @@ This is not a regular property that the user would configure. Instead, NetworkMa
 
-
+

 
 

ap-isolation

 
NMTernary (int32)

 
Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode.
+Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from -1 (default) only when the interface is configured in AP mode.
 
-If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.
+If set to 1 (true), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.
 
-If set to NM_TERNARY_FALSE (0), devices can talk to each other.
+If set to 0 (false), devices can talk to each other.
 
-When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).
 

 

 
assigned-mac-address
mac-address-randomization

 
uint32

 
0
One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address).One of 0 (default) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  1 (never) (never randomize the MAC address), or 2 (always) (always randomize the MAC address).
 

 

 
mode
powersave

 
uint32

 
0
One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.One of 2 (disable) (disable Wi-Fi power saving), 3 (enable) (enable Wi-Fi power saving), 1 (ignore) (don't touch currently configure setting) or 0 (default) (use the globally configured value). All other values are reserved.
 

 

 
rate
wake-on-wlan

 
uint32

 
1
The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of 0x2 (any), 0x4 (disconnect), 0x8 (magic), 0x10 (gtk-rekey-failure), 0x20 (eap-identity-request), 0x40 (4way-handshake), 0x80 (rfkill-release), 0x100 (tcp) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).
 

 
 

diff --git a/docs/api/html/settings-802-1x.html b/docs/api/html/settings-802-1x.html
index 32c1d60e..f72bffab 100644
--- a/docs/api/html/settings-802-1x.html
+++ b/docs/api/html/settings-802-1x.html
@@ -38,7 +38,7 @@
             Properties
         
 

-
Table 38. 

+
Table 39. 

 
diff --git a/docs/api/html/settings-802-3-ethernet.html b/docs/api/html/settings-802-3-ethernet.html
index 100e5f46..a182b834 100644
--- a/docs/api/html/settings-802-3-ethernet.html
+++ b/docs/api/html/settings-802-3-ethernet.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 79. 

+
Table 80. 

 

 
 

 
@@ -151,7 +151,7 @@ Currently, NetworkManager itself does nothing with this information. However, s3
 
-
+
diff --git a/docs/api/html/settings-adsl.html b/docs/api/html/settings-adsl.html
index e387739d..b380f612 100644
--- a/docs/api/html/settings-adsl.html
+++ b/docs/api/html/settings-adsl.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 39. 

+
Table 40. 

 

 
 

wake-on-lan

 
uint32

 
1
The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of 0x2 (phy), 0x4 (unicast), 0x8 (multicast), 0x10 (broadcast), 0x20 (arp), 0x40 (magic) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).
 

 

 
wake-on-lan-password

 
diff --git a/docs/api/html/settings-bluetooth.html b/docs/api/html/settings-bluetooth.html
index 9c329bbc..4ca42c86 100644
--- a/docs/api/html/settings-bluetooth.html
+++ b/docs/api/html/settings-bluetooth.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 40. 

+
Table 41. 

 

 
 

 
diff --git a/docs/api/html/settings-bond-port.html b/docs/api/html/settings-bond-port.html
index 9b2eb6e5..f924f9d9 100644
--- a/docs/api/html/settings-bond-port.html
+++ b/docs/api/html/settings-bond-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 84. 

+
Table 85. 

 

 
 

 
diff --git a/docs/api/html/settings-bond.html b/docs/api/html/settings-bond.html
index f76e24d1..0fc4d41c 100644
--- a/docs/api/html/settings-bond.html
+++ b/docs/api/html/settings-bond.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 41. 

+
Table 42. 

 

 
 

 
diff --git a/docs/api/html/settings-bridge-port.html b/docs/api/html/settings-bridge-port.html
index 689f63ab..9a666227 100644
--- a/docs/api/html/settings-bridge-port.html
+++ b/docs/api/html/settings-bridge-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 43. 

+
Table 44. 

 

 
 

 
diff --git a/docs/api/html/settings-bridge.html b/docs/api/html/settings-bridge.html
index 745b81b3..5b1531b3 100644
--- a/docs/api/html/settings-bridge.html
+++ b/docs/api/html/settings-bridge.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 42. 

+
Table 43. 

 

 
 

 
diff --git a/docs/api/html/settings-cdma.html b/docs/api/html/settings-cdma.html
index 56fdf8c0..7d3e51d4 100644
--- a/docs/api/html/settings-cdma.html
+++ b/docs/api/html/settings-cdma.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 44. 

+
Table 45. 

 

 
 

 
diff --git a/docs/api/html/settings-connection.html b/docs/api/html/settings-connection.html
index cb7262c2..d451fb79 100644
--- a/docs/api/html/settings-connection.html
+++ b/docs/api/html/settings-connection.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 36. 

+
Table 37. 

 

 
 

 
@@ -94,6 +94,12 @@ Depending on "connection.multi-connect", a profile can (auto)connect only once a
 
+
+
+
+
+
+
@@ -145,7 +151,9 @@ This feature requires a plugin which supports LLMNR. Otherwise, the setting has
 
-
+
@@ -212,6 +220,12 @@ If the per-profile value is unspecified (the default), a global connection defau
 At this time only the "user" [type] is allowed.  Any other values are ignored and reserved for future use.  [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use.  All of [type], [id], and [reserved] must be valid UTF-8.
+
+
+
+
+
+
@@ -227,7 +241,9 @@ At this time only the "user" [type] is allowed.  Any other values are ignored an
 
-
+
@@ -239,7 +255,7 @@ The stable-id is used for generating IPv6 stable private addresses with ipv6.add
 
 Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.
 
-The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$".  For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
+The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-SSID, per-boot, or every time.  The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. "${NETWORK_SSID}" uses the SSID for Wi-Fi networks and falls back to "${CONNECTION}" on other networks. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$".  For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
 
 If the value is unset, a global connection default is consulted. If the value is still unset, the default is "default${CONNECTION}" go generate an ID unique per connection profile.
diff --git a/docs/api/html/settings-dcb.html b/docs/api/html/settings-dcb.html
index 7f179d8f..21152664 100644
--- a/docs/api/html/settings-dcb.html
+++ b/docs/api/html/settings-dcb.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 45. 

+
Table 46. 

 

 
 

Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.
 

 
controller
string
Interface name of the controller device or UUID of the controller connection.

 
dns-over-tls

 
int32

 
-1
master

 
string

 
Interface name of the master device or UUID of the master connection.Interface name of the master device or UUID of the master connection.
+
+Deprecated 1.46. Use "controller" instead, this is just an alias.
 

 

 
mdns

 

 
port-type
string
Setting name of the device type of this port's controller connection (eg, "bond"), or NULL if this connection is not a port.

 
read-only

 
boolean

 
FALSE
slave-type

 
string

 
Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.
+
+Deprecated 1.46. Use "port-type" instead, this is just an alias.
 

 

 
stable-id

 

 
@@ -57,7 +57,7 @@
 
-
+
@@ -71,31 +71,31 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject
 
-
+
-
+
-
+
-
+
-
+
@@ -113,7 +113,7 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject
 
-
+
@@ -125,7 +125,7 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject
 
-
+
diff --git a/docs/api/html/settings-dummy.html b/docs/api/html/settings-dummy.html
index 5193e674..63d50436 100644
--- a/docs/api/html/settings-dummy.html
+++ b/docs/api/html/settings-dummy.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 46. 

+
Table 47. 

 

 
 

app-fcoe-flags

 
NMSettingDcbFlags (uint32)

 
Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
app-fcoe-mode
app-fcoe-priority

 
int32

 
-1
The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the 0x1 (enable) flag.
 

 

 
app-fip-flags

 
NMSettingDcbFlags (uint32)

 
Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
app-fip-priority

 
int32

 
-1
The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the 0x1 (enable) flag.
 

 

 
app-iscsi-flags

 
NMSettingDcbFlags (uint32)

 
Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
app-iscsi-priority

 
int32

 
-1
The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the 0x1 (enable) flag.
 

 

 
priority-bandwidth
priority-flow-control-flags

 
NMSettingDcbFlags (uint32)

 
Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
priority-group-bandwidth
priority-group-flags

 
NMSettingDcbFlags (uint32)

 
Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).
 

 

 
priority-group-id

 
diff --git a/docs/api/html/settings-ethtool.html b/docs/api/html/settings-ethtool.html
index 0013fe8d..d89dda9f 100644
--- a/docs/api/html/settings-ethtool.html
+++ b/docs/api/html/settings-ethtool.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 47. 

+
Table 48. 

 

 
 

 
diff --git a/docs/api/html/settings-generic.html b/docs/api/html/settings-generic.html
index 5c1254d8..4beac3ac 100644
--- a/docs/api/html/settings-generic.html
+++ b/docs/api/html/settings-generic.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 48. 

+
Table 49. 

 

 
 

 
diff --git a/docs/api/html/settings-gsm.html b/docs/api/html/settings-gsm.html
index 0e250b4a..b0eab6b0 100644
--- a/docs/api/html/settings-gsm.html
+++ b/docs/api/html/settings-gsm.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 49. 

+
Table 50. 

 

 
 

 
@@ -57,7 +57,9 @@
 
-
+
diff --git a/docs/api/html/settings-hostname.html b/docs/api/html/settings-hostname.html
index 4f6fe458..acaffc6f 100644
--- a/docs/api/html/settings-hostname.html
+++ b/docs/api/html/settings-hostname.html
@@ -7,7 +7,7 @@
 
-
+
@@ -22,7 +22,7 @@
 
-
+

 
 

apn

 
string

 
The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network.  The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network.  The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.
+
+If the APN is unset (the default) then it may be detected based on "auto-config" setting. The property can be explicitly set to the empty string to prevent that and use no APN.
 

 

 
auto-config

 
 
 
 
 Home
 Up
 PrevNextNext
 

 

 

@@ -38,7 +38,7 @@
             Properties
         
 

-
Table 85. 

+
Table 86. 

 
@@ -59,7 +59,7 @@
 
+When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 1 (true).
@@ -67,17 +67,17 @@ When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used
 
+When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 1 (true).
-
+When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 0 (false).
diff --git a/docs/api/html/settings-hsr.html b/docs/api/html/settings-hsr.html
new file mode 100644
index 00000000..855002f8
--- /dev/null
+++ b/docs/api/html/settings-hsr.html
@@ -0,0 +1,89 @@
+
+
+
+
+hsr: NetworkManager Reference Manual
+
+
+
+
+
+
+
+
+
+

 
 


 Whether the system hostname can be determined from DHCP on this connection.
 
-When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).
 

 

 
from-dns-lookup

 Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.
 
-When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).
 

 

 
only-from-default

 
NMTernary (int32)

 
If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).
+If set to 1 (true), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).
 
-If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route.
+If set to 0 (false), the hostname can be set from this device even if it doesn't have the default route.
 
-When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).
 

 

 
priority

+
+
+
+
+
+
+

+

+

+
+
+

+
hsr

+
hsr — HSR/PRP Settings

+

+

+

+            Properties
+        

+

+
Table 87. 

+

++++++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+






Key NameValue TypeDefault ValueValue Description
multicast-spec
uint32
0
The last byte of supervision address.
port1
string
The port1 interface name of the HSR. This property is mandatory.
port2
string
The port2 interface name of the HSR. This property is mandatory.
prp
boolean
FALSE
The protocol used by the interface, whether it is PRP or HSR.

+

+


+

+

+

+
Generated by GTK-Doc V1.33.1

+
+
\ No newline at end of file
diff --git a/docs/api/html/settings-infiniband.html b/docs/api/html/settings-infiniband.html
index c7a5e73c..797cd995 100644
--- a/docs/api/html/settings-infiniband.html
+++ b/docs/api/html/settings-infiniband.html
@@ -38,7 +38,7 @@
             Properties
         
 

-
Table 50. 

+
Table 51. 

 
diff --git a/docs/api/html/settings-ip-tunnel.html b/docs/api/html/settings-ip-tunnel.html
index 25615224..5fcffc84 100644
--- a/docs/api/html/settings-ip-tunnel.html
+++ b/docs/api/html/settings-ip-tunnel.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 53. 

+
Table 54. 

 

 
 

 
@@ -57,13 +57,13 @@
 
-
+
-
+
@@ -93,7 +93,7 @@
 
-
+
diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html
index 37aaaed0..74379ebf 100644
--- a/docs/api/html/settings-ipv4.html
+++ b/docs/api/html/settings-ipv4.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 51. 

+
Table 52. 

 

 
 

encapsulation-limit

 
uint32

 
0
How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1) to ip-tunnel flags.How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add 0x1 (ip6-ign-encap-limit) to ip-tunnel flags.
 

 

 
flags

 
uint32

 
0
Tunnel flags. Currently, the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20). They are valid only for IPv6 tunnels.Tunnel flags. Currently, the following values are supported: 0x1 (ip6-ign-encap-limit), 0x2 (ip6-use-orig-tclass), 0x4 (ip6-use-orig-flowlabel), 0x8 (ip6-mip6-dev), 0x10 (ip6-rcv-dscp-copy), 0x20 (ip6-use-orig-fwmark). They are valid only for IPv6 tunnels.
 

 

 
flow-label
mode

 
uint32

 
0
The tunneling mode. Valid values: NM_IP_TUNNEL_MODE_IPIP (1), NM_IP_TUNNEL_MODE_GRE (2), NM_IP_TUNNEL_MODE_SIT (3), NM_IP_TUNNEL_MODE_ISATAP (4), NM_IP_TUNNEL_MODE_VTI (5), NM_IP_TUNNEL_MODE_IP6IP6 (6), NM_IP_TUNNEL_MODE_IPIP6 (7), NM_IP_TUNNEL_MODE_IP6GRE (8), NM_IP_TUNNEL_MODE_VTI6 (9), NM_IP_TUNNEL_MODE_GRETAP (10) and NM_IP_TUNNEL_MODE_IP6GRETAP (11)The tunneling mode. Valid values: 1 (ipip), 2 (gre), 3 (sit), 4 (isatap), 5 (vti), 6 (ip6ip6), 7 (ipip6), 8 (ip6gre), 9 (vti6), 10 (gretap) and 11 (ip6gretap)
 

 

 
mtu

 
@@ -78,9 +78,9 @@ For other connection types, adding such an automatic route is currently not supp
 
-
+A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.
@@ -96,7 +96,9 @@ The special value "duid" generates a RFC4361-compliant client identifier based o
 
 The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.
 
-If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.
+The special value "none" prevents any client identifier from being sent. Note that this is normally not recommended.
+
+If unset, a globally configured default from NetworkManager.conf is used. If still unset, the default depends on the DHCP plugin. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won't sent any client-id otherwise.
@@ -116,9 +118,9 @@ If unset, a globally configured default is used. If still unset, the default dep
 
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.
@@ -178,15 +180,17 @@ Set to 2147483647 (MAXINT32) for infinity.
-
+When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.
diff --git a/docs/api/html/settings-ipv6.html b/docs/api/html/settings-ipv6.html
index 2e8747cc..70d0f5ed 100644
--- a/docs/api/html/settings-ipv6.html
+++ b/docs/api/html/settings-ipv6.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 52. 

+
Table 53. 

 

 
 

dad-timeout

 
int32

 
-1
Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail.  A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero).  A value greater than zero is a timeout in milliseconds.
+Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
 
-The property is currently implemented only for IPv4.
 

 

 
dhcp-client-id

 

 

 
dhcp-fqdn
0

 Flags for the DHCP hostname and FQDN.
 
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
 
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.
 

 

 
dhcp-iaid

 
dns-options

 
array of string

 
Array of DNS options as described in man 5 resolv.conf.
+Array of DNS options to be added to resolv.conf.
 
 NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
+
+In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
 
 The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
 
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.
 

 

 
dns-priority

 
@@ -59,7 +59,7 @@
 
-
+A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.
@@ -126,9 +126,9 @@ When the property is unset, the global value provided for "ipv6.dhcp-duid" is us
 
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.
@@ -188,15 +188,17 @@ Set to 2147483647 (MAXINT32) for infinity.
-
+When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.
diff --git a/docs/api/html/settings-link.html b/docs/api/html/settings-link.html
index c06d98d7..be92482b 100644
--- a/docs/api/html/settings-link.html
+++ b/docs/api/html/settings-link.html
@@ -6,7 +6,7 @@
 
-
+
@@ -21,7 +21,7 @@
 
-
+

 
 

3

 Configure the method for creating the IPv6 interface identifier of addresses for RFC4862 IPv6 Stateless Address Autoconfiguration and IPv6 Link Local.
 
-The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3).
+The permitted values are: 0 (eui64), 1 (stable-privacy). 2 (default-or-eui64) or 3 (default).
 
 If the property is set to "eui64", the addresses will be generated using the interface token derived from the hardware address. This makes the host part of the address constant, making it possible to track the host's presence when it changes networks. The address changes when the interface hardware is replaced. If a duplicate address is detected, there is no fallback to generate another address. When configured, the "ipv6.token" is used instead of the MAC address to generate addresses for stateless autoconfiguration.
 
@@ -96,9 +96,9 @@ For other connection types, adding such an automatic route is currently not supp
 
dad-timeout

 
int32

 
-1
Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail.  A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero).  A value greater than zero is a timeout in milliseconds.
+Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
 
-The property is currently implemented only for IPv4.
 

 

 
dhcp-duid
0

 Flags for the DHCP hostname and FQDN.
 
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
 
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.
 

 

 
dhcp-iaid

 
dns-options

 
array of string

 
Array of DNS options as described in man 5 resolv.conf.
+Array of DNS options to be added to resolv.conf.
 
 NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
+
+In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
 
 The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
 
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.
 

 

 
dns-priority

 
 
 
 
 
 Home
 UpPrevPrev
 Next
 

 

@@ -34,11 +34,11 @@
 
 

 

-

+

             Properties
         

 

-
Table 86. 

+
Table 88. 

 
diff --git a/docs/api/html/settings-loopback.html b/docs/api/html/settings-loopback.html
index d8073387..5cd6ee73 100644
--- a/docs/api/html/settings-loopback.html
+++ b/docs/api/html/settings-loopback.html
@@ -34,11 +34,11 @@
 

 
 


 

 

-

+

             Properties
         

 

-
Table 87. 

+
Table 89. 

 
diff --git a/docs/api/html/settings-macsec.html b/docs/api/html/settings-macsec.html
index 6659b01f..13977556 100644
--- a/docs/api/html/settings-macsec.html
+++ b/docs/api/html/settings-macsec.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 54. 

+
Table 55. 

 

 
 

 
diff --git a/docs/api/html/settings-macvlan.html b/docs/api/html/settings-macvlan.html
index 54733b85..44b2492f 100644
--- a/docs/api/html/settings-macvlan.html
+++ b/docs/api/html/settings-macvlan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 55. 

+
Table 56. 

 

 
 

 
diff --git a/docs/api/html/settings-match.html b/docs/api/html/settings-match.html
index 828fb6e7..497e4466 100644
--- a/docs/api/html/settings-match.html
+++ b/docs/api/html/settings-match.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 56. 

+
Table 57. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-bridge.html b/docs/api/html/settings-ovs-bridge.html
index bfa44b26..57383e6f 100644
--- a/docs/api/html/settings-ovs-bridge.html
+++ b/docs/api/html/settings-ovs-bridge.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 58. 

+
Table 59. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-dpdk.html b/docs/api/html/settings-ovs-dpdk.html
index 39eed1ef..9a0b4851 100644
--- a/docs/api/html/settings-ovs-dpdk.html
+++ b/docs/api/html/settings-ovs-dpdk.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 59. 

+
Table 60. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-external-ids.html b/docs/api/html/settings-ovs-external-ids.html
index ad8a703b..82082f8d 100644
--- a/docs/api/html/settings-ovs-external-ids.html
+++ b/docs/api/html/settings-ovs-external-ids.html
@@ -34,11 +34,11 @@
 

 
 


 

 

-

+

             Properties
         

 

-
Table 88. 

+
Table 90. 

 
diff --git a/docs/api/html/settings-ovs-interface.html b/docs/api/html/settings-ovs-interface.html
index 0e3b830e..43790176 100644
--- a/docs/api/html/settings-ovs-interface.html
+++ b/docs/api/html/settings-ovs-interface.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 60. 

+
Table 61. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-other-config.html b/docs/api/html/settings-ovs-other-config.html
index bd188e63..c7d3322b 100644
--- a/docs/api/html/settings-ovs-other-config.html
+++ b/docs/api/html/settings-ovs-other-config.html
@@ -34,11 +34,11 @@
 

 
 


 

 

-

+

             Properties
         

 

-
Table 89. 

+
Table 91. 

 
diff --git a/docs/api/html/settings-ovs-patch.html b/docs/api/html/settings-ovs-patch.html
index e97d2974..0e6d7603 100644
--- a/docs/api/html/settings-ovs-patch.html
+++ b/docs/api/html/settings-ovs-patch.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 61. 

+
Table 62. 

 

 
 

 
diff --git a/docs/api/html/settings-ovs-port.html b/docs/api/html/settings-ovs-port.html
index e53d3aba..00946903 100644
--- a/docs/api/html/settings-ovs-port.html
+++ b/docs/api/html/settings-ovs-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 62. 

+
Table 63. 

 

 
 

 
diff --git a/docs/api/html/settings-ppp.html b/docs/api/html/settings-ppp.html
index a8d08545..339ff0e2 100644
--- a/docs/api/html/settings-ppp.html
+++ b/docs/api/html/settings-ppp.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 63. 

+
Table 64. 

 

 
 

 
diff --git a/docs/api/html/settings-pppoe.html b/docs/api/html/settings-pppoe.html
index 7dee82f6..a16d8144 100644
--- a/docs/api/html/settings-pppoe.html
+++ b/docs/api/html/settings-pppoe.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 64. 

+
Table 65. 

 

 
 

 
diff --git a/docs/api/html/settings-proxy.html b/docs/api/html/settings-proxy.html
index 15deb102..443f0918 100644
--- a/docs/api/html/settings-proxy.html
+++ b/docs/api/html/settings-proxy.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 65. 

+
Table 66. 

 

 
 

 
@@ -63,7 +63,7 @@
 
-
+
diff --git a/docs/api/html/settings-serial.html b/docs/api/html/settings-serial.html
index e8397851..54a5051e 100644
--- a/docs/api/html/settings-serial.html
+++ b/docs/api/html/settings-serial.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 66. 

+
Table 67. 

 

 
 

method

 
int32

 
0
Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)Method for proxy configuration, Default is 0 (none)
 

 

 
pac-script

 
diff --git a/docs/api/html/settings-sriov.html b/docs/api/html/settings-sriov.html
index 7610c14b..3d3b9aa5 100644
--- a/docs/api/html/settings-sriov.html
+++ b/docs/api/html/settings-sriov.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 67. 

+
Table 68. 

 

 
 

 
@@ -59,11 +59,11 @@
 
+When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 1 (true).
diff --git a/docs/api/html/settings-tc.html b/docs/api/html/settings-tc.html
index abc54523..2fcefc9a 100644
--- a/docs/api/html/settings-tc.html
+++ b/docs/api/html/settings-tc.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 68. 

+
Table 69. 

 

 
 


 Whether to autoprobe virtual functions by a compatible driver.
 
-If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.
+If set to 1 (true), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.
 
-If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them.
+If set to 0 (false), VFs will not be claimed and no network interfaces will be created for them.
 
-When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1).
 

 

 
total-vfs

 
diff --git a/docs/api/html/settings-team-port.html b/docs/api/html/settings-team-port.html
index 73db2e13..04aaab22 100644
--- a/docs/api/html/settings-team-port.html
+++ b/docs/api/html/settings-team-port.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 70. 

+
Table 71. 

 

 
 

 
diff --git a/docs/api/html/settings-team.html b/docs/api/html/settings-team.html
index c6adf30a..17dbd11d 100644
--- a/docs/api/html/settings-team.html
+++ b/docs/api/html/settings-team.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 69. 

+
Table 70. 

 

 
 

 
diff --git a/docs/api/html/settings-tun.html b/docs/api/html/settings-tun.html
index a5b5a994..15306dee 100644
--- a/docs/api/html/settings-tun.html
+++ b/docs/api/html/settings-tun.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 71. 

+
Table 72. 

 

 
 

 
@@ -63,7 +63,7 @@
 
-
+
diff --git a/docs/api/html/settings-user.html b/docs/api/html/settings-user.html
index 704c4580..6a2340c3 100644
--- a/docs/api/html/settings-user.html
+++ b/docs/api/html/settings-user.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 72. 

+
Table 73. 

 

 
 

mode

 
uint32

 
1
The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one.The operating mode of the virtual device. Allowed values are 1 (tun) to create a layer 3 device and 2 (tap) to create an Ethernet-like layer 2 one.
 

 

 
multi-queue

 
diff --git a/docs/api/html/settings-veth.html b/docs/api/html/settings-veth.html
index 586a57bd..98e577fa 100644
--- a/docs/api/html/settings-veth.html
+++ b/docs/api/html/settings-veth.html
@@ -34,11 +34,11 @@
 

 
 


 

 

-

+

             Properties
         

 

-
Table 90. 

+
Table 92. 

 
diff --git a/docs/api/html/settings-vlan.html b/docs/api/html/settings-vlan.html
index f6d6f1aa..0ae6d9e6 100644
--- a/docs/api/html/settings-vlan.html
+++ b/docs/api/html/settings-vlan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 73. 

+
Table 74. 

 

 
 

 
@@ -63,7 +63,7 @@
 
-
diff --git a/docs/api/html/settings-vpn.html b/docs/api/html/settings-vpn.html
index 612a69dd..783d33e1 100644
--- a/docs/api/html/settings-vpn.html
+++ b/docs/api/html/settings-vpn.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 74. 

+
Table 75. 

 

 
 

flags

 
NMVlanFlags (uint32)

 
One or more flags which control the behavior and features of the VLAN interface.  Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol).
+One or more flags which control the behavior and features of the VLAN interface.  Flags include 0x1 (reorder-headers) (reordering of output packet headers), 0x2 (gvrp) (use of the GVRP protocol), and 0x4 (loose-binding) (loose binding of the interface to its master device's operating state). 0x8 (mvrp) (use of the MVRP protocol).
 
 The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.
 

 
diff --git a/docs/api/html/settings-vrf.html b/docs/api/html/settings-vrf.html
index d9f90e04..87012fcb 100644
--- a/docs/api/html/settings-vrf.html
+++ b/docs/api/html/settings-vrf.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 75. 

+
Table 76. 

 

 
 

 
diff --git a/docs/api/html/settings-vxlan.html b/docs/api/html/settings-vxlan.html
index be0edb5a..4c0df3f2 100644
--- a/docs/api/html/settings-vxlan.html
+++ b/docs/api/html/settings-vxlan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 76. 

+
Table 77. 

 

 
 

 
diff --git a/docs/api/html/settings-wifi-p2p.html b/docs/api/html/settings-wifi-p2p.html
index ac0865b7..64ce4ada 100644
--- a/docs/api/html/settings-wifi-p2p.html
+++ b/docs/api/html/settings-wifi-p2p.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 77. 

+
Table 78. 

 

 
 

 
diff --git a/docs/api/html/settings-wimax.html b/docs/api/html/settings-wimax.html
index 56bf88d7..5c05752b 100644
--- a/docs/api/html/settings-wimax.html
+++ b/docs/api/html/settings-wimax.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 78. 

+
Table 79. 

 

 
 

 
diff --git a/docs/api/html/settings-wireguard.html b/docs/api/html/settings-wireguard.html
index 685061fb..9e1859ba 100644
--- a/docs/api/html/settings-wireguard.html
+++ b/docs/api/html/settings-wireguard.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 80. 

+
Table 81. 

 

 
 

 
diff --git a/docs/api/html/settings-wpan.html b/docs/api/html/settings-wpan.html
index 4fddfd2a..a5986d80 100644
--- a/docs/api/html/settings-wpan.html
+++ b/docs/api/html/settings-wpan.html
@@ -38,7 +38,7 @@
             Properties
         

-
Table 83. 

+
Table 84. 

 

 
 

 
diff --git a/docs/api/html/spec.html b/docs/api/html/spec.html
index a4ec537b..b41e5ef1 100644
--- a/docs/api/html/spec.html
+++ b/docs/api/html/spec.html
@@ -72,6 +72,9 @@
 org.freedesktop.NetworkManager.Device.Generic — Unrecognized Device.

+org.freedesktop.NetworkManager.Device.Hsr — HSR Device.
+

+

 org.freedesktop.NetworkManager.Device.IPTunnel — IP Tunneling Device.
 

diff --git a/docs/api/network-manager-docs.xml b/docs/api/network-manager-docs.xml
index d8f4725c..faee8799 100644
--- a/docs/api/network-manager-docs.xml
+++ b/docs/api/network-manager-docs.xml
@@ -33,15 +33,7 @@
 	Texts. You may obtain a copy of the GNU Free
 	Documentation License from the Free Software
 	Foundation by visiting their Web site or by writing
-	to:
-
-	

-	  The Free Software Foundation, Inc.,
-	  51 Franklin Street - Fifth Floor,
-	  Boston, MA 02110-1301,
-	  USA
-	

+	url="http://www.fsf.org">their Web site.
       
     
 
@@ -191,6 +183,7 @@
       
       
       
+      
       
       
       
@@ -322,14 +315,7 @@
 
     
       You should have received a copy of the GNU
-      General Public License along with this program;
-      if not, write to the
-      

-        Free Software Foundation, Inc.,
-        51 Franklin Street - Fifth Floor,
-        Boston, MA 02110-1301,
-        USA
-      

+      General Public License along with this program.
     
 
     
diff --git a/docs/api/settings-spec.xml b/docs/api/settings-spec.xml
index 2618265f..111f90ae 100644
--- a/docs/api/settings-spec.xml
+++ b/docs/api/settings-spec.xml
@@ -12,7 +12,7 @@ Note that autoconnect is not implemented for VPN profiles. See "secondaries" as
 
 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-priorityautoconnect-priorityint320The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.autoconnect-retriesautoconnect-retriesint32-1The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.autoconnect-slavesautoconnect-slavesNMSettingConnectionAutoconnectSlaves (int32)Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.dns-over-tlsdns-over-tlsint32-1Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.
+Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.autoconnect-priorityautoconnect-priorityint320The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.autoconnect-retriesautoconnect-retriesint32-1The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.autoconnect-slavesautoconnect-slavesNMSettingConnectionAutoconnectSlaves (int32)Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.controllercontrollerstringInterface name of the controller device or UUID of the controller connection.dns-over-tlsdns-over-tlsint32-1Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.
 
 The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting.
 
@@ -24,7 +24,9 @@ For connection types where interface names cannot easily be made persistent (e.g
 
 The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").
 
-This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.mastermasterstringInterface name of the master device or UUID of the master connection.mdnsmdnsint32-1Whether mDNS is enabled for the connection.
+This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.mastermasterstringInterface name of the master device or UUID of the master connection.
+
+Deprecated 1.46. Use "controller" instead, this is just an alias.mdnsmdnsint32-1Whether mDNS is enabled for the connection.
 
 The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").
 
@@ -52,13 +54,15 @@ The special value "none" is allowed to indicate that no MUD URL is used.
 
 If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".multi-connectmulti-connectint320Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.permissionspermissionsarray of stringAn array of strings defining what access a given user has to this connection.  If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list.  When this is not empty, the connection can be active only when one of the specified users is logged into an active session.  Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah".
 
-At this time only the "user" [type] is allowed.  Any other values are ignored and reserved for future use.  [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use.  All of [type], [id], and [reserved] must be valid UTF-8.read-onlyread-onlybooleanFALSEThis property is deprecated and has no meaning.secondariessecondariesarray of stringList of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.slave-typeslave-typestringSetting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.stable-idstable-idstringThis represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.
+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.port-typeport-typestringSetting name of the device type of this port's controller connection (eg, "bond"), or NULL if this connection is not a port.read-onlyread-onlybooleanFALSEThis property is deprecated and has no meaning.secondariessecondariesarray of stringList of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.slave-typeslave-typestringSetting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.
+
+Deprecated 1.46. Use "port-type" instead, this is just an alias.stable-idstable-idstringThis represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.
 
 The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used to derive the DHCP client identifier with ipv4.dhcp-client-id=stable, the DHCPv6 DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid] and the DHCP IAID with ipv4.iaid=stable and ipv6.iaid=stable.
 
 Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.
 
-The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$".  For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
+The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-SSID, per-boot, or every time.  The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. "${NETWORK_SSID}" uses the SSID for Wi-Fi networks and falls back to "${CONNECTION}" on other networks. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$".  For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
 
 If the value is unset, a global connection default is consulted. If the value is still unset, the default is "default${CONNECTION}" go generate an ID unique per connection profile.timestamptimestampuint640The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.
 
@@ -130,9 +134,9 @@ where $vid is either a single id between 1 and 4094 or a range, represented as a
             Properties
         

 
 

 
 
 
Key NameValue TypeDefault ValueValue Descriptionmtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.numbernumberstringThe number to dial to establish the connection to the CDMA-based mobile broadband network, if any.  If not specified, the default number (#777) is used when required.passwordpasswordstringThe password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.usernameusernamestringThe username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.
dcbData Center Bridging Settings
             Properties
-        Key NameValue TypeDefault ValueValue Descriptionapp-fcoe-flagsapp-fcoe-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-fcoe-modeapp-fcoe-modestringThe FCoE controller mode; either "fabric" or "vn2vn".
+        
Key NameValue TypeDefault ValueValue Descriptionapp-fcoe-flagsapp-fcoe-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).app-fcoe-modeapp-fcoe-modestringThe FCoE controller mode; either "fabric" or "vn2vn".
 
-Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".app-fcoe-priorityapp-fcoe-priorityint32-1The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.app-fip-flagsapp-fip-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-fip-priorityapp-fip-priorityint32-1The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.app-iscsi-flagsapp-iscsi-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-iscsi-priorityapp-iscsi-priorityint32-1The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.priority-bandwidthpriority-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use.  The sum of all percentages for priorities which belong to the same group must total 100 percents.priority-flow-controlpriority-flow-controlarray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.priority-flow-control-flagspriority-flow-control-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).priority-group-bandwidthpriority-group-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group.  Allowed values are 0 - 100, and the sum of all values must total 100 percents.priority-group-flagspriority-group-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).priority-group-idpriority-group-idarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID.  Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.priority-strict-bandwidthpriority-strict-bandwidtharray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.priority-traffic-classpriority-traffic-classarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.
dummyDummy Link Settings
+Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".</entry></row><row><entry><screen>app-fcoe-priority<indexterm zone="settings-dcb"><primary sortas="app-fcoe-priority">app-fcoe-priority</primary></indexterm></screen></entry><entry><screen>int32</screen></entry><entry><screen>-1</screen></entry><entry>The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the 0x1 (enable) flag.</entry></row><row><entry><screen>app-fip-flags<indexterm zone="settings-dcb"><primary sortas="app-fip-flags">app-fip-flags</primary></indexterm></screen></entry><entry><screen>NMSettingDcbFlags (uint32)</screen></entry><entry><screen/></entry><entry>Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).</entry></row><row><entry><screen>app-fip-priority<indexterm zone="settings-dcb"><primary sortas="app-fip-priority">app-fip-priority</primary></indexterm></screen></entry><entry><screen>int32</screen></entry><entry><screen>-1</screen></entry><entry>The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the 0x1 (enable) flag.</entry></row><row><entry><screen>app-iscsi-flags<indexterm zone="settings-dcb"><primary sortas="app-iscsi-flags">app-iscsi-flags</primary></indexterm></screen></entry><entry><screen>NMSettingDcbFlags (uint32)</screen></entry><entry><screen/></entry><entry>Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).</entry></row><row><entry><screen>app-iscsi-priority<indexterm zone="settings-dcb"><primary sortas="app-iscsi-priority">app-iscsi-priority</primary></indexterm></screen></entry><entry><screen>int32</screen></entry><entry><screen>-1</screen></entry><entry>The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the 0x1 (enable) flag.</entry></row><row><entry><screen>priority-bandwidth<indexterm zone="settings-dcb"><primary sortas="priority-bandwidth">priority-bandwidth</primary></indexterm></screen></entry><entry><screen>array of uint32</screen></entry><entry><screen/></entry><entry>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.</entry></row><row><entry><screen>priority-flow-control<indexterm zone="settings-dcb"><primary sortas="priority-flow-control">priority-flow-control</primary></indexterm></screen></entry><entry><screen>array of uint32</screen></entry><entry><screen/></entry><entry>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.</entry></row><row><entry><screen>priority-flow-control-flags<indexterm zone="settings-dcb"><primary sortas="priority-flow-control-flags">priority-flow-control-flags</primary></indexterm></screen></entry><entry><screen>NMSettingDcbFlags (uint32)</screen></entry><entry><screen/></entry><entry>Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).</entry></row><row><entry><screen>priority-group-bandwidth<indexterm zone="settings-dcb"><primary sortas="priority-group-bandwidth">priority-group-bandwidth</primary></indexterm></screen></entry><entry><screen>array of uint32</screen></entry><entry><screen/></entry><entry>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.</entry></row><row><entry><screen>priority-group-flags<indexterm zone="settings-dcb"><primary sortas="priority-group-flags">priority-group-flags</primary></indexterm></screen></entry><entry><screen>NMSettingDcbFlags (uint32)</screen></entry><entry><screen/></entry><entry>Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).</entry></row><row><entry><screen>priority-group-id<indexterm zone="settings-dcb"><primary sortas="priority-group-id">priority-group-id</primary></indexterm></screen></entry><entry><screen>array of uint32</screen></entry><entry><screen/></entry><entry>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.</entry></row><row><entry><screen>priority-strict-bandwidth<indexterm zone="settings-dcb"><primary sortas="priority-strict-bandwidth">priority-strict-bandwidth</primary></indexterm></screen></entry><entry><screen>array of uint32</screen></entry><entry><screen/></entry><entry>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.</entry></row><row><entry><screen>priority-traffic-class<indexterm zone="settings-dcb"><primary sortas="priority-traffic-class">priority-traffic-class</primary></indexterm></screen></entry><entry><screen>array of uint32</screen></entry><entry><screen/></entry><entry>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.</entry></row></tbody></tgroup></table></para></refsect1></refentry><refentry id="settings-dummy"><refnamediv><refname>dummy</refname><refpurpose>Dummy Link Settings</refpurpose></refnamediv><refsect1 role="properties"><title id="settings-dummy.properties">
             Properties
         Key NameValue TypeDefault ValueValue Description
ethtoolEthtool Ethernet Settings
             Properties
@@ -140,7 +144,9 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject
             Properties
         Key NameValue TypeDefault ValueValue Description
gsmGSM-based Mobile Broadband Settings
             Properties
-        Key NameValue TypeDefault ValueValue DescriptionapnapnstringThe 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-configauto-configbooleanFALSEWhen 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-iddevice-idstringThe 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-onlyhome-onlybooleanFALSEWhen TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.initial-eps-bearer-apninitial-eps-bearer-apnstringFor LTE modems, this sets the APN for the initial EPS bearer that is set up when attaching to the network.  Setting this parameter implies initial-eps-bearer-configure to be TRUE.initial-eps-bearer-configureinitial-eps-bearer-configurebooleanFALSEFor LTE modems, this setting determines whether the initial EPS bearer shall be configured when bringing up the connection.  It is inferred TRUE if initial-eps-bearer-apn is set.mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.network-idnetwork-idstringThe 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.numbernumberstringLegacy setting that used to help establishing PPP data sessions for GSM-based modems.passwordpasswordstringThe password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.pinpinstringIf 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-flagspin-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "pin" property.sim-idsim-idstringThe 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-idsim-operator-idstringA 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.usernameusernamestringThe username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.
infinibandInfiniband Settings
+        Key NameValue TypeDefault ValueValue DescriptionapnapnstringThe GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network.  The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.
+
+If the APN is unset (the default) then it may be detected based on "auto-config" setting. The property can be explicitly set to the empty string to prevent that and use no APN.auto-configauto-configbooleanFALSEWhen 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-iddevice-idstringThe 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-onlyhome-onlybooleanFALSEWhen TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.initial-eps-bearer-apninitial-eps-bearer-apnstringFor LTE modems, this sets the APN for the initial EPS bearer that is set up when attaching to the network.  Setting this parameter implies initial-eps-bearer-configure to be TRUE.initial-eps-bearer-configureinitial-eps-bearer-configurebooleanFALSEFor LTE modems, this setting determines whether the initial EPS bearer shall be configured when bringing up the connection.  It is inferred TRUE if initial-eps-bearer-apn is set.mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.network-idnetwork-idstringThe 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.numbernumberstringLegacy setting that used to help establishing PPP data sessions for GSM-based modems.passwordpasswordstringThe password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.pinpinstringIf 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-flagspin-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "pin" property.sim-idsim-idstringThe 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-idsim-operator-idstringA 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.usernameusernamestringThe username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.
infinibandInfiniband Settings
             Properties
         Key NameValue TypeDefault ValueValue Descriptionmac-addressmac-addressbyte arrayIf 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).mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.p-keyp-keyint32-1The 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 0x8000 is set if it is a "full membership" p-key. The values 0 and 0x8000 are not allowed.
 
@@ -151,9 +157,9 @@ Note that kernel will internally always set the full membership bit, although th
         
Key NameValue TypeDefault ValueValue Descriptionaddress-dataaddress-dataarray of vardictArray of IPv4 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.addressesaddressesarray of array of uint32Deprecated 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-gwauto-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-timeoutdad-timeoutint32-1Timeout 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.
+For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.dad-timeoutdad-timeoutint32-1Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
 
-The property is currently implemented only for IPv4.dhcp-client-iddhcp-client-idstringA 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 zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.dhcp-client-iddhcp-client-idstringA 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.
 
@@ -163,11 +169,13 @@ The special value "duid" generates a RFC4361-compliant client identifier based o
 
 The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.
 
-If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.dhcp-fqdndhcp-fqdnstringIf 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-hostnamedhcp-hostnamestringIf 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-flagsdhcp-hostname-flagsuint320Flags for the DHCP hostname and FQDN.
+The special value "none" prevents any client identifier from being sent. Note that this is normally not recommended.
+
+If unset, a globally configured default from NetworkManager.conf is used. If still unset, the default depends on the DHCP plugin. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won't sent any client-id otherwise.dhcp-fqdndhcp-fqdnstringIf 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-hostnamedhcp-hostnamestringIf 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-flagsdhcp-hostname-flagsuint320Flags for the DHCP hostname and FQDN.
 
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
 
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.dhcp-iaiddhcp-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.dhcp-iaiddhcp-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".
 
 For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.
 
@@ -179,15 +187,17 @@ For DHCPv4, each element must be an IPv4 address, optionally followed by a slash
 
 This property is currently not implemented for DHCPv6.dhcp-send-hostnamedhcp-send-hostnamebooleanTRUEIf 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-timeoutdhcp-timeoutint320A 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-identifierdhcp-vendor-class-identifierstringThe 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.dnsdnsarray of uint32Array of IP addresses of DNS servers (as network-byte-order integers)dns-datadns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsdns-optionsarray of stringArray of DNS options as described in man 5 resolv.conf.
+Set to 2147483647 (MAXINT32) for infinity.dhcp-vendor-class-identifierdhcp-vendor-class-identifierstringThe 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.dnsdnsarray of uint32Array of IP addresses of DNS servers (as network-byte-order integers)dns-datadns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsdns-optionsarray of stringArray of DNS options to be added to resolv.conf.
 
 NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
+
+In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
 
 The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
 
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.dns-prioritydns-priorityint320DNS servers priority.
+When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.dns-prioritydns-priorityint320DNS servers priority.
 
 The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
 
@@ -236,7 +246,7 @@ Array of IPv4 route structures.  Each IPv4 route structure is composed of 4 32-b
             Properties
         
Key NameValue TypeDefault ValueValue Descriptionaddr-gen-modeaddr-gen-modeint323Configure the method for creating the IPv6 interface identifier of addresses for RFC4862 IPv6 Stateless Address Autoconfiguration and IPv6 Link Local.
 
-The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3).
+The permitted values are: 0 (eui64), 1 (stable-privacy). 2 (default-or-eui64) or 3 (default).
 
 If the property is set to "eui64", the addresses will be generated using the interface token derived from the hardware address. This makes the host part of the address constant, making it possible to track the host's presence when it changes networks. The address changes when the interface hardware is replaced. If a duplicate address is detected, there is no fallback to generate another address. When configured, the "ipv6.token" is used instead of the MAC address to generate addresses for stateless autoconfiguration.
 
@@ -249,9 +259,9 @@ For libnm, the property defaults to "default" since 1.40.  Previously it used to
 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.address-dataaddress-dataarray of vardictArray of IPv6 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.addressesaddressesarray 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.auto-route-ext-gwauto-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-timeoutdad-timeoutint32-1Timeout 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.
+For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.dad-timeoutdad-timeoutint32-1Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
 
-The property is currently implemented only for IPv4.dhcp-duiddhcp-duidstringA 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 zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.dhcp-duiddhcp-duidstringA 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.
 
@@ -261,9 +271,9 @@ The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a D
 
 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-hostnamedhcp-hostnamestringIf 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-flagsdhcp-hostname-flagsuint320Flags for the DHCP hostname and FQDN.
 
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
 
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.dhcp-iaiddhcp-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.dhcp-iaiddhcp-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".
 
 For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.
 
@@ -275,15 +285,17 @@ For DHCPv4, each element must be an IPv4 address, optionally followed by a slash
 
 This property is currently not implemented for DHCPv6.dhcp-send-hostnamedhcp-send-hostnamebooleanTRUEIf 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-timeoutdhcp-timeoutint320A 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.dnsdnsarray of byte arrayArray of IP addresses of DNS servers (in network byte order)dns-datadns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsdns-optionsarray of stringArray of DNS options as described in man 5 resolv.conf.
+Set to 2147483647 (MAXINT32) for infinity.dnsdnsarray of byte arrayArray of IP addresses of DNS servers (in network byte order)dns-datadns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsdns-optionsarray of stringArray of DNS options to be added to resolv.conf.
 
 NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
+
+In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
 
 The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
 
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.dns-prioritydns-priorityint320DNS servers priority.
+When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.dns-prioritydns-priorityint320DNS servers priority.
 
 The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
 
@@ -338,7 +350,7 @@ Array of IPv6 route structures.  Each IPv6 route structure is composed of an IPv
 
 When set, the token is used as IPv6 interface identifier instead of the hardware address. This only applies to addresses from stateless autoconfiguration, not to IPv6 link local addresses.
ip-tunnelIP Tunneling Settings
             Properties
-        Key NameValue TypeDefault ValueValue Descriptionencapsulation-limitencapsulation-limituint320How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1) to ip-tunnel flags.flagsflagsuint320Tunnel 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-labelflow-labeluint320The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.fwmarkfwmarkuint320The fwmark value to assign to tunnel packets. This property can be set to a non zero value only on VTI and VTI6 tunnels.input-keyinput-keystringThe key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.locallocalstringThe local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.modemodeuint320The tunneling mode. Valid values: NM_IP_TUNNEL_MODE_IPIP (1), NM_IP_TUNNEL_MODE_GRE (2), NM_IP_TUNNEL_MODE_SIT (3), NM_IP_TUNNEL_MODE_ISATAP (4), NM_IP_TUNNEL_MODE_VTI (5), NM_IP_TUNNEL_MODE_IP6IP6 (6), NM_IP_TUNNEL_MODE_IPIP6 (7), NM_IP_TUNNEL_MODE_IP6GRE (8), NM_IP_TUNNEL_MODE_VTI6 (9), NM_IP_TUNNEL_MODE_GRETAP (10) and NM_IP_TUNNEL_MODE_IP6GRETAP (11)mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.output-keyoutput-keystringThe key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.parentparentstringIf 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-discoverypath-mtu-discoverybooleanTRUEWhether to enable Path MTU Discovery on this tunnel.remoteremotestringThe remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.tostosuint320The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.ttlttluint320The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.
macsecMACSec Settings
+        Key NameValue TypeDefault ValueValue Descriptionencapsulation-limitencapsulation-limituint320How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add 0x1 (ip6-ign-encap-limit) to ip-tunnel flags.flagsflagsuint320Tunnel flags. Currently, the following values are supported: 0x1 (ip6-ign-encap-limit), 0x2 (ip6-use-orig-tclass), 0x4 (ip6-use-orig-flowlabel), 0x8 (ip6-mip6-dev), 0x10 (ip6-rcv-dscp-copy), 0x20 (ip6-use-orig-fwmark). They are valid only for IPv6 tunnels.flow-labelflow-labeluint320The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.fwmarkfwmarkuint320The fwmark value to assign to tunnel packets. This property can be set to a non zero value only on VTI and VTI6 tunnels.input-keyinput-keystringThe key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.locallocalstringThe local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.modemodeuint320The tunneling mode. Valid values: 1 (ipip), 2 (gre), 3 (sit), 4 (isatap), 5 (vti), 6 (ip6ip6), 7 (ipip6), 8 (ip6gre), 9 (vti6), 10 (gretap) and 11 (ip6gretap)mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.output-keyoutput-keystringThe key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.parentparentstringIf 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-discoverypath-mtu-discoverybooleanTRUEWhether to enable Path MTU Discovery on this tunnel.remoteremotestringThe remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.tostosuint320The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.ttlttluint320The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.
macsecMACSec Settings
             Properties
         Key NameValue TypeDefault ValueValue DescriptionencryptencryptbooleanTRUEWhether the transmitted traffic must be encrypted.mka-cakmka-cakstringThe pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.mka-cak-flagsmka-cak-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "mka-cak" property.mka-cknmka-cknstringThe 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.modemodeint320Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.parentparentstringIf 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.portportint321The port component of the SCI (Secure Channel Identifier), between 1 and 65534.send-scisend-scibooleanTRUESpecifies whether the SCI (Secure Channel Identifier) is included in every packet.validationvalidationint322Specifies the validation mode for incoming frames.
macvlanMAC VLAN Settings
             Properties
@@ -380,17 +392,17 @@ The property is valid only for ports with mode "trunk", "native-tagged", or "nat
             Properties
         Key NameValue TypeDefault ValueValue DescriptionparentparentstringIf 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.passwordpasswordstringPassword used to authenticate with the PPPoE service.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.serviceservicestringIf 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.usernameusernamestringUsername used to authenticate with the PPPoE service.
proxyWWW Proxy Settings
             Properties
-        Key NameValue TypeDefault ValueValue Descriptionbrowser-onlybrowser-onlybooleanFALSEWhether the proxy configuration is for browser only.methodmethodint320Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)pac-scriptpac-scriptstringPAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.pac-urlpac-urlstringPAC URL for obtaining PAC file.
serialSerial Link Settings
+        Key NameValue TypeDefault ValueValue Descriptionbrowser-onlybrowser-onlybooleanFALSEWhether the proxy configuration is for browser only.methodmethodint320Method for proxy configuration, Default is 0 (none)pac-scriptpac-scriptstringPAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.pac-urlpac-urlstringPAC URL for obtaining PAC file.
serialSerial Link Settings
             Properties
         Key NameValue TypeDefault ValueValue Descriptionbaudbauduint3257600Speed 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.bitsbitsuint328Byte-width of the serial communication. The 8 in "8n1" for example.parityparitybyteThe connection parity: 69 (ASCII 'E') for even parity, 111 (ASCII 'o') for odd, 110 (ASCII 'n') for none.send-delaysend-delayuint640Time to delay between each byte sent to the modem, in microseconds.stopbitsstopbitsuint321Number of stop bits for communication on the serial port.  Either 1 or 2. The 1 in "8n1" for example.
sriovSR-IOV settings
             Properties
         Key NameValue TypeDefault ValueValue Descriptionautoprobe-driversautoprobe-driversNMTernary (int32)Whether to autoprobe virtual functions by a compatible driver.
 
-If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.
+If set to 1 (true), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.
 
-If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them.
+If set to 0 (false), VFs will not be claimed and no network interfaces will be created for them.
 
-When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1).total-vfstotal-vfsuint320The total number of virtual functions to create.
+When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 1 (true).total-vfstotal-vfsuint320The 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.vfsvfsarray of vardictArray of virtual function descriptors.
 
@@ -426,11 +438,11 @@ If the "tc" setting is not present, NetworkManager doesn't touch the filters pre
             Properties
         
Key NameValue TypeDefault ValueValue DescriptionconfigconfigstringThe 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-keylacp-keyint32-1Corresponds to the teamd ports.PORTIFNAME.lacp_key.lacp-priolacp-prioint32-1Corresponds to the teamd ports.PORTIFNAME.lacp_prio.link-watcherslink-watchersarray of vardictLink 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.prioprioint320Corresponds to the teamd ports.PORTIFNAME.prio.queue-idqueue-idint32-1Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.stickystickybooleanFALSECorresponds to the teamd ports.PORTIFNAME.sticky.
tunTunnel Settings
             Properties
-        Key NameValue TypeDefault ValueValue DescriptiongroupgroupstringThe group ID which will own the device. If set to NULL everyone will be able to use the device.modemodeuint321The 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-queuemulti-queuebooleanFALSEIf 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.ownerownerstringThe user ID which will own the device. If set to NULL everyone will be able to use the device.pipibooleanFALSEIf TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.vnet-hdrvnet-hdrbooleanFALSEIf TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.
userGeneral User Profile Settings
+        Key NameValue TypeDefault ValueValue DescriptiongroupgroupstringThe group ID which will own the device. If set to NULL everyone will be able to use the device.modemodeuint321The operating mode of the virtual device. Allowed values are 1 (tun) to create a layer 3 device and 2 (tap) to create an Ethernet-like layer 2 one.multi-queuemulti-queuebooleanFALSEIf 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.ownerownerstringThe user ID which will own the device. If set to NULL everyone will be able to use the device.pipibooleanFALSEIf TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.vnet-hdrvnet-hdrbooleanFALSEIf TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.
userGeneral User Profile Settings
             Properties
         Key NameValue TypeDefault ValueValue Descriptiondatadatadict 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.
vlanVLAN Settings
             Properties
-        Key NameValue TypeDefault ValueValue Descriptionegress-priority-mapegress-priority-maparray of stringFor 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".flagsflagsNMVlanFlags (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).
+        
Key NameValue TypeDefault ValueValue Descriptionegress-priority-mapegress-priority-maparray of stringFor 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".flagsflagsNMVlanFlags (uint32)One or more flags which control the behavior and features of the VLAN interface.  Flags include 0x1 (reorder-headers) (reordering of output packet headers), 0x2 (gvrp) (use of the GVRP protocol), and 0x4 (loose-binding) (loose binding of the interface to its master device's operating state). 0x8 (mvrp) (use of the MVRP protocol).
 
 The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.ididuint320The 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-mapingress-priority-maparray of stringFor 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".interface-nameinterface-namestringDeprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the vlan's interface name.parentparentstringIf 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.protocolprotocolstringSpecifies the VLAN protocol to use for encapsulation.
 
@@ -460,7 +472,7 @@ If the value contains one additional MAC address after the mask, this address is
 
 If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.mac-addressmac-addressbyte arrayIf specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).mac-address-blacklistmac-address-blacklistarray of stringIf specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.portportstringSpecific port type to use if the device supports multiple attachment methods.  One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.s390-nettypes390-nettypestrings390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.s390-optionss390-optionsdict of string to string{}Dictionary of key/value pairs of s390-specific device options.  Both keys and values must be strings.  Allowed keys include "portno", "layer2", "portname", "protocol", among others.  Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).
 
-Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.s390-subchannelss390-subchannelsarray of stringIdentifies specific subchannels that this network device uses for communication with z/VM or s390 host.  Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels.  The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.speedspeeduint320When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.wake-on-lanwake-on-lanuint321The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).wake-on-lan-passwordwake-on-lan-passwordstringIf specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address.  If NULL, no password will be required.
wireguardWireGuard Settings
+Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.</entry></row><row><entry><screen>s390-subchannels<indexterm zone="settings-802-3-ethernet"><primary sortas="s390-subchannels">s390-subchannels</primary></indexterm></screen></entry><entry><screen>array of string</screen></entry><entry><screen/></entry><entry>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.</entry></row><row><entry><screen>speed<indexterm zone="settings-802-3-ethernet"><primary sortas="speed">speed</primary></indexterm></screen></entry><entry><screen>uint32</screen></entry><entry><screen>0</screen></entry><entry>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.</entry></row><row><entry><screen>wake-on-lan<indexterm zone="settings-802-3-ethernet"><primary sortas="wake-on-lan">wake-on-lan</primary></indexterm></screen></entry><entry><screen>uint32</screen></entry><entry><screen>1</screen></entry><entry>The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of 0x2 (phy), 0x4 (unicast), 0x8 (multicast), 0x10 (broadcast), 0x20 (arp), 0x40 (magic) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).</entry></row><row><entry><screen>wake-on-lan-password<indexterm zone="settings-802-3-ethernet"><primary sortas="wake-on-lan-password">wake-on-lan-password</primary></indexterm></screen></entry><entry><screen>string</screen></entry><entry><screen/></entry><entry>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.</entry></row></tbody></tgroup></table></para></refsect1></refentry><refentry id="settings-wireguard"><refnamediv><refname>wireguard</refname><refpurpose>WireGuard Settings</refpurpose></refnamediv><refsect1 role="properties"><title id="settings-wireguard.properties">
             Properties
         Key NameValue TypeDefault ValueValue Descriptionfwmarkfwmarkuint320The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise, it is a 32-bit fwmark for outgoing packets.
 
@@ -474,13 +486,13 @@ If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, thi
 
 Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.peerspeersarray of 'a{sv}'Array of dictionaries for the WireGuard peers.private-keyprivate-keystringThe 256 bit private-key in base64 encoding.private-key-flagsprivate-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "private-key" property.
802-11-wirelessWi-Fi Settings
             Properties
-        Key NameValue TypeDefault ValueValue Descriptionap-isolationap-isolationNMTernary (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.
+        
Key NameValue TypeDefault ValueValue Descriptionap-isolationap-isolationNMTernary (int32)Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from -1 (default) only when the interface is configured in AP mode.
 
-If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.
+If set to 1 (true), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.
 
-If set to NM_TERNARY_FALSE (0), devices can talk to each other.
+If set to 0 (false), devices can talk to each other.
 
-When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).assigned-mac-addressassigned-mac-addressstringThe new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".bandbandstring802.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.bssidbssidbyte arrayIf 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.
+When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 0 (false).assigned-mac-addressassigned-mac-addressstringThe new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".bandbandstring802.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.bssidbssidbyte arrayIf 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.channelchanneluint320Wireless 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.cloned-mac-addresscloned-mac-addressbyte arrayThis D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".generate-mac-address-maskgenerate-mac-address-maskstringWith "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.
 
@@ -496,13 +508,13 @@ In infrastructure mode, various workarounds are used for a more reliable discove
 
 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-addressmac-addressbyte arrayIf 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-blacklistmac-address-blacklistarray of stringA 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-randomizationmac-address-randomizationuint320One 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).modemodestringWi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.powersavepowersaveuint320One 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.raterateuint320This property is not implemented and has no effect.securitysecurityThis property is deprecated and has no effect. For backwards compatibility, it can be set to "802-11-wireless-security" if the profile has a wireless security setting.seen-bssidsseen-bssidsarray of stringA 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.
+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-addressmac-addressbyte arrayIf 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-blacklistmac-address-blacklistarray of stringA 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-randomizationmac-address-randomizationuint320One of 0 (default) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  1 (never) (never randomize the MAC address), or 2 (always) (always randomize the MAC address).modemodestringWi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.powersavepowersaveuint320One of 2 (disable) (disable Wi-Fi power saving), 3 (enable) (enable Wi-Fi power saving), 1 (ignore) (don't touch currently configure setting) or 0 (default) (use the globally configured value). All other values are reserved.raterateuint320This property is not implemented and has no effect.securitysecurityThis property is deprecated and has no effect. For backwards compatibility, it can be set to "802-11-wireless-security" if the profile has a wireless security setting.seen-bssidsseen-bssidsarray of stringA list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network.  NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.
 
-This is not a regular property that the user would configure. Instead, NetworkManager automatically sets the seen BSSIDs and tracks them internally in "/var/lib/NetworkManager/seen-bssids" file.ssidssidbyte arraySSID of the Wi-Fi network. Must be specified.tx-powertx-poweruint320This property is not implemented and has no effect.wake-on-wlanwake-on-wlanuint321The 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).
802-11-wireless-securityWi-Fi Security Settings
+This is not a regular property that the user would configure. Instead, NetworkManager automatically sets the seen BSSIDs and tracks them internally in "/var/lib/NetworkManager/seen-bssids" file.</entry></row><row><entry><screen>ssid<indexterm zone="settings-802-11-wireless"><primary sortas="ssid">ssid</primary></indexterm></screen></entry><entry><screen>byte array</screen></entry><entry><screen/></entry><entry>SSID of the Wi-Fi network. Must be specified.</entry></row><row><entry><screen>tx-power<indexterm zone="settings-802-11-wireless"><primary sortas="tx-power">tx-power</primary></indexterm></screen></entry><entry><screen>uint32</screen></entry><entry><screen>0</screen></entry><entry>This property is not implemented and has no effect.</entry></row><row><entry><screen>wake-on-wlan<indexterm zone="settings-802-11-wireless"><primary sortas="wake-on-wlan">wake-on-wlan</primary></indexterm></screen></entry><entry><screen>uint32</screen></entry><entry><screen>1</screen></entry><entry>The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of 0x2 (any), 0x4 (disconnect), 0x8 (magic), 0x10 (gtk-rekey-failure), 0x20 (eap-identity-request), 0x40 (4way-handshake), 0x80 (rfkill-release), 0x100 (tcp) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).</entry></row></tbody></tgroup></table></para></refsect1></refentry><refentry id="settings-802-11-wireless-security"><refnamediv><refname>802-11-wireless-security</refname><refpurpose>Wi-Fi Security Settings</refpurpose></refnamediv><refsect1 role="properties"><title id="settings-802-11-wireless-security.properties">
             Properties
-        Key NameValue TypeDefault ValueValue Descriptionauth-algauth-algstringWhen WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here.  One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP.  When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.filsfilsint320Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection.  One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported).  When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.groupgrouparray of stringA list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list.  For maximum compatibility leave this property empty.  Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".key-mgmtkey-mgmtstringKey management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only).
+        
Key NameValue TypeDefault ValueValue Descriptionauth-algauth-algstringWhen WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here.  One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP.  When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.filsfilsint320Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection.  One of 0 (default) (use global default value), 1 (disable) (disable FILS), 2 (optional) (enable FILS if the supplicant and the access point support it) or 3 (required) (enable FILS and fail if not supported).  When set to 0 (default) and no global default is set, FILS will be optionally enabled.groupgrouparray of stringA list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list.  For maximum compatibility leave this property empty.  Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".key-mgmtkey-mgmtstringKey management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only).
 
-This property must be set for any Wi-Fi connection that uses security.leap-passwordleap-passwordstringThe login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").leap-password-flagsleap-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "leap-password" property.leap-usernameleap-usernamestringThe login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").pairwisepairwisearray of stringA list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty.  Each list element may be one of "tkip" or "ccmp".pmfpmfint320Indicates whether Protected Management Frames (802.11w) must be enabled for the connection.  One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported).  When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.protoprotoarray of stringList of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN).  If not specified, both WPA and RSN connections are allowed.pskpskstringPre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.psk-flagspsk-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "psk" property.wep-key-flagswep-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.wep-key-typewep-key-typeNMWepKeyType (uint32)Controls the interpretation of WEP keys.  Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.wep-key0wep-key0stringIndex 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key1wep-key1stringIndex 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key2wep-key2stringIndex 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key3wep-key3stringIndex 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-tx-keyidxwep-tx-keyidxuint320When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here.  Valid values are 0 (default key) through 3.  Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.wps-methodwps-methoduint320Flags indicating which mode of WPS is to be used if any.
+This property must be set for any Wi-Fi connection that uses security.leap-passwordleap-passwordstringThe login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").leap-password-flagsleap-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "leap-password" property.leap-usernameleap-usernamestringThe login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").pairwisepairwisearray of stringA list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty.  Each list element may be one of "tkip" or "ccmp".pmfpmfint320Indicates whether Protected Management Frames (802.11w) must be enabled for the connection.  One of 0 (default) (use global default value), 1 (disable) (disable PMF), 2 (optional) (enable PMF if the supplicant and the access point support it) or 3 (required) (enable PMF and fail if not supported).  When set to 0 (default) and no global default is set, PMF will be optionally enabled.protoprotoarray of stringList of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN).  If not specified, both WPA and RSN connections are allowed.pskpskstringPre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.psk-flagspsk-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "psk" property.wep-key-flagswep-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.wep-key-typewep-key-typeNMWepKeyType (uint32)Controls the interpretation of WEP keys.  Allowed values are 1 (key), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or 2 (passphrase), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.wep-key0wep-key0stringIndex 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key1wep-key1stringIndex 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key2wep-key2stringIndex 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key3wep-key3stringIndex 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-tx-keyidxwep-tx-keyidxuint320When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here.  Valid values are 0 (default key) through 3.  Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.wps-methodwps-methoduint320Flags indicating which mode of WPS is to be used if any.
 
 There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities.
 
@@ -514,17 +526,19 @@ WPS can be disabled by setting this property to a value of 1.
Key NameValue TypeDefault ValueValue Descriptionfrom-dhcpfrom-dhcpNMTernary (int32)Whether the system hostname can be determined from DHCP on this connection.
 
-When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).from-dns-lookupfrom-dns-lookupNMTernary (int32)Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.
+When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 1 (true).from-dns-lookupfrom-dns-lookupNMTernary (int32)Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.
 
-When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).only-from-defaultonly-from-defaultNMTernary (int32)If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).
+When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 1 (true).only-from-defaultonly-from-defaultNMTernary (int32)If set to 1 (true), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).
 
-If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route.
+If set to 0 (false), the hostname can be set from this device even if it doesn't have the default route.
 
-When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).prioritypriorityint320The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority.
+When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 0 (false).prioritypriorityint320The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority.
 
 If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100.
 
-Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.
linkLink settings
+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.</entry></row></tbody></tgroup></table></para></refsect1></refentry><refentry id="settings-hsr"><refnamediv><refname>hsr</refname><refpurpose>HSR/PRP Settings</refpurpose></refnamediv><refsect1 role="properties"><title id="settings-hsr.properties">
+            Properties
+        Key NameValue TypeDefault ValueValue Descriptionmulticast-specmulticast-specuint320The last byte of supervision address.port1port1stringThe port1 interface name of the HSR. This property is mandatory.port2port2stringThe port2 interface name of the HSR. This property is mandatory.prpprpbooleanFALSEThe protocol used by the interface, whether it is PRP or HSR.
linkLink settings
             Properties
         Key NameValue TypeDefault ValueValue Descriptiongro-max-sizegro-max-sizeint64-1The maximum size of a packet built by the Generic Receive Offload stack for this device. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.gso-max-segmentsgso-max-segmentsint64-1The maximum segments of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.gso-max-sizegso-max-sizeint64-1The maximum size of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.tx-queue-lengthtx-queue-lengthint64-1The size of the transmit queue for the device, in number of packets. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.
loopbackLoopback Link Settings
             Properties
diff --git a/docs/api/version.xml b/docs/api/version.xml
index 00aecdb4..8ce2f7ea 100644
--- a/docs/api/version.xml
+++ b/docs/api/version.xml
@@ -1 +1 @@
-1.44.2
+1.45.90
diff --git a/docs/libnm/Makefile.am b/docs/libnm/Makefile.am
index 7a10848f..87ab81cc 100644
--- a/docs/libnm/Makefile.am
+++ b/docs/libnm/Makefile.am
@@ -52,7 +52,6 @@ IGNORE_HFILES= \
 	\
 	nm-connection-private.h \
 	nm-default-libnm-core.h \
-	nm-property-compare.h \
 	nm-setting-private.h \
 	nm-team-utils.h \
 	nm-utils-private.h \
diff --git a/docs/libnm/Makefile.in b/docs/libnm/Makefile.in
index 03e2953e..218d8393 100644
--- a/docs/libnm/Makefile.in
+++ b/docs/libnm/Makefile.in
@@ -164,7 +164,6 @@ ACLOCAL = @ACLOCAL@
 AMTAR = @AMTAR@
 AM_CFLAGS = @AM_CFLAGS@
 AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@
-AM_TESTS_FD_REDIRECT = @AM_TESTS_FD_REDIRECT@
 AR = @AR@
 AUTOCONF = @AUTOCONF@
 AUTOHEADER = @AUTOHEADER@
@@ -353,8 +352,6 @@ SELINUX_LIBS = @SELINUX_LIBS@
 SET_MAKE = @SET_MAKE@
 SHELL = @SHELL@
 STRIP = @STRIP@
-SYSTEMD_200_CFLAGS = @SYSTEMD_200_CFLAGS@
-SYSTEMD_200_LIBS = @SYSTEMD_200_LIBS@
 SYSTEMD_INHIBIT_CFLAGS = @SYSTEMD_INHIBIT_CFLAGS@
 SYSTEMD_INHIBIT_LIBS = @SYSTEMD_INHIBIT_LIBS@
 SYSTEMD_JOURNAL_CFLAGS = @SYSTEMD_JOURNAL_CFLAGS@
@@ -506,7 +503,6 @@ IGNORE_HFILES = \
 	\
 	nm-connection-private.h \
 	nm-default-libnm-core.h \
-	nm-property-compare.h \
 	nm-setting-private.h \
 	nm-team-utils.h \
 	nm-utils-private.h \
diff --git a/docs/libnm/html/NMAccessPoint.html b/docs/libnm/html/NMAccessPoint.html
index cc8d8247..fb8aceb1 100644
--- a/docs/libnm/html/NMAccessPoint.html
+++ b/docs/libnm/html/NMAccessPoint.html
@@ -122,6 +122,14 @@
 </tr>
 <tr>
 <td class="function_type">
+<a href="https://developer.gnome.org/glib/unstable/glib-Basic-Types.html#guint32"><span class="returnvalue">guint32</span></a>
+</td>
+<td class="function_name">
+<a class="link" href="NMAccessPoint.html#nm-access-point-get-bandwidth" title="nm_access_point_get_bandwidth ()">nm_access_point_get_bandwidth</a> <span class="c_punctuation">()</span>
+</td>
+</tr>
+<tr>
+<td class="function_type">
 <a href="https://developer.gnome.org/glib/unstable/glib-Pointer-Arrays.html#GPtrArray"><span class="returnvalue">GPtrArray</span></a> *
 </td>
 <td class="function_name">
@@ -149,6 +157,11 @@
 </colgroup>
 <tbody>
 <tr>
+<td class="property_type"><a href="https://developer.gnome.org/glib/unstable/glib-Basic-Types.html#guint"><span class="type">guint</span></a></td>
+<td class="property_name"><a class="link" href="NMAccessPoint.html#NMAccessPoint--bandwidth" title="The “bandwidth” property">bandwidth</a></td>
+<td class="property_flags">Read</td>
+</tr>
+<tr>
 <td class="property_type">
 <span class="type">char</span> *</td>
 <td class="property_name"><a class="link" href="NMAccessPoint.html#NMAccessPoint--bssid" title="The “bssid” property">bssid</a></td>
@@ -259,6 +272,10 @@
 </tr>
 <tr>
 <td class="define_keyword">#define</td>
+<td class="function_name"><a class="link" href="NMAccessPoint.html#NM-ACCESS-POINT-BANDWIDTH:CAPS" title="NM_ACCESS_POINT_BANDWIDTH">NM_ACCESS_POINT_BANDWIDTH</a></td>
+</tr>
+<tr>
+<td class="define_keyword">#define</td>
 <td class="function_name"><a class="link" href="NMAccessPoint.html#NM-ACCESS-POINT-HW-ADDRESS:CAPS" title="NM_ACCESS_POINT_HW_ADDRESS">NM_ACCESS_POINT_HW_ADDRESS</a></td>
 </tr>
 <tr>
@@ -548,6 +565,33 @@ point has not been found in a scan.</p>
 </div>
 <hr>
 <div class="refsect2">
+<a name="nm-access-point-get-bandwidth"></a><h3>nm_access_point_get_bandwidth ()</h3>
+<pre class="programlisting"><a href="https://developer.gnome.org/glib/unstable/glib-Basic-Types.html#guint32"><span class="returnvalue">guint32</span></a>
+nm_access_point_get_bandwidth (<em class="parameter"><code><a class="link" href="NMAccessPoint.html" title="NMAccessPoint"><span class="type">NMAccessPoint</span></a> *ap</code></em>);</pre>
+<p>Gets the bandwidth advertised by the access point in MHz.</p>
+<div class="refsect3">
+<a name="nm-access-point-get-bandwidth.parameters"></a><h4>Parameters</h4>
+<div class="informaltable"><table class="informaltable" width="100%" border="0">
+<colgroup>
+<col width="150px" class="parameters_name">
+<col class="parameters_description">
+<col width="200px" class="parameters_annotations">
+</colgroup>
+<tbody><tr>
+<td class="parameter_name"><p>ap</p></td>
+<td class="parameter_description"><p>a <a class="link" href="NMAccessPoint.html" title="NMAccessPoint"><span class="type">NMAccessPoint</span></a></p></td>
+<td class="parameter_annotations"> </td>
+</tr></tbody>
+</table></div>
+</div>
+<div class="refsect3">
+<a name="nm-access-point-get-bandwidth.returns"></a><h4>Returns</h4>
+<p> the advertised bandwidth (MHz)</p>
+</div>
+<p class="since">Since: 1.46</p>
+</div>
+<hr>
+<div class="refsect2">
 <a name="nm-access-point-filter-connections"></a><h3>nm_access_point_filter_connections ()</h3>
 <pre class="programlisting"><a href="https://developer.gnome.org/glib/unstable/glib-Pointer-Arrays.html#GPtrArray"><span class="returnvalue">GPtrArray</span></a> *
 nm_access_point_filter_connections (<em class="parameter"><code><a class="link" href="NMAccessPoint.html" title="NMAccessPoint"><span class="type">NMAccessPoint</span></a> *ap</code></em>,
@@ -701,6 +745,12 @@ against</p></td>
 </div>
 <hr>
 <div class="refsect2">
+<a name="NM-ACCESS-POINT-BANDWIDTH:CAPS"></a><h3>NM_ACCESS_POINT_BANDWIDTH</h3>
+<pre class="programlisting">#define NM_ACCESS_POINT_BANDWIDTH   "bandwidth"
+</pre>
+</div>
+<hr>
+<div class="refsect2">
 <a name="NM-ACCESS-POINT-HW-ADDRESS:CAPS"></a><h3>NM_ACCESS_POINT_HW_ADDRESS</h3>
 <pre class="programlisting">#define NM_ACCESS_POINT_HW_ADDRESS "hw-address"
 </pre>
@@ -714,6 +764,16 @@ against</p></td>
 <div class="refsect1">
 <a name="NMAccessPoint.property-details"></a><h2>Property Details</h2>
 <div class="refsect2">
+<a name="NMAccessPoint--bandwidth"></a><h3>The <code class="literal">“bandwidth”</code> property</h3>
+<pre class="programlisting">  “bandwidth”                <a href="https://developer.gnome.org/glib/unstable/glib-Basic-Types.html#guint"><span class="type">guint</span></a></pre>
+<p>The channel bandwidth announced by the AP in MHz.</p>
+<p>Owner: NMAccessPoint</p>
+<p>Flags: Read</p>
+<p>Default value: 0</p>
+<p class="since">Since: 1.46</p>
+</div>
+<hr>
+<div class="refsect2">
 <a name="NMAccessPoint--bssid"></a><h3>The <code class="literal">“bssid”</code> property</h3>
 <pre class="programlisting">  “bssid”                    <span class="type">char</span> *</pre>
 <p>The BSSID of the access point.</p>
diff --git a/docs/libnm/html/NMClient.html b/docs/libnm/html/NMClient.html
index ea71511a..7e923ca9 100644
--- a/docs/libnm/html/NMClient.html
+++ b/docs/libnm/html/NMClient.html
@@ -5435,11 +5435,25 @@ setting LIBNM_CLIENT_DEBUG and uses thereby <a href="https://developer.gnome.org
 <a href="https://developer.gnome.org/glib/unstable/glib-Warnings-and-Assertions.html#g-print"><code class="function">g_print()</code></a>. A plain "<code class="function">print()</code>" function in python is not in sync
 with these functions (it implements additional buffering). By
 using <a class="link" href="NMClient.html#nm-utils-print" title="nm_utils_print ()"><code class="function">nm_utils_print()</code></a>, the same logging mechanisms can be used.</p>
-<p>Also, libnm honors LIBNM_CLIENT_DEBUG_FILE environment. If this
-is set to a filename pattern (accepting "<code class="literal">p</code>" for the process ID),
-then the debug log is written to that file instead. With <em class="parameter"><code>output_mode</code></em>
-
-zero, the same location will be written. Since: 1.44.</p>
+<p>LIBNM_CLIENT_DEBUG is a list of keywords separated by commas. The keyword
+"trace" enables printing messages of the lowest up to the highest severity.
+Likewise, the severities "debug", "warn" ("warning") and "error" are honored
+in similar way. Setting the flags "ERROR" or "WARN" ("WARNING") implies that
+respective levels are enabled, but also are ERROR messages printed with
+<a href="https://developer.gnome.org/glib/unstable/glib-Message-Logging.html#g-critical"><code class="function">g_critical()</code></a> and WARN messages with <a href="https://developer.gnome.org/glib/unstable/glib-Message-Logging.html#g-warning"><code class="function">g_warning()</code></a>. Together with G_DEBUG="fatal-warnings"
+or G_DEBUG="fatal-critical" this can be used to abort the program on errors.
+Note that all <error> messages imply an unexpected data on the D-Bus API
+(due to a bug). <warn> also implies unexepected data, but that can happen
+when using different versions of libnm and daemon. For testing, it is
+good to turn these into assertions.</p>
+<p>By default, messages are printed to stderr, unless LIBNM_CLIENT_DEBUG
+contains "stdout" flag. Also, libnm honors LIBNM_CLIENT_DEBUG_FILE
+environment. If this is set to a filename pattern (accepting "%<code class="literal">p</code>" for the
+process ID), then the debug log is written to that file instead of
+stderr/stdout. With <em class="parameter"><code>output_mode</code></em>
+ zero, the same location will be written.</p>
+<p>LIBNM_CLIENT_DEBUG_FILE is supported since 1.44. "ERROR", "WARN" and "WARNING"
+are supported since 1.46.</p>
 <div class="refsect3">
 <a name="nm-utils-print.parameters"></a><h4>Parameters</h4>
 <div class="informaltable"><table class="informaltable" width="100%" border="0">
diff --git a/docs/libnm/html/NMDevice.html b/docs/libnm/html/NMDevice.html
index 7656f9b2..21fb84ab 100644
--- a/docs/libnm/html/NMDevice.html
+++ b/docs/libnm/html/NMDevice.html
@@ -902,6 +902,7 @@
             <span class="lineart">├──</span> <a class="link" href="NMDeviceDummy.html" title="NMDeviceDummy">NMDeviceDummy</a>
             <span class="lineart">├──</span> <a class="link" href="NMDeviceEthernet.html" title="NMDeviceEthernet">NMDeviceEthernet</a>
             <span class="lineart">├──</span> <a class="link" href="NMDeviceGeneric.html" title="NMDeviceGeneric">NMDeviceGeneric</a>
+            <span class="lineart">├──</span> <a class="link" href="NMDeviceHsr.html" title="NMDeviceHsr">NMDeviceHsr</a>
             <span class="lineart">├──</span> <a class="link" href="NMDeviceInfiniband.html" title="NMDeviceInfiniband">NMDeviceInfiniband</a>
             <span class="lineart">├──</span> <a class="link" href="NMDeviceIPTunnel.html" title="NMDeviceIPTunnel">NMDeviceIPTunnel</a>
             <span class="lineart">├──</span> <a class="link" href="NMDeviceLoopback.html" title="NMDeviceLoopback">NMDeviceLoopback</a>
diff --git a/docs/libnm/html/NMDeviceGeneric.html b/docs/libnm/html/NMDeviceGeneric.html
index 62284b4c..d97855f9 100644
--- a/docs/libnm/html/NMDeviceGeneric.html
+++ b/docs/libnm/html/NMDeviceGeneric.html
@@ -7,7 +7,7 @@
 <link rel="home" href="index.html" title="libnm Reference Manual">
 <link rel="up" href="ch04.html" title="Device and Runtime Configuration API Reference">
 <link rel="prev" href="NMDeviceEthernet.html" title="NMDeviceEthernet">
-<link rel="next" href="NMDeviceInfiniband.html" title="NMDeviceInfiniband">
+<link rel="next" href="NMDeviceHsr.html" title="NMDeviceHsr">
 <meta name="generator" content="GTK-Doc V1.33.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
@@ -22,7 +22,7 @@
 <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
 <td><a accesskey="u" href="ch04.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
 <td><a accesskey="p" href="NMDeviceEthernet.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
-<td><a accesskey="n" href="NMDeviceInfiniband.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
+<td><a accesskey="n" href="NMDeviceHsr.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
 </tr></table>
 <div class="refentry">
 <a name="NMDeviceGeneric"></a><div class="titlepage"></div>
diff --git a/docs/libnm/html/NMDeviceHsr.html b/docs/libnm/html/NMDeviceHsr.html
new file mode 100644
index 00000000..39cbab48
--- /dev/null
+++ b/docs/libnm/html/NMDeviceHsr.html
@@ -0,0 +1,398 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>NMDeviceHsr: libnm Reference Manual
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

+

+

+
+
+

+
NMDeviceHsr

+
NMDeviceHsr

+

+

+
Functions

+

++++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+





+NMDevice *
+
+nm_device_hsr_get_port1 ()
+

+NMDevice *
+
+nm_device_hsr_get_port2 ()
+
const char *
+
+nm_device_hsr_get_supervision_address ()
+

+guint8
+
+nm_device_hsr_get_multicast_spec ()
+

+gboolean
+
+nm_device_hsr_get_prp ()
+

+

+

+
Properties

+

+++++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+





gucharmulticast-specRead

+NMDevice *port1Read

+NMDevice *port2Read
gbooleanprpRead

+char *supervision-addressRead

+

+

+
Types and Values

+

++++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+




#defineNM_DEVICE_HSR_PORT1
#defineNM_DEVICE_HSR_PORT2
#defineNM_DEVICE_HSR_SUPERVISION_ADDRESS
#defineNM_DEVICE_HSR_MULTICAST_SPEC
#defineNM_DEVICE_HSR_PRP
 NMDeviceHsr

+

+

+
Object Hierarchy

+
    GObject
+    ╰── NMObject
+        ╰── NMDevice
+            ╰── NMDeviceHsr
+

+

+

+
Description

+

+

+
Functions

+

+
nm_device_hsr_get_port1 ()

+
NMDevice *
+nm_device_hsr_get_port1 (NMDeviceHsr *device);

+

+
Parameters

+

+++++
+
+
+
+
+
+





device
a NMDeviceHsr
 

+

+

+
Returns

+
the device's port1 device. 

+
[transfer none]

+

+
Since: 1.46

+

+

+

+
nm_device_hsr_get_port2 ()

+
NMDevice *
+nm_device_hsr_get_port2 (NMDeviceHsr *device);

+

+
Parameters

+

+++++
+
+
+
+
+
+





device
a NMDeviceHsr
 

+

+

+
Returns

+
the device's port2 device. 

+
[transfer none]

+

+
Since: 1.46

+

+

+

+
nm_device_hsr_get_supervision_address ()

+
const char *
+nm_device_hsr_get_supervision_address (NMDeviceHsr *device);

+

+
Parameters

+

+++++
+
+
+
+
+
+





device
a NMDeviceHsr
 

+

+

+
Returns

+
 the supervision MAC adddress

+

+
Since: 1.46

+

+

+

+
nm_device_hsr_get_multicast_spec ()

+
guint8
+nm_device_hsr_get_multicast_spec (NMDeviceHsr *device);

+

+
Parameters

+

+++++
+
+
+
+
+
+





device
a NMDeviceHsr
 

+

+

+
Returns

+
 the last byte of the supervision address

+

+
Since: 1.46

+

+

+

+
nm_device_hsr_get_prp ()

+
gboolean
+nm_device_hsr_get_prp (NMDeviceHsr *device);

+

+
Parameters

+

+++++
+
+
+
+
+
+





device
a NMDeviceHsr
 

+

+

+
Returns

+
 whether PRP protocol is used or not

+

+
Since: 1.46

+

+

+

+
Types and Values

+

+
NM_DEVICE_HSR_PORT1

+
#define NM_DEVICE_HSR_PORT1               "port1"
+

+

+

+

+
NM_DEVICE_HSR_PORT2

+
#define NM_DEVICE_HSR_PORT2               "port2"
+

+

+

+

+
NM_DEVICE_HSR_SUPERVISION_ADDRESS

+
#define NM_DEVICE_HSR_SUPERVISION_ADDRESS "supervision-address"
+

+

+

+

+
NM_DEVICE_HSR_MULTICAST_SPEC

+
#define NM_DEVICE_HSR_MULTICAST_SPEC      "multicast-spec"
+

+

+

+

+
NM_DEVICE_HSR_PRP

+
#define NM_DEVICE_HSR_PRP                 "prp"
+

+

+

+

+
NMDeviceHsr

+
typedef struct _NMDeviceHsr NMDeviceHsr;

+
Since: 1.46

+

+

+

+
Property Details

+

+
The “multicast-spec” property

+
  “multicast-spec”           guchar

+
The device last byte of the supervision address.

+
Owner: NMDeviceHsr

+
Flags: Read

+
Default value: 0

+
Since: 1.46

+

+

+

+
The “port1” property

+
  “port1”                    NMDevice *

+
The device's port1 device.

+
Owner: NMDeviceHsr

+
Flags: Read

+
Since: 1.46

+

+

+

+
The “port2” property

+
  “port2”                    NMDevice *

+
The device's port2 device.

+
Owner: NMDeviceHsr

+
Flags: Read

+
Since: 1.46

+

+

+

+
The “prp” property

+
  “prp”                      gboolean

+
Whether the PRP protocol is used or not.

+
Owner: NMDeviceHsr

+
Flags: Read

+
Default value: FALSE

+
Since: 1.46

+

+

+

+
The “supervision-address” property

+
  “supervision-address”      char *

+
The device supervision MAC adddress.

+
Owner: NMDeviceHsr

+
Flags: Read

+
Default value: NULL

+
Since: 1.46

+

+

+

+

+
Generated by GTK-Doc V1.33.1

+
+
\ No newline at end of file
diff --git a/docs/libnm/html/NMDeviceIPTunnel.html b/docs/libnm/html/NMDeviceIPTunnel.html
index 9058daf8..d3bc1474 100644
--- a/docs/libnm/html/NMDeviceIPTunnel.html
+++ b/docs/libnm/html/NMDeviceIPTunnel.html
@@ -127,6 +127,14 @@
 
 
 
+guint32
+
+
+nm_device_ip_tunnel_get_fwmark ()
+
+
+
+
 NMIPTunnelFlags
 
 
@@ -161,6 +169,11 @@
 Read
 
 
+guint
+fwmark
+Read
+
+
 
 char *
 input-key
@@ -267,6 +280,10 @@
 
 
 #define
+NM_DEVICE_IP_TUNNEL_FWMARK
+
+
+#define
 NM_DEVICE_IP_TUNNEL_FLAGS
 
 
@@ -580,6 +597,33 @@ nm_device_ip_tunnel_get_flow_label (
 

 

+
nm_device_ip_tunnel_get_fwmark ()

+
guint32
+nm_device_ip_tunnel_get_fwmark (NMDeviceIPTunnel *device);

+

+
Parameters

+

+++++
+
+
+
+
+
+





device
a NMDeviceIPTunnel
 

+

+

+
Returns

+
 the fwmark assigned to tunnel packets. This property applies only
+to VTI tunnels.

+

+
Since: 1.46

+

+

+

 
nm_device_ip_tunnel_get_flags ()

 
NMIPTunnelFlags
 nm_device_ip_tunnel_get_flags (NMDeviceIPTunnel *device);

@@ -674,6 +718,12 @@ nm_device_ip_tunnel_get_flags (
 

 

+
NM_DEVICE_IP_TUNNEL_FWMARK

+
#define NM_DEVICE_IP_TUNNEL_FWMARK              "fwmark"
+

+

+

+

 
NM_DEVICE_IP_TUNNEL_FLAGS

 
#define NM_DEVICE_IP_TUNNEL_FLAGS               "flags"
 

@@ -722,6 +772,17 @@ applies only to IPv6 tunnels.

 

 

 

+
The “fwmark” property

+
  “fwmark”                   guint

+
The fwmark value to assign to tunnel packets. This property applies only
+to VTI tunnels.

+
Owner: NMDeviceIPTunnel

+
Flags: Read

+
Default value: 0

+
Since: 1.46

+

+

+

 
The “input-key” property

 
  “input-key”                char *

 
The key used for tunneled input packets, if applicable.

diff --git a/docs/libnm/html/NMDeviceInfiniband.html b/docs/libnm/html/NMDeviceInfiniband.html
index e3791ead..433c25f9 100644
--- a/docs/libnm/html/NMDeviceInfiniband.html
+++ b/docs/libnm/html/NMDeviceInfiniband.html
@@ -6,7 +6,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
 
 Home
 Up
-Prev
+Prev
 Next
 
 

diff --git a/docs/libnm/html/NMSettingConnection.html b/docs/libnm/html/NMSettingConnection.html
index 2f52b0c0..03ea59e7 100644
--- a/docs/libnm/html/NMSettingConnection.html
+++ b/docs/libnm/html/NMSettingConnection.html
@@ -194,6 +194,13 @@
 
 
 
+const char *
+
+
+nm_setting_connection_get_controller ()
+
+
+
 
 gboolean
 
@@ -209,6 +216,13 @@
 
 
 
+const char *
+
+
+nm_setting_connection_get_port_type ()
+
+
+
 
 NMSettingConnectionAutoconnectSlaves
 
@@ -427,10 +441,18 @@
 
 
 #define
+NM_SETTING_CONNECTION_CONTROLLER
+
+
+#define
 NM_SETTING_CONNECTION_SLAVE_TYPE
 
 
 #define
+NM_SETTING_CONNECTION_PORT_TYPE
+
+
+#define
 NM_SETTING_CONNECTION_AUTOCONNECT_SLAVES
 
 
@@ -1123,6 +1145,11 @@ be a username. See “permissions”: for more details
 
nm_setting_connection_get_master ()

 
const char *
 nm_setting_connection_get_master (NMSettingConnection *setting);

+

+
nm_setting_connection_get_master has been deprecated since version 1.46. and should not be used in newly-written code.

+
Use nm_setting_connection_get_controller() instead which
+is just an alias.

+

 
Returns the “master” property of the connection.

 

 
Parameters

@@ -1147,10 +1174,39 @@ connection.

 

 

 

+
nm_setting_connection_get_controller ()

+
const char *
+nm_setting_connection_get_controller (NMSettingConnection *setting);

+
Returns the “controller” property of the connection.

+

+
Parameters

+

+++++
+
+
+
+
+
+





setting
the NMSettingConnection
 

+

+

+
Returns

+
 interface name of the controller device or UUID of the controller
+connection.

+

+
Since: 1.46

+

+

+

 
nm_setting_connection_is_slave_type ()

 
gboolean
 nm_setting_connection_is_slave_type (NMSettingConnection *setting,
                                      const char *type);

+
nm_setting_connection_is_slave_type has been deprecated since version 1.46. and should not be used in newly-written code.

 

 
Parameters

 

@@ -1186,6 +1242,11 @@ against setting
nm_setting_connection_get_slave_type ()
const char *
 nm_setting_connection_get_slave_type (NMSettingConnection *setting);

+

+
nm_setting_connection_get_slave_type has been deprecated since version 1.46. and should not be used in newly-written code.

+
Use nm_setting_connection_get_port_type() instead which
+is just an alias.

+
Returns the “slave-type” property of the connection.

 
Parameters

@@ -1209,6 +1270,33 @@ nm_setting_connection_get_slave_type (
+
nm_setting_connection_get_port_type ()

+
const char *
+nm_setting_connection_get_port_type (NMSettingConnection *setting);

+
Returns the “port-type” property of the connection.

+

+
Parameters

+

 
 
 
 

+++++
+
+
+
+
+
+





setting
the NMSettingConnection
 

+

+

+
Returns

+
 the type of port this connection is, if any.

+

+
Since: 1.46

+

+

+

 
nm_setting_connection_get_autoconnect_slaves ()

 
NMSettingConnectionAutoconnectSlaves
 nm_setting_connection_get_autoconnect_slaves
@@ -1810,12 +1898,24 @@ property.

 

 

 

+
NM_SETTING_CONNECTION_CONTROLLER

+
#define NM_SETTING_CONNECTION_CONTROLLER            "controller"
+

+

+

+

 
NM_SETTING_CONNECTION_SLAVE_TYPE

 
#define NM_SETTING_CONNECTION_SLAVE_TYPE            "slave-type"
 

 

 

 

+
NM_SETTING_CONNECTION_PORT_TYPE

+
#define NM_SETTING_CONNECTION_PORT_TYPE             "port-type"
+

+

+

+

 
NM_SETTING_CONNECTION_AUTOCONNECT_SLAVES

 
#define NM_SETTING_CONNECTION_AUTOCONNECT_SLAVES    "autoconnect-slaves"
 

diff --git a/docs/libnm/html/NMSettingEthtool.html b/docs/libnm/html/NMSettingEthtool.html
index 17229f97..0f7af39b 100644
--- a/docs/libnm/html/NMSettingEthtool.html
+++ b/docs/libnm/html/NMSettingEthtool.html
@@ -73,6 +73,22 @@
 
 
 
+gboolean
+
+
+nm_ethtool_optname_is_channels ()
+
+
+
+
+gboolean
+
+
+nm_ethtool_optname_is_eee ()
+
+
+
+
 NMSetting *
 
 
@@ -253,6 +269,64 @@ is valid

 

 

 

+
nm_ethtool_optname_is_channels ()

+
gboolean
+nm_ethtool_optname_is_channels (const char *optname);

+
Checks whether optname
+ is a valid option name for a channels setting.

+

+
Parameters

+

+++++
+
+
+
+
+
+





optname
the option name to check. 
[nullable]

+

+

+
Returns

+
 TRUE, if optname
+is valid

+

+
Since: 1.46

+

+

+

+
nm_ethtool_optname_is_eee ()

+
gboolean
+nm_ethtool_optname_is_eee (const char *optname);

+
Checks whether optname
+ is a valid option name for an eee setting.

+

+
Parameters

+

+++++
+
+
+
+
+
+





optname
the option name to check. 
[nullable]

+

+

+
Returns

+
 TRUE, if optname
+is valid

+

+
Since: 1.46

+

+

+

 
nm_setting_ethtool_new ()

 
NMSetting *
 nm_setting_ethtool_new (void);

diff --git a/docs/libnm/html/NMSettingHostname.html b/docs/libnm/html/NMSettingHostname.html
index 6b0f3d43..4c1ec75f 100644
--- a/docs/libnm/html/NMSettingHostname.html
+++ b/docs/libnm/html/NMSettingHostname.html
@@ -7,7 +7,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
 Home
 Up
 Prev
-Next
+Next
 
 

 

diff --git a/docs/libnm/html/NMSettingHsr.html b/docs/libnm/html/NMSettingHsr.html
new file mode 100644
index 00000000..4d9cf5db
--- /dev/null
+++ b/docs/libnm/html/NMSettingHsr.html
@@ -0,0 +1,274 @@
+
+
+
+
+NMSettingHsr: libnm Reference Manual
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

+

+

+
+
+

+
NMSettingHsr

+
NMSettingHsr — Describes connection properties for HSR/PRP interfaces

+

+

+
Functions

+

++++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+





+NMSetting *
+
+nm_setting_hsr_new ()
+
const char *
+
+nm_setting_hsr_get_port1 ()
+
const char *
+
+nm_setting_hsr_get_port2 ()
+

+guint32
+
+nm_setting_hsr_get_multicast_spec ()
+

+gboolean
+
+nm_setting_hsr_get_prp ()
+

+

+

+
Types and Values

+

++++
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+




#defineNM_SETTING_HSR_SETTING_NAME
#defineNM_SETTING_HSR_PORT1
#defineNM_SETTING_HSR_PORT2
#defineNM_SETTING_HSR_MULTICAST_SPEC
#defineNM_SETTING_HSR_PRP

+

+

+
Description

+
The NMSettingHsr object is a NMSetting subclass that describes properties
+necessary for HSR/PRP connections.

+

+

+
Functions

+

+
nm_setting_hsr_new ()

+
NMSetting *
+nm_setting_hsr_new (void);

+
Creates a new NMSettingHsr object with default values.

+

+
Returns

+
the new empty NMSettingHsr object. 

+
[transfer full]

+

+
Since: 1.46

+

+

+

+
nm_setting_hsr_get_port1 ()

+
const char *
+nm_setting_hsr_get_port1 (NMSettingHsr *setting);

+

+
Parameters

+

+++++
+
+
+
+
+
+





setting
the NMSettingHsr
 

+

+

+
Returns

+
 the “port1” property of the setting

+

+
Since: 1.46

+

+

+

+
nm_setting_hsr_get_port2 ()

+
const char *
+nm_setting_hsr_get_port2 (NMSettingHsr *setting);

+

+
Parameters

+

+++++
+
+
+
+
+
+





setting
the NMSettingHsr
 

+

+

+
Returns

+
 the “port2” property of the setting

+

+
Since: 1.46

+

+

+

+
nm_setting_hsr_get_multicast_spec ()

+
guint32
+nm_setting_hsr_get_multicast_spec (NMSettingHsr *setting);

+

+
Parameters

+

+++++
+
+
+
+
+
+





setting
the NMSettingHsr
 

+

+

+
Returns

+
 the “multicast_spec” property of the setting

+

+
Since: 1.46

+

+

+

+
nm_setting_hsr_get_prp ()

+
gboolean
+nm_setting_hsr_get_prp (NMSettingHsr *setting);

+

+
Parameters

+

+++++
+
+
+
+
+
+





setting
the NMSettingHsr
 

+

+

+
Returns

+
 the “prp” property of the setting

+

+
Since: 1.46

+

+

+

+
Types and Values

+

+
NM_SETTING_HSR_SETTING_NAME

+
#define NM_SETTING_HSR_SETTING_NAME "hsr"
+

+

+

+

+
NM_SETTING_HSR_PORT1

+
#define NM_SETTING_HSR_PORT1          "port1"
+

+

+

+

+
NM_SETTING_HSR_PORT2

+
#define NM_SETTING_HSR_PORT2          "port2"
+

+

+

+

+
NM_SETTING_HSR_MULTICAST_SPEC

+
#define NM_SETTING_HSR_MULTICAST_SPEC "multicast-spec"
+

+

+

+

+
NM_SETTING_HSR_PRP

+
#define NM_SETTING_HSR_PRP            "prp"
+

+

+

+

+

+
Generated by GTK-Doc V1.33.1

+
+
\ No newline at end of file
diff --git a/docs/libnm/html/NMSettingIPConfig.html b/docs/libnm/html/NMSettingIPConfig.html
index af4014f4..332cf285 100644
--- a/docs/libnm/html/NMSettingIPConfig.html
+++ b/docs/libnm/html/NMSettingIPConfig.html
@@ -1481,6 +1481,14 @@ addressing, routing, and name service properties

 NM_SETTING_DNS_OPTION_NO_AAAA
 
 
+#define
+NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_EDNS0
+
+
+#define
+NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_TRUST_AD
+
+
 enum
 NMDhcpHostnameFlags
 
@@ -4626,6 +4634,7 @@ nm_setting_ip_config_get_num_dns_searches
 
const char *
 nm_setting_ip_config_get_dns_search (NMSettingIPConfig *setting,
                                      int idx);

+
Since 1.46, access at index "len" is allowed and returns NULL.

 

 
Parameters

 

@@ -4844,6 +4853,7 @@ a default configuration, while the former explicitly means "no-options".
const char *
 nm_setting_ip_config_get_dns_option (NMSettingIPConfig *setting,
                                      guint idx);

+
Since 1.46, access at index "len" is allowed and returns NULL.

 
Parameters

 

 
 

@@ -6640,6 +6650,18 @@ rule verfies or fail.

+
NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_EDNS0

+
#define NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_EDNS0    "_no-add-edns0"
+

+

+

+

+
NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_TRUST_AD

+
#define NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_TRUST_AD "_no-add-trust-ad"
+

+

+

+

 
enum NMDhcpHostnameFlags

 
NMDhcpHostnameFlags describe flags related to the DHCP hostname and
 FQDN.

diff --git a/docs/libnm/html/NMSettingInfiniband.html b/docs/libnm/html/NMSettingInfiniband.html
index 185907d0..7517142d 100644
--- a/docs/libnm/html/NMSettingInfiniband.html
+++ b/docs/libnm/html/NMSettingInfiniband.html
@@ -6,7 +6,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
 
 

-
+

 
 
 
Home
 UpPrevPrev
 Next
 

 

diff --git a/docs/libnm/html/NMSettingMatch.html b/docs/libnm/html/NMSettingMatch.html
index b947087b..19caee40 100644
--- a/docs/libnm/html/NMSettingMatch.html
+++ b/docs/libnm/html/NMSettingMatch.html
@@ -356,6 +356,7 @@ nm_setting_match_get_num_interface_names
 
const char *
 nm_setting_match_get_interface_name (NMSettingMatch *setting,
                                      int idx);

+
Since 1.46, access at index "len" is allowed and returns NULL.

 

 
Parameters

 

@@ -582,6 +583,7 @@ nm_setting_match_get_num_kernel_command_lines
 nm_setting_match_get_kernel_command_line
                                (NMSettingMatch *setting,
                                 guint idx);
+
Since 1.46, access at index "len" is allowed and returns NULL.

 
Parameters

 

 

@@ -806,6 +808,7 @@ nm_setting_match_get_num_drivers (const char *
 nm_setting_match_get_driver (NMSettingMatch *setting,
                              guint idx);
+
Since 1.46, access at index "len" is allowed and returns NULL.

 

 
Parameters

 

@@ -1026,6 +1029,7 @@ nm_setting_match_get_num_paths (const char *
 nm_setting_match_get_path (NMSettingMatch *setting,
                            guint idx);
+
Since 1.46, access at index "len" is allowed and returns NULL.

 

 
Parameters

 

diff --git a/docs/libnm/html/NMSettingWired.html b/docs/libnm/html/NMSettingWired.html
index ce30f971..18510898 100644
--- a/docs/libnm/html/NMSettingWired.html
+++ b/docs/libnm/html/NMSettingWired.html
@@ -614,6 +614,7 @@ nm_setting_wired_get_num_mac_blacklist_items
 nm_setting_wired_get_mac_blacklist_item
                                (NMSettingWired *setting,
                                 guint32 idx);
+
Since 1.46, access at index "len" is allowed and returns NULL.

 

 
Parameters

 

diff --git a/docs/libnm/html/NMSettingWireless.html b/docs/libnm/html/NMSettingWireless.html
index 23a7e62e..b3693736 100644
--- a/docs/libnm/html/NMSettingWireless.html
+++ b/docs/libnm/html/NMSettingWireless.html
@@ -716,6 +716,7 @@ nm_setting_wireless_get_num_mac_blacklist_items
 nm_setting_wireless_get_mac_blacklist_item
                                (NMSettingWireless *setting,
                                 guint32 idx);
+
Since 1.46, access at index "len" is allowed and returns NULL.

 

 
Parameters

 

diff --git a/docs/libnm/html/api-index-full.html b/docs/libnm/html/api-index-full.html
index 3720b3f9..bec94dd6 100644
--- a/docs/libnm/html/api-index-full.html
+++ b/docs/libnm/html/api-index-full.html
@@ -73,6 +73,10 @@
 
 

 

+NMAccessPoint:bandwidth, object property in NMAccessPoint
+

+

+

 NMAccessPoint:bssid, object property in NMAccessPoint
 

 

@@ -117,6 +121,10 @@
 
 

 

+NM_ACCESS_POINT_BANDWIDTH, macro in NMAccessPoint
+

+

+

 NM_ACCESS_POINT_BSSID, macro in NMAccessPoint
 

 

@@ -137,6 +145,10 @@
 
 

 

+nm_access_point_get_bandwidth, function in NMAccessPoint
+

+

+

 nm_access_point_get_bssid, function in NMAccessPoint
 

 

@@ -541,6 +553,10 @@
 
 

 

+NM_AVAILABLE_IN_1_46, macro in nm-version
+

+

+

 NM_AVAILABLE_IN_1_6, macro in nm-version
 

 

@@ -1828,6 +1844,10 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+NM_DBUS_INTERFACE_DEVICE_HSR, macro in nm-dbus-interface
+

+

+

 NM_DBUS_INTERFACE_DEVICE_INFINIBAND, macro in nm-dbus-interface
 

 

@@ -2272,6 +2292,14 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+NM_DEPRECATED_IN_1_46, macro in nm-version
+

+

+

+NM_DEPRECATED_IN_1_46_FOR, macro in nm-version
+

+

+

 NM_DEPRECATED_IN_1_4_FOR, macro in nm-version
 

 

@@ -2524,6 +2552,30 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+NMDeviceHsr, struct in NMDeviceHsr
+

+

+

+NMDeviceHsr:multicast-spec, object property in NMDeviceHsr
+

+

+

+NMDeviceHsr:port1, object property in NMDeviceHsr
+

+

+

+NMDeviceHsr:port2, object property in NMDeviceHsr
+

+

+

+NMDeviceHsr:prp, object property in NMDeviceHsr
+

+

+

+NMDeviceHsr:supervision-address, object property in NMDeviceHsr
+

+

+

 NMDeviceInfiniband, struct in NMDeviceInfiniband
 

 

@@ -2552,6 +2604,10 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+NMDeviceIPTunnel:fwmark, object property in NMDeviceIPTunnel
+

+

+

 NMDeviceIPTunnel:input-key, object property in NMDeviceIPTunnel
 

 

@@ -3412,6 +3468,46 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+nm_device_hsr_get_multicast_spec, function in NMDeviceHsr
+

+

+

+nm_device_hsr_get_port1, function in NMDeviceHsr
+

+

+

+nm_device_hsr_get_port2, function in NMDeviceHsr
+

+

+

+nm_device_hsr_get_prp, function in NMDeviceHsr
+

+

+

+nm_device_hsr_get_supervision_address, function in NMDeviceHsr
+

+

+

+NM_DEVICE_HSR_MULTICAST_SPEC, macro in NMDeviceHsr
+

+

+

+NM_DEVICE_HSR_PORT1, macro in NMDeviceHsr
+

+

+

+NM_DEVICE_HSR_PORT2, macro in NMDeviceHsr
+

+

+

+NM_DEVICE_HSR_PRP, macro in NMDeviceHsr
+

+

+

+NM_DEVICE_HSR_SUPERVISION_ADDRESS, macro in NMDeviceHsr
+

+

+

 NM_DEVICE_HW_ADDRESS, macro in NMDevice
 

 

@@ -3472,6 +3568,10 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+NM_DEVICE_IP_TUNNEL_FWMARK, macro in NMDeviceIPTunnel
+

+

+

 nm_device_ip_tunnel_get_encapsulation_limit, function in NMDeviceIPTunnel
 

 

@@ -3484,6 +3584,10 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+nm_device_ip_tunnel_get_fwmark, function in NMDeviceIPTunnel
+

+

+

 nm_device_ip_tunnel_get_input_key, function in NMDeviceIPTunnel
 

 

@@ -4445,6 +4549,22 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+NM_ETHTOOL_OPTNAME_CHANNELS_COMBINED, macro in nm-ethtool-utils
+

+

+

+NM_ETHTOOL_OPTNAME_CHANNELS_OTHER, macro in nm-ethtool-utils
+

+

+

+NM_ETHTOOL_OPTNAME_CHANNELS_RX, macro in nm-ethtool-utils
+

+

+

+NM_ETHTOOL_OPTNAME_CHANNELS_TX, macro in nm-ethtool-utils
+

+

+

 NM_ETHTOOL_OPTNAME_COALESCE_ADAPTIVE_RX, macro in nm-ethtool-utils
 

 

@@ -4533,6 +4653,10 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+NM_ETHTOOL_OPTNAME_EEE_ENABLED, macro in nm-ethtool-utils
+

+

+

 NM_ETHTOOL_OPTNAME_FEATURE_ESP_HW_OFFLOAD, macro in nm-ethtool-utils
 

 

@@ -4765,10 +4889,18 @@ NMConnection::secrets-updated, object signal in NMSettingOvs
 
 

 

+nm_ethtool_optname_is_channels, function in NMSettingEthtool
+

+

+

 nm_ethtool_optname_is_coalesce, function in NMSettingEthtool
 

 

 

+nm_ethtool_optname_is_eee, function in NMSettingEthtool
+

+

+

 nm_ethtool_optname_is_feature, function in NMSettingEthtool
 

 

@@ -6400,6 +6532,10 @@ NMSettingConnection:autoconnect-slaves, object property in NMSettingOvs
 
 

 

+NMSettingConnection:controller, object property in NMSettingOvs
+

+

+

 NMSettingConnection:dns-over-tls, object property in NMSettingOvs
 

 

@@ -6452,6 +6588,10 @@ NMSettingConnection:permissions, object property in NMSettingOvs
 
 

 

+NMSettingConnection:port-type, object property in NMSettingOvs
+

+

+

 NMSettingConnection:read-only, object property in NMSettingOvs
 

 

@@ -6684,6 +6824,26 @@ NMSettingHostname:priority, object property in NMSettingOvs
 
 

 

+NMSettingHsr, struct in NMSettingOvs
+

+

+

+NMSettingHsr:multicast-spec, object property in NMSettingOvs
+

+

+

+NMSettingHsr:port1, object property in NMSettingOvs
+

+

+

+NMSettingHsr:port2, object property in NMSettingOvs
+

+

+

+NMSettingHsr:prp, object property in NMSettingOvs
+

+

+

 NMSettingInfiniband, struct in NMSettingOvs
 

 

@@ -9304,6 +9464,10 @@ NMSettingWpan:short-address, object property in NMSettingOvs
 
 

 

+NM_SETTING_CONNECTION_CONTROLLER, macro in NMSettingConnection
+

+

+

 NM_SETTING_CONNECTION_DNS_OVER_TLS, macro in NMSettingConnection
 

 

@@ -9336,6 +9500,10 @@ NMSettingWpan:short-address, object property in NMSettingOvs
 
 

 

+nm_setting_connection_get_controller, function in NMSettingConnection
+

+

+

 nm_setting_connection_get_dns_over_tls, function in NMSettingConnection
 

 

@@ -9396,6 +9564,10 @@ NMSettingWpan:short-address, object property in NMSettingOvs
 
 

 

+nm_setting_connection_get_port_type, function in NMSettingConnection
+

+

+

 nm_setting_connection_get_read_only, function in NMSettingConnection
 

 

@@ -9488,6 +9660,10 @@ NMSettingWpan:short-address, object property in NMSettingOvs
 
 

 

+NM_SETTING_CONNECTION_PORT_TYPE, macro in NMSettingConnection
+

+

+

 NM_SETTING_CONNECTION_READ_ONLY, macro in NMSettingConnection
 

 

@@ -9728,6 +9904,14 @@ NMSettingWpan:short-address, object property in NMSettingOvs
 
 

 

+NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_EDNS0, macro in NMSettingIPConfig
+

+

+

+NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_TRUST_AD, macro in NMSettingIPConfig
+

+

+

 NM_SETTING_DNS_OPTION_IP6_BYTESTRING, macro in NMSettingIPConfig
 

 

@@ -10020,6 +10204,46 @@ NMSettingWpan:short-address, object property in NMSettingOvs
 
 

 

+nm_setting_hsr_get_multicast_spec, function in NMSettingHsr
+

+

+

+nm_setting_hsr_get_port1, function in NMSettingHsr
+

+

+

+nm_setting_hsr_get_port2, function in NMSettingHsr
+

+

+

+nm_setting_hsr_get_prp, function in NMSettingHsr
+

+

+

+NM_SETTING_HSR_MULTICAST_SPEC, macro in NMSettingHsr
+

+

+

+nm_setting_hsr_new, function in NMSettingHsr
+

+

+

+NM_SETTING_HSR_PORT1, macro in NMSettingHsr
+

+

+

+NM_SETTING_HSR_PORT2, macro in NMSettingHsr
+

+

+

+NM_SETTING_HSR_PRP, macro in NMSettingHsr
+

+

+

+NM_SETTING_HSR_SETTING_NAME, macro in NMSettingHsr
+

+

+

 nm_setting_infiniband_get_mac_address, function in NMSettingInfiniband
 

 

@@ -14139,6 +14363,10 @@ NMUtilsPredicateStr, user_function in NMSettingOvs
 
 

 

+NM_VERSION_1_46, macro in nm-version-macros
+

+

+

 NM_VERSION_1_6, macro in nm-version-macros
 

 

diff --git a/docs/libnm/html/ch03.html b/docs/libnm/html/ch03.html
index 6428e294..e451a49e 100644
--- a/docs/libnm/html/ch03.html
+++ b/docs/libnm/html/ch03.html
@@ -84,6 +84,9 @@
 NMSettingHostname — Contains properties related to the hostname
 
 

+NMSettingHsr — Describes connection properties for HSR/PRP interfaces
+

+

 NMSettingInfiniband — Describes connection properties for IP-over-InfiniBand networks
 

 

diff --git a/docs/libnm/html/ch04.html b/docs/libnm/html/ch04.html
index b38c0cec..0ad612d9 100644
--- a/docs/libnm/html/ch04.html
+++ b/docs/libnm/html/ch04.html
@@ -51,6 +51,9 @@
 NMDeviceGeneric
 

 

+NMDeviceHsr
+

+

 NMDeviceInfiniband
 

 

diff --git a/docs/libnm/html/index.html b/docs/libnm/html/index.html
index ecb41286..41acbafb 100644
--- a/docs/libnm/html/index.html
+++ b/docs/libnm/html/index.html
@@ -15,7 +15,7 @@
 

 

 

-      for libnm 1.44.2
+      for libnm 1.45.90
 
       The latest version of this documentation can be found on-line at
       https://networkmanager.dev/docs/libnm/latest/.
@@ -30,17 +30,7 @@
 	Invariant Sections, no Front-Cover Texts, and no Back-Cover
 	Texts. You may obtain a copy of the GNU Free
 	Documentation License from the Free Software
-	Foundation by visiting their Web site or by writing
-	to:
-
-	

-


-	  The Free Software Foundation, Inc.,

-	  51 Franklin Street - Fifth Floor,

-	  Boston, MA 02110-1301,

-	  USA

-	

-

+	Foundation by visiting their Web site.
       

 

 

@@ -136,6 +126,9 @@
 NMSettingHostname — Contains properties related to the hostname
 

 

+NMSettingHsr — Describes connection properties for HSR/PRP interfaces
+

+

 NMSettingInfiniband — Describes connection properties for IP-over-InfiniBand networks
 

 

@@ -290,6 +283,9 @@ use WEP, LEAP, WPA or WPA2/RSN security
 NMDeviceGeneric
 

 

+NMDeviceHsr
+

+

 NMDeviceInfiniband
 

 

diff --git a/docs/libnm/html/libnm-nm-dbus-interface.html b/docs/libnm/html/libnm-nm-dbus-interface.html
index 7516f13a..ddb782bc 100644
--- a/docs/libnm/html/libnm-nm-dbus-interface.html
+++ b/docs/libnm/html/libnm-nm-dbus-interface.html
@@ -106,6 +106,10 @@
 
 
 #define
+NM_DBUS_INTERFACE_DEVICE_HSR
+
+
+#define
 NM_DBUS_INTERFACE_DEVICE_INFINIBAND
 
 
@@ -676,6 +680,12 @@
 

 

 

+
NM_DBUS_INTERFACE_DEVICE_HSR

+
#define NM_DBUS_INTERFACE_DEVICE_HSR           NM_DBUS_INTERFACE_DEVICE ".Hsr"
+

+

+

+

 
NM_DBUS_INTERFACE_DEVICE_INFINIBAND

 
#define NM_DBUS_INTERFACE_DEVICE_INFINIBAND    NM_DBUS_INTERFACE_DEVICE ".Infiniband"
 

@@ -1406,6 +1416,13 @@ GSM/UMTS, or LTE network access protocols

 
  
 
+
+
NM_DEVICE_TYPE_HSR

+
+
A HSR/PRP device. Since: 1.46.

+
+ 
+
 
 

 
@@ -1560,6 +1577,13 @@ GSM/UMTS, or LTE network access protocols

  
 
 
+
NM_WIFI_DEVICE_CAP_FREQ_6GHZ

+
+
device supports 6GHz frequencies. Since: 1.46.

+
+ 
+
+
 
NM_WIFI_DEVICE_CAP_MESH

 
 
device supports acting as a mesh point. Since: 1.20.

@@ -3334,7 +3358,7 @@ disconnect any new device appeared after the checkpoint. Since: 1.6.

 
NM_CHECKPOINT_CREATE_FLAG_ALLOW_OVERLAPPING

 
 
by default, creating
-a checkpoint fails if there are already existing checkoints that
+a checkpoint fails if there are already existing checkpoints that
 reference the same devices. With this flag, creation of such
 checkpoints is allowed, however, if an older checkpoint
 that references overlapping devices gets rolled back, it will
diff --git a/docs/libnm/html/libnm-nm-ethtool-utils.html b/docs/libnm/html/libnm-nm-ethtool-utils.html
index 5e731c7c..466236aa 100644
--- a/docs/libnm/html/libnm-nm-ethtool-utils.html
+++ b/docs/libnm/html/libnm-nm-ethtool-utils.html
@@ -387,6 +387,26 @@
 #define
 NM_ETHTOOL_OPTNAME_PAUSE_TX
 
+
+#define
+NM_ETHTOOL_OPTNAME_CHANNELS_RX
+
+
+#define
+NM_ETHTOOL_OPTNAME_CHANNELS_TX
+
+
+#define
+NM_ETHTOOL_OPTNAME_CHANNELS_OTHER
+
+
+#define
+NM_ETHTOOL_OPTNAME_CHANNELS_COMBINED
+
+
+#define
+NM_ETHTOOL_OPTNAME_EEE_ENABLED
+
 
 
 
@@ -917,6 +937,36 @@
 
#define NM_ETHTOOL_OPTNAME_PAUSE_TX      "pause-tx"
 

 
+

+

+
NM_ETHTOOL_OPTNAME_CHANNELS_RX

+
#define NM_ETHTOOL_OPTNAME_CHANNELS_RX       "channels-rx"
+

+

+

+

+
NM_ETHTOOL_OPTNAME_CHANNELS_TX

+
#define NM_ETHTOOL_OPTNAME_CHANNELS_TX       "channels-tx"
+

+

+

+

+
NM_ETHTOOL_OPTNAME_CHANNELS_OTHER

+
#define NM_ETHTOOL_OPTNAME_CHANNELS_OTHER    "channels-other"
+

+

+

+

+
NM_ETHTOOL_OPTNAME_CHANNELS_COMBINED

+
#define NM_ETHTOOL_OPTNAME_CHANNELS_COMBINED "channels-combined"
+

+

+

+

+
NM_ETHTOOL_OPTNAME_EEE_ENABLED

+
#define NM_ETHTOOL_OPTNAME_EEE_ENABLED "eee-enabled"
+

+

 
 
 

diff --git a/docs/libnm/html/libnm-nm-utils.html b/docs/libnm/html/libnm-nm-utils.html
index a4846dcf..7d53938f 100644
--- a/docs/libnm/html/libnm-nm-utils.html
+++ b/docs/libnm/html/libnm-nm-utils.html
@@ -716,10 +716,16 @@ number of known SSID-cloaking methods.

 
const char *
 nm_utils_escape_ssid (const guint8 *ssid,
                       gsize len);

+

+
nm_utils_escape_ssid has been deprecated since version 1.46 and should not be used in newly-written code.

+
use nm_utils_ssid_to_utf8() or nm_utils_bin2hexstr().

+

 
This function does a quick printable character conversion of the SSID, simply
 replacing embedded NULLs and non-printable characters with the hexadecimal
 representation of that character.  Intended for debugging only, should not
 be used for display of SSIDs.

+
Warning: this function uses a static buffer. It is not thread-safe. Don't
+  use this function.

 

 
Parameters

 

@@ -1118,6 +1124,8 @@ type 'au' representing an array of IPv4 addresses.

 nm_utils_ip4_dns_from_variant (GVariant *value);
Utility function to convert a GVariant of type 'au' representing a list of
 IPv4 addresses into an array of IP address strings.

+
Since 1.46, an empty list is returned if the variant type is not valid
+(before it was checked as assertion)

 
Parameters

 

 
 

@@ -1191,7 +1199,10 @@ NetworkManager IPv4 addresses (which are tuples of address, prefix, and
 gateway) into a GPtrArray of NMIPAddress objects. The "gateway" field of
 the first address (if set) will be returned in out_gateway
 ; the "gateway" fields
-of the other addresses are ignored.

+of the other addresses are ignored. Note that invalid addresses are discarded
+but the valid addresses are still returned.

+
Since 1.46, an empty list is returned if the variant type is not valid
+(before it was checked as assertion)

 
Parameters

 

 

@@ -1260,7 +1271,10 @@ metric).

 nm_utils_ip4_routes_from_variant (GVariant *value);
Utility function to convert a GVariant of type 'aau' representing an array
 of NetworkManager IPv4 routes (which are tuples of route, prefix, next hop,
-and metric) into a GPtrArray of NMIPRoute objects.

+and metric) into a GPtrArray of NMIPRoute objects. Note that invalid routes
+are discarded but the valid routes are still returned.

+
Since 1.46, an empty list is returned if the variant type is not valid
+(before it was checked as assertion)

 
Parameters

 

 
 

@@ -1407,6 +1421,8 @@ nm_utils_ip6_dns_from_variant (
+
Since 1.46, an empty list is returned if the variant type is not valid
+(before it was checked as assertion)

 

 
Parameters

 

@@ -1481,7 +1497,10 @@ list of NetworkManager IPv6 addresses (which are tuples of address, prefix,
 and gateway) into a GPtrArray of NMIPAddress objects. The "gateway" field
 of the first address (if set) will be returned in out_gateway
 ; the "gateway"
-fields of the other addresses are ignored.

+fields of the other addresses are ignored. Note that invalid addresses are
+discarded but the valid addresses are still returned.

+
Since 1.46, an empty list is returned if the variant type is not valid
+(before it was checked as assertion)

 

 
Parameters

 

@@ -1550,7 +1569,10 @@ metric).

 nm_utils_ip6_routes_from_variant (GVariant *value);
 
Utility function to convert a GVariant of type 'a(ayuayu)' representing an
 array of NetworkManager IPv6 routes (which are tuples of route, prefix, next
-hop, and metric) into a GPtrArray of NMIPRoute objects.

+hop, and metric) into a GPtrArray of NMIPRoute objects. Note that invalid
+routes are ignored but the valid ones are still returned.

+
Since 1.46, an empty list is returned if the variant type is not valid
+(before it was checked as assertion)

 

 
Parameters

 

@@ -1615,7 +1637,10 @@ nm_utils_ip_addresses_from_variant (GVariant representing a list of new-style
 NetworkManager IPv4 or IPv6 addresses (as described in the documentation for
 nm_utils_ip_addresses_to_variant()) into a GPtrArray of NMIPAddress
-objects.

+objects. Note that invalid addresses are discarded but the valid addresses
+are still returned.

+
Since 1.46, an empty list is returned if the variant type is not valid
+(before it was checked as assertion)

 

 
Parameters

 

@@ -1653,8 +1678,11 @@ objects.

 nm_utils_ip_routes_to_variant (GPtrArray *routes);
 
Utility function to convert a GPtrArray of NMIPRoute objects representing
 IPv4 or IPv6 routes into a GVariant of type 'aa{sv}' representing an array
-of new-style NetworkManager IP routes (which are tuples of destination,
-prefix, next hop, metric, and additional attributes).

+of new-style NetworkManager IP routes. All routes will include "dest" (an IP
+address string), "prefix" (an uint) and optionally "next-hop" (an IP address
+string) and "metric" (an uint). Some routes may include additional attributes.
+Note that invalid routes are discarded and only a warning is emitted, but the
+valid routes are still returned.

 

 
Parameters

 

@@ -1685,9 +1713,11 @@ prefix, next hop, metric, and additional attributes).

 nm_utils_ip_routes_from_variant (GVariant *value,
                                  int family);
 
Utility function to convert a GVariant representing a list of new-style
-NetworkManager IPv4 or IPv6 addresses (which are tuples of destination,
-prefix, next hop, metric, and additional attributes) into a GPtrArray of
-NMIPRoute objects.

+NetworkManager IPv4 or IPv6 addresses (as described in the documentation for
+nm_utils_ip_routes_to_variant()) into a GPtrArray of NMIPRoute objects.
+Invalid routes are discarded but the valid routes are still returned.

+
Since 1.46, an empty list is returned if the variant type is not valid
+(before it was checked as assertion)

 

 
Parameters

 

diff --git a/docs/libnm/html/libnm-nm-version-macros.html b/docs/libnm/html/libnm-nm-version-macros.html
index 07492f59..2055eb48 100644
--- a/docs/libnm/html/libnm-nm-version-macros.html
+++ b/docs/libnm/html/libnm-nm-version-macros.html
@@ -176,6 +176,10 @@
 
 
+
+
+
+
@@ -253,7 +257,7 @@ is compiled against.

 

 

 
NM_MINOR_VERSION

-
#define NM_MINOR_VERSION (44)
+
#define NM_MINOR_VERSION (45)
 

 
Evaluates to the minor version number of NetworkManager which this source
 is compiled against.

@@ -261,7 +265,7 @@ is compiled against.

 

 

 
NM_MICRO_VERSION

-
#define NM_MICRO_VERSION (2)
+
#define NM_MICRO_VERSION (90)
 

 
Evaluates to the micro version number of NetworkManager which this source
 compiled against.

@@ -418,6 +422,12 @@ compiled against.

 

 

 

+
NM_VERSION_1_46

+
#define NM_VERSION_1_46   (NM_ENCODE_VERSION(1, 46, 0))
+

+

+

+

 
NM_API_VERSION

 
#define             NM_API_VERSION

 

diff --git a/docs/libnm/html/libnm-nm-version.html b/docs/libnm/html/libnm-nm-version.html
index 41e099a7..75b3a322 100644
--- a/docs/libnm/html/libnm-nm-version.html
+++ b/docs/libnm/html/libnm-nm-version.html
@@ -183,6 +183,12 @@
 NM_DEPRECATED_IN_1_44_FOR()
 
 

+
+
+
+

 #defineNM_VERSION_1_46
#define
 NM_API_VERSION
 

 
#define
+NM_DEPRECATED_IN_1_46_FOR()
+

 
 

 

@@ -394,6 +400,14 @@
 #define
 NM_AVAILABLE_IN_1_44
 
+
+#define
+NM_DEPRECATED_IN_1_46
+
+
+#define
+NM_AVAILABLE_IN_1_46
+
 
 

 
@@ -544,6 +558,12 @@
 
#define NM_DEPRECATED_IN_1_44_FOR(f) G_DEPRECATED_FOR(f)
 

 
+

+

+
NM_DEPRECATED_IN_1_46_FOR()

+
#define NM_DEPRECATED_IN_1_46_FOR(f) G_DEPRECATED_FOR(f)
+

+

 
 

 
Types and Values

@@ -844,6 +864,18 @@
 
#define NM_AVAILABLE_IN_1_44 G_UNAVAILABLE(1, 44)
 

 

+

+

+
NM_DEPRECATED_IN_1_46

+
#define NM_DEPRECATED_IN_1_46        G_DEPRECATED
+

+

+

+

+
NM_AVAILABLE_IN_1_46

+
#define NM_AVAILABLE_IN_1_46 G_UNAVAILABLE(1, 46)
+

+

 
 
 

diff --git a/docs/libnm/html/libnm.devhelp2 b/docs/libnm/html/libnm.devhelp2
index 99b33593..05f39c05 100644
--- a/docs/libnm/html/libnm.devhelp2
+++ b/docs/libnm/html/libnm.devhelp2
@@ -34,6 +34,7 @@
       
       
       
+      
       
       
       
@@ -85,6 +86,7 @@
       
       
       
+      
       
       
       
@@ -411,6 +413,7 @@
     
     
     
+    
     
     
     
@@ -749,9 +752,11 @@
     
     
     
-    
-    
-    
+    
+    
+    
+    
+    
     
     
     
@@ -787,7 +792,9 @@
     
     
     
+    
     
+    
     
     
     
@@ -1184,6 +1191,8 @@
     
     
     
+    
+    
     
     
     
@@ -1236,6 +1245,16 @@
     
     
     
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
     
     
     
@@ -1464,6 +1483,8 @@
     
     
     
+    
+    
     
     
     
@@ -2506,6 +2527,22 @@
     
     
     
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
     
     
     
@@ -2523,6 +2560,7 @@
     
     
     
+    
     
     
     
@@ -2535,11 +2573,13 @@
     
     
     
+    
     
     
     
     
     
+    
     
     
     
@@ -2907,6 +2947,7 @@
     
     
     
+    
     
     
     
@@ -2919,8 +2960,10 @@
     
     
     
+    
     
     
+    
     
     
     
@@ -3032,7 +3075,7 @@
     
     
     
-    
+    
     
     
     
@@ -3199,6 +3242,11 @@
     
     
     
+    
+    
+    
+    
+    
     
     
     
@@ -3223,6 +3271,7 @@
     
     
     
+    
     
     
     
@@ -3273,6 +3322,8 @@
     
     
     
+    
+    
     
     
     
@@ -3303,6 +3354,7 @@
     
     
     
+    
     
     
     
@@ -3544,6 +3596,7 @@
     
     
     
+    
     
     
     
@@ -3561,6 +3614,7 @@
     
     
     
+    
     
     
     
diff --git a/docs/libnm/html/license.html b/docs/libnm/html/license.html
index 207a9d49..78cee885 100644
--- a/docs/libnm/html/license.html
+++ b/docs/libnm/html/license.html
@@ -38,15 +38,7 @@
 

       You should have received a copy of the GNU
       Lesser General Public License along with this
-      library; if not, write to the
-      

-


-        Free Software Foundation, Inc.,

-        51 Franklin Street - Fifth Floor,

-        Boston, MA 02110-1301,

-        USA

-      

-

+      library.
     

 

       A copy of the GNU Lesser General Public License
diff --git a/docs/libnm/html/object-tree.html b/docs/libnm/html/object-tree.html
index a6b63718..60ccc96c 100644
--- a/docs/libnm/html/object-tree.html
+++ b/docs/libnm/html/object-tree.html
@@ -39,6 +39,7 @@
     │   │   ├── NMDeviceEthernet
     │   │   │   ╰── NMDeviceVeth
     │   │   ├── NMDeviceGeneric
+    │   │   ├── NMDeviceHsr
     │   │   ├── NMDeviceInfiniband
     │   │   ├── NMDeviceIPTunnel
     │   │   ├── NMDeviceLoopback
@@ -84,6 +85,7 @@
     │   ├── NMSettingGeneric
     │   ├── NMSettingGsm
     │   ├── NMSettingHostname
+    │   ├── NMSettingHsr
     │   ├── NMSettingInfiniband
     │   ├── NMSettingIPConfig
     │   │   ├── NMSettingIP4Config
diff --git a/docs/libnm/html/usage.html b/docs/libnm/html/usage.html
index 48daca1d..52d131d3 100644
--- a/docs/libnm/html/usage.html
+++ b/docs/libnm/html/usage.html
@@ -96,7 +96,7 @@
         

 
$ cc $(pkg-config --libs --cflags libnm) -o hello-nm hello-nm.c
   $ ./hello-nm
-  NetworkManager version: 1.44.2
+  NetworkManager version: 1.45.90
 
   $ 

 

diff --git a/docs/libnm/libnm-docs.xml b/docs/libnm/libnm-docs.xml
index 09468a5c..f2b5658c 100644
--- a/docs/libnm/libnm-docs.xml
+++ b/docs/libnm/libnm-docs.xml
@@ -34,15 +34,7 @@
 	Texts. You may obtain a copy of the GNU Free
 	Documentation License from the Free Software
 	Foundation by visiting their Web site or by writing
-	to:
-
-	

-	  The Free Software Foundation, Inc.,
-	  51 Franklin Street - Fifth Floor,
-	  Boston, MA 02110-1301,
-	  USA
-	

+	url="http://www.fsf.org">their Web site.
       
     
   
@@ -327,6 +319,7 @@ print ("NetworkManager version " + client.get_version())]]>
     
     
+    
     
     
     
@@ -382,6 +375,7 @@ print ("NetworkManager version " + client.get_version())]]>
     
     
+    
     
     
     
@@ -467,13 +461,7 @@ print ("NetworkManager version " + client.get_version())]]>
       You should have received a copy of the GNU
       Lesser General Public License along with this
-      library; if not, write to the
-      

-        Free Software Foundation, Inc.,
-        51 Franklin Street - Fifth Floor,
-        Boston, MA 02110-1301,
-        USA
-      

+      library.
     
 
     
diff --git a/docs/libnm/libnm-sections.txt b/docs/libnm/libnm-sections.txt
index b2797a93..b54bc9c3 100644
--- a/docs/libnm/libnm-sections.txt
+++ b/docs/libnm/libnm-sections.txt
@@ -16,6 +16,7 @@ NM_ACCESS_POINT_MODE
 NM_ACCESS_POINT_MAX_BITRATE
 NM_ACCESS_POINT_STRENGTH
 NM_ACCESS_POINT_LAST_SEEN
+NM_ACCESS_POINT_BANDWIDTH
 NM_ACCESS_POINT_HW_ADDRESS
 nm_access_point_get_flags
 nm_access_point_get_wpa_flags
@@ -27,6 +28,7 @@ nm_access_point_get_mode
 nm_access_point_get_max_bitrate
 nm_access_point_get_strength
 nm_access_point_get_last_seen
+nm_access_point_get_bandwidth
 nm_access_point_filter_connections
 nm_access_point_connection_valid
 NMAccessPoint
@@ -573,6 +575,7 @@ NMSettingEthtool
 NMSettingGeneric
 NMSettingGsm
 NMSettingHostname
+NMSettingHsr
 NMSettingIP4Config
 NMSettingIP6Config
 NMSettingIPConfig
@@ -634,6 +637,7 @@ NM_DBUS_INTERFACE_DEVICE_BRIDGE
 NM_DBUS_INTERFACE_DEVICE_DUMMY
 NM_DBUS_INTERFACE_DEVICE_GENERIC
 NM_DBUS_INTERFACE_DEVICE_GRE
+NM_DBUS_INTERFACE_DEVICE_HSR
 NM_DBUS_INTERFACE_DEVICE_INFINIBAND
 NM_DBUS_INTERFACE_DEVICE_IP_TUNNEL
 NM_DBUS_INTERFACE_DEVICE_LOOPBACK
@@ -1012,6 +1016,31 @@ NM_TYPE_DEVICE_GENERIC
 nm_device_generic_get_type
 
 
+

+nm-device-hsr
+NMDeviceHsr
+NM_DEVICE_HSR_PORT1
+NM_DEVICE_HSR_PORT2
+NM_DEVICE_HSR_SUPERVISION_ADDRESS
+NM_DEVICE_HSR_MULTICAST_SPEC
+NM_DEVICE_HSR_PRP
+nm_device_hsr_get_port1
+nm_device_hsr_get_port2
+nm_device_hsr_get_supervision_address
+nm_device_hsr_get_multicast_spec
+nm_device_hsr_get_prp
+NMDeviceHsr
+
+NMDeviceHsrClass
+NM_DEVICE_HSR
+NM_DEVICE_HSR_CLASS
+NM_DEVICE_HSR_GET_CLASS
+NM_IS_DEVICE_HSR
+NM_IS_DEVICE_HSR_CLASS
+NM_TYPE_DEVICE_HSR
+nm_device_hsr_get_type
+

+
 

 nm-device-infiniband
 NMDeviceInfiniband
@@ -1045,6 +1074,7 @@ NM_DEVICE_IP_TUNNEL_INPUT_KEY
 NM_DEVICE_IP_TUNNEL_OUTPUT_KEY
 NM_DEVICE_IP_TUNNEL_ENCAPSULATION_LIMIT
 NM_DEVICE_IP_TUNNEL_FLOW_LABEL
+NM_DEVICE_IP_TUNNEL_FWMARK
 NM_DEVICE_IP_TUNNEL_FLAGS
 nm_device_ip_tunnel_get_parent
 nm_device_ip_tunnel_get_mode
@@ -1057,6 +1087,7 @@ nm_device_ip_tunnel_get_input_key
 nm_device_ip_tunnel_get_output_key
 nm_device_ip_tunnel_get_encapsulation_limit
 nm_device_ip_tunnel_get_flow_label
+nm_device_ip_tunnel_get_fwmark
 nm_device_ip_tunnel_get_flags
 NMDeviceIPTunnel
 
@@ -1699,6 +1730,11 @@ NM_ETHTOOL_OPTNAME_RING_TX
 NM_ETHTOOL_OPTNAME_PAUSE_AUTONEG
 NM_ETHTOOL_OPTNAME_PAUSE_RX
 NM_ETHTOOL_OPTNAME_PAUSE_TX
+NM_ETHTOOL_OPTNAME_CHANNELS_RX
+NM_ETHTOOL_OPTNAME_CHANNELS_TX
+NM_ETHTOOL_OPTNAME_CHANNELS_OTHER
+NM_ETHTOOL_OPTNAME_CHANNELS_COMBINED
+NM_ETHTOOL_OPTNAME_EEE_ENABLED
 

 
 

@@ -2379,7 +2415,9 @@ NM_SETTING_CONNECTION_READ_ONLY
 NM_SETTING_CONNECTION_PERMISSIONS
 NM_SETTING_CONNECTION_ZONE
 NM_SETTING_CONNECTION_MASTER
+NM_SETTING_CONNECTION_CONTROLLER
 NM_SETTING_CONNECTION_SLAVE_TYPE
+NM_SETTING_CONNECTION_PORT_TYPE
 NM_SETTING_CONNECTION_AUTOCONNECT_SLAVES
 NM_SETTING_CONNECTION_SECONDARIES
 NM_SETTING_CONNECTION_GATEWAY_PING_TIMEOUT
@@ -2418,8 +2456,10 @@ nm_setting_connection_add_permission
 nm_setting_connection_remove_permission
 nm_setting_connection_remove_permission_by_value
 nm_setting_connection_get_master
+nm_setting_connection_get_controller
 nm_setting_connection_is_slave_type
 nm_setting_connection_get_slave_type
+nm_setting_connection_get_port_type
 nm_setting_connection_get_autoconnect_slaves
 nm_setting_connection_get_num_secondaries
 nm_setting_connection_get_secondary
@@ -2526,6 +2566,8 @@ nm_ethtool_optname_is_feature
 nm_ethtool_optname_is_coalesce
 nm_ethtool_optname_is_ring
 nm_ethtool_optname_is_pause
+nm_ethtool_optname_is_channels
+nm_ethtool_optname_is_eee
 NM_SETTING_ETHTOOL_SETTING_NAME
 nm_setting_ethtool_new
 nm_setting_ethtool_get_optnames
@@ -2631,6 +2673,29 @@ NM_TYPE_SETTING_HOSTNAME
 nm_setting_hostname_get_type
 

 
+

+nm-setting-hsr
+NMSettingHsr
+NM_SETTING_HSR_SETTING_NAME
+NM_SETTING_HSR_PORT1
+NM_SETTING_HSR_PORT2
+NM_SETTING_HSR_MULTICAST_SPEC
+NM_SETTING_HSR_PRP
+nm_setting_hsr_new
+nm_setting_hsr_get_port1
+nm_setting_hsr_get_port2
+nm_setting_hsr_get_multicast_spec
+nm_setting_hsr_get_prp
+
+NMSettingHsrClass
+NM_IS_SETTING_HSR
+NM_IS_SETTING_HSR_CLASS
+NM_SETTING_HSR
+NM_SETTING_HSR_GET_CLASS
+NM_TYPE_SETTING_HSR
+nm_setting_hsr_get_type
+

+
 

 nm-setting-infiniband
 NMSettingInfiniband
@@ -2818,6 +2883,8 @@ NM_SETTING_DNS_OPTION_USE_VC
 NM_SETTING_DNS_OPTION_NO_RELOAD
 NM_SETTING_DNS_OPTION_TRUST_AD
 NM_SETTING_DNS_OPTION_NO_AAAA
+NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_EDNS0
+NM_SETTING_DNS_OPTION_INTERNAL_NO_ADD_TRUST_AD
 NMDhcpHostnameFlags
 nm_setting_ip_config_get_method
 nm_setting_ip_config_get_num_dns
@@ -4465,6 +4532,9 @@ NM_AVAILABLE_IN_1_42
 NM_DEPRECATED_IN_1_44
 NM_DEPRECATED_IN_1_44_FOR
 NM_AVAILABLE_IN_1_44
+NM_DEPRECATED_IN_1_46
+NM_DEPRECATED_IN_1_46_FOR
+NM_AVAILABLE_IN_1_46
 

 
 

@@ -4499,6 +4569,7 @@ NM_VERSION_1_38
 NM_VERSION_1_40
 NM_VERSION_1_42
 NM_VERSION_1_44
+NM_VERSION_1_46
 NM_API_VERSION
 NM_VERSION_CUR_STABLE
 NM_VERSION_NEXT_STABLE
diff --git a/docs/libnm/libnm.types b/docs/libnm/libnm.types
index 6c83a5ad..f7e744c8 100644
--- a/docs/libnm/libnm.types
+++ b/docs/libnm/libnm.types
@@ -34,6 +34,7 @@ nm_device_error_get_type
 nm_device_ethernet_get_type
 nm_device_generic_get_type
 nm_device_get_type
+nm_device_hsr_get_type
 nm_device_infiniband_get_type
 nm_device_interface_flags_get_type
 nm_device_ip_tunnel_get_type
@@ -118,6 +119,7 @@ nm_setting_generic_get_type
 nm_setting_get_type
 nm_setting_gsm_get_type
 nm_setting_hostname_get_type
+nm_setting_hsr_get_type
 nm_setting_infiniband_get_type
 nm_setting_ip4_config_get_type
 nm_setting_ip4_link_local_get_type
diff --git a/docs/libnm/meson.build b/docs/libnm/meson.build
index 01c9b669..faac586d 100644
--- a/docs/libnm/meson.build
+++ b/docs/libnm/meson.build
@@ -15,7 +15,6 @@ private_headers = [
 
   'nm-connection-private.h',
   'nm-default-libnm-core.h',
-  'nm-property-compare.h',
   'nm-setting-private.h',
   'nm-team-utils.h',
   'nm-utils-private.h',
@@ -27,7 +26,7 @@ private_headers = [
 scan_args = [
   '--rebuild-types',
   '--rebuild-sections',
-  '--ignore-decorators=NM_AVAILABLE_IN_\d+_\d+|NM_DEPRECATED_IN_\d+_\d+|NM_DEPRECATED_IN_\d+_\d+_FOR\(\)',
+  '--ignore-decorators=NM_AVAILABLE_IN_[0-9]+_[0-9]+|NM_DEPRECATED_IN_[0-9]+_[0-9]+|NM_DEPRECATED_IN_[0-9]+_[0-9]+_FOR[(][)]',
   '--ignore-headers=' + ' '.join(private_headers),
 ]
 
@@ -43,6 +42,8 @@ gnome.gtkdoc(
   src_dir: [
     libnm_core_public_inc,
     libnm_client_public_inc,
+    libnm_core_impl_inc,
+    libnm_client_impl_inc
   ],
   dependencies: libnm_dep,
   scan_args: scan_args,
diff --git a/docs/libnm/version.xml b/docs/libnm/version.xml
index 00aecdb4..8ce2f7ea 100644
--- a/docs/libnm/version.xml
+++ b/docs/libnm/version.xml
@@ -1 +1 @@
-1.44.2
+1.45.90
diff --git a/examples/python/gi/gmaincontext.py b/examples/python/gi/gmaincontext.py
index 64a5620b..25283f18 100755
--- a/examples/python/gi/gmaincontext.py
+++ b/examples/python/gi/gmaincontext.py
@@ -71,6 +71,7 @@ def error_is_cancelled(e):
 
 ###############################################################################
 
+
 # A Context manager for running a mainloop. Of course, this does
 # not do anything magically. You can run the context/mainloop without
 # this context object.
@@ -265,7 +266,6 @@ def create_nmc(dbus_connection):
 
 
 def make_call(nmc):
-
     log("[make_call]: make some async D-Bus call")
 
     if not nmc:
@@ -273,7 +273,6 @@ def make_call(nmc):
         return
 
     with MainLoopRun("make_call", nmc.get_main_context(), 1) as r:
-
         # There are two reasons why async operations are preferable with
         # D-Bus and libnm:
         #
@@ -405,7 +404,6 @@ def destroy_nmc(nmc_holder, destroy_mode):
             raise Exception("Failure to destroy NMClient: something keeps it alive")
 
     else:
-
         if destroy_mode == 1:
             ctx = GLib.MainContext.default()
         else:
diff --git a/examples/python/gi/nm-add-connection2.py b/examples/python/gi/nm-add-connection2.py
index 2cd760a2..7ac95c6d 100755
--- a/examples/python/gi/nm-add-connection2.py
+++ b/examples/python/gi/nm-add-connection2.py
@@ -49,7 +49,6 @@ def die(msg, print_usage=False):
 
 
 def main():
-
     main_loop = GLib.MainLoop()
 
     nm_client = NM.Client.new(None)
diff --git a/examples/python/gi/nm-up-many.py b/examples/python/gi/nm-up-many.py
index e5faad19..3bca3e5a 100755
--- a/examples/python/gi/nm-up-many.py
+++ b/examples/python/gi/nm-up-many.py
@@ -51,7 +51,6 @@ def nmc_new(io_priority=GLib.PRIORITY_DEFAULT, cancellable=None):
     result = []
 
     def cb(source_object, res):
-
         try:
             source_object.init_finish(res)
         except Exception as e:
@@ -73,7 +72,6 @@ def nmc_new(io_priority=GLib.PRIORITY_DEFAULT, cancellable=None):
 
 
 def nmc_destroy(nmc_transfer_ref):
-
     # Just for fun, show how to completely cleanup a NMClient instance.
     # An NMClient instance registers D-Bus signals and unrefing the instance
     # will cancel/unsubscribe those signals, but there might still be some
@@ -106,7 +104,6 @@ def nmc_destroy(nmc_transfer_ref):
 
 
 def find_connections(nmc, argv):
-
     # parse the inpurt argv and select the connection profiles to activate.
     # The arguments are either "connection.id" or "connection.uuid", possibly
     # qualified by "id" or "uuid".
@@ -173,7 +170,6 @@ class Activation(object):
         return "%s (%s)" % (self.con.get_id(), self.con.get_uuid())
 
     def is_done(self, log=log):
-
         if self.state == Activation.ACTIVATION_STATE_DONE:
             return True
 
@@ -206,7 +202,6 @@ class Activation(object):
         return False
 
     def start(self, nmc, cancellable=None, activated_callback=None, log=log):
-
         # Call nmc.activate_connection_async() and return a user data
         # with the information about the pending operation.
 
@@ -242,7 +237,6 @@ class Activation(object):
         )
 
     def wait(self, done_callback=None, log=log):
-
         assert self.state == Activation.ACTIVATION_STATE_WAITING
         assert self.result_ac
         assert self.wait_id is None
@@ -259,7 +253,6 @@ class Activation(object):
 
 class Manager(object):
     def __init__(self, nmc, cons):
-
         self.nmc = nmc
 
         self.ac_start = [Activation(c) for c in cons]
@@ -268,7 +261,6 @@ class Manager(object):
         self.ac_done = []
 
     def _log(self, msg):
-
         lists = [self.ac_start, self.ac_starting, self.ac_waiting, self.ac_done]
 
         n = sum(len(l) for l in lists)
@@ -278,11 +270,9 @@ class Manager(object):
         log("%s: %s" % (prefix, msg))
 
     def ac_run(self):
-
         loop = GLib.MainLoop(self.nmc.get_main_context())
 
         while self.ac_start or self.ac_starting or self.ac_waiting:
-
             rate_limit_parallel_in_progress = (
                 len(self.ac_starting) + len(self.ac_waiting) >= NUM_PARALLEL_IN_PROGRESS
             )
diff --git a/examples/python/gi/nm-update2.py b/examples/python/gi/nm-update2.py
index 9d272ead..87dd6fb1 100755
--- a/examples/python/gi/nm-update2.py
+++ b/examples/python/gi/nm-update2.py
@@ -52,7 +52,6 @@ def die(msg, print_usage=False):
 
 
 def main():
-
     main_loop = GLib.MainLoop()
 
     nm_client = NM.Client.new(None)
diff --git a/examples/python/gi/nm-wg-set b/examples/python/gi/nm-wg-set
index 4d162570..dd7e81f7 100755
--- a/examples/python/gi/nm-wg-set
+++ b/examples/python/gi/nm-wg-set
@@ -146,7 +146,6 @@ def print_hint(nm_client):
 
 
 def argv_get_one(argv, idx, type_ctor=None, topic=None):
-
     if topic is not None:
         try:
             v = argv_get_one(argv, idx, type_ctor, None)
@@ -479,7 +478,6 @@ def do_set(nm_client, conn, argv):
 ###############################################################################
 
 if __name__ == "__main__":
-
     nm_client = NM.Client.new(None)
 
     argv = sys.argv
diff --git a/examples/python/gi/ovs-external-ids.py b/examples/python/gi/ovs-external-ids.py
index 0a03c9c5..b33b4581 100755
--- a/examples/python/gi/ovs-external-ids.py
+++ b/examples/python/gi/ovs-external-ids.py
@@ -111,7 +111,6 @@ def mainloop_run(timeout_msec=0, mainloop=None):
 
 
 def connection_update2(remote_connection, connection):
-
     mainloop = GLib.MainLoop()
     result_error = []
 
@@ -160,7 +159,6 @@ def device_get_applied_connection(device):
 
 
 def device_reapply(device, connection, version_id):
-
     mainloop = GLib.MainLoop()
     result_error = []
 
@@ -443,7 +441,6 @@ def connection_print(connection, mode, ids_arg, dbus_path, prefix=""):
         _print("%s   %s" % (prefix, dbus_path))
 
     for data_type in [DataTypeE, DataTypeO]:
-
         if data_type.setting_type is None:
             continue
 
@@ -465,7 +462,6 @@ def connection_print(connection, mode, ids_arg, dbus_path, prefix=""):
 
 
 def sett_update(connection, ids_arg):
-
     for d in ids_arg:
         op = d[0][0]
         key = d[0][1:]
@@ -554,7 +550,6 @@ def do_get(connections, ids_arg):
 
 
 def do_set(nmc, connection, ids_arg, do_test):
-
     remote_connection = connection
     connection = NM.SimpleConnection.new_clone(remote_connection)
 
@@ -611,7 +606,6 @@ def do_set(nmc, connection, ids_arg, do_test):
 
 
 def do_apply(nmc, device, ids_arg, do_test):
-
     try:
         connection_orig, version_id = device_get_applied_connection(device)
     except Exception as e:
@@ -677,13 +671,11 @@ def do_apply(nmc, device, ids_arg, do_test):
 ###############################################################################
 
 if __name__ == "__main__":
-
     args = parse_args(sys.argv)
 
     nmc = NM.Client.new(None)
 
     if args["mode"] == MODE_APPLY:
-
         devices = devices_filter(nmc.get_devices(), args["select_arg"])
 
         if len(devices) != 1:
@@ -695,7 +687,6 @@ if __name__ == "__main__":
         do_apply(nmc, devices[0], args["ids_arg"], do_test=args["do_test"])
 
     else:
-
         connections = connections_filter(nmc.get_connections(), args["select_arg"])
 
         if args["mode"] == MODE_SET:
diff --git a/introspection/meson.build b/introspection/meson.build
index 9a355488..77479277 100644
--- a/introspection/meson.build
+++ b/introspection/meson.build
@@ -15,6 +15,7 @@ ifaces = [
   'org.freedesktop.NetworkManager.Device.Bridge',
   'org.freedesktop.NetworkManager.Device.Dummy',
   'org.freedesktop.NetworkManager.Device.Generic',
+  'org.freedesktop.NetworkManager.Device.Hsr',
   'org.freedesktop.NetworkManager.Device.IPTunnel',
   'org.freedesktop.NetworkManager.Device.Infiniband',
   'org.freedesktop.NetworkManager.Device.Loopback',
diff --git a/introspection/org.freedesktop.NetworkManager.AccessPoint.xml b/introspection/org.freedesktop.NetworkManager.AccessPoint.xml
index 7340bda3..287bfaa9 100644
--- a/introspection/org.freedesktop.NetworkManager.AccessPoint.xml
+++ b/introspection/org.freedesktop.NetworkManager.AccessPoint.xml
@@ -79,6 +79,13 @@
     -->
     
 
+    
+    
+
     
+  
+
+    
+    
+
+    
+    
+
+    
+    
+
+    
+    
+
+    
+    
+
+  
+
diff --git a/introspection/org.freedesktop.NetworkManager.IP4Config.xml b/introspection/org.freedesktop.NetworkManager.IP4Config.xml
index f6e18b76..cc72e2c7 100644
--- a/introspection/org.freedesktop.NetworkManager.IP4Config.xml
+++ b/introspection/org.freedesktop.NetworkManager.IP4Config.xml
@@ -12,7 +12,9 @@
 
         Array of arrays of IPv4 address/prefix/gateway. All 3 elements of each
         array are in network byte order. Essentially: [(addr, prefix, gateway),
-        (addr, prefix, gateway), ...] Deprecated: use AddressData and Gateway
+        (addr, prefix, gateway), ...].
+
+        DEPRECATED: use AddressData and Gateway
     -->
     
 
@@ -39,7 +41,9 @@
         are in network byte order. 'route' and 'next hop' are IPv4 addresses,
         while prefix and metric are simple unsigned integers. Essentially:
         [(route, prefix, next-hop, metric), (route, prefix, next-hop, metric),
-        ...] Deprecated: use RouteData
+        ...].
+
+        DEPRECATED: use RouteData
     -->
     
 
@@ -55,7 +59,9 @@
     
     
 
@@ -101,7 +107,9 @@
         WinsServers:
 
         The Windows Internet Name Service servers associated with the connection.
-        Each address is in network byte order. Deprecated: use WinsServerData
+        Each address is in network byte order.
+
+        DEPRECATED: use WinsServerData
     -->
     
 
diff --git a/introspection/org.freedesktop.NetworkManager.IP6Config.xml b/introspection/org.freedesktop.NetworkManager.IP6Config.xml
index e47b35f2..3991f6ae 100644
--- a/introspection/org.freedesktop.NetworkManager.IP6Config.xml
+++ b/introspection/org.freedesktop.NetworkManager.IP6Config.xml
@@ -10,8 +10,9 @@
     
     
 
@@ -34,7 +35,9 @@
     
     
 
diff --git a/m4/attributes.m4 b/m4/attributes.m4
index 51ac88be..7f785afa 100644
--- a/m4/attributes.m4
+++ b/m4/attributes.m4
@@ -14,9 +14,7 @@ dnl MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 dnl GNU General Public License for more details.
 dnl
 dnl You should have received a copy of the GNU General Public License
-dnl along with this program; if not, write to the Free Software
-dnl Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
-dnl 02110-1301, USA.
+dnl along with this program.
 dnl
 dnl As a special exception, the copyright owners of the
 dnl macro gives unlimited permission to copy, distribute and modify the
diff --git a/m4/vapigen.m4 b/m4/vapigen.m4
index 3ade411e..a2055fe1 100644
--- a/m4/vapigen.m4
+++ b/m4/vapigen.m4
@@ -13,8 +13,7 @@ dnl MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 dnl Lesser General Public License for more details.
 dnl
 dnl You should have received a copy of the GNU Lesser General Public
-dnl License along with this library; if not, write to the Free Software
-dnl Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301  USA
+dnl License along with this library.
 
 # VAPIGEN_CHECK([VERSION], [API_VERSION], [FOUND-INTROSPECTION])
 # --------------------------------------
diff --git a/man/NetworkManager-dispatcher.8 b/man/NetworkManager-dispatcher.8
index 1c64fa85..ad442441 100644
--- a/man/NetworkManager-dispatcher.8
+++ b/man/NetworkManager-dispatcher.8
@@ -2,9 +2,9 @@
 .\"     Title: NetworkManager-dispatcher
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Network management daemons
-.\"    Source: NetworkManager-dispatcher 1.44.2
+.\"    Source: NetworkManager-dispatcher 1.45.90
 .\"  Language: English
 .\"
 .TH "NETWORKMANAGER\-DISPATCHER" "8" "" "NetworkManager\-dispatcher 1\&" "Network management daemons"
@@ -43,9 +43,10 @@ directory or subdirectories in alphabetical order in response to network events\
 Each script receives two arguments, the first being the interface name of the device an operation just happened on, and second the action\&. For device actions, the interface is the name of the kernel interface suitable for IP configuration\&. Thus it is either VPN_IP_IFACE, DEVICE_IP_IFACE, or DEVICE_IFACE, as applicable\&. For the
 \fIhostname\fR
 action the device name is always
-"none"
-and for
+"none"\&. For
 \fIconnectivity\-change\fR
+and
+\fIdns\-change\fR
 it is empty\&.
 .PP
 The actions are:
@@ -123,6 +124,12 @@ The network connectivity state has changed (no connectivity, went online, etc)\&
 The connection was reapplied on the device\&.
 .RE
 .PP
+\fIdns\-change\fR
+.RS 4
+The DNS configuration has changed\&. This action is raised even if NetworkManager is configured to not manage resolv\&.conf (for example, via dns=none)\&. In such case, the dispatch script can discover the DNS configuration provided by currently active connections by looking at file
+/run/NetworkManager/resolv\&.conf
+.RE
+.PP
 The environment contains more information about the interface and the connection\&. The following variables are available for the use in the dispatcher scripts:
 .PP
 \fINM_DISPATCHER_ACTION\fR
diff --git a/man/NetworkManager-dispatcher.xml b/man/NetworkManager-dispatcher.xml
index 036b3c8d..f6e1d22d 100644
--- a/man/NetworkManager-dispatcher.xml
+++ b/man/NetworkManager-dispatcher.xml
@@ -7,22 +7,13 @@
 ]>
 
 
 
 
@@ -68,8 +59,9 @@
       device an operation just happened on, and second the action. For device actions,
       the interface is the name of the kernel interface suitable for IP configuration.
       Thus it is either VPN_IP_IFACE, DEVICE_IP_IFACE, or DEVICE_IFACE, as applicable.
-      For the hostname action the device name is always "none"
-      and for connectivity-change it is empty.
+      For the hostname action the device name is always
+      "none". For connectivity-change and
+      dns-change it is empty.
     
     The actions are:
     
@@ -170,6 +162,16 @@
           The connection was reapplied on the device.
         
       
+      
+        dns-change
+        
+            The DNS configuration has changed. This action is raised even if
+            NetworkManager is configured to not manage resolv.conf (for example,
+            via dns=none). In such case, the dispatch script can discover the
+            DNS configuration provided by currently active connections by
+            looking at file /run/NetworkManager/resolv.conf
+        
+      
     
     
       The environment contains more information about the interface and the connection.
diff --git a/man/NetworkManager-wait-online.service.8 b/man/NetworkManager-wait-online.service.8
index e7ffd0d7..37077e93 100644
--- a/man/NetworkManager-wait-online.service.8
+++ b/man/NetworkManager-wait-online.service.8
@@ -2,9 +2,9 @@
 .\"     Title: NetworkManager-wait-online.service
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Network management daemons
-.\"    Source: NetworkManager-wait-online.service 1.44.2
+.\"    Source: NetworkManager-wait-online.service 1.45.90
 .\"  Language: English
 .\"
 .TH "NETWORKMANAGER\-WAIT\-ONLINE\&" "8" "" "NetworkManager\-wait\-online\&" "Network management daemons"
diff --git a/man/NetworkManager-wait-online.service.xml b/man/NetworkManager-wait-online.service.xml
index 46068ea5..4776002c 100644
--- a/man/NetworkManager-wait-online.service.xml
+++ b/man/NetworkManager-wait-online.service.xml
@@ -7,18 +7,9 @@
 ]>
 
 
 
 
diff --git a/man/NetworkManager.8 b/man/NetworkManager.8
index 1df61c61..eb5ec2c8 100644
--- a/man/NetworkManager.8
+++ b/man/NetworkManager.8
@@ -2,12 +2,12 @@
 .\"     Title: NetworkManager
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Network management daemons
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NETWORKMANAGER" "8" "" "NetworkManager 1\&.44\&.2" "Network management daemons"
+.TH "NETWORKMANAGER" "8" "" "NetworkManager 1\&.45\&.90" "Network management daemons"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -143,6 +143,37 @@ or
 "device*\&.managed=1"
 in NetworkManager\&.conf\&.
 .RE
+.PP
+\fIID_NET_MANAGED_BY\fR
+.RS 4
+If
+\fINM_UNMANAGED\fR
+is set, this has no effect\&. Otherwise, if the attribute is set to anything but
+"org\&.freedesktop\&.NetworkManager", the device is unmanaged\&.
+.RE
+.PP
+\fINM_AUTO_DEFAULT_LINK_LOCAL_ONLY\fR
+.RS 4
+If set to
+"1"
+or
+"true", the automatically generated connections "Wired connection N" will only enable link local addressing for IPv4 and IPv6\&. This can be useful on thunderbolt devices or host\-to\-host USB devices\&.
+.RE
+.PP
+\fIID_NET_AUTO_LINK_LOCAL_ONLY\fR
+.RS 4
+Honored and treated the same as if
+\fINM_AUTO_DEFAULT_LINK_LOCAL_ONLY\fR
+were set\&.
+.RE
+.PP
+\fIID_NET_DHCP_BROADCAST\fR
+.RS 4
+If set to
+"1"
+or
+"true", use broadcast requests for DHCPv4 offers\&. This can make sense of devices that can\*(Aqt handle unicast messages until being configured\&.
+.RE
 .SH "SIGNALS"
 .PP
 NetworkManager process handles the following signals:
@@ -241,7 +272,7 @@ Please report any bugs you find in NetworkManager at the
 \fBnmcli\fR(1),
 \fBnmcli-examples\fR(7),
 \fBnm-online\fR(1),
-\fBnm-settings\fR(5),
+\fBnm-settings-nmcli\fR(5),
 \fBnm-applet\fR(1),
 \fBnm-connection-editor\fR(1),
 \fBudev\fR(7)
diff --git a/man/NetworkManager.conf.5 b/man/NetworkManager.conf.5
index d85d3950..f321598d 100644
--- a/man/NetworkManager.conf.5
+++ b/man/NetworkManager.conf.5
@@ -2,12 +2,12 @@
 .\"     Title: NetworkManager.conf
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Configuration
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NETWORKMANAGER\&.CONF" "5" "" "NetworkManager 1\&.44\&.2" "Configuration"
+.TH "NETWORKMANAGER\&.CONF" "5" "" "NetworkManager 1\&.45\&.90" "Configuration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -370,15 +370,6 @@ connection\&.autoconnect\-retries
 property set to \-1\&. If not specified, connections will be tried 4 times\&. Setting this value to 1 means to try activation once, without retry\&.
 .RE
 .PP
-\fIslaves\-order\fR
-.RS 4
-This key specifies in which order slave connections are auto\-activated on boot or when the master activates them\&. Allowed values are
-name
-(order connection by interface name, the default), or
-index
-(order slaves by their kernel index)\&.
-.RE
-.PP
 \fIfirewall\-backend\fR
 .RS 4
 The firewall backend for configuring masquerading with shared mode\&. Set to either
@@ -509,7 +500,9 @@ domains=ALL
 .sp
 and restart the daemon with
 \fBsystemctl restart NetworkManager\fR\&. Then reproduce the problem\&. You can find the logs in syslog (for example
-\fBjournalctl\fR)\&.
+\fBjournalctl\fR, or
+\fBjournalctl \-u NetworkManager\fR
+to show only logs from NetworkManager)\&.
 .PP
 Any settings here are overridden by the
 \fB\-\-log\-level\fR
@@ -770,7 +763,7 @@ ipv6\&.ip6\-privacy=0
 .SS "Supported Properties"
 .PP
 Not all properties can be overwritten, only the following properties are supported to have their default values configured (see
-\fBnm-settings\fR(5)
+\fBnm-settings-nmcli\fR(5)
 for details)\&.
 .PP
 
@@ -1215,7 +1208,7 @@ Like the per\-connection settings
 ethernet\&.generate\-mac\-address\-mask
 and
 wifi\&.generate\-mac\-address\-mask, this allows to configure the generated MAC addresses during scanning\&. See
-\fBnm-settings\fR(5)
+\fBnm-settings-nmcli\fR(5)
 for details\&.
 .RE
 .PP
@@ -1426,7 +1419,7 @@ plugin is the generic plugin that supports all the connection types and capabili
 for details about the file format\&.
 .sp
 The stored connection file may contain passwords, secrets and private keys in plain text, so it will be made readable only to root, and the plugin will ignore files that are readable or writable by any user or group other than root\&. See "Secret flag types" in
-\fBnm-settings\fR(5)
+\fBnm-settings-nmcli\fR(5)
 for how to avoid storing passwords in plain text\&.
 .sp
 This plugin is always active, and will automatically be used to store any connections that aren\*(Aqt supported by any other active plugin\&.
@@ -1621,6 +1614,6 @@ Backslash is supported to escape the separators \*(Aq;\*(Aq and \*(Aq,\*(Aq, and
 \fBnmcli\fR(1),
 \fBnmcli-examples\fR(7),
 \fBnm-online\fR(1),
-\fBnm-settings\fR(5),
+\fBnm-settings-nmcli\fR(5),
 \fBnm-applet\fR(1),
 \fBnm-connection-editor\fR(1)
diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml
index c795d295..5a7f0d83 100644
--- a/man/NetworkManager.conf.xml
+++ b/man/NetworkManager.conf.xml
@@ -7,20 +7,11 @@
 ]>
 
 
 
 
@@ -469,20 +460,6 @@ no-auto-default=*
         
       
 
-      
-        slaves-order
-        
-          
-            This key specifies in which order slave connections are
-            auto-activated on boot or when the master activates
-            them. Allowed values are name (order
-            connection by interface name, the default), or
-            index (order slaves by their kernel
-            index).
-          
-        
-      
-
       
         firewall-backend
         
@@ -657,7 +634,9 @@ level=TRACE
 domains=ALL
 
     and restart the daemon with systemctl restart NetworkManager. Then
-    reproduce the problem. You can find the logs in syslog (for example journalctl).
+    reproduce the problem. You can find the logs in syslog (for example
+    journalctl, or journalctl -u NetworkManager
+    to show only logs from NetworkManager).
     
 
     
@@ -856,7 +835,7 @@ ipv6.ip6-privacy=0
     
       Not all properties can be overwritten, only the following
       properties are supported to have their default values configured
-      (see nm-settings5 for details).
+      (see nm-settings-nmcli5 for details).
     
     
       
@@ -1353,7 +1332,7 @@ managed=1
             
               Like the per-connection settings ethernet.generate-mac-address-mask
               and wifi.generate-mac-address-mask, this allows to configure the
-              generated MAC addresses during scanning. See nm-settings5
+              generated MAC addresses during scanning. See nm-settings-nmcli5
               for details.
             
           
@@ -1656,7 +1635,7 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16
             private keys in plain text, so it will be made readable only to
             root, and the plugin will ignore files that are readable or
             writable by any user or group other than root. See "Secret flag types"
-            in nm-settings5
+            in nm-settings-nmcli5
             for how to avoid storing passwords in plain text.
           
           
@@ -1881,7 +1860,7 @@ interface-name:vboxnet*,except:interface-name:vboxnet2
       nmcli1,
       nmcli-examples7,
       nm-online1,
-      nm-settings5,
+      nm-settings-nmcli5,
       nm-applet1,
       nm-connection-editor1
     
diff --git a/man/NetworkManager.xml b/man/NetworkManager.xml
index f0b0f33f..ff1635cd 100644
--- a/man/NetworkManager.xml
+++ b/man/NetworkManager.xml
@@ -7,22 +7,13 @@
 ]>
 
 
 
 
@@ -202,6 +193,42 @@
         
         
       
+      
+        ID_NET_MANAGED_BY
+        
+          If NM_UNMANAGED is set, this has no effect. Otherwise,
+          if the attribute is set to anything but
+          "org.freedesktop.NetworkManager", the device is unmanaged.
+        
+        
+      
+      
+        NM_AUTO_DEFAULT_LINK_LOCAL_ONLY
+        
+          If set to "1" or "true", the
+          automatically generated connections "Wired connection N" will only
+          enable link local addressing for IPv4 and IPv6. This can be useful
+          on thunderbolt devices or host-to-host USB devices.
+        
+        
+      
+      
+        ID_NET_AUTO_LINK_LOCAL_ONLY
+        
+          Honored and treated the same as if NM_AUTO_DEFAULT_LINK_LOCAL_ONLY
+          were set.
+        
+        
+      
+      
+        ID_NET_DHCP_BROADCAST
+        
+          If set to "1" or "true", use
+          broadcast requests for DHCPv4 offers. This can make sense of devices
+          that can't handle unicast messages until being configured.
+        
+        
+      
     
   
 
@@ -357,7 +384,7 @@
       nmcli1,
       nmcli-examples7,
       nm-online1,
-      nm-settings5,
+      nm-settings-nmcli5,
       nm-applet1,
       nm-connection-editor1,
       udev7
diff --git a/man/meson.build b/man/meson.build
index a2e1de83..f0113cd5 100644
--- a/man/meson.build
+++ b/man/meson.build
@@ -62,40 +62,40 @@ foreach man: mans
 endforeach
 
 if enable_introspection
+  merge_cmd = join_paths(meson.source_root(), 'tools', 'generate-docs-nm-settings-docs-merge.py')
 
   name = 'dbus'
   nm_settings_docs_xml_dbus = custom_target(
     'nm-settings-docs-' + name + '.xml',
-    input: [nm_settings_docs_xml_gir, nm_property_infos_xml[name]],
+    input: [merge_cmd, nm_property_infos_xml[name], nm_settings_docs_xml_gir[name]],
     output: 'nm-settings-docs-' + name + '.xml',
     command: [
       python.path(),
-      join_paths(meson.source_root(), 'tools', 'generate-docs-nm-settings-docs-merge.py'),
+      merge_cmd,
       '@OUTPUT@',
       nm_property_infos_xml[name],
-      nm_settings_docs_xml_gir,
+      nm_settings_docs_xml_gir[name]
     ],
   )
 
   name = 'nmcli'
   nm_settings_docs_xml_nmcli = custom_target(
     'nm-settings-docs-' + name + '.xml',
-    input: [nm_settings_docs_xml_gir, nm_property_infos_xml[name]],
+    input: [merge_cmd, nm_property_infos_xml[name], gen_metadata_nm_settings_nmcli_xml, nm_settings_docs_xml_gir[name]],
     output: 'nm-settings-docs-' + name + '.xml',
     command: [
       python.path(),
-      join_paths(meson.source_root(), 'tools', 'generate-docs-nm-settings-docs-merge.py'),
+      merge_cmd,
       '@OUTPUT@',
       '--only-properties-from',
       gen_metadata_nm_settings_nmcli_xml,
       nm_property_infos_xml[name],
       gen_metadata_nm_settings_nmcli_xml,
-      nm_settings_docs_xml_gir,
+      nm_settings_docs_xml_gir[name]
     ],
   )
 
   nm_settings_docs_xml = {
-    'gir':   nm_settings_docs_xml_gir,
     'dbus':  nm_settings_docs_xml_dbus,
     'nmcli':  nm_settings_docs_xml_nmcli,
   }
@@ -112,14 +112,15 @@ if enable_introspection
 
   foreach man: mans
     output = man[0] + '.xml'
+    template = join_paths(meson.current_source_dir(), man[0] + '.xsl')
 
     input = custom_target(
       output,
-      input: man[2],
+      input: [template, man[2]],
       output: output,
-      command: xsltproc_options + [join_paths(meson.current_source_dir(), man[0] + '.xsl'), '@INPUT@'],
+      command: xsltproc_options + ['@INPUT@'],
     )
-    content_files += input.full_path()
+    content_files += input
 
     output = '@0@.@1@'.format(man[0], man[1])
 
diff --git a/man/nm-cloud-setup.8 b/man/nm-cloud-setup.8
index d7f70191..3f10803c 100644
--- a/man/nm-cloud-setup.8
+++ b/man/nm-cloud-setup.8
@@ -2,12 +2,12 @@
 .\"     Title: nm-cloud-setup
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Automatic Network Configuration in Cloud with NetworkManager
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NM\-CLOUD\-SETUP" "8" "" "NetworkManager 1\&.44\&.2" "Automatic Network Configuratio"
+.TH "NM\-CLOUD\-SETUP" "8" "" "NetworkManager 1\&.45\&.90" "Automatic Network Configuratio"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
diff --git a/man/nm-cloud-setup.xml b/man/nm-cloud-setup.xml
index 74ec0400..d0e14b4f 100644
--- a/man/nm-cloud-setup.xml
+++ b/man/nm-cloud-setup.xml
@@ -7,20 +7,11 @@
 ]>
 
 
 
 
diff --git a/man/nm-initrd-generator.8 b/man/nm-initrd-generator.8
index 6b78b351..8684c7cc 100644
--- a/man/nm-initrd-generator.8
+++ b/man/nm-initrd-generator.8
@@ -2,12 +2,12 @@
 .\"     Title: nm-initrd-generator
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: System Administration
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NM\-INITRD\-GENERATOR" "8" "" "NetworkManager 1\&.44\&.2" "System Administration"
+.TH "NM\-INITRD\-GENERATOR" "8" "" "NetworkManager 1\&.45\&.90" "System Administration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
diff --git a/man/nm-initrd-generator.xml b/man/nm-initrd-generator.xml
index 1905b7b6..336d7f03 100644
--- a/man/nm-initrd-generator.xml
+++ b/man/nm-initrd-generator.xml
@@ -7,20 +7,11 @@
 ]>
 
 
 
 
diff --git a/man/nm-online.1 b/man/nm-online.1
index 801577c8..1525bc66 100644
--- a/man/nm-online.1
+++ b/man/nm-online.1
@@ -2,12 +2,12 @@
 .\"     Title: nm-online
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: General Commands Manual
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NM\-ONLINE" "1" "" "NetworkManager 1\&.44\&.2" "General Commands Manual"
+.TH "NM\-ONLINE" "1" "" "NetworkManager 1\&.45\&.90" "General Commands Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
diff --git a/man/nm-online.xml b/man/nm-online.xml
index 87672f74..e9deb83e 100644
--- a/man/nm-online.xml
+++ b/man/nm-online.xml
@@ -7,20 +7,11 @@
 ]>
 
 
 
 
diff --git a/man/nm-openvswitch.7 b/man/nm-openvswitch.7
index acc5a824..0078cf7d 100644
--- a/man/nm-openvswitch.7
+++ b/man/nm-openvswitch.7
@@ -2,12 +2,12 @@
 .\"     Title: nm-openvswitch
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Open vSwitch support overview
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NM\-OPENVSWITCH" "7" "" "NetworkManager 1\&.44\&.2" "Open vSwitch support overview"
+.TH "NM\-OPENVSWITCH" "7" "" "NetworkManager 1\&.45\&.90" "Open vSwitch support overview"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -195,7 +195,7 @@ Connection \*(Aqovs\-slave\-eth3\*(Aq (8dedeecb\-ed12\-482b\-b77a\-24a4fb835136)
 .RE
 .\}
 .PP
-It\*(Aqs just a Port with multiple interfaces\&. See nm\-settings manual for Bonding options you can use with "nmcli c add" or "nmcli c modify"\&. You could even set a VLAN tag on the same Port to do VLAN tagging and bonding at the same time\&.
+It\*(Aqs just a Port with multiple interfaces\&. See nm\-settings\-nmcli manual for Bonding options you can use with "nmcli c add" or "nmcli c modify"\&. You could even set a VLAN tag on the same Port to do VLAN tagging and bonding at the same time\&.
 .SH "BUGS"
 .sp
 .RS 4
@@ -226,7 +226,7 @@ Probably many more\&.
 \m[blue]\fBRFC 7047: The Open vSwitch Database Management Protocol\fR\m[]\&\s-2\u[1]\d\s+2,
 \fBovs-vsctl\fR(8),
 \fBovs-vswitchd.conf.db\fR(5),
-\fBnm-settings\fR(5),
+\fBnm-settings-nmcli\fR(5),
 \fBnmcli\fR(1)
 .SH "NOTES"
 .IP " 1." 4
diff --git a/man/nm-openvswitch.xml b/man/nm-openvswitch.xml
index 52ecf96b..f0c2ca94 100644
--- a/man/nm-openvswitch.xml
+++ b/man/nm-openvswitch.xml
@@ -7,20 +7,11 @@
 ]>
 
 
 
 
@@ -170,7 +161,7 @@ Connection 'ovs-slave-eth2' (475ac1bf-30b2-4534-a877-27f33f58b082) successfully
 $ nmcli conn add type ethernet conn.interface eth3 master bond0
 Connection 'ovs-slave-eth3' (8dedeecb-ed12-482b-b77a-24a4fb835136) successfully added.
 
-      It's just a Port with multiple interfaces. See nm-settings manual for
+      It's just a Port with multiple interfaces. See nm-settings-nmcli manual for
       Bonding options you can use with "nmcli c add" or "nmcli c modify". You could
       even set a VLAN tag on the same Port to do VLAN tagging and bonding at the same
       time.
@@ -197,7 +188,7 @@ Connection 'ovs-slave-eth3' (8dedeecb-ed12-482b-b77a-24a4fb835136) successfully
       RFC 7047: The Open vSwitch Database Management Protocol,
       ovs-vsctl8,
       ovs-vswitchd.conf.db5,
-      nm-settings5,
+      nm-settings-nmcli5,
       nmcli1
     
   
diff --git a/man/nm-settings-dbus.5 b/man/nm-settings-dbus.5
index 400bb91e..d8c4087a 100644
--- a/man/nm-settings-dbus.5
+++ b/man/nm-settings-dbus.5
@@ -2,12 +2,12 @@
 .\"     Title: nm-settings-dbus
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Configuration
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NM\-SETTINGS\-DBUS" "5" "" "NetworkManager 1\&.44\&.2" "Configuration"
+.TH "NM\-SETTINGS\-DBUS" "5" "" "NetworkManager 1\&.45\&.90" "Configuration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -101,6 +101,8 @@ l l l l
 l l l l
 l l l l
 l l l l
+l l l l
+l l l l
 l l l l.
 T{
 auth\-retries
@@ -158,6 +160,15 @@ T}:T{
 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\&.
 T}
 T{
+controller
+T}:T{
+string
+T}:T{
+\ \&
+T}:T{
+Interface name of the controller device or UUID of the controller connection\&.
+T}
+T{
 dns\-over\-tls
 T}:T{
 int32
@@ -231,6 +242,8 @@ T}:T{
 \ \&
 T}:T{
 Interface name of the master device or UUID of the master connection\&.
+
+Deprecated 1\&.46\&. Use "controller" instead, this is just an alias\&.
 T}
 T{
 mdns
@@ -315,6 +328,15 @@ An array of strings defining what access a given user has to this connection\&.
 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\&.
 T}
 T{
+port\-type
+T}:T{
+string
+T}:T{
+\ \&
+T}:T{
+Setting name of the device type of this port\*(Aqs controller connection (eg, "bond"), or NULL if this connection is not a port\&.
+T}
+T{
 read\-only
 T}:T{
 boolean
@@ -342,6 +364,8 @@ T}:T{
 \ \&
 T}:T{
 Setting name of the device type of this slave\*(Aqs master connection (eg, "bond"), or NULL if this connection is not a slave\&.
+
+Deprecated 1\&.46\&. Use "port\-type" instead, this is just an alias\&.
 T}
 T{
 stable\-id
@@ -356,7 +380,7 @@ The stable\-id is used for generating IPv6 stable private addresses with ipv6\&.
 
 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\*(Aqs 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 \*(Aq$\*(Aq character is treated special to perform dynamic substitutions at activation time\&. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}"\&.  These effectively create unique IDs per\-connection, per\-device, per\-boot, or every time\&. The "${CONNECTION}" uses the profile\*(Aqs connection\&.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device\&. Any unrecognized patterns following \*(Aq$\*(Aq are treated verbatim, however are reserved for future use\&. You are thus advised to avoid \*(Aq$\*(Aq 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 \*(Aq$\*(Aq character is treated special to perform dynamic substitutions at activation time\&. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}"\&.  These effectively create unique IDs per\-connection, per\-device, per\-SSID, per\-boot, or every time\&.  The "${CONNECTION}" uses the profile\*(Aqs connection\&.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device\&. "${NETWORK_SSID}" uses the SSID for Wi\-Fi networks and falls back to "${CONNECTION}" on other networks\&. Any unrecognized patterns following \*(Aq$\*(Aq are treated verbatim, however are reserved for future use\&. You are thus advised to avoid \*(Aq$\*(Aq or escape it as "$$"\&.  For example, set it to "${CONNECTION}\-${BOOT}\-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates\&.
 
 If the value is unset, a global connection default is consulted\&. If the value is still unset, the default is "default${CONNECTION}" go generate an ID unique per connection profile\&.
 T}
@@ -1616,7 +1640,7 @@ NMSettingDcbFlags (uint32)
 T}:T{
 \ \&
 T}:T{
-Specifies the NMSettingDcbFlags for the DCB FCoE application\&.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for the DCB FCoE application\&.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing)\&.
 T}
 T{
 app\-fcoe\-mode
@@ -1636,7 +1660,7 @@ int32
 T}:T{
 \-1
 T}:T{
-The highest User Priority (0 \- 7) which FCoE frames should use, or \-1 for default priority\&.  Only used when the "app\-fcoe\-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag\&.
+The highest User Priority (0 \- 7) which FCoE frames should use, or \-1 for default priority\&.  Only used when the "app\-fcoe\-flags" property includes the 0x1 (enable) flag\&.
 T}
 T{
 app\-fip\-flags
@@ -1645,7 +1669,7 @@ NMSettingDcbFlags (uint32)
 T}:T{
 \ \&
 T}:T{
-Specifies the NMSettingDcbFlags for the DCB FIP application\&.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for the DCB FIP application\&.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing)\&.
 T}
 T{
 app\-fip\-priority
@@ -1654,7 +1678,7 @@ int32
 T}:T{
 \-1
 T}:T{
-The highest User Priority (0 \- 7) which FIP frames should use, or \-1 for default priority\&.  Only used when the "app\-fip\-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag\&.
+The highest User Priority (0 \- 7) which FIP frames should use, or \-1 for default priority\&.  Only used when the "app\-fip\-flags" property includes the 0x1 (enable) flag\&.
 T}
 T{
 app\-iscsi\-flags
@@ -1663,7 +1687,7 @@ NMSettingDcbFlags (uint32)
 T}:T{
 \ \&
 T}:T{
-Specifies the NMSettingDcbFlags for the DCB iSCSI application\&.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for the DCB iSCSI application\&.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing)\&.
 T}
 T{
 app\-iscsi\-priority
@@ -1672,7 +1696,7 @@ int32
 T}:T{
 \-1
 T}:T{
-The highest User Priority (0 \- 7) which iSCSI frames should use, or \-1 for default priority\&. Only used when the "app\-iscsi\-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag\&.
+The highest User Priority (0 \- 7) which iSCSI frames should use, or \-1 for default priority\&. Only used when the "app\-iscsi\-flags" property includes the 0x1 (enable) flag\&.
 T}
 T{
 priority\-bandwidth
@@ -1699,7 +1723,7 @@ NMSettingDcbFlags (uint32)
 T}:T{
 \ \&
 T}:T{
-Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC)\&. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC)\&. Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing)\&.
 T}
 T{
 priority\-group\-bandwidth
@@ -1717,7 +1741,7 @@ NMSettingDcbFlags (uint32)
 T}:T{
 \ \&
 T}:T{
-Specifies the NMSettingDcbFlags for DCB Priority Groups\&.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for DCB Priority Groups\&.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing)\&.
 T}
 T{
 priority\-group\-id
@@ -1845,6 +1869,8 @@ T}:T{
 \ \&
 T}:T{
 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\*(Aqs mobile broadband plan\&. The APN may only be composed of the characters a\-z, 0\-9, \&., and \- per GSM 03\&.60 Section 14\&.9\&.
+
+If the APN is unset (the default) then it may be detected based on "auto\-config" setting\&. The property can be explicitly set to the empty string to prevent that and use no APN\&.
 T}
 T{
 auto\-config
@@ -2142,9 +2168,9 @@ int32
 T}:T{
 \-1
 T}:T{
-Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network\&.  If an address conflict is detected, the activation will fail\&.  A zero value means that no duplicate address detection is performed, \-1 means the default value (either configuration ipvx\&.dad\-timeout override or zero)\&.  A value greater than zero is a timeout in milliseconds\&.
+Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network\&.  If an address conflict is detected, the activation will fail\&. The property is currently implemented only for IPv4\&.
 
-The property is currently implemented only for IPv4\&.
+A zero value means that no duplicate address detection is performed, \-1 means the default value (either the value configured globally in NetworkManger\&.conf or 200ms)\&.  A value greater than zero is a timeout in milliseconds\&.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property\&.
 T}
 T{
 dhcp\-client\-id
@@ -2163,7 +2189,9 @@ The special value "duid" generates a RFC4361\-compliant client identifier based
 
 The special value "stable" is supported to generate a type 0 client identifier based on the stable\-id (see connection\&.stable\-id) and a per\-host key\&. If you set the stable\-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per\-device key\&.
 
-If unset, a globally configured default is used\&. If still unset, the default depends on the DHCP plugin\&.
+The special value "none" prevents any client identifier from being sent\&. Note that this is normally not recommended\&.
+
+If unset, a globally configured default from NetworkManager\&.conf is used\&. If still unset, the default depends on the DHCP plugin\&. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won\*(Aqt sent any client\-id otherwise\&.
 T}
 T{
 dhcp\-fqdn
@@ -2192,9 +2220,9 @@ T}:T{
 T}:T{
 Flags for the DHCP hostname and FQDN\&.
 
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option\&. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4)\&.  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag\&. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6\&.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option\&. Supported FQDN flags are 0x1 (fqdn\-serv\-update), 0x2 (fqdn\-encoded) and 0x4 (fqdn\-no\-update)\&.  When no FQDN flag is set and 0x8 (fqdn\-clear\-flags) is set, the DHCP FQDN option will contain no flag\&. Otherwise, if no FQDN flag is set and 0x8 (fqdn\-clear\-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn\-serv\-update), 0x2 (fqdn\-encoded) for IPv4 and 0x1 (fqdn\-serv\-update) for IPv6\&.
 
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration\&. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests\&.
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration\&. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests\&.
 T}
 T{
 dhcp\-iaid
@@ -2278,15 +2306,17 @@ array of string
 T}:T{
 \ \&
 T}:T{
-Array of DNS options as described in man 5 resolv\&.conf\&.
+Array of DNS options to be added to resolv\&.conf\&.
 
 NULL means that the options are unset and left at the default\&. In this case NetworkManager will use default options\&. This is distinct from an empty list of properties\&.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6\-bytestring", "ip6\-dotint", "ndots", "no\-aaaa", "no\-check\-names", "no\-ip6\-dotint", "no\-reload", "no\-tld\-query", "rotate", "single\-request", "single\-request\-reopen", "timeout", "trust\-ad", "use\-vc"\&.
+The following options are directly added to resolv\&.conf: "attempts", "debug", "edns0", "inet6", "ip6\-bytestring", "ip6\-dotint", "ndots", "no\-aaaa", "no\-check\-names", "no\-ip6\-dotint", "no\-reload", "no\-tld\-query", "rotate", "single\-request", "single\-request\-reopen", "timeout", "trust\-ad", "use\-vc"\&. See the resolv\&.conf(5) man page for a detailed description of these options\&.
+
+In addition, NetworkManager supports the special options "_no\-add\-edns0" and "_no\-add\-trust\-ad"\&. They are not added to resolv\&.conf, and can be used to prevent the automatic addition of options "edns0" and "trust\-ad" when using caching DNS plugins (see below)\&.
 
 The "trust\-ad" setting is only honored if the profile contributes name servers to resolv\&.conf, and if all contributing profiles have "trust\-ad" enabled\&.
 
-When using a caching DNS plugin (dnsmasq or systemd\-resolved in NetworkManager\&.conf) then "edns0" and "trust\-ad" are automatically added\&.
+When using a caching DNS plugin (dnsmasq or systemd\-resolved in NetworkManager\&.conf) then "edns0" and "trust\-ad" are automatically added, unless "_no\-add\-edns0" and "_no\-add\-trust\-ad" are present\&.
 T}
 T{
 dns\-priority
@@ -2539,7 +2569,7 @@ T}:T{
 T}:T{
 Configure the method for creating the IPv6 interface identifier of addresses for RFC4862 IPv6 Stateless Address Autoconfiguration and IPv6 Link Local\&.
 
-The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1)\&. NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3)\&.
+The permitted values are: 0 (eui64), 1 (stable\-privacy)\&. 2 (default\-or\-eui64) or 3 (default)\&.
 
 If the property is set to "eui64", the addresses will be generated using the interface token derived from the hardware address\&. This makes the host part of the address constant, making it possible to track the host\*(Aqs presence when it changes networks\&. The address changes when the interface hardware is replaced\&. If a duplicate address is detected, there is no fallback to generate another address\&. When configured, the "ipv6\&.token" is used instead of the MAC address to generate addresses for stateless autoconfiguration\&.
 
@@ -2588,9 +2618,9 @@ int32
 T}:T{
 \-1
 T}:T{
-Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network\&.  If an address conflict is detected, the activation will fail\&.  A zero value means that no duplicate address detection is performed, \-1 means the default value (either configuration ipvx\&.dad\-timeout override or zero)\&.  A value greater than zero is a timeout in milliseconds\&.
+Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network\&.  If an address conflict is detected, the activation will fail\&. The property is currently implemented only for IPv4\&.
 
-The property is currently implemented only for IPv4\&.
+A zero value means that no duplicate address detection is performed, \-1 means the default value (either the value configured globally in NetworkManger\&.conf or 200ms)\&.  A value greater than zero is a timeout in milliseconds\&.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property\&.
 T}
 T{
 dhcp\-duid
@@ -2627,9 +2657,9 @@ T}:T{
 T}:T{
 Flags for the DHCP hostname and FQDN\&.
 
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option\&. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4)\&.  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag\&. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6\&.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option\&. Supported FQDN flags are 0x1 (fqdn\-serv\-update), 0x2 (fqdn\-encoded) and 0x4 (fqdn\-no\-update)\&.  When no FQDN flag is set and 0x8 (fqdn\-clear\-flags) is set, the DHCP FQDN option will contain no flag\&. Otherwise, if no FQDN flag is set and 0x8 (fqdn\-clear\-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn\-serv\-update), 0x2 (fqdn\-encoded) for IPv4 and 0x1 (fqdn\-serv\-update) for IPv6\&.
 
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration\&. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests\&.
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration\&. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests\&.
 T}
 T{
 dhcp\-iaid
@@ -2713,15 +2743,17 @@ array of string
 T}:T{
 \ \&
 T}:T{
-Array of DNS options as described in man 5 resolv\&.conf\&.
+Array of DNS options to be added to resolv\&.conf\&.
 
 NULL means that the options are unset and left at the default\&. In this case NetworkManager will use default options\&. This is distinct from an empty list of properties\&.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6\-bytestring", "ip6\-dotint", "ndots", "no\-aaaa", "no\-check\-names", "no\-ip6\-dotint", "no\-reload", "no\-tld\-query", "rotate", "single\-request", "single\-request\-reopen", "timeout", "trust\-ad", "use\-vc"\&.
+The following options are directly added to resolv\&.conf: "attempts", "debug", "edns0", "inet6", "ip6\-bytestring", "ip6\-dotint", "ndots", "no\-aaaa", "no\-check\-names", "no\-ip6\-dotint", "no\-reload", "no\-tld\-query", "rotate", "single\-request", "single\-request\-reopen", "timeout", "trust\-ad", "use\-vc"\&. See the resolv\&.conf(5) man page for a detailed description of these options\&.
+
+In addition, NetworkManager supports the special options "_no\-add\-edns0" and "_no\-add\-trust\-ad"\&. They are not added to resolv\&.conf, and can be used to prevent the automatic addition of options "edns0" and "trust\-ad" when using caching DNS plugins (see below)\&.
 
 The "trust\-ad" setting is only honored if the profile contributes name servers to resolv\&.conf, and if all contributing profiles have "trust\-ad" enabled\&.
 
-When using a caching DNS plugin (dnsmasq or systemd\-resolved in NetworkManager\&.conf) then "edns0" and "trust\-ad" are automatically added\&.
+When using a caching DNS plugin (dnsmasq or systemd\-resolved in NetworkManager\&.conf) then "edns0" and "trust\-ad" are automatically added, unless "_no\-add\-edns0" and "_no\-add\-trust\-ad" are present\&.
 T}
 T{
 dns\-priority
@@ -2986,7 +3018,7 @@ uint32
 T}:T{
 0
 T}:T{
-How many additional levels of encapsulation are permitted to be prepended to packets\&. This property applies only to IPv6 tunnels\&. To disable this option, add NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1) to ip\-tunnel flags\&.
+How many additional levels of encapsulation are permitted to be prepended to packets\&. This property applies only to IPv6 tunnels\&. To disable this option, add 0x1 (ip6\-ign\-encap\-limit) to ip\-tunnel flags\&.
 T}
 T{
 flags
@@ -2995,7 +3027,7 @@ uint32
 T}:T{
 0
 T}:T{
-Tunnel flags\&. Currently, the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20)\&. They are valid only for IPv6 tunnels\&.
+Tunnel flags\&. Currently, the following values are supported: 0x1 (ip6\-ign\-encap\-limit), 0x2 (ip6\-use\-orig\-tclass), 0x4 (ip6\-use\-orig\-flowlabel), 0x8 (ip6\-mip6\-dev), 0x10 (ip6\-rcv\-dscp\-copy), 0x20 (ip6\-use\-orig\-fwmark)\&. They are valid only for IPv6 tunnels\&.
 T}
 T{
 flow\-label
@@ -3040,7 +3072,7 @@ uint32
 T}:T{
 0
 T}:T{
-The tunneling mode\&. Valid values: NM_IP_TUNNEL_MODE_IPIP (1), NM_IP_TUNNEL_MODE_GRE (2), NM_IP_TUNNEL_MODE_SIT (3), NM_IP_TUNNEL_MODE_ISATAP (4), NM_IP_TUNNEL_MODE_VTI (5), NM_IP_TUNNEL_MODE_IP6IP6 (6), NM_IP_TUNNEL_MODE_IPIP6 (7), NM_IP_TUNNEL_MODE_IP6GRE (8), NM_IP_TUNNEL_MODE_VTI6 (9), NM_IP_TUNNEL_MODE_GRETAP (10) and NM_IP_TUNNEL_MODE_IP6GRETAP (11)
+The tunneling mode\&. Valid values: 1 (ipip), 2 (gre), 3 (sit), 4 (isatap), 5 (vti), 6 (ip6ip6), 7 (ipip6), 8 (ip6gre), 9 (vti6), 10 (gretap) and 11 (ip6gretap)
 T}
 T{
 mtu
@@ -3979,7 +4011,7 @@ int32
 T}:T{
 0
 T}:T{
-Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)
+Method for proxy configuration, Default is 0 (none)
 T}
 T{
 pac\-script
@@ -4097,11 +4129,11 @@ T}:T{
 T}:T{
 Whether to autoprobe virtual functions by a compatible driver\&.
 
-If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF\&.
+If set to 1 (true), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF\&.
 
-If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them\&.
+If set to 0 (false), VFs will not be claimed and no network interfaces will be created for them\&.
 
-When set to NM_TERNARY_DEFAULT (\-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1)\&.
+When set to \-1 (default), the global default is used; in case the global default is unspecified it is assumed to be 1 (true)\&.
 T}
 T{
 total\-vfs
@@ -4503,7 +4535,7 @@ uint32
 T}:T{
 1
 T}:T{
-The operating mode of the virtual device\&. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet\-like layer 2 one\&.
+The operating mode of the virtual device\&. Allowed values are 1 (tun) to create a layer 3 device and 2 (tap) to create an Ethernet\-like layer 2 one\&.
 T}
 T{
 multi\-queue
@@ -4610,7 +4642,7 @@ NMVlanFlags (uint32)
 T}:T{
 \ \&
 T}:T{
-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\*(Aqs operating state)\&. NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol)\&.
+One or more flags which control the behavior and features of the VLAN interface\&.  Flags include 0x1 (reorder\-headers) (reordering of output packet headers), 0x2 (gvrp) (use of the GVRP protocol), and 0x4 (loose\-binding) (loose binding of the interface to its master device\*(Aqs operating state)\&. 0x8 (mvrp) (use of the MVRP protocol)\&.
 
 The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0\&. To preserve backward compatibility, the default\-value in the D\-Bus API continues to be 0 and a missing property on D\-Bus is still considered as 0\&.
 T}
@@ -5216,7 +5248,7 @@ uint32
 T}:T{
 1
 T}:T{
-The NMSettingWiredWakeOnLan options to enable\&. Not all devices support all options\&. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake\-on\-LAN in NetworkManager)\&.
+The NMSettingWiredWakeOnLan options to enable\&. Not all devices support all options\&. May be any combination of 0x2 (phy), 0x4 (unicast), 0x8 (multicast), 0x10 (broadcast), 0x20 (arp), 0x40 (magic) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake\-on\-LAN in NetworkManager)\&.
 T}
 T{
 wake\-on\-lan\-password
@@ -5390,13 +5422,13 @@ NMTernary (int32)
 T}:T{
 \ \&
 T}:T{
-Configures AP isolation, which prevents communication between wireless devices connected to this AP\&. This property can be set to a value different from NM_TERNARY_DEFAULT (\-1) only when the interface is configured in AP mode\&.
+Configures AP isolation, which prevents communication between wireless devices connected to this AP\&. This property can be set to a value different from \-1 (default) only when the interface is configured in AP mode\&.
 
-If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other\&. This increases security because it protects devices against attacks from other clients in the network\&. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc\&.
+If set to 1 (true), devices are not able to communicate with each other\&. This increases security because it protects devices against attacks from other clients in the network\&. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc\&.
 
-If set to NM_TERNARY_FALSE (0), devices can talk to each other\&.
+If set to 0 (false), devices can talk to each other\&.
 
-When set to NM_TERNARY_DEFAULT (\-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0)\&.
+When set to \-1 (default), the global default is used; in case the global default is unspecified it is assumed to be 0 (false)\&.
 T}
 T{
 assigned\-mac\-address
@@ -5502,7 +5534,7 @@ uint32
 T}:T{
 0
 T}:T{
-One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address)\&.
+One of 0 (default) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  1 (never) (never randomize the MAC address), or 2 (always) (always randomize the MAC address)\&.
 
 This property is deprecated since version 1\&.4\&.Use the "cloned\-mac\-address" property instead\&.
 T}
@@ -5531,7 +5563,7 @@ uint32
 T}:T{
 0
 T}:T{
-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\*(Aqt touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value)\&. All other values are reserved\&.
+One of 2 (disable) (disable Wi\-Fi power saving), 3 (enable) (enable Wi\-Fi power saving), 1 (ignore) (don\*(Aqt touch currently configure setting) or 0 (default) (use the globally configured value)\&. All other values are reserved\&.
 T}
 T{
 rate
@@ -5591,7 +5623,7 @@ uint32
 T}:T{
 1
 T}:T{
-The NMSettingWirelessWakeOnWLan options to enable\&. Not all devices support all options\&. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake\-on\-LAN in NetworkManager)\&.
+The NMSettingWirelessWakeOnWLan options to enable\&. Not all devices support all options\&. May be any combination of 0x2 (any), 0x4 (disconnect), 0x8 (magic), 0x10 (gtk\-rekey\-failure), 0x20 (eap\-identity\-request), 0x40 (4way\-handshake), 0x80 (rfkill\-release), 0x100 (tcp) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake\-on\-LAN in NetworkManager)\&.
 T}
 .TE
 .sp 1
@@ -5647,7 +5679,7 @@ int32
 T}:T{
 0
 T}:T{
-Indicates whether Fast Initial Link Setup (802\&.11ai) must be enabled for the connection\&.  One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported)\&.  When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled\&.
+Indicates whether Fast Initial Link Setup (802\&.11ai) must be enabled for the connection\&.  One of 0 (default) (use global default value), 1 (disable) (disable FILS), 2 (optional) (enable FILS if the supplicant and the access point support it) or 3 (required) (enable FILS and fail if not supported)\&.  When set to 0 (default) and no global default is set, FILS will be optionally enabled\&.
 T}
 T{
 group
@@ -5712,7 +5744,7 @@ int32
 T}:T{
 0
 T}:T{
-Indicates whether Protected Management Frames (802\&.11w) must be enabled for the connection\&.  One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported)\&.  When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled\&.
+Indicates whether Protected Management Frames (802\&.11w) must be enabled for the connection\&.  One of 0 (default) (use global default value), 1 (disable) (disable PMF), 2 (optional) (enable PMF if the supplicant and the access point support it) or 3 (required) (enable PMF and fail if not supported)\&.  When set to 0 (default) and no global default is set, PMF will be optionally enabled\&.
 T}
 T{
 proto
@@ -5757,7 +5789,7 @@ NMWepKeyType (uint32)
 T}:T{
 \ \&
 T}:T{
-Controls the interpretation of WEP keys\&.  Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10\- or 26\-character hexadecimal string, or a 5\- or 13\-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de\-facto MD5 method to derive the actual WEP key\&.
+Controls the interpretation of WEP keys\&.  Allowed values are 1 (key), in which case the key is either a 10\- or 26\-character hexadecimal string, or a 5\- or 13\-character ASCII password; or 2 (passphrase), in which case the passphrase is provided as a string and will be hashed using the de\-facto MD5 method to derive the actual WEP key\&.
 T}
 T{
 wep\-key0
@@ -5954,7 +5986,7 @@ T}:T{
 T}:T{
 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\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1)\&.
+When set to \-1 (default), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be 1 (true)\&.
 T}
 T{
 from\-dns\-lookup
@@ -5965,7 +5997,7 @@ T}:T{
 T}:T{
 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\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1)\&.
+When set to \-1 (default), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be 1 (true)\&.
 T}
 T{
 only\-from\-default
@@ -5974,11 +6006,11 @@ NMTernary (int32)
 T}:T{
 \ \&
 T}:T{
-If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6)\&.
+If set to 1 (true), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6)\&.
 
-If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn\*(Aqt have the default route\&.
+If set to 0 (false), the hostname can be set from this device even if it doesn\*(Aqt have the default route\&.
 
-When set to NM_TERNARY_DEFAULT (\-1), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0)\&.
+When set to \-1 (default), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be 0 (false)\&.
 T}
 T{
 priority
@@ -5995,6 +6027,64 @@ Negative values have the special effect of excluding other connections with a gr
 T}
 .TE
 .sp 1
+.SS "hsr setting"
+.PP
+HSR/PRP Settings\&.
+.TS
+allbox tab(:);
+lB lB lB lB.
+T{
+Key Name
+T}:T{
+Value Type
+T}:T{
+Default Value
+T}:T{
+Value Description
+T}
+.T&
+l l l l
+l l l l
+l l l l
+l l l l.
+T{
+multicast\-spec
+T}:T{
+uint32
+T}:T{
+0
+T}:T{
+The last byte of supervision address\&.
+T}
+T{
+port1
+T}:T{
+string
+T}:T{
+\ \&
+T}:T{
+The port1 interface name of the HSR\&. This property is mandatory\&.
+T}
+T{
+port2
+T}:T{
+string
+T}:T{
+\ \&
+T}:T{
+The port2 interface name of the HSR\&. This property is mandatory\&.
+T}
+T{
+prp
+T}:T{
+boolean
+T}:T{
+FALSE
+T}:T{
+The protocol used by the interface, whether it is PRP or HSR\&.
+T}
+.TE
+.sp 1
 .SS "link setting"
 .PP
 Link settings\&.
diff --git a/man/nm-settings-dbus.xml b/man/nm-settings-dbus.xml
index db2f3b12..d7184d26 100644
--- a/man/nm-settings-dbus.xml
+++ b/man/nm-settings-dbus.xml
@@ -1,6 +1,6 @@
 
 
-nm-settings-dbusNetworkManager developersnm-settings-dbus5NetworkManagerConfiguration1.44.2nm-settings-dbusDescription of settings and properties of NetworkManager connection profiles on the D-Bus APIDescription
+nm-settings-dbusNetworkManager developersnm-settings-dbus5NetworkManagerConfiguration1.45.90nm-settings-dbusDescription of settings and properties of NetworkManager connection profiles on the D-Bus APIDescription
           NetworkManager is based on a concept of connection profiles, sometimes referred to as
           connections only. These connection profiles contain a network configuration. When
           NetworkManager activates a connection profile on a network device the configuration will
@@ -42,7 +42,7 @@ Note that autoconnect is not implemented for VPN profiles. See "secondaries" as
 
 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-priorityint320The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.autoconnect-retriesint32-1The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.autoconnect-slavesNMSettingConnectionAutoconnectSlaves (int32)Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.dns-over-tlsint32-1Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.
+Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.autoconnect-priorityint320The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.autoconnect-retriesint32-1The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.autoconnect-slavesNMSettingConnectionAutoconnectSlaves (int32)Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.controllerstringInterface name of the controller device or UUID of the controller connection.dns-over-tlsint32-1Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.
 
 The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting.
 
@@ -54,7 +54,9 @@ For connection types where interface names cannot easily be made persistent (e.g
 
 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.masterstringInterface name of the master device or UUID of the master connection.mdnsint32-1Whether mDNS is enabled for the connection.
+This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.masterstringInterface name of the master device or UUID of the master connection.
+
+Deprecated 1.46. Use "controller" instead, this is just an alias.mdnsint32-1Whether mDNS is enabled for the connection.
 
 The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").
 
@@ -82,15 +84,17 @@ 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-connectint320Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.permissionsarray of stringAn array of strings defining what access a given user has to this connection.  If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list.  When this is not empty, the connection can be active only when one of the specified users is logged into an active session.  Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah".
 
-At this time only the "user" [type] is allowed.  Any other values are ignored and reserved for future use.  [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use.  All of [type], [id], and [reserved] must be valid UTF-8.read-onlybooleanFALSEThis property is deprecated and has no meaning.
+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.port-typestringSetting name of the device type of this port's controller connection (eg, "bond"), or NULL if this connection is not a port.read-onlybooleanFALSEThis property is deprecated and has no meaning.
+
+This property is deprecated since version 1.44.This property is deprecated and has no meaning.secondariesarray of stringList of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.slave-typestringSetting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.
 
-This property is deprecated since version 1.44.This property is deprecated and has no meaning.secondariesarray of stringList of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.slave-typestringSetting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.stable-idstringThis represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.
+Deprecated 1.46. Use "port-type" instead, this is just an alias.stable-idstringThis represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.
 
 The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used to derive the DHCP client identifier with ipv4.dhcp-client-id=stable, the DHCPv6 DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid] and the DHCP IAID with ipv4.iaid=stable and ipv6.iaid=stable.
 
 Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.
 
-The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$".  For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
+The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-SSID, per-boot, or every time.  The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. "${NETWORK_SSID}" uses the SSID for Wi-Fi networks and falls back to "${CONNECTION}" on other networks. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$".  For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
 
 If the value is unset, a global connection default is consulted. If the value is still unset, the default is "default${CONNECTION}" go generate an ID unique per connection profile.timestampuint640The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.
 
@@ -150,9 +154,11 @@ 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.cdma settingCDMA-based Mobile Broadband Settings.Key NameValue TypeDefault ValueValue Descriptionmtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.numberstringThe 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.passwordstringThe 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-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.usernamestringThe 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.dcb settingData Center Bridging Settings.Key NameValue TypeDefault ValueValue Descriptionapp-fcoe-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-fcoe-modestringThe FCoE controller mode; either "fabric" or "vn2vn".
+where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.cdma settingCDMA-based Mobile Broadband Settings.Key NameValue TypeDefault ValueValue Descriptionmtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.numberstringThe 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.passwordstringThe 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-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.usernamestringThe 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.dcb settingData Center Bridging Settings.Key NameValue TypeDefault ValueValue Descriptionapp-fcoe-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).app-fcoe-modestringThe FCoE controller mode; either "fabric" or "vn2vn".
+
+Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".app-fcoe-priorityint32-1The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the 0x1 (enable) flag.app-fip-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).app-fip-priorityint32-1The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the 0x1 (enable) flag.app-iscsi-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).app-iscsi-priorityint32-1The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the 0x1 (enable) flag.priority-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use.  The sum of all percentages for priorities which belong to the same group must total 100 percents.priority-flow-controlarray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.priority-flow-control-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).priority-group-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group.  Allowed values are 0 - 100, and the sum of all values must total 100 percents.priority-group-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).priority-group-idarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID.  Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.priority-strict-bandwidtharray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.priority-traffic-classarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.dummy settingDummy Link Settings.Key NameValue TypeDefault ValueValue Descriptionethtool settingEthtool Ethernet Settings.Key NameValue TypeDefault ValueValue Descriptiongeneric settingGeneric Link Settings.Key NameValue TypeDefault ValueValue Descriptiongsm settingGSM-based Mobile Broadband Settings.Key NameValue TypeDefault ValueValue DescriptionapnstringThe 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.
 
-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-priorityint32-1The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.app-fip-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-fip-priorityint32-1The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.app-iscsi-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).app-iscsi-priorityint32-1The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.priority-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use.  The sum of all percentages for priorities which belong to the same group must total 100 percents.priority-flow-controlarray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.priority-flow-control-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).priority-group-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group.  Allowed values are 0 - 100, and the sum of all values must total 100 percents.priority-group-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).priority-group-idarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID.  Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.priority-strict-bandwidtharray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.priority-traffic-classarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.dummy settingDummy Link Settings.Key NameValue TypeDefault ValueValue Descriptionethtool settingEthtool Ethernet Settings.Key NameValue TypeDefault ValueValue Descriptiongeneric settingGeneric Link Settings.Key NameValue TypeDefault ValueValue Descriptiongsm settingGSM-based Mobile Broadband Settings.Key NameValue TypeDefault ValueValue DescriptionapnstringThe 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-configbooleanFALSEWhen 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-idstringThe 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-onlybooleanFALSEWhen TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.initial-eps-bearer-apnstringFor LTE modems, this sets the APN for the initial EPS bearer that is set up when attaching to the network.  Setting this parameter implies initial-eps-bearer-configure to be TRUE.initial-eps-bearer-configurebooleanFALSEFor LTE modems, this setting determines whether the initial EPS bearer shall be configured when bringing up the connection.  It is inferred TRUE if initial-eps-bearer-apn is set.mtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.network-idstringThe 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.numberstringLegacy setting that used to help establishing PPP data sessions for GSM-based modems.
+If the APN is unset (the default) then it may be detected based on "auto-config" setting. The property can be explicitly set to the empty string to prevent that and use no APN.auto-configbooleanFALSEWhen 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-idstringThe 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-onlybooleanFALSEWhen TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.initial-eps-bearer-apnstringFor LTE modems, this sets the APN for the initial EPS bearer that is set up when attaching to the network.  Setting this parameter implies initial-eps-bearer-configure to be TRUE.initial-eps-bearer-configurebooleanFALSEFor LTE modems, this setting determines whether the initial EPS bearer shall be configured when bringing up the connection.  It is inferred TRUE if initial-eps-bearer-apn is set.mtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.network-idstringThe 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.numberstringLegacy 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.passwordstringThe 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-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.pinstringIf 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-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "pin" property.sim-idstringThe 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-idstringA 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.usernamestringThe 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.infiniband settingInfiniband Settings.Key NameValue TypeDefault ValueValue Descriptionmac-addressbyte arrayIf 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).mtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.p-keyint32-1The 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 0x8000 is set if it is a "full membership" p-key. The values 0 and 0x8000 are not allowed.
 
@@ -161,9 +167,9 @@ With the p-key set, the interface name is always "$parent.$p_key". Setting "conn
 Note that kernel will internally always set the full membership bit, although the interface name does not reflect that. Usually the user would want to configure a full membership p-key with 0x8000 flag set.parentstringThe 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-modestringThe IP-over-InfiniBand transport mode. Either "datagram" or "connected".ipv4 settingIPv4 Settings.Key NameValue TypeDefault ValueValue Descriptionaddress-dataarray of vardictArray of IPv4 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.addressesarray of array of uint32Deprecated 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-timeoutint32-1Timeout 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.
+For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.dad-timeoutint32-1Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
 
-The property is currently implemented only for IPv4.dhcp-client-idstringA 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 zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.dhcp-client-idstringA 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.
 
@@ -173,11 +179,13 @@ The special value "duid" generates a RFC4361-compliant client identifier based o
 
 The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.
 
-If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.dhcp-fqdnstringIf 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-hostnamestringIf 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-flagsuint320Flags for the DHCP hostname and FQDN.
+The special value "none" prevents any client identifier from being sent. Note that this is normally not recommended.
 
-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.
+If unset, a globally configured default from NetworkManager.conf is used. If still unset, the default depends on the DHCP plugin. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won't sent any client-id otherwise.dhcp-fqdnstringIf 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-hostnamestringIf 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-flagsuint320Flags for the DHCP hostname and FQDN.
 
-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-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
+
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.dhcp-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".
 
 For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.
 
@@ -189,15 +197,17 @@ For DHCPv4, each element must be an IPv4 address, optionally followed by a slash
 
 This property is currently not implemented for DHCPv6.dhcp-send-hostnamebooleanTRUEIf 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-timeoutint320A 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-identifierstringThe 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.dnsarray of uint32Array of IP addresses of DNS servers (as network-byte-order integers)dns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsarray of stringArray of DNS options as described in man 5 resolv.conf.
+Set to 2147483647 (MAXINT32) for infinity.dhcp-vendor-class-identifierstringThe 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.dnsarray of uint32Array of IP addresses of DNS servers (as network-byte-order integers)dns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsarray of stringArray of DNS options to be added to resolv.conf.
 
 NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
+
+In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
 
 The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
 
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.dns-priorityint320DNS servers priority.
+When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.dns-priorityint320DNS servers priority.
 
 The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
 
@@ -244,7 +254,7 @@ If the table setting is left at zero, it is eligible to be overwritten via globa
 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.routesarray of array of uint32Deprecated 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).ipv6 settingIPv6 Settings.Key NameValue TypeDefault ValueValue Descriptionaddr-gen-modeint323Configure the method for creating the IPv6 interface identifier of addresses for RFC4862 IPv6 Stateless Address Autoconfiguration and IPv6 Link Local.
 
-The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3).
+The permitted values are: 0 (eui64), 1 (stable-privacy). 2 (default-or-eui64) or 3 (default).
 
 If the property is set to "eui64", the addresses will be generated using the interface token derived from the hardware address. This makes the host part of the address constant, making it possible to track the host's presence when it changes networks. The address changes when the interface hardware is replaced. If a duplicate address is detected, there is no fallback to generate another address. When configured, the "ipv6.token" is used instead of the MAC address to generate addresses for stateless autoconfiguration.
 
@@ -257,9 +267,9 @@ For libnm, the property defaults to "default" since 1.40.  Previously it used to
 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.address-dataarray of vardictArray of IPv6 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.addressesarray 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.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-timeoutint32-1Timeout 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.
+For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.dad-timeoutint32-1Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
 
-The property is currently implemented only for IPv4.dhcp-duidstringA 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 zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.dhcp-duidstringA 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.
 
@@ -269,9 +279,9 @@ The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a D
 
 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-hostnamestringIf 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-flagsuint320Flags for the DHCP hostname and FQDN.
 
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
 
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.dhcp-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".
+When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.dhcp-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".
 
 For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.
 
@@ -283,15 +293,17 @@ For DHCPv4, each element must be an IPv4 address, optionally followed by a slash
 
 This property is currently not implemented for DHCPv6.dhcp-send-hostnamebooleanTRUEIf 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-timeoutint320A 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.dnsarray of byte arrayArray of IP addresses of DNS servers (in network byte order)dns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsarray of stringArray of DNS options as described in man 5 resolv.conf.
+Set to 2147483647 (MAXINT32) for infinity.dnsarray of byte arrayArray of IP addresses of DNS servers (in network byte order)dns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsarray of stringArray of DNS options to be added to resolv.conf.
 
 NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
 
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
+
+In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
 
 The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
 
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.dns-priorityint320DNS servers priority.
+When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.dns-priorityint320DNS servers priority.
 
 The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
 
@@ -344,7 +356,7 @@ If the table setting is left at zero, it is eligible to be overwritten via globa
 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.routesarray 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.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).tokenstringConfigure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.
 
-When set, the token is used as IPv6 interface identifier instead of the hardware address. This only applies to addresses from stateless autoconfiguration, not to IPv6 link local addresses.ip-tunnel settingIP Tunneling Settings.Key NameValue TypeDefault ValueValue Descriptionencapsulation-limituint320How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1) to ip-tunnel flags.flagsuint320Tunnel 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-labeluint320The 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-keystringThe key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.localstringThe local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.modeuint320The tunneling mode. Valid values: NM_IP_TUNNEL_MODE_IPIP (1), NM_IP_TUNNEL_MODE_GRE (2), NM_IP_TUNNEL_MODE_SIT (3), NM_IP_TUNNEL_MODE_ISATAP (4), NM_IP_TUNNEL_MODE_VTI (5), NM_IP_TUNNEL_MODE_IP6IP6 (6), NM_IP_TUNNEL_MODE_IPIP6 (7), NM_IP_TUNNEL_MODE_IP6GRE (8), NM_IP_TUNNEL_MODE_VTI6 (9), NM_IP_TUNNEL_MODE_GRETAP (10) and NM_IP_TUNNEL_MODE_IP6GRETAP (11)mtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.output-keystringThe key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.parentstringIf 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-discoverybooleanTRUEWhether to enable Path MTU Discovery on this tunnel.remotestringThe remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.tosuint320The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.ttluint320The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.macsec settingMACSec Settings.Key NameValue TypeDefault ValueValue DescriptionencryptbooleanTRUEWhether the transmitted traffic must be encrypted.mka-cakstringThe pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.mka-cak-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "mka-cak" property.mka-cknstringThe 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.modeint320Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.parentstringIf 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.portint321The port component of the SCI (Secure Channel Identifier), between 1 and 65534.send-scibooleanTRUESpecifies whether the SCI (Secure Channel Identifier) is included in every packet.validationint322Specifies the validation mode for incoming frames.macvlan settingMAC VLAN Settings.Key NameValue TypeDefault ValueValue Descriptionmodeuint320The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.parentstringIf 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.promiscuousbooleanTRUEWhether the interface should be put in promiscuous mode.tapbooleanFALSEWhether the interface should be a MACVTAP.match settingMatch settings.Key NameValue TypeDefault ValueValue Descriptiondriverarray of stringA list of driver names to match. Each element is a shell wildcard pattern.
+When set, the token is used as IPv6 interface identifier instead of the hardware address. This only applies to addresses from stateless autoconfiguration, not to IPv6 link local addresses.ip-tunnel settingIP Tunneling Settings.Key NameValue TypeDefault ValueValue Descriptionencapsulation-limituint320How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add 0x1 (ip6-ign-encap-limit) to ip-tunnel flags.flagsuint320Tunnel flags. Currently, the following values are supported: 0x1 (ip6-ign-encap-limit), 0x2 (ip6-use-orig-tclass), 0x4 (ip6-use-orig-flowlabel), 0x8 (ip6-mip6-dev), 0x10 (ip6-rcv-dscp-copy), 0x20 (ip6-use-orig-fwmark). They are valid only for IPv6 tunnels.flow-labeluint320The 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-keystringThe key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.localstringThe local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.modeuint320The tunneling mode. Valid values: 1 (ipip), 2 (gre), 3 (sit), 4 (isatap), 5 (vti), 6 (ip6ip6), 7 (ipip6), 8 (ip6gre), 9 (vti6), 10 (gretap) and 11 (ip6gretap)mtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.output-keystringThe key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.parentstringIf 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-discoverybooleanTRUEWhether to enable Path MTU Discovery on this tunnel.remotestringThe remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.tosuint320The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.ttluint320The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.macsec settingMACSec Settings.Key NameValue TypeDefault ValueValue DescriptionencryptbooleanTRUEWhether the transmitted traffic must be encrypted.mka-cakstringThe pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.mka-cak-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "mka-cak" property.mka-cknstringThe 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.modeint320Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.parentstringIf 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.portint321The port component of the SCI (Secure Channel Identifier), between 1 and 65534.send-scibooleanTRUESpecifies whether the SCI (Secure Channel Identifier) is included in every packet.validationint322Specifies the validation mode for incoming frames.macvlan settingMAC VLAN Settings.Key NameValue TypeDefault ValueValue Descriptionmodeuint320The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.parentstringIf 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.promiscuousbooleanTRUEWhether the interface should be put in promiscuous mode.tapbooleanFALSEWhether the interface should be a MACVTAP.match settingMatch settings.Key NameValue TypeDefault ValueValue Descriptiondriverarray of stringA 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-namearray of stringA list of interface names to match. Each element is a shell wildcard pattern.
 
@@ -362,13 +374,13 @@ See NMSettingMatch:interface-name for how special characters '|', '&', '!' a
 
 This is currently only implemented by dhclient DHCP plugin.ssidbyte arraySSID of the mesh network to join.ovs-bridge settingOvsBridge Link Settings.Key NameValue TypeDefault ValueValue Descriptiondatapath-typestringThe data path type. One of "system", "netdev" or empty.fail-modestringThe bridge failure mode. One of "secure", "standalone" or empty.mcast-snooping-enablebooleanFALSEEnable or disable multicast snooping.rstp-enablebooleanFALSEEnable or disable RSTP.stp-enablebooleanFALSEEnable or disable STP.ovs-dpdk settingOvsDpdk Link Settings.Key NameValue TypeDefault ValueValue DescriptiondevargsstringOpen vSwitch DPDK device arguments.n-rxquint320Open 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.ovs-interface settingOpen vSwitch Interface Settings.Key NameValue TypeDefault ValueValue Descriptionofport-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.typestringThe interface type. Either "internal", "system", "patch", "dpdk", or empty.ovs-patch settingOvsPatch Link Settings.Key NameValue TypeDefault ValueValue DescriptionpeerstringSpecifies 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 settingOvsPort Link Settings.Key NameValue TypeDefault ValueValue Descriptionbond-downdelayuint320The time port must be inactive in order to be considered down.bond-modestringBonding mode. One of "active-backup", "balance-slb", or "balance-tcp".bond-updelayuint320The time port must be active before it starts forwarding traffic.lacpstringLACP mode. One of "active", "off", or "passive".taguint320The VLAN tag in the range 0-4095.trunksarray of vardictA 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-modestringThe VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk", "dot1q-tunnel" or unset.ppp settingPoint-to-Point Protocol Settings.Key NameValue TypeDefault ValueValue Descriptionbauduint320If 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.crtsctsbooleanFALSEIf 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-failureuint320If 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-intervaluint320If 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-statefulbooleanFALSEIf TRUE, stateful MPPE is used.  See pppd documentation for more information on stateful MPPE.mruuint320If 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.mtuuint320If non-zero, instruct pppd to send packets no larger than the specified size.no-vj-compbooleanFALSEIf TRUE, Van Jacobsen TCP header compression will not be requested.noauthbooleanTRUEIf 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.nobsdcompbooleanFALSEIf TRUE, BSD compression will not be requested.nodeflatebooleanFALSEIf TRUE, "deflate" compression will not be requested.refuse-chapbooleanFALSEIf TRUE, the CHAP authentication method will not be used.refuse-eapbooleanFALSEIf TRUE, the EAP authentication method will not be used.refuse-mschapbooleanFALSEIf TRUE, the MSCHAP authentication method will not be used.refuse-mschapv2booleanFALSEIf TRUE, the MSCHAPv2 authentication method will not be used.refuse-papbooleanFALSEIf TRUE, the PAP authentication method will not be used.require-mppebooleanFALSEIf 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-128booleanFALSEIf 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.pppoe settingPPP-over-Ethernet Settings.Key NameValue TypeDefault ValueValue DescriptionparentstringIf 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.passwordstringPassword used to authenticate with the PPPoE service.password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.servicestringIf 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.usernamestringUsername used to authenticate with the PPPoE service.proxy settingWWW Proxy Settings.Key NameValue TypeDefault ValueValue Descriptionbrowser-onlybooleanFALSEWhether the proxy configuration is for browser only.methodint320Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)pac-scriptstringPAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.pac-urlstringPAC URL for obtaining PAC file.serial settingSerial Link Settings.Key NameValue TypeDefault ValueValue Descriptionbauduint3257600Speed 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.bitsuint328Byte-width of the serial communication. The 8 in "8n1" for example.paritybyteThe connection parity: 69 (ASCII 'E') for even parity, 111 (ASCII 'o') for odd, 110 (ASCII 'n') for none.send-delayuint640Time to delay between each byte sent to the modem, in microseconds.stopbitsuint321Number of stop bits for communication on the serial port.  Either 1 or 2. The 1 in "8n1" for example.sriov settingSR-IOV settings.Key NameValue TypeDefault ValueValue Descriptionautoprobe-driversNMTernary (int32)Whether to autoprobe virtual functions by a compatible driver.
+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-modestringThe VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk", "dot1q-tunnel" or unset.ppp settingPoint-to-Point Protocol Settings.Key NameValue TypeDefault ValueValue Descriptionbauduint320If 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.crtsctsbooleanFALSEIf 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-failureuint320If 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-intervaluint320If 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-statefulbooleanFALSEIf TRUE, stateful MPPE is used.  See pppd documentation for more information on stateful MPPE.mruuint320If 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.mtuuint320If non-zero, instruct pppd to send packets no larger than the specified size.no-vj-compbooleanFALSEIf TRUE, Van Jacobsen TCP header compression will not be requested.noauthbooleanTRUEIf 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.nobsdcompbooleanFALSEIf TRUE, BSD compression will not be requested.nodeflatebooleanFALSEIf TRUE, "deflate" compression will not be requested.refuse-chapbooleanFALSEIf TRUE, the CHAP authentication method will not be used.refuse-eapbooleanFALSEIf TRUE, the EAP authentication method will not be used.refuse-mschapbooleanFALSEIf TRUE, the MSCHAP authentication method will not be used.refuse-mschapv2booleanFALSEIf TRUE, the MSCHAPv2 authentication method will not be used.refuse-papbooleanFALSEIf TRUE, the PAP authentication method will not be used.require-mppebooleanFALSEIf 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-128booleanFALSEIf 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.pppoe settingPPP-over-Ethernet Settings.Key NameValue TypeDefault ValueValue DescriptionparentstringIf 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.passwordstringPassword used to authenticate with the PPPoE service.password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.servicestringIf 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.usernamestringUsername used to authenticate with the PPPoE service.proxy settingWWW Proxy Settings.Key NameValue TypeDefault ValueValue Descriptionbrowser-onlybooleanFALSEWhether the proxy configuration is for browser only.methodint320Method for proxy configuration, Default is 0 (none)pac-scriptstringPAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.pac-urlstringPAC URL for obtaining PAC file.serial settingSerial Link Settings.Key NameValue TypeDefault ValueValue Descriptionbauduint3257600Speed 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.bitsuint328Byte-width of the serial communication. The 8 in "8n1" for example.paritybyteThe connection parity: 69 (ASCII 'E') for even parity, 111 (ASCII 'o') for odd, 110 (ASCII 'n') for none.send-delayuint640Time to delay between each byte sent to the modem, in microseconds.stopbitsuint321Number of stop bits for communication on the serial port.  Either 1 or 2. The 1 in "8n1" for example.sriov settingSR-IOV settings.Key NameValue TypeDefault ValueValue Descriptionautoprobe-driversNMTernary (int32)Whether to autoprobe virtual functions by a compatible driver.
 
-If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.
+If set to 1 (true), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.
 
-If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them.
+If set to 0 (false), VFs will not be claimed and no network interfaces will be created for them.
 
-When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1).total-vfsuint320The total number of virtual functions to create.
+When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 1 (true).total-vfsuint320The 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.vfsarray of vardictArray of virtual function descriptors.
 
@@ -396,7 +408,7 @@ If the "tc" setting is not present, NetworkManager doesn't touch the qdiscs pres
 
 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.team settingTeaming Settings.Key NameValue TypeDefault ValueValue DescriptionconfigstringThe 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.interface-namestringDeprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the team's interface name.link-watchersarray of vardictLink 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-countint32-1Corresponds to the teamd mcast_rejoin.count.mcast-rejoin-intervalint32-1Corresponds to the teamd mcast_rejoin.interval.notify-peers-countint32-1Corresponds to the teamd notify_peers.count.notify-peers-intervalint32-1Corresponds to the teamd notify_peers.interval.runnerstringCorresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".runner-activebooleanTRUECorresponds to the teamd runner.active.runner-agg-select-policystringCorresponds to the teamd runner.agg_select_policy.runner-fast-ratebooleanFALSECorresponds to the teamd runner.fast_rate.runner-hwaddr-policystringCorresponds to the teamd runner.hwaddr_policy.runner-min-portsint32-1Corresponds to the teamd runner.min_ports.runner-sys-prioint32-1Corresponds to the teamd runner.sys_prio.runner-tx-balancerstringCorresponds to the teamd runner.tx_balancer.name.runner-tx-balancer-intervalint32-1Corresponds to the teamd runner.tx_balancer.interval.runner-tx-hasharray of stringCorresponds to the teamd runner.tx_hash.team-port settingTeam Port Settings.Key NameValue TypeDefault ValueValue DescriptionconfigstringThe 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-keyint32-1Corresponds to the teamd ports.PORTIFNAME.lacp_key.lacp-prioint32-1Corresponds to the teamd ports.PORTIFNAME.lacp_prio.link-watchersarray of vardictLink 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.prioint320Corresponds to the teamd ports.PORTIFNAME.prio.queue-idint32-1Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.stickybooleanFALSECorresponds to the teamd ports.PORTIFNAME.sticky.tun settingTunnel Settings.Key NameValue TypeDefault ValueValue DescriptiongroupstringThe group ID which will own the device. If set to NULL everyone will be able to use the device.modeuint321The 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-queuebooleanFALSEIf 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.ownerstringThe user ID which will own the device. If set to NULL everyone will be able to use the device.pibooleanFALSEIf TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.vnet-hdrbooleanFALSEIf TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.user settingGeneral User Profile Settings.Key NameValue TypeDefault ValueValue Descriptiondatadict 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.vlan settingVLAN Settings.Key NameValue TypeDefault ValueValue Descriptionegress-priority-maparray of stringFor 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".flagsNMVlanFlags (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).
+If the "tc" setting is not present, NetworkManager doesn't touch the filters present on the interface.team settingTeaming Settings.Key NameValue TypeDefault ValueValue DescriptionconfigstringThe 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.interface-namestringDeprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the team's interface name.link-watchersarray of vardictLink 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-countint32-1Corresponds to the teamd mcast_rejoin.count.mcast-rejoin-intervalint32-1Corresponds to the teamd mcast_rejoin.interval.notify-peers-countint32-1Corresponds to the teamd notify_peers.count.notify-peers-intervalint32-1Corresponds to the teamd notify_peers.interval.runnerstringCorresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".runner-activebooleanTRUECorresponds to the teamd runner.active.runner-agg-select-policystringCorresponds to the teamd runner.agg_select_policy.runner-fast-ratebooleanFALSECorresponds to the teamd runner.fast_rate.runner-hwaddr-policystringCorresponds to the teamd runner.hwaddr_policy.runner-min-portsint32-1Corresponds to the teamd runner.min_ports.runner-sys-prioint32-1Corresponds to the teamd runner.sys_prio.runner-tx-balancerstringCorresponds to the teamd runner.tx_balancer.name.runner-tx-balancer-intervalint32-1Corresponds to the teamd runner.tx_balancer.interval.runner-tx-hasharray of stringCorresponds to the teamd runner.tx_hash.team-port settingTeam Port Settings.Key NameValue TypeDefault ValueValue DescriptionconfigstringThe 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-keyint32-1Corresponds to the teamd ports.PORTIFNAME.lacp_key.lacp-prioint32-1Corresponds to the teamd ports.PORTIFNAME.lacp_prio.link-watchersarray of vardictLink 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.prioint320Corresponds to the teamd ports.PORTIFNAME.prio.queue-idint32-1Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.stickybooleanFALSECorresponds to the teamd ports.PORTIFNAME.sticky.tun settingTunnel Settings.Key NameValue TypeDefault ValueValue DescriptiongroupstringThe group ID which will own the device. If set to NULL everyone will be able to use the device.modeuint321The operating mode of the virtual device. Allowed values are 1 (tun) to create a layer 3 device and 2 (tap) to create an Ethernet-like layer 2 one.multi-queuebooleanFALSEIf 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.ownerstringThe user ID which will own the device. If set to NULL everyone will be able to use the device.pibooleanFALSEIf TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.vnet-hdrbooleanFALSEIf TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.user settingGeneral User Profile Settings.Key NameValue TypeDefault ValueValue Descriptiondatadict 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.vlan settingVLAN Settings.Key NameValue TypeDefault ValueValue Descriptionegress-priority-maparray of stringFor 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".flagsNMVlanFlags (uint32)One or more flags which control the behavior and features of the VLAN interface.  Flags include 0x1 (reorder-headers) (reordering of output packet headers), 0x2 (gvrp) (use of the GVRP protocol), and 0x4 (loose-binding) (loose binding of the interface to its master device's operating state). 0x8 (mvrp) (use of the MVRP protocol).
 
 The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.iduint320The 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-maparray of stringFor 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".interface-namestringDeprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the vlan's interface name.parentstringIf 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.protocolstringSpecifies the VLAN protocol to use for encapsulation.
 
@@ -418,7 +430,7 @@ If the value contains one additional MAC address after the mask, this address is
 
 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-addressbyte arrayIf specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).mac-address-blacklistarray of stringIf specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).mtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.portstringSpecific 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-nettypestrings390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.s390-optionsdict of string to string{}Dictionary of key/value pairs of s390-specific device options.  Both keys and values must be strings.  Allowed keys include "portno", "layer2", "portname", "protocol", among others.  Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).
 
-Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.s390-subchannelsarray of stringIdentifies specific subchannels that this network device uses for communication with z/VM or s390 host.  Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels.  The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.speeduint320When 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-lanuint321The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).wake-on-lan-passwordstringIf specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address.  If NULL, no password will be required.wireguard settingWireGuard Settings.Key NameValue TypeDefault ValueValue Descriptionfwmarkuint320The 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.
+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-subchannelsarray of stringIdentifies specific subchannels that this network device uses for communication with z/VM or s390 host.  Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels.  The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.speeduint320When 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-lanuint321The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of 0x2 (phy), 0x4 (unicast), 0x8 (multicast), 0x10 (broadcast), 0x20 (arp), 0x40 (magic) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).wake-on-lan-passwordstringIf specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address.  If NULL, no password will be required.wireguard settingWireGuard Settings.Key NameValue TypeDefault ValueValue Descriptionfwmarkuint320The 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-routeNMTernary (int32)Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing".
 
@@ -428,13 +440,13 @@ Leaving this at the default will enable this option automatically if ipv4.never-
 
 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-routesbooleanTRUEWhether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively.
 
-Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.peersarray of 'a{sv}'Array of dictionaries for the WireGuard peers.private-keystringThe 256 bit private-key in base64 encoding.private-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "private-key" property.802-11-wireless settingWi-Fi Settings.Key NameValue TypeDefault ValueValue Descriptionap-isolationNMTernary (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.
+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.peersarray of 'a{sv}'Array of dictionaries for the WireGuard peers.private-keystringThe 256 bit private-key in base64 encoding.private-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "private-key" property.802-11-wireless settingWi-Fi Settings.Key NameValue TypeDefault ValueValue Descriptionap-isolationNMTernary (int32)Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from -1 (default) only when the interface is configured in AP mode.
 
-If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.
+If set to 1 (true), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.
 
-If set to NM_TERNARY_FALSE (0), devices can talk to each other.
+If set to 0 (false), devices can talk to each other.
 
-When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).assigned-mac-addressstringThe new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".bandstring802.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.bssidbyte arrayIf 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.
+When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 0 (false).assigned-mac-addressstringThe new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".bandstring802.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.bssidbyte arrayIf 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.channeluint320Wireless 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.cloned-mac-addressbyte arrayThis D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".generate-mac-address-maskstringWith "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.
 
@@ -450,33 +462,33 @@ In infrastructure mode, various workarounds are used for a more reliable discove
 
 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-addressbyte arrayIf 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-blacklistarray of stringA 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-randomizationuint320One 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).
+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-addressbyte arrayIf 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-blacklistarray of stringA 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-randomizationuint320One of 0 (default) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  1 (never) (never randomize the MAC address), or 2 (always) (always randomize the MAC address).
 
-This property is deprecated since version 1.4.Use the "cloned-mac-address" property instead.modestringWi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.mtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.powersaveuint320One 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.rateuint320This property is not implemented and has no effect.
+This property is deprecated since version 1.4.Use the "cloned-mac-address" property instead.modestringWi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.mtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.powersaveuint320One of 2 (disable) (disable Wi-Fi power saving), 3 (enable) (enable Wi-Fi power saving), 1 (ignore) (don't touch currently configure setting) or 0 (default) (use the globally configured value). All other values are reserved.rateuint320This property is not implemented and has no effect.
 
 This property is deprecated since version 1.44.This property is not implemented and has no effect.securityThis property is deprecated and has no effect. For backwards compatibility, it can be set to "802-11-wireless-security" if the profile has a wireless security setting.seen-bssidsarray of stringA list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network.  NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.
 
 This is not a regular property that the user would configure. Instead, NetworkManager automatically sets the seen BSSIDs and tracks them internally in "/var/lib/NetworkManager/seen-bssids" file.ssidbyte arraySSID of the Wi-Fi network. Must be specified.tx-poweruint320This property is not implemented and has no effect.
 
-This property is deprecated since version 1.44.This property is not implemented and has no effect.wake-on-wlanuint321The 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).802-11-wireless-security settingWi-Fi Security Settings.Key NameValue TypeDefault ValueValue Descriptionauth-algstringWhen WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here.  One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP.  When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.filsint320Indicates 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.grouparray of stringA list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list.  For maximum compatibility leave this property empty.  Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".key-mgmtstringKey management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only).
+This property is deprecated since version 1.44.This property is not implemented and has no effect.wake-on-wlanuint321The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of 0x2 (any), 0x4 (disconnect), 0x8 (magic), 0x10 (gtk-rekey-failure), 0x20 (eap-identity-request), 0x40 (4way-handshake), 0x80 (rfkill-release), 0x100 (tcp) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).802-11-wireless-security settingWi-Fi Security Settings.Key NameValue TypeDefault ValueValue Descriptionauth-algstringWhen WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here.  One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP.  When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.filsint320Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection.  One of 0 (default) (use global default value), 1 (disable) (disable FILS), 2 (optional) (enable FILS if the supplicant and the access point support it) or 3 (required) (enable FILS and fail if not supported).  When set to 0 (default) and no global default is set, FILS will be optionally enabled.grouparray of stringA list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list.  For maximum compatibility leave this property empty.  Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".key-mgmtstringKey management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only).
 
-This property must be set for any Wi-Fi connection that uses security.leap-passwordstringThe login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").leap-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "leap-password" property.leap-usernamestringThe login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").pairwisearray of stringA list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty.  Each list element may be one of "tkip" or "ccmp".pmfint320Indicates 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.protoarray of stringList of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN).  If not specified, both WPA and RSN connections are allowed.pskstringPre-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-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "psk" property.wep-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.wep-key-typeNMWepKeyType (uint32)Controls the interpretation of WEP keys.  Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.wep-key0stringIndex 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key1stringIndex 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key2stringIndex 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key3stringIndex 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-tx-keyidxuint320When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here.  Valid values are 0 (default key) through 3.  Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.wps-methoduint320Flags indicating which mode of WPS is to be used if any.
+This property must be set for any Wi-Fi connection that uses security.leap-passwordstringThe login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").leap-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "leap-password" property.leap-usernamestringThe login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").pairwisearray of stringA list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty.  Each list element may be one of "tkip" or "ccmp".pmfint320Indicates whether Protected Management Frames (802.11w) must be enabled for the connection.  One of 0 (default) (use global default value), 1 (disable) (disable PMF), 2 (optional) (enable PMF if the supplicant and the access point support it) or 3 (required) (enable PMF and fail if not supported).  When set to 0 (default) and no global default is set, PMF will be optionally enabled.protoarray of stringList of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN).  If not specified, both WPA and RSN connections are allowed.pskstringPre-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-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "psk" property.wep-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.wep-key-typeNMWepKeyType (uint32)Controls the interpretation of WEP keys.  Allowed values are 1 (key), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or 2 (passphrase), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.wep-key0stringIndex 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key1stringIndex 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key2stringIndex 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key3stringIndex 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-tx-keyidxuint320When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here.  Valid values are 0 (default key) through 3.  Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.wps-methoduint320Flags indicating which mode of WPS is to be used if any.
 
 There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities.
 
 WPS can be disabled by setting this property to a value of 1.wpan settingIEEE 802.15.4 (WPAN) MAC Settings.Key NameValue TypeDefault ValueValue Descriptionchannelint32-1IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".mac-addressstringIf specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.pageint32-1IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".pan-iduint3265535IEEE 802.15.4 Personal Area Network (PAN) identifier.short-addressuint3265535Short IEEE 802.15.4 address to be used within a restricted environment.bond-port settingBond Port Settings.Key NameValue TypeDefault ValueValue Descriptionprioint320The port priority for bond active port re-selection during failover. A higher number means a higher priority in selection. The primary port has the highest priority. This option is only compatible with active-backup, balance-tlb and balance-alb modes.queue-iduint320The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.hostname settingHostname settings.Key NameValue TypeDefault ValueValue Descriptionfrom-dhcpNMTernary (int32)Whether the system hostname can be determined from DHCP on this connection.
 
-When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).from-dns-lookupNMTernary (int32)Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.
+When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 1 (true).from-dns-lookupNMTernary (int32)Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.
 
-When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).only-from-defaultNMTernary (int32)If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).
+When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 1 (true).only-from-defaultNMTernary (int32)If set to 1 (true), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).
 
-If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route.
+If set to 0 (false), the hostname can be set from this device even if it doesn't have the default route.
 
-When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).priorityint320The 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.
+When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 0 (false).priorityint320The 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.link settingLink settings.Key NameValue TypeDefault ValueValue Descriptiongro-max-sizeint64-1The maximum size of a packet built by the Generic Receive Offload stack for this device. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.gso-max-segmentsint64-1The maximum segments of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.gso-max-sizeint64-1The maximum size of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.tx-queue-lengthint64-1The size of the transmit queue for the device, in number of packets. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.loopback settingLoopback Link Settings.Key NameValue TypeDefault ValueValue Descriptionmtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.ovs-external-ids settingOVS External IDs Settings.Key NameValue TypeDefault ValueValue Descriptiondatadict of string to string{}A dictionary of key/value pairs with external-ids for OVS.ovs-other-config settingOVS Other Config Settings.Key NameValue TypeDefault ValueValue Descriptiondatadict 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 settingVeth Settings.Key NameValue TypeDefault ValueValue DescriptionpeerstringThis property specifies the peer interface name of the veth. This property is mandatory.Secret flag types:
+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.hsr settingHSR/PRP Settings.Key NameValue TypeDefault ValueValue Descriptionmulticast-specuint320The last byte of supervision address.port1stringThe port1 interface name of the HSR. This property is mandatory.port2stringThe port2 interface name of the HSR. This property is mandatory.prpbooleanFALSEThe protocol used by the interface, whether it is PRP or HSR.link settingLink settings.Key NameValue TypeDefault ValueValue Descriptiongro-max-sizeint64-1The maximum size of a packet built by the Generic Receive Offload stack for this device. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.gso-max-segmentsint64-1The maximum segments of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.gso-max-sizeint64-1The maximum size of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.tx-queue-lengthint64-1The size of the transmit queue for the device, in number of packets. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.loopback settingLoopback Link Settings.Key NameValue TypeDefault ValueValue Descriptionmtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.ovs-external-ids settingOVS External IDs Settings.Key NameValue TypeDefault ValueValue Descriptiondatadict of string to string{}A dictionary of key/value pairs with external-ids for OVS.ovs-other-config settingOVS Other Config Settings.Key NameValue TypeDefault ValueValue Descriptiondatadict 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 settingVeth Settings.Key NameValue TypeDefault ValueValue DescriptionpeerstringThis property specifies the peer interface name of the veth. This property is mandatory.Secret flag types:
             Each password or secret property in a setting has an associated flags property
             that describes how to handle that secret. The flags property is a bitfield
             that contains zero or more of the following values logically OR-ed together.
diff --git a/man/nm-settings-ifcfg-rh.5 b/man/nm-settings-ifcfg-rh.5
index 1ae6afbe..8f94a60f 100644
--- a/man/nm-settings-ifcfg-rh.5
+++ b/man/nm-settings-ifcfg-rh.5
@@ -2,12 +2,12 @@
 .\"     Title: nm-settings-ifcfg-rh
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Configuration
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NM\-SETTINGS\-IFCFG\-RH" "5" "" "NetworkManager 1\&.44\&.2" "Configuration"
+.TH "NM\-SETTINGS\-IFCFG\-RH" "5" "" "NetworkManager 1\&.45\&.90" "Configuration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -32,7 +32,7 @@ nm-settings-ifcfg-rh \- Description of \fIifcfg\-rh\fR settings plugin
 .SH "DESCRIPTION"
 .PP
 NetworkManager is based on the concept of connection profiles that contain network configuration (see
-\fBnm-settings\fR(5)
+\fBnm-settings-nmcli\fR(5)
 for details)\&. The profiles can be stored in various formats\&. NetworkManager uses plugins for reading and writing the data\&. The plugins can be configured in
 \fBNetworkManager.conf\fR(5)\&.
 .PP
@@ -2528,7 +2528,29 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&13.\ \&infiniband setting
+.B Table\ \&13.\ \&hsr setting
+.TS
+allbox tab(:);
+lB lB lB lB.
+T{
+Property
+T}:T{
+Ifcfg\-rh Variable
+T}:T{
+Default
+T}:T{
+Description
+T}
+.T&
+.
+.TE
+.sp 1
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.B Table\ \&14.\ \&infiniband setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -2605,7 +2627,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&14.\ \&ipv4 setting
+.B Table\ \&15.\ \&ipv4 setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -2807,7 +2829,7 @@ IPV4_AUTO_ROUTE_EXT_GW\fI(+)\fR
 T}:T{
 yes
 T}:T{
-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\&.
+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\&.
 T}
 T{
 replace\-local\-rule
@@ -2816,7 +2838,7 @@ IPV4_REPLACE_LOCAL_RULE\fI(+)\fR
 T}:T{
 no
 T}:T{
-Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to %TRUE\&.
+Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE\&.
 T}
 T{
 dhcp\-client\-id
@@ -2902,7 +2924,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&15.\ \&ipv6 setting
+.B Table\ \&16.\ \&ipv6 setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3113,7 +3135,7 @@ IPV6_AUTO_ROUTE_EXT_GW\fI(+)\fR
 T}:T{
 yes
 T}:T{
-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\&.
+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\&.
 T}
 T{
 replace\-local\-rule
@@ -3122,7 +3144,7 @@ IPV6_REPLACE_LOCAL_RULE\fI(+)\fR
 T}:T{
 no
 T}:T{
-Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to %TRUE\&.
+Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE\&.
 T}
 T{
 ip6\-privacy
@@ -3201,7 +3223,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&16.\ \&match setting
+.B Table\ \&17.\ \&match setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3234,7 +3256,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&17.\ \&ovs\-external\-ids setting
+.B Table\ \&18.\ \&ovs\-external\-ids setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3256,7 +3278,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&18.\ \&ovs\-other\-config setting
+.B Table\ \&19.\ \&ovs\-other\-config setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3278,7 +3300,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&19.\ \&proxy setting
+.B Table\ \&20.\ \&proxy setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3345,7 +3367,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&20.\ \&sriov setting
+.B Table\ \&21.\ \&sriov setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3402,7 +3424,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&21.\ \&tc setting
+.B Table\ \&22.\ \&tc setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3447,7 +3469,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&22.\ \&team setting
+.B Table\ \&23.\ \&team setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3478,7 +3500,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&23.\ \&team\-port setting
+.B Table\ \&24.\ \&team\-port setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3509,7 +3531,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&24.\ \&user setting
+.B Table\ \&25.\ \&user setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3542,7 +3564,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&25.\ \&vlan setting
+.B Table\ \&26.\ \&vlan setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3702,7 +3724,7 @@ unused
 /usr/share/doc/initscripts/sysconfig\&.txt
 .SH "SEE ALSO"
 .PP
-\fBnm-settings\fR(5),
+\fBnm-settings-nmcli\fR(5),
 \fBnm-settings-keyfile\fR(5),
 \fBNetworkManager\fR(8),
 \fBNetworkManager.conf\fR(5),
diff --git a/man/nm-settings-ifcfg-rh.xml b/man/nm-settings-ifcfg-rh.xml
index b19b5daa..46b6d9cf 100644
--- a/man/nm-settings-ifcfg-rh.xml
+++ b/man/nm-settings-ifcfg-rh.xml
@@ -1,8 +1,8 @@
 
 
-nm-settings-ifcfg-rhNetworkManager developersnm-settings-ifcfg-rh5NetworkManagerConfiguration1.44.2nm-settings-ifcfg-rhDescription of ifcfg-rh settings pluginDescription
+nm-settings-ifcfg-rhNetworkManager developersnm-settings-ifcfg-rh5NetworkManagerConfiguration1.45.90nm-settings-ifcfg-rhDescription of ifcfg-rh settings pluginDescription
           NetworkManager is based on the concept of connection profiles that contain
-          network configuration (see nm-settings5 for details). The profiles can be
+          network configuration (see nm-settings-nmcli5 for details). The profiles can be
           stored in various formats. NetworkManager uses plugins for reading and writing
           the data. The plugins can be configured in NetworkManager.conf5.
         
@@ -421,7 +421,7 @@ Example: HOSTNAME_FROM_DHCP=0,1HOSTNAME_FROM_DNS_LOOKUP=0,1only-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,1infiniband settingPropertyIfcfg-rh VariableDefaultDescriptionmac-addressHWADDRIBoIP 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: HOSTNAME_ONLY_FROM_DEFAULT=0,1
hsr settingPropertyIfcfg-rh VariableDefaultDescription
infiniband settingPropertyIfcfg-rh VariableDefaultDescriptionmac-addressHWADDRIBoIP 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:11mtuMTUMTU of the interface.transport-modeCONNECTED_MODECONNECTED_MODE=noCONNECTED_MODE=yes for "connected" mode, CONNECTED_MODE=no for "datagram" modep-keyPKEY_ID or PKEY_ID_NM(*) (requires 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 must be specified. Note that ifcfg-rh format will always automatically set the full membership flag 0x8000 for the PKEY_ID variable. To express IDs without the full membership flag, use PKEY_ID_NM. Note that kernel internally treats the interface as having the full membership flag set, this mainly affects the interface name. For the ifcfg file to be supported by initscripts' ifup-ib, the DEVICE= must always be set. NetworkManager does not require that.
 
@@ -439,7 +439,7 @@ Example: GATEWAY=10.5.5.1route
 
 Example: RES_OPTIONS=ndots:2 timeout:3dns-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=20auto-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.replace-local-ruleIPV4_REPLACE_LOCAL_RULE(+)noConnections will default to keep the autogenerated priority 0 local rule unless this setting is set to %TRUE.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').
+Example: IPV4_DNS_PRIORITY=20auto-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.replace-local-ruleIPV4_REPLACE_LOCAL_RULE(+)noConnections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.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').
 
 Example: DHCP_CLIENT_ID=ax-srv-1; DHCP_CLIENT_ID=01:44:44:44:44:44:44dad-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.
 
@@ -465,7 +465,7 @@ Example: DHCPV6_HOSTNAME_FLAGS=5dns-optionsIPV6_RES_OPTIONS(+)List of DNS options to be added to /etc/resolv.conf
 
-Example: IPV6_RES_OPTIONS=ndots:2 timeout:3auto-route-ext-gwIPV6_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.replace-local-ruleIPV6_REPLACE_LOCAL_RULE(+)noConnections will default to keep the autogenerated priority 0 local rule unless this setting is set to %TRUE.ip6-privacyIPV6_PRIVACY, IPV6_PRIVACY_PREFER_PUBLIC_IP(+)noConfigure IPv6 Privacy Extensions for SLAAC (RFC4941).
+Example: IPV6_RES_OPTIONS=ndots:2 timeout:3auto-route-ext-gwIPV6_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.replace-local-ruleIPV6_REPLACE_LOCAL_RULE(+)noConnections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.ip6-privacyIPV6_PRIVACY, IPV6_PRIVACY_PREFER_PUBLIC_IP(+)noConfigure IPv6 Privacy Extensions for SLAAC (RFC4941).
 
 Example: IPV6_PRIVACY=rfc3041 IPV6_PRIVACY_PREFER_PUBLIC_IP=yes
 
@@ -522,7 +522,7 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12ask - the associated password is not saved but it will be
               requested from the user each time it is required.unused - in some situations it cannot be automatically determined
               that a secret is required or not. This flag hints that the secret is not required and should
-              not be requested from the user.Files/etc/sysconfig/network-scripts/ifcfg-*/etc/sysconfig/network-scripts/keys-*/etc/sysconfig/network-scripts/route-*/etc/sysconfig/network-scripts/route6-*/usr/share/doc/initscripts/sysconfig.txtSee Alsonm-settings5,
+              not be requested from the user.Files/etc/sysconfig/network-scripts/ifcfg-*/etc/sysconfig/network-scripts/keys-*/etc/sysconfig/network-scripts/route-*/etc/sysconfig/network-scripts/route6-*/usr/share/doc/initscripts/sysconfig.txtSee Alsonm-settings-nmcli5,
         nm-settings-keyfile5,
         NetworkManager8,
         NetworkManager.conf5,
diff --git a/man/nm-settings-ifcfg-rh.xsl b/man/nm-settings-ifcfg-rh.xsl
index b389b7e9..7b270e9b 100644
--- a/man/nm-settings-ifcfg-rh.xsl
+++ b/man/nm-settings-ifcfg-rh.xsl
@@ -36,7 +36,7 @@
       Description
         
           NetworkManager is based on the concept of connection profiles that contain
-          network configuration (see nm-settings
+          network configuration (see nm-settings-nmcli
           5 for details). The profiles can be
           stored in various formats. NetworkManager uses plugins for reading and writing
           the data. The plugins can be configured in 
@@ -322,7 +322,7 @@ DEVICETYPE=TeamPort
         /usr/share/doc/initscripts/sysconfig.txt
       
       See Also
-        nm-settings5,
+        nm-settings-nmcli5,
         nm-settings-keyfile5,
         NetworkManager8,
         NetworkManager.conf5,
diff --git a/man/nm-settings-keyfile.5 b/man/nm-settings-keyfile.5
index 1f13445d..17fc8fd6 100644
--- a/man/nm-settings-keyfile.5
+++ b/man/nm-settings-keyfile.5
@@ -2,12 +2,12 @@
 .\"     Title: nm-settings-keyfile
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Configuration
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NM\-SETTINGS\-KEYFILE" "5" "" "NetworkManager 1\&.44\&.2" "Configuration"
+.TH "NM\-SETTINGS\-KEYFILE" "5" "" "NetworkManager 1\&.45\&.90" "Configuration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -32,7 +32,7 @@ nm-settings-keyfile \- Description of \fIkeyfile\fR settings plugin
 .SH "DESCRIPTION"
 .PP
 NetworkManager is based on the concept of connection profiles that contain network configuration (see
-\fBnm-settings\fR(5)
+\fBnm-settings-nmcli\fR(5)
 for details)\&. The profiles can be stored in various formats\&. NetworkManager uses plugins for reading and writing the data\&. The plugins can be configured in
 \fBNetworkManager.conf\fR(5)\&.
 .PP
@@ -47,14 +47,19 @@ and
 .PP
 The
 \fIkeyfile\fR
-config format is a simple \&.ini\-style format\&. It consists of sections (groups) of key\-value pairs\&. Each section corresponds to a setting name as described in the settings specification (\fBnm-settings\fR(5))\&. Each configuration key/value pair in the section is one of the properties listed in the settings specification\&. The majority of properties of the specification is written in the same format into the
-\fIkeyfile\fR
-too\&. However some values are inconvenient for people to use\&. These are stored in the files in more readable ways\&. These properties are described below\&. An example could be IP addresses that are not written as integer arrays, but more reasonably as "1\&.2\&.3\&.4/12 1\&.2\&.3\&.254"\&. More information of the generic key file format can be found at
+config format is a simple \&.ini\-style format\&. It consists of sections (groups) of key\-value pairs\&. More information of the generic key file format can be found at
 \m[blue]\fBGLib key file format\fR\m[]\&\s-2\u[1]\d\s+2
 (Lines beginning with a \*(Aq#\*(Aq are comments, lists are separated by character
 ;
 etc\&.)\&.
 .PP
+Each section corresponds to a setting name as described in the settings specification (\fBnm-settings-nmcli\fR(5))\&. Each key/value pair in a section is one of the properties from the specification\&.
+.PP
+The majority of properties are written in the same format as the specification into the
+\fIkeyfile\fR\&. However, some values are inconvenient for people to use so they are stored in the
+\fIkeyfile\fR
+in more readable ways\&. These properties that differ from the specification are described below\&. An example could be IP addresses that are not written as integer arrays, but more reasonably as "1\&.2\&.3\&.4/12 1\&.2\&.3\&.254"\&. Also, some lists of complex values (addresses, routes, routing\-rules), instead of using a semicolon separated list, use one key\-value pair per list element, with the key being the singular of the property name followed by the numeric index (i\&.e address1, address2, \&.\&.\&.)\&.
+.PP
 Users can create or modify the
 \fIkeyfile\fR
 connection files manually, even if that is not the recommended way of managing the profiles\&. However, if they choose to do that, they must inform NetworkManager about their changes (for example via
@@ -207,7 +212,7 @@ id=4
 plugin variables for the majority of NetworkManager properties have one\-to\-one mapping\&. It means a NetworkManager property is stored in the keyfile as a variable of the same name and in the same format\&. There are several exceptions to this rule, mainly for making keyfile syntax easier for humans\&. The exceptions handled specially by
 \fIkeyfile\fR
 plugin are listed below\&. Refer to
-\fBnm-settings\fR(5)
+\fBnm-settings-nmcli\fR(5)
 for all available settings and properties and their description\&.
 .PP
 \fBName aliases\fR. Some of the NetworkManager setting names are somewhat hard to type or remember\&. Therefore
@@ -431,6 +436,8 @@ T}
 l l l l
 l l l l
 l l l l
+l l l l
+l l l l
 l l l l.
 T{
 dns
@@ -476,6 +483,28 @@ List of IP routes\&.\fB
 
 Example: \fRroute1=8\&.8\&.8\&.0/24,10\&.1\&.1\&.1,77 route2=7\&.7\&.0\&.0/16
 T}
+T{
+routes (attributes)
+T}:T{
+route1_options, route2_options, \&.\&.\&.
+T}:T{
+key=val[,key=val\&.\&.\&.]
+T}:T{
+Attributes defined for the routes, if any\&. The supported attributes are explained in ipv4\&.routes entry in `man nm\-settings\-nmcli`\&.\fB
+
+Example: \fRroute1_options=mtu=1000,onlink=true
+T}
+T{
+routing\-rules
+T}:T{
+routing\-rule1, routing\-rule2, \&.\&.\&.
+T}:T{
+routing rule string
+T}:T{
+Routing rules as defined with `ip rule add`, but with mandatory fixed priority\&.\fB
+
+Example: \fRrouting\-rule1=priority 5 from 192\&.167\&.4\&.0/24 table 45
+T}
 .TE
 .sp 1
 .sp
@@ -500,6 +529,8 @@ T}
 l l l l
 l l l l
 l l l l
+l l l l
+l l l l
 l l l l.
 T{
 dns
@@ -545,6 +576,28 @@ List of IP routes\&.\fB
 
 Example: \fRroute1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11:5403
 T}
+T{
+routes (attributes)
+T}:T{
+route1_options, route2_options, \&.\&.\&.
+T}:T{
+key=val[,key=val\&.\&.\&.]
+T}:T{
+Attributes defined for the routes, if any\&. The supported attributes are explained in ipv6\&.routes entry in `man nm\-settings\-nmcli`\&.\fB
+
+Example: \fRroute1_options=mtu=1000,onlink=true
+T}
+T{
+routing\-rules
+T}:T{
+routing\-rule1, routing\-rule2, \&.\&.\&.
+T}:T{
+routing rule string
+T}:T{
+Routing rules as defined with `ip rule add`, but with mandatory fixed priority\&.\fB
+
+Example: \fRrouting\-rule1=priority 5 from 2001:4860:4860::/64 table 45
+T}
 .TE
 .sp 1
 .sp
@@ -745,7 +798,7 @@ variable is a decimal number (0 \- 7) defined as a sum of the following values:
 /etc/NetworkManager/system\-connections/*
 .SH "SEE ALSO"
 .PP
-\fBnm-settings\fR(5),
+\fBnm-settings-nmcli\fR(5),
 \fBnm-settings-ifcfg-rh\fR(5),
 \fBNetworkManager\fR(8),
 \fBNetworkManager.conf\fR(5),
diff --git a/man/nm-settings-keyfile.xml b/man/nm-settings-keyfile.xml
index 8a249541..3f61aef1 100644
--- a/man/nm-settings-keyfile.xml
+++ b/man/nm-settings-keyfile.xml
@@ -1,8 +1,8 @@
 
 
-nm-settings-keyfileNetworkManager developersnm-settings-keyfile5NetworkManagerConfiguration1.44.2nm-settings-keyfileDescription of keyfile settings pluginDescription
+nm-settings-keyfileNetworkManager developersnm-settings-keyfile5NetworkManagerConfiguration1.45.90nm-settings-keyfileDescription of keyfile settings pluginDescription
           NetworkManager is based on the concept of connection profiles that contain
-          network configuration (see nm-settings5 for details). The profiles can be
+          network configuration (see nm-settings-nmcli5 for details). The profiles can be
           stored in various formats. NetworkManager uses plugins for reading and writing
           the data. The plugins can be configured in NetworkManager.conf5.
         
@@ -18,20 +18,27 @@
           in plaintext inside the file.
         File Format
           The keyfile config format is a simple .ini-style
-          format. It consists of sections (groups) of key-value pairs. Each section
-          corresponds to a setting name as described in the settings specification
-          (nm-settings5). Each configuration key/value
-          pair in the section is one of the properties listed in the settings
-          specification. The majority of properties of the specification is written
-          in the same format into the keyfile too. However
-          some values are inconvenient for people to use. These are stored in the
-          files in more readable ways. These properties are described below.
-          An example could be IP addresses that are not written as integer arrays,
-          but more reasonably as "1.2.3.4/12 1.2.3.254".
+          format. It consists of sections (groups) of key-value pairs.
           More information of the generic key file format can be found at
           
           GLib key file format (Lines beginning with a '#' are comments,
           lists are separated by character ; etc.).
+        
+          Each section corresponds to a setting name as described in the settings
+          specification (nm-settings-nmcli5). Each key/value pair in a
+          section is one of the properties from the specification.
+        
+          The majority of properties are written in the same format as the
+          specification into the keyfile. However, some
+          values are inconvenient for people to use so they are stored in the
+          keyfile in more readable ways. These properties
+          that differ from the specification are described below.
+          An example could be IP addresses that are not written as integer arrays,
+          but more reasonably as "1.2.3.4/12 1.2.3.254".
+          Also, some lists of complex values (addresses, routes, routing-rules),
+          instead of using a semicolon separated list, use one key-value pair
+          per list element, with the key being the singular of the property name
+          followed by the numeric index (i.e address1, address2, ...).
         
           Users can create or modify the keyfile connection files
           manually, even if that is not the recommended way of managing the profiles.
@@ -129,7 +136,7 @@ id=4
           There are several exceptions to this rule, mainly for making keyfile syntax easier
           for humans. The exceptions handled specially by keyfile
           plugin are listed below. Refer to
-          nm-settings5
+          nm-settings-nmcli5
           for all available settings and properties and their description.
         Name aliases
             Some of the NetworkManager setting names are somewhat hard to type or remember. Therefore
@@ -152,7 +159,11 @@ Example: address1=192.168.100.100/24 address2=10.1.1.5/24gateway=192.168.100.1routesroute1, route2, ...route/plen[,gateway,metric]List of IP routes.
 
-Example: route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16
ipv6 setting (section)PropertyKeyfile VariableFormatDescriptiondnslist of DNS IP addressesList of DNS servers.
+Example: route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16routes (attributes)route1_options, route2_options, ...key=val[,key=val...]Attributes defined for the routes, if any. The supported attributes are explained in ipv4.routes entry in `man nm-settings-nmcli`.
+
+Example: route1_options=mtu=1000,onlink=truerouting-rulesrouting-rule1, routing-rule2, ...routing rule stringRouting rules as defined with `ip rule add`, but with mandatory fixed priority.
+
+Example: routing-rule1=priority 5 from 192.167.4.0/24 table 45
ipv6 setting (section)PropertyKeyfile VariableFormatDescriptiondnslist of DNS IP addressesList of DNS servers.
 
 Example: dns=2001:4860:4860::8888;2001:4860:4860::8844;addressesaddress1, address2, ...address/plenList of static IP addresses.
 
@@ -160,7 +171,11 @@ Example: address1=abbe::cafe/96 address2=2001::1234gateway=abbe::1routesroute1, route2, ...route/plen[,gateway,metric]List of IP routes.
 
-Example: route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11:5403
serial setting (section)PropertyKeyfile VariableFormatDescriptionparity'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.
+Example: route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11:5403routes (attributes)route1_options, route2_options, ...key=val[,key=val...]Attributes defined for the routes, if any. The supported attributes are explained in ipv6.routes entry in `man nm-settings-nmcli`.
+
+Example: route1_options=mtu=1000,onlink=truerouting-rulesrouting-rule1, routing-rule2, ...routing rule stringRouting rules as defined with `ip rule add`, but with mandatory fixed priority.
+
+Example: routing-rule1=priority 5 from 2001:4860:4860::/64 table 45
serial setting (section)PropertyKeyfile VariableFormatDescriptionparity'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.
 
 Example: parity=n
vpn setting (section)PropertyKeyfile VariableFormatDescriptiondataseparate variables named after keys of the dictionaryThe keys of the data dictionary are used as variable names directly under [vpn] section.
 
@@ -175,7 +190,7 @@ Example: password=Popocatepetl

               and storing this secret; when it is required, agents will be asked to provide it.2 - (not-saved) - this secret should not be saved but should be requested
               from the user each time it is required.4 - (not-required) - in some situations it cannot be automatically determined
               that a secret is required or not. This flag hints that the secret is not required
-              and should not be requested from the user.Files/etc/NetworkManager/system-connections/*See Alsonm-settings5,
+              and should not be requested from the user.Files/etc/NetworkManager/system-connections/*See Alsonm-settings-nmcli5,
         nm-settings-ifcfg-rh5,
         NetworkManager8,
         NetworkManager.conf5,
diff --git a/man/nm-settings-keyfile.xsl b/man/nm-settings-keyfile.xsl
index d63abf0f..450cc6fd 100644
--- a/man/nm-settings-keyfile.xsl
+++ b/man/nm-settings-keyfile.xsl
@@ -32,7 +32,7 @@
       Description
         
           NetworkManager is based on the concept of connection profiles that contain
-          network configuration (see nm-settings
+          network configuration (see nm-settings-nmcli
           5 for details). The profiles can be
           stored in various formats. NetworkManager uses plugins for reading and writing
           the data. The plugins can be configured in 
@@ -54,22 +54,31 @@
       File Format
         
           The keyfile config format is a simple .ini-style
-          format. It consists of sections (groups) of key-value pairs. Each section
-          corresponds to a setting name as described in the settings specification
-          (nm-settings
-          5). Each configuration key/value
-          pair in the section is one of the properties listed in the settings
-          specification. The majority of properties of the specification is written
-          in the same format into the keyfile too. However
-          some values are inconvenient for people to use. These are stored in the
-          files in more readable ways. These properties are described below.
-          An example could be IP addresses that are not written as integer arrays,
-          but more reasonably as "1.2.3.4/12 1.2.3.254".
+          format. It consists of sections (groups) of key-value pairs.
           More information of the generic key file format can be found at
           
           GLib key file format (Lines beginning with a '#' are comments,
           lists are separated by character ; etc.).
         
+        
+          Each section corresponds to a setting name as described in the settings
+          specification (nm-settings-nmcli
+          5). Each key/value pair in a
+          section is one of the properties from the specification.
+        
+        
+          The majority of properties are written in the same format as the
+          specification into the keyfile. However, some
+          values are inconvenient for people to use so they are stored in the
+          keyfile in more readable ways. These properties
+          that differ from the specification are described below.
+          An example could be IP addresses that are not written as integer arrays,
+          but more reasonably as "1.2.3.4/12 1.2.3.254".
+          Also, some lists of complex values (addresses, routes, routing-rules),
+          instead of using a semicolon separated list, use one key-value pair
+          per list element, with the key being the singular of the property name
+          followed by the numeric index (i.e address1, address2, ...).
+        
         
           Users can create or modify the keyfile connection files
           manually, even if that is not the recommended way of managing the profiles.
@@ -195,7 +204,7 @@ id=4
           There are several exceptions to this rule, mainly for making keyfile syntax easier
           for humans. The exceptions handled specially by keyfile
           plugin are listed below. Refer to
-          nm-settings5
+          nm-settings-nmcli5
           for all available settings and properties and their description.
         
         Name aliases
@@ -246,7 +255,7 @@ id=4
       
 
       See Also
-        nm-settings5,
+        nm-settings-nmcli5,
         nm-settings-ifcfg-rh5,
         NetworkManager8,
         NetworkManager.conf5,
diff --git a/man/nm-settings-nmcli.5 b/man/nm-settings-nmcli.5
index 30a3bf2f..174cf43a 100644
--- a/man/nm-settings-nmcli.5
+++ b/man/nm-settings-nmcli.5
@@ -2,12 +2,12 @@
 .\"     Title: nm-settings-nmcli
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Configuration
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.44\&.2" "Configuration"
+.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.45\&.90" "Configuration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -74,7 +74,9 @@ The number of retries for the authentication\&. Zero means to try indefinitely;
 .sp
 Currently, this only applies to 802\-1x authentication\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-1 \- 2147483647
 .RE
 .PP
 \fBconnection\&.autoconnect\fR
@@ -92,27 +94,46 @@ If multiple profiles are ready to autoconnect on the same device, the one with t
 Depending on "connection\&.multi\-connect", a profile can (auto)connect only once at a time or multiple times\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBconnection\&.autoconnect\-priority\fR
 .RS 4
 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\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-999 \- 999
 .RE
 .PP
 \fBconnection\&.autoconnect\-retries\fR
 .RS 4
 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\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-1 \- 2147483647
+.sp
+Special values: default (\-1), forever (0)
 .RE
 .PP
 \fBconnection\&.autoconnect\-slaves\fR
 .RS 4
 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\&.
 .sp
-Format: NMSettingConnectionAutoconnectSlaves (int32)
+Format: choice (NMSettingConnectionAutoconnectSlaves)
+.sp
+Valid values: default (\-1), no (0), yes (1)
+.RE
+.PP
+\fBconnection\&.controller\fR
+.RS 4
+Alias: controller
+.sp
+Interface name of the controller device or UUID of the controller connection\&.
+.sp
+Format: string
 .RE
 .PP
 \fBconnection\&.dns\-over\-tls\fR
@@ -123,14 +144,18 @@ The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "oppor
 .sp
 This feature requires a plugin which supports DNSOverTls\&. Otherwise, the setting has no effect\&. One such plugin is dns\-systemd\-resolved\&.
 .sp
-Format: int32
+Format: choice (NMSettingConnectionDnsOverTls)
+.sp
+Valid values: default (\-1), no (0), opportunistic (1), yes (2)
 .RE
 .PP
 \fBconnection\&.gateway\-ping\-timeout\fR
 .RS 4
 If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 600
 .RE
 .PP
 \fBconnection\&.id\fR
@@ -159,7 +184,9 @@ Format: string
 .RS 4
 Whether LLDP is enabled for the connection\&.
 .sp
-Format: int32
+Format: choice (NMSettingConnectionLldp)
+.sp
+Valid values: default (\-1), disable (0), enable\-rx/enable (1)
 .RE
 .PP
 \fBconnection\&.llmnr\fR
@@ -170,7 +197,9 @@ The permitted values are: "yes" (2) register hostname and resolving for the conn
 .sp
 This feature requires a plugin which supports LLMNR\&. Otherwise, the setting has no effect\&. One such plugin is dns\-systemd\-resolved\&.
 .sp
-Format: int32
+Format: choice (NMSettingConnectionLlmnr)
+.sp
+Valid values: default (\-1), no (0), resolve (1), yes (2)
 .RE
 .PP
 \fBconnection\&.master\fR
@@ -179,6 +208,8 @@ Alias: master
 .sp
 Interface name of the master device or UUID of the master connection\&.
 .sp
+Deprecated 1\&.46\&. Use "controller" instead, this is just an alias\&.
+.sp
 Format: string
 .RE
 .PP
@@ -190,7 +221,9 @@ The permitted values are: "yes" (2) register hostname and resolving for the conn
 .sp
 This feature requires a plugin which supports mDNS\&. Otherwise, the setting has no effect\&. One such plugin is dns\-systemd\-resolved\&.
 .sp
-Format: int32
+Format: choice (NMSettingConnectionMdns)
+.sp
+Valid values: default (\-1), no (0), resolve (1), yes (2)
 .RE
 .PP
 \fBconnection\&.metered\fR
@@ -199,7 +232,9 @@ Whether the connection is metered\&.
 .sp
 When updating this property on a currently activated connection, the change takes effect immediately\&.
 .sp
-Format: NMMetered (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBconnection\&.mptcp\-flags\fR
@@ -222,7 +257,9 @@ NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/
 .sp
 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)\&.
 .sp
-Format: uint32
+Format: flags (NMMptcpFlags)
+.sp
+Valid values: none/default (0x0), disabled (0x1), enabled (0x2), also\-without\-sysctl (0x4), also\-without\-default\-route (0x8), signal (0x10), subflow (0x20), backup (0x40), fullmesh (0x80)
 .RE
 .PP
 \fBconnection\&.mud\-url\fR
@@ -240,7 +277,9 @@ Format: string
 .RS 4
 Specifies whether the profile can be active multiple times at a particular moment\&. The value is of type NMConnectionMultiConnect\&.
 .sp
-Format: int32
+Format: choice (NMConnectionMultiConnect)
+.sp
+Valid values: default (0), single (1), manual\-multiple (2), multiple (3)
 .RE
 .PP
 \fBconnection\&.permissions\fR
@@ -249,14 +288,25 @@ An array of strings defining what access a given user has to this connection\&.
 .sp
 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\&.
 .sp
-Format: array of string
+Format: list of strings
+.RE
+.PP
+\fBconnection\&.port\-type\fR
+.RS 4
+Alias: port\-type
+.sp
+Setting name of the device type of this port\*(Aqs controller connection (eg, "bond"), or NULL if this connection is not a port\&.
+.sp
+Format: string
+.sp
+Valid values: bond, bridge, ovs\-bridge, ovs\-port, team, vrf
 .RE
 .PP
 \fBconnection\&.secondaries\fR
 .RS 4
 List of connection UUIDs that should be activated when the base connection itself is activated\&. Currently, only VPN connections are supported\&.
 .sp
-Format: array of string
+Format: list of strings
 .RE
 .PP
 \fBconnection\&.slave\-type\fR
@@ -265,7 +315,11 @@ Alias: slave\-type
 .sp
 Setting name of the device type of this slave\*(Aqs master connection (eg, "bond"), or NULL if this connection is not a slave\&.
 .sp
+Deprecated 1\&.46\&. Use "port\-type" instead, this is just an alias\&.
+.sp
 Format: string
+.sp
+Valid values: bond, bridge, ovs\-bridge, ovs\-port, team, vrf
 .RE
 .PP
 \fBconnection\&.stable\-id\fR
@@ -276,7 +330,7 @@ The stable\-id is used for generating IPv6 stable private addresses with ipv6\&.
 .sp
 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\*(Aqs 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\&.
 .sp
-The \*(Aq$\*(Aq character is treated special to perform dynamic substitutions at activation time\&. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}"\&. These effectively create unique IDs per\-connection, per\-device, per\-boot, or every time\&. The "${CONNECTION}" uses the profile\*(Aqs connection\&.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device\&. Any unrecognized patterns following \*(Aq$\*(Aq are treated verbatim, however are reserved for future use\&. You are thus advised to avoid \*(Aq$\*(Aq 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 \*(Aq$\*(Aq character is treated special to perform dynamic substitutions at activation time\&. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}"\&. These effectively create unique IDs per\-connection, per\-device, per\-SSID, per\-boot, or every time\&. The "${CONNECTION}" uses the profile\*(Aqs connection\&.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device\&. "${NETWORK_SSID}" uses the SSID for Wi\-Fi networks and falls back to "${CONNECTION}" on other networks\&. Any unrecognized patterns following \*(Aq$\*(Aq are treated verbatim, however are reserved for future use\&. You are thus advised to avoid \*(Aq$\*(Aq 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\&.
 .sp
 If the value is unset, a global connection default is consulted\&. If the value is still unset, the default is "default${CONNECTION}" go generate an ID unique per connection profile\&.
 .sp
@@ -289,7 +343,7 @@ The time, in seconds since the Unix Epoch, that the connection was last _success
 .sp
 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)\&.
 .sp
-Format: uint64
+Format: read only
 .RE
 .PP
 \fBconnection\&.type\fR
@@ -299,6 +353,8 @@ 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)\&.
 .sp
 Format: string
+.sp
+Valid values: 6lowpan, 802\-11\-olpc\-mesh, 802\-11\-wireless, 802\-3\-ethernet, adsl, bluetooth, bond, bridge, cdma, dummy, generic, gsm, hsr, infiniband, ip\-tunnel, loopback, macsec, macvlan, ovs\-bridge, ovs\-dpdk, ovs\-interface, ovs\-patch, ovs\-port, pppoe, team, tun, veth, vlan, vpn, vrf, vxlan, wifi\-p2p, wimax, wireguard, wpan
 .RE
 .PP
 \fBconnection\&.uuid\fR
@@ -307,7 +363,7 @@ The connection\&.uuid is the real identifier of a profile\&. It cannot change an
 .sp
 The UUID cannot be changed, except in offline mode\&. In that case, the special values "new", "generate" and "" are allowed to generate a new random UUID\&.
 .sp
-Format: a valid RFC4122 universally unique identifier (UUID)\&.
+Format: string
 .RE
 .PP
 \fBconnection\&.wait\-activation\-delay\fR
@@ -316,7 +372,9 @@ Time in milliseconds to wait for connection to be considered activated\&. The wa
 .sp
 The value 0 means no wait time\&. The default value is \-1, which currently has the same meaning as no wait time\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-1 \- 2147483647
 .RE
 .PP
 \fBconnection\&.wait\-device\-timeout\fR
@@ -325,7 +383,9 @@ Timeout in milliseconds to wait for device at startup\&. During boot, devices ma
 .sp
 The value 0 means no wait time\&. The default value is \-1, which currently has the same meaning as no wait time\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-1 \- 2147483647
 .RE
 .PP
 \fBconnection\&.zone\fR
@@ -360,7 +420,7 @@ Properties:
 .RS 4
 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\*(Aqs altSubjectName is performed\&.
 .sp
-Format: array of string
+Format: list of strings
 .RE
 .PP
 \fB802\-1x\&.anonymous\-identity\fR
@@ -374,7 +434,9 @@ Format: string
 .RS 4
 A timeout for the authentication\&. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: 0 \- 2147483647
 .RE
 .PP
 \fB802\-1x\&.ca\-cert\fR
@@ -385,7 +447,7 @@ Certificate data is specified using a "scheme"; three are currently supported: b
 .sp
 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\&.
 .sp
-Format: byte array
+Format: filesystem path
 .RE
 .PP
 \fB802\-1x\&.ca\-cert\-password\fR
@@ -399,11 +461,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "ca\-cert\-password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-1x\&.ca\-path\fR
@@ -421,7 +481,7 @@ Contains the client certificate if used by the EAP method specified in the "eap"
 .sp
 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\*(Aqs 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\&.
 .sp
-Format: byte array
+Format: filesystem path
 .RE
 .PP
 \fB802\-1x\&.client\-cert\-password\fR
@@ -435,11 +495,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "client\-cert\-password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-1x\&.domain\-match\fR
@@ -460,7 +518,9 @@ Format: string
 .RS 4
 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\&.
 .sp
-Format: array of string
+Format: list of strings
+.sp
+Valid values: leap, md5, tls, peap, ttls, sim, fast, pwd
 .RE
 .PP
 \fB802\-1x\&.identity\fR
@@ -475,6 +535,8 @@ Format: string
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fB802\-1x\&.pac\-file\fR
@@ -495,36 +557,34 @@ Format: string
 .RS 4
 Flags indicating how to handle the "password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-1x\&.password\-raw\fR
 .RS 4
 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\&.
 .sp
-Format: byte array
+Format: bytes
 .RE
 .PP
 \fB802\-1x\&.password\-raw\-flags\fR
 .RS 4
 Flags indicating how to handle the "password\-raw" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-1x\&.phase1\-auth\-flags\fR
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: flags (NMSetting8021xAuthFlags)
+.sp
+Valid values: none (0x0), tls\-1\-0\-disable (0x1), tls\-1\-1\-disable (0x2), tls\-1\-2\-disable (0x4), tls\-disable\-time\-checks (0x8), tls\-1\-3\-disable (0x10), tls\-1\-0\-enable (0x20), tls\-1\-1\-enable (0x40), tls\-1\-2\-enable (0x80), tls\-1\-3\-enable (0x100), all (0x1ff)
 .RE
 .PP
 \fB802\-1x\&.phase1\-fast\-provisioning\fR
@@ -532,6 +592,8 @@ Format: uint32
 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\&.
 .sp
 Format: string
+.sp
+Valid values: 0, 1, 2, 3
 .RE
 .PP
 \fB802\-1x\&.phase1\-peaplabel\fR
@@ -539,6 +601,8 @@ Format: 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\&.
 .sp
 Format: string
+.sp
+Valid values: 0, 1
 .RE
 .PP
 \fB802\-1x\&.phase1\-peapver\fR
@@ -546,13 +610,15 @@ Format: 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\&.
 .sp
 Format: string
+.sp
+Valid values: 0, 1
 .RE
 .PP
 \fB802\-1x\&.phase2\-altsubject\-matches\fR
 .RS 4
 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\*(Aqs altSubjectName is performed\&.
 .sp
-Format: array of string
+Format: list of strings
 .RE
 .PP
 \fB802\-1x\&.phase2\-auth\fR
@@ -560,6 +626,8 @@ Format: array of 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\&.
 .sp
 Format: string
+.sp
+Valid values: pap, chap, mschap, mschapv2, gtc, otp, md5, tls
 .RE
 .PP
 \fB802\-1x\&.phase2\-autheap\fR
@@ -567,6 +635,8 @@ Format: 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\&.
 .sp
 Format: string
+.sp
+Valid values: md5, mschapv2, otp, gtc, tls
 .RE
 .PP
 \fB802\-1x\&.phase2\-ca\-cert\fR
@@ -577,7 +647,7 @@ Certificate data is specified using a "scheme"; three are currently supported: b
 .sp
 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\&.
 .sp
-Format: byte array
+Format: filesystem path
 .RE
 .PP
 \fB802\-1x\&.phase2\-ca\-cert\-password\fR
@@ -591,11 +661,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "phase2\-ca\-cert\-password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-1x\&.phase2\-ca\-path\fR
@@ -604,7 +672,7 @@ UTF\-8 encoded path to a directory containing PEM or DER formatted certificates
 .sp
 If NMSetting8021x:system\-ca\-certs is enabled and the built\-in CA path is an existing directory, then this setting is ignored\&.
 .sp
-Format: string
+Format: filesystem path
 .RE
 .PP
 \fB802\-1x\&.phase2\-client\-cert\fR
@@ -613,7 +681,7 @@ Contains the "phase 2" client certificate if used by the EAP method specified in
 .sp
 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\*(Aqs 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\&.
 .sp
-Format: byte array
+Format: filesystem path
 .RE
 .PP
 \fB802\-1x\&.phase2\-client\-cert\-password\fR
@@ -627,11 +695,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "phase2\-client\-cert\-password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-1x\&.phase2\-domain\-match\fR
@@ -654,7 +720,7 @@ Contains the "phase 2" inner private key when the "phase2\-auth" or "phase2\-aut
 .sp
 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\*(Aqs 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\&.
 .sp
-Format: byte array
+Format: filesystem path
 .RE
 .PP
 \fB802\-1x\&.phase2\-private\-key\-password\fR
@@ -668,11 +734,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "phase2\-private\-key\-password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-1x\&.phase2\-subject\-match\fR
@@ -695,11 +759,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "pin" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-1x\&.private\-key\fR
@@ -710,7 +772,7 @@ Key data is specified using a "scheme"; two are currently supported: blob and pa
 .sp
 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\&.
 .sp
-Format: byte array
+Format: filesystem path
 .RE
 .PP
 \fB802\-1x\&.private\-key\-password\fR
@@ -724,11 +786,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "private\-key\-password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-1x\&.subject\-match\fR
@@ -745,6 +805,8 @@ Format: string
 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)\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .SS "adsl setting"
 .PP
@@ -759,6 +821,8 @@ Alias: encapsulation
 Encapsulation of ADSL connection\&. Can be "vcmux" or "llc"\&.
 .sp
 Format: string
+.sp
+Valid values: vcmux, llc
 .RE
 .PP
 \fBadsl\&.password\fR
@@ -774,11 +838,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fBadsl\&.protocol\fR
@@ -788,6 +850,8 @@ Alias: protocol
 ADSL connection protocol\&. Can be "pppoa", "pppoe" or "ipoatm"\&.
 .sp
 Format: string
+.sp
+Valid values: pppoa, pppoe, ipoatm
 .RE
 .PP
 \fBadsl\&.username\fR
@@ -803,14 +867,18 @@ Format: string
 .RS 4
 VCI of ADSL connection
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65536
 .RE
 .PP
 \fBadsl\&.vpi\fR
 .RS 4
 VPI of ADSL connection
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65536
 .RE
 .SS "bluetooth setting"
 .PP
@@ -824,7 +892,7 @@ Alias: addr
 .sp
 The Bluetooth address of the device\&.
 .sp
-Format: byte array
+Format: MAC address
 .RE
 .PP
 \fBbluetooth\&.type\fR
@@ -834,6 +902,8 @@ Alias: bt\-type
 Either "dun" for Dial\-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile\&.
 .sp
 Format: string
+.sp
+Valid values: dun, panu, nap
 .RE
 .SS "bond setting"
 .PP
@@ -845,7 +915,7 @@ Properties:
 .RS 4
 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])\&.
 .sp
-Format: dict of string to string
+Format: list of key/value options
 .RE
 .SS "bridge setting"
 .PP
@@ -859,7 +929,9 @@ Alias: ageing\-time
 .sp
 The Ethernet MAC address aging time, in seconds\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 1000000
 .RE
 .PP
 \fBbridge\&.forward\-delay\fR
@@ -868,7 +940,9 @@ Alias: forward\-delay
 .sp
 The Spanning Tree Protocol (STP) forwarding delay, in seconds\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 30
 .RE
 .PP
 \fBbridge\&.group\-address\fR
@@ -877,7 +951,7 @@ If specified, The MAC address of the multicast group this bridge uses for STP\&.
 .sp
 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\&.
 .sp
-Format: byte array
+Format: MAC address
 .RE
 .PP
 \fBbridge\&.group\-forward\-mask\fR
@@ -886,7 +960,9 @@ Alias: group\-forward\-mask
 .sp
 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\*(Aqt have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
 .RE
 .PP
 \fBbridge\&.hello\-time\fR
@@ -895,7 +971,9 @@ Alias: hello\-time
 .sp
 The Spanning Tree Protocol (STP) hello time, in seconds\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 10
 .RE
 .PP
 \fBbridge\&.mac\-address\fR
@@ -908,7 +986,7 @@ If this field is left unspecified, the "ethernet\&.cloned\-mac\-address" is refe
 .sp
 This property is deprecated since version 1\&.12\&. Use the "cloned\-mac\-address" property instead\&.
 .sp
-Format: byte array
+Format: MAC address
 .RE
 .PP
 \fBbridge\&.max\-age\fR
@@ -917,35 +995,45 @@ Alias: max\-age
 .sp
 The Spanning Tree Protocol (STP) maximum message age, in seconds\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 40
 .RE
 .PP
 \fBbridge\&.multicast\-hash\-max\fR
 .RS 4
 Set maximum size of multicast hash table (value must be a power of 2)\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 1 \- 4294967295
 .RE
 .PP
 \fBbridge\&.multicast\-last\-member\-count\fR
 .RS 4
 Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBbridge\&.multicast\-last\-member\-interval\fR
 .RS 4
 Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received\&.
 .sp
-Format: uint64
+Format: integer
+.sp
+Valid values: 0 \- 18446744073709551615
 .RE
 .PP
 \fBbridge\&.multicast\-membership\-interval\fR
 .RS 4
 Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received\&.
 .sp
-Format: uint64
+Format: integer
+.sp
+Valid values: 0 \- 18446744073709551615
 .RE
 .PP
 \fBbridge\&.multicast\-querier\fR
@@ -953,27 +1041,35 @@ Format: uint64
 Enable or disable sending of multicast queries by the bridge\&. If not specified the option is disabled\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBbridge\&.multicast\-querier\-interval\fR
 .RS 4
 If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries\&.
 .sp
-Format: uint64
+Format: integer
+.sp
+Valid values: 0 \- 18446744073709551615
 .RE
 .PP
 \fBbridge\&.multicast\-query\-interval\fR
 .RS 4
 Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase\&.
 .sp
-Format: uint64
+Format: integer
+.sp
+Valid values: 0 \- 18446744073709551615
 .RE
 .PP
 \fBbridge\&.multicast\-query\-response\-interval\fR
 .RS 4
 Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge\&.
 .sp
-Format: uint64
+Format: integer
+.sp
+Valid values: 0 \- 18446744073709551615
 .RE
 .PP
 \fBbridge\&.multicast\-query\-use\-ifaddr\fR
@@ -981,6 +1077,8 @@ Format: uint64
 If enabled the bridge\*(Aqs own IP address is used as the source address for IGMP queries otherwise the default of 0\&.0\&.0\&.0 is used\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBbridge\&.multicast\-router\fR
@@ -990,6 +1088,8 @@ Sets bridge\*(Aqs multicast router\&. Multicast\-snooping must be enabled for th
 Supported values are: \*(Aqauto\*(Aq, \*(Aqdisabled\*(Aq, \*(Aqenabled\*(Aq to which kernel assigns the numbers 1, 0, and 2, respectively\&. If not specified the default value is \*(Aqauto\*(Aq (1)\&.
 .sp
 Format: string
+.sp
+Valid values: auto, disabled, enabled
 .RE
 .PP
 \fBbridge\&.multicast\-snooping\fR
@@ -999,20 +1099,26 @@ 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBbridge\&.multicast\-startup\-query\-count\fR
 .RS 4
 Set the number of IGMP queries to send during startup phase\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBbridge\&.multicast\-startup\-query\-interval\fR
 .RS 4
 Sets the time (in deciseconds) between queries sent out at startup to determine membership information\&.
 .sp
-Format: uint64
+Format: integer
+.sp
+Valid values: 0 \- 18446744073709551615
 .RE
 .PP
 \fBbridge\&.priority\fR
@@ -1021,7 +1127,9 @@ Alias: priority
 .sp
 Sets the Spanning Tree Protocol (STP) priority for this bridge\&. Lower values are "better"; the lowest priority bridge will be elected the root bridge\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
 .RE
 .PP
 \fBbridge\&.stp\fR
@@ -1031,13 +1139,17 @@ Alias: stp
 Controls whether Spanning Tree Protocol (STP) is enabled for this bridge\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBbridge\&.vlan\-default\-pvid\fR
 .RS 4
 The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4094
 .RE
 .PP
 \fBbridge\&.vlan\-filtering\fR
@@ -1045,6 +1157,8 @@ Format: uint32
 Control whether VLAN filtering is enabled on the bridge\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBbridge\&.vlan\-protocol\fR
@@ -1054,6 +1168,8 @@ If specified, the protocol used for VLAN filtering\&.
 Supported values are: \*(Aq802\&.1Q\*(Aq, \*(Aq802\&.1ad\*(Aq\&. If not specified the default value is \*(Aq802\&.1Q\*(Aq\&.
 .sp
 Format: string
+.sp
+Valid values: 802\&.1Q, 802\&.1ad
 .RE
 .PP
 \fBbridge\&.vlan\-stats\-enabled\fR
@@ -1061,6 +1177,8 @@ Format: string
 Controls whether per\-VLAN stats accounting is enabled\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBbridge\&.vlans\fR
@@ -1073,7 +1191,7 @@ $vid [pvid] [untagged] [, $vid [pvid] [untagged]]\&.\&.\&.
 .sp
 where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash\&.
 .sp
-Format: array of vardict
+Format: list of bridge\&.vlans objects
 .RE
 .SS "bridge\-port setting"
 .PP
@@ -1088,6 +1206,8 @@ 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBbridge\-port\&.path\-cost\fR
@@ -1096,7 +1216,9 @@ Alias: path\-cost
 .sp
 The Spanning Tree Protocol (STP) port cost for destinations via this port\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
 .RE
 .PP
 \fBbridge\-port\&.priority\fR
@@ -1105,7 +1227,9 @@ Alias: priority
 .sp
 The Spanning Tree Protocol (STP) priority of this bridge port\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 63
 .RE
 .PP
 \fBbridge\-port\&.vlans\fR
@@ -1118,7 +1242,7 @@ $vid [pvid] [untagged] [, $vid [pvid] [untagged]]\&.\&.\&.
 .sp
 where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash\&.
 .sp
-Format: array of vardict
+Format: list of bridge\-port\&.vlans objects
 .RE
 .SS "cdma setting"
 .PP
@@ -1130,7 +1254,9 @@ Properties:
 .RS 4
 If non\-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .PP
 \fBcdma\&.number\fR
@@ -1153,11 +1279,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fBcdma\&.username\fR
@@ -1176,9 +1300,11 @@ Properties:
 .PP
 \fBdcb\&.app\-fcoe\-flags\fR
 .RS 4
-Specifies the NMSettingDcbFlags for the DCB FCoE application\&. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for the DCB FCoE application\&. Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4)\&.
 .sp
-Format: NMSettingDcbFlags (uint32)
+Format: flags (NMSettingDcbFlags)
+.sp
+Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)
 .RE
 .PP
 \fBdcb\&.app\-fcoe\-mode\fR
@@ -1188,97 +1314,131 @@ 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"\&.
 .sp
 Format: string
+.sp
+Valid values: fabric, vn2vn
 .RE
 .PP
 \fBdcb\&.app\-fcoe\-priority\fR
 .RS 4
-The highest User Priority (0 \- 7) which FCoE frames should use, or \-1 for default priority\&. Only used when the "app\-fcoe\-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag\&.
+The highest User Priority (0 \- 7) which FCoE frames should use, or \-1 for default priority\&. Only used when the "app\-fcoe\-flags" property includes the "enable" (0x1) flag\&.
+.sp
+Format: integer
 .sp
-Format: int32
+Valid values: \-1 \- 7
+.sp
+Special values: unset (\-1)
 .RE
 .PP
 \fBdcb\&.app\-fip\-flags\fR
 .RS 4
-Specifies the NMSettingDcbFlags for the DCB FIP application\&. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for the DCB FIP application\&. Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4)\&.
+.sp
+Format: flags (NMSettingDcbFlags)
 .sp
-Format: NMSettingDcbFlags (uint32)
+Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)
 .RE
 .PP
 \fBdcb\&.app\-fip\-priority\fR
 .RS 4
-The highest User Priority (0 \- 7) which FIP frames should use, or \-1 for default priority\&. Only used when the "app\-fip\-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag\&.
+The highest User Priority (0 \- 7) which FIP frames should use, or \-1 for default priority\&. Only used when the "app\-fip\-flags" property includes the "enable" (0x1) flag\&.
+.sp
+Format: integer
+.sp
+Valid values: \-1 \- 7
 .sp
-Format: int32
+Special values: unset (\-1)
 .RE
 .PP
 \fBdcb\&.app\-iscsi\-flags\fR
 .RS 4
-Specifies the NMSettingDcbFlags for the DCB iSCSI application\&. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for the DCB iSCSI application\&. Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4)\&.
 .sp
-Format: NMSettingDcbFlags (uint32)
+Format: flags (NMSettingDcbFlags)
+.sp
+Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)
 .RE
 .PP
 \fBdcb\&.app\-iscsi\-priority\fR
 .RS 4
-The highest User Priority (0 \- 7) which iSCSI frames should use, or \-1 for default priority\&. Only used when the "app\-iscsi\-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag\&.
+The highest User Priority (0 \- 7) which iSCSI frames should use, or \-1 for default priority\&. Only used when the "app\-iscsi\-flags" property includes the "enable" (0x1) flag\&.
+.sp
+Format: integer
+.sp
+Valid values: \-1 \- 7
 .sp
-Format: int32
+Special values: unset (\-1)
 .RE
 .PP
 \fBdcb\&.priority\-bandwidth\fR
 .RS 4
 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\*(Aqs assigned group that the priority may use\&. The sum of all percentages for priorities which belong to the same group must total 100 percents\&.
 .sp
-Format: array of uint32
+Format: list of integers
+.sp
+Valid values: 0 \- 100
 .RE
 .PP
 \fBdcb\&.priority\-flow\-control\fR
 .RS 4
 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\&.
 .sp
-Format: array of uint32
+Format: list of booleans
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBdcb\&.priority\-flow\-control\-flags\fR
 .RS 4
-Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC)\&. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC)\&. Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4)\&.
 .sp
-Format: NMSettingDcbFlags (uint32)
+Format: flags (NMSettingDcbFlags)
+.sp
+Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)
 .RE
 .PP
 \fBdcb\&.priority\-group\-bandwidth\fR
 .RS 4
 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\&.
 .sp
-Format: array of uint32
+Format: list of integers
+.sp
+Valid values: 0 \- 100
 .RE
 .PP
 \fBdcb\&.priority\-group\-flags\fR
 .RS 4
-Specifies the NMSettingDcbFlags for DCB Priority Groups\&. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4)\&.
+Specifies the NMSettingDcbFlags for DCB Priority Groups\&. Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4)\&.
 .sp
-Format: NMSettingDcbFlags (uint32)
+Format: flags (NMSettingDcbFlags)
+.sp
+Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)
 .RE
 .PP
 \fBdcb\&.priority\-group\-id\fR
 .RS 4
 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\&.
 .sp
-Format: array of uint32
+Format: list of integers
+.sp
+Valid values: 0 \- 7, 15
 .RE
 .PP
 \fBdcb\&.priority\-strict\-bandwidth\fR
 .RS 4
 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\&.
 .sp
-Format: array of uint32
+Format: list of booleans
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBdcb\&.priority\-traffic\-class\fR
 .RS 4
 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\&.
 .sp
-Format: array of uint32
+Format: list of integers
+.sp
+Valid values: 0 \- 7
 .RE
 .SS "ethtool setting"
 .PP
@@ -1286,352 +1446,648 @@ Ethtool Ethernet Settings\&.
 .PP
 Properties:
 .PP
+\fBethtool\&.channels\-combined\fR
+.RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
+.RE
+.PP
+\fBethtool\&.channels\-other\fR
+.RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
+.RE
+.PP
+\fBethtool\&.channels\-rx\fR
+.RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
+.RE
+.PP
+\fBethtool\&.channels\-tx\fR
+.RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
+.RE
+.PP
 \fBethtool\&.coalesce\-adaptive\-rx\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-adaptive\-tx\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-pkt\-rate\-high\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-pkt\-rate\-low\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-rx\-frames\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-rx\-frames\-high\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-rx\-frames\-irq\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-rx\-frames\-low\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-rx\-usecs\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-rx\-usecs\-high\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-rx\-usecs\-irq\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-rx\-usecs\-low\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-sample\-interval\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-stats\-block\-usecs\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-tx\-frames\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-tx\-frames\-high\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-tx\-frames\-irq\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-tx\-frames\-low\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-tx\-usecs\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-tx\-usecs\-high\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-tx\-usecs\-irq\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.coalesce\-tx\-usecs\-low\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
+.RE
+.PP
+\fBethtool\&.eee\-enabled\fR
+.RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-esp\-hw\-offload\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-esp\-tx\-csum\-hw\-offload\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-fcoe\-mtu\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-gro\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-gso\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-highdma\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-hw\-tc\-offload\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-l2\-fwd\-offload\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-loopback\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-lro\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-macsec\-hw\-offload\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-ntuple\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\-all\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\-fcs\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\-gro\-hw\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\-gro\-list\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\-udp\-gro\-forwarding\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\-udp_tunnel\-port\-offload\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\-vlan\-filter\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\-vlan\-stag\-filter\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rx\-vlan\-stag\-hw\-parse\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rxhash\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-rxvlan\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-sg\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tls\-hw\-record\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tls\-hw\-rx\-offload\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tls\-hw\-tx\-offload\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tso\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-checksum\-fcoe\-crc\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-checksum\-ip\-generic\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-checksum\-ipv4\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-checksum\-ipv6\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-checksum\-sctp\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-esp\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-fcoe\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-gre\-csum\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-gre\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-gso\-list\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-gso\-partial\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-gso\-robust\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-ipxip4\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-ipxip6\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-nocache\-copy\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-scatter\-gather\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-scatter\-gather\-fraglist\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-sctp\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-tcp\-ecn\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-tcp\-mangleid\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-tcp\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-tcp6\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-tunnel\-remcsum\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-udp\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-udp_tnl\-csum\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-udp_tnl\-segmentation\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-tx\-vlan\-stag\-hw\-insert\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.feature\-txvlan\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.pause\-autoneg\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.pause\-rx\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.pause\-tx\fR
 .RS 4
+Format: ternary
+.sp
+Valid values: on, off, ignore
 .RE
 .PP
 \fBethtool\&.ring\-rx\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.ring\-rx\-jumbo\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.ring\-rx\-mini\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBethtool\&.ring\-tx\fR
 .RS 4
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .SS "gsm setting"
 .PP
@@ -1645,6 +2101,8 @@ Alias: apn
 .sp
 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\*(Aqs mobile broadband plan\&. The APN may only be composed of the characters a\-z, 0\-9, \&., and \- per GSM 03\&.60 Section 14\&.9\&.
 .sp
+If the APN is unset (the default) then it may be detected based on "auto\-config" setting\&. The property can be explicitly set to the empty string to prevent that and use no APN\&.
+.sp
 Format: string
 .RE
 .PP
@@ -1653,6 +2111,8 @@ Format: string
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBgsm\&.device\-id\fR
@@ -1667,6 +2127,8 @@ Format: string
 When TRUE, only connections to the home network will be allowed\&. Connections to roaming networks will not be made\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBgsm\&.initial\-eps\-bearer\-apn\fR
@@ -1681,13 +2143,17 @@ Format: string
 For LTE modems, this setting determines whether the initial EPS bearer shall be configured when bringing up the connection\&. It is inferred TRUE if initial\-eps\-bearer\-apn is set\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBgsm\&.mtu\fR
 .RS 4
 If non\-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .PP
 \fBgsm\&.network\-id\fR
@@ -1719,11 +2185,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fBgsm\&.pin\fR
@@ -1737,11 +2201,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "pin" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fBgsm\&.sim\-id\fR
@@ -1778,7 +2240,7 @@ Alias: mac
 .sp
 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)\&.
 .sp
-Format: byte array
+Format: Infiniband MAC address
 .RE
 .PP
 \fBinfiniband\&.mtu\fR
@@ -1787,7 +2249,9 @@ Alias: mtu
 .sp
 If non\-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .PP
 \fBinfiniband\&.p\-key\fR
@@ -1800,7 +2264,11 @@ With the p\-key set, the interface name is always "$parent\&.$p_key"\&. Setting
 .sp
 Note that kernel will internally always set the full membership bit, although the interface name does not reflect that\&. Usually the user would want to configure a full membership p\-key with 0x8000 flag set\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-1 \- 65535
+.sp
+Special values: default (\-1)
 .RE
 .PP
 \fBinfiniband\&.parent\fR
@@ -1819,6 +2287,8 @@ Alias: transport\-mode
 The IP\-over\-InfiniBand transport mode\&. Either "datagram" or "connected"\&.
 .sp
 Format: string
+.sp
+Valid values: datagram, connected
 .RE
 .SS "ipv4 setting"
 .PP
@@ -1832,7 +2302,7 @@ Alias: ip4
 .sp
 A list of IPv4 addresses and their prefix length\&. Multiple addresses can be separated by comma\&. For example "192\&.168\&.1\&.5/24, 10\&.1\&.0\&.5/24"\&. The addresses are listed in decreasing priority, meaning the first address will be the primary address\&.
 .sp
-Format: a comma separated list of addresses
+Format: list of ipv4\&.addresses objects
 .RE
 .PP
 \fBipv4\&.auto\-route\-ext\-gw\fR
@@ -1841,16 +2311,22 @@ VPN connections will default to add the route automatically unless this setting
 .sp
 For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect\&.
 .sp
-Format: NMTernary (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBipv4\&.dad\-timeout\fR
 .RS 4
-Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network\&. If an address conflict is detected, the activation will fail\&. A zero value means that no duplicate address detection is performed, \-1 means the default value (either configuration ipvx\&.dad\-timeout override or zero)\&. A value greater than zero is a timeout in milliseconds\&.
+Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network\&. If an address conflict is detected, the activation will fail\&. The property is currently implemented only for IPv4\&.
+.sp
+A zero value means that no duplicate address detection is performed, \-1 means the default value (either the value configured globally in NetworkManger\&.conf or 200ms)\&. A value greater than zero is a timeout in milliseconds\&. Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property\&.
 .sp
-The property is currently implemented only for IPv4\&.
+Format: integer
 .sp
-Format: int32
+Valid values: \-1 \- 30000
+.sp
+Special values: default (\-1), off (0)
 .RE
 .PP
 \fBipv4\&.dhcp\-client\-id\fR
@@ -1865,9 +2341,13 @@ The special value "duid" generates a RFC4361\-compliant client identifier based
 .sp
 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\&.
 .sp
-If unset, a globally configured default is used\&. If still unset, the default depends on the DHCP plugin\&.
+The special value "none" prevents any client identifier from being sent\&. Note that this is normally not recommended\&.
+.sp
+If unset, a globally configured default from NetworkManager\&.conf is used\&. If still unset, the default depends on the DHCP plugin\&. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won\*(Aqt sent any client\-id otherwise\&.
 .sp
 Format: string
+.sp
+Special values: mac, perm\-mac, duid, ipv6\-duid, stable, none
 .RE
 .PP
 \fBipv4\&.dhcp\-fqdn\fR
@@ -1888,11 +2368,13 @@ Format: string
 .RS 4
 Flags for the DHCP hostname and FQDN\&.
 .sp
-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 "fqdn\-serv\-update" (0x1), "fqdn\-encoded" (0x2) and "fqdn\-no\-update" (0x4)\&. When no FQDN flag is set and "fqdn\-clear\-flags" (0x8) is set, the DHCP FQDN option will contain no flag\&. Otherwise, if no FQDN flag is set and "fqdn\-clear\-flags" (0x8) is not set, the standard FQDN flags are set in the request: "fqdn\-serv\-update" (0x1), "fqdn\-encoded" (0x2) for IPv4 and "fqdn\-serv\-update" (0x1) for IPv6\&.
+.sp
+When this property is set to the default value "none" (0x0), a global default is looked up in NetworkManager configuration\&. If that value is unset or also "none" (0x0), then the standard FQDN flags described above are sent in the DHCP requests\&.
 .sp
-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: flags (NMDhcpHostnameFlags)
 .sp
-Format: uint32
+Valid values: none (0x0), fqdn\-serv\-update (0x1), fqdn\-encoded (0x2), fqdn\-no\-update (0x4), fqdn\-clear\-flags (0x8)
 .RE
 .PP
 \fBipv4\&.dhcp\-iaid\fR
@@ -1916,7 +2398,7 @@ For DHCPv4, each element must be an IPv4 address, optionally followed by a slash
 .sp
 This property is currently not implemented for DHCPv6\&.
 .sp
-Format: array of string
+Format: list of IPv4 addresses
 .RE
 .PP
 \fBipv4\&.dhcp\-send\-hostname\fR
@@ -1924,6 +2406,8 @@ Format: array of string
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv4\&.dhcp\-timeout\fR
@@ -1932,7 +2416,11 @@ A timeout for a DHCP transaction in seconds\&. If zero (the default), a globally
 .sp
 Set to 2147483647 (MAXINT32) for infinity\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: 0 \- 2147483647
+.sp
+Special values: default (0), infinity (2147483647)
 .RE
 .PP
 \fBipv4\&.dhcp\-vendor\-class\-identifier\fR
@@ -1948,7 +2436,7 @@ Array of IP addresses of DNS servers\&.
 .sp
 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\&.
 .sp
-Format: array of uint32
+Format: list of IPv4 addresses
 .RE
 .PP
 \fBipv4\&.dns\-options\fR
@@ -1965,7 +2453,7 @@ When using a caching DNS plugin (dnsmasq or systemd\-resolved in NetworkManager\
 .sp
 The valid "ipv4\&.dns\-options" and "ipv6\&.dns\-options" get merged together\&.
 .sp
-Format: a comma separated list of DNS options
+Format: list of strings
 .RE
 .PP
 \fBipv4\&.dns\-priority\fR
@@ -1986,7 +2474,9 @@ When using dns=default, servers with higher priority will be on top of resolv\&.
 .sp
 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 \*(Aq~\&.\*(Aq 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\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
 .RE
 .PP
 \fBipv4\&.dns\-search\fR
@@ -1997,7 +2487,7 @@ When using a DNS plugin that supports Conditional Forwarding or Split DNS, then
 .sp
 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)\&.
 .sp
-Format: array of string
+Format: list of strings
 .RE
 .PP
 \fBipv4\&.gateway\fR
@@ -2010,7 +2500,7 @@ Setting the gateway causes NetworkManager to configure a standard default route
 .sp
 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"\&.
 .sp
-Format: string
+Format: IPv4 address
 .RE
 .PP
 \fBipv4\&.ignore\-auto\-dns\fR
@@ -2018,6 +2508,8 @@ Format: string
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv4\&.ignore\-auto\-routes\fR
@@ -2025,6 +2517,8 @@ Format: boolean
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv4\&.link\-local\fR
@@ -2033,7 +2527,9 @@ Enable and disable the IPv4 link\-local configuration independently of the ipv4\
 .sp
 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"\&.
 .sp
-Format: int32
+Format: choice (NMSettingIP4LinkLocal)
+.sp
+Valid values: default (0), auto (1), disabled (2), enabled (3)
 .RE
 .PP
 \fBipv4\&.may\-fail\fR
@@ -2041,6 +2537,8 @@ Format: int32
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv4\&.method\fR
@@ -2108,6 +2606,8 @@ Sets the IPv4 connection method\&. You can set one of the following values:
 .RE
 .sp
 Format: string
+.sp
+Valid values: auto, link\-local, manual, shared, disabled
 .RE
 .PP
 \fBipv4\&.never\-default\fR
@@ -2115,13 +2615,17 @@ Format: string
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv4\&.replace\-local\-rule\fR
 .RS 4
 Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE\&.
 .sp
-Format: NMTernary (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBipv4\&.required\-timeout\fR
@@ -2134,14 +2638,20 @@ Note that if "may\-fail" is FALSE for the same address family, this property has
 .sp
 A zero value means that no required timeout is present, \-1 means the default value (either configuration ipvx\&.required\-timeout override or zero)\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-1 \- 2147483647
+.sp
+Special values: default (\-1), infinity (2147483647)
 .RE
 .PP
 \fBipv4\&.route\-metric\fR
 .RS 4
 The default metric for routes that don\*(Aqt 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\*(Aqt 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\&.
 .sp
-Format: int64
+Format: integer
+.sp
+Valid values: \-1 \- 4294967295
 .RE
 .PP
 \fBipv4\&.route\-table\fR
@@ -2154,7 +2664,11 @@ If the table setting is left at zero, it is eligible to be overwritten via globa
 .sp
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
+.sp
+Special values: unspec (0), main (254)
 .RE
 .PP
 \fBipv4\&.routes\fR
@@ -2426,7 +2940,7 @@ Note that in NetworkManager, currently all nexthops of a ECMP route must share t
 .sp
 For details see also `man ip\-route`\&.
 .sp
-Format: a comma separated list of routes
+Format: list of ipv4\&.routes objects
 .RE
 .PP
 \fBipv4\&.routing\-rules\fR
@@ -2438,7 +2952,7 @@ syntax and mostly compatible\&. One difference is that routing rules in NetworkM
 Example:
 priority 5 from 192\&.167\&.4\&.0/24 table 45
 .sp
-Format: a comma separated list of routing rules
+Format: list of ipv4\&.routing\-rules objects
 .RE
 .SS "ipv6 setting"
 .PP
@@ -2462,7 +2976,9 @@ If not specified, when creating a new profile the default is "default"\&.
 .sp
 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\&.
 .sp
-Format: one of "eui64" (0), "stable\-privacy" (1), "default" (3) or "default\-or\-eui64" (2)
+Format: choice (NMSettingIP6ConfigAddrGenMode)
+.sp
+Valid values: eui64 (0), stable\-privacy (1), default\-or\-eui64 (2), default (3)
 .RE
 .PP
 \fBipv6\&.addresses\fR
@@ -2471,7 +2987,7 @@ Alias: ip6
 .sp
 A list of IPv6 addresses and their prefix length\&. Multiple addresses can be separated by comma\&. For example "2001:db8:85a3::8a2e:370:7334/64, 2001:db8:85a3::5/64"\&. The addresses are listed in decreasing priority, meaning the first address will be the primary address\&. This can make a difference with IPv6 source address selection (RFC 6724, section 5)\&.
 .sp
-Format: a comma separated list of addresses
+Format: list of ipv6\&.addresses objects
 .RE
 .PP
 \fBipv6\&.auto\-route\-ext\-gw\fR
@@ -2480,7 +2996,9 @@ VPN connections will default to add the route automatically unless this setting
 .sp
 For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect\&.
 .sp
-Format: NMTernary (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBipv6\&.dhcp\-duid\fR
@@ -2509,11 +3027,13 @@ Format: string
 .RS 4
 Flags for the DHCP hostname and FQDN\&.
 .sp
-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 "fqdn\-serv\-update" (0x1), "fqdn\-encoded" (0x2) and "fqdn\-no\-update" (0x4)\&. When no FQDN flag is set and "fqdn\-clear\-flags" (0x8) is set, the DHCP FQDN option will contain no flag\&. Otherwise, if no FQDN flag is set and "fqdn\-clear\-flags" (0x8) is not set, the standard FQDN flags are set in the request: "fqdn\-serv\-update" (0x1), "fqdn\-encoded" (0x2) for IPv4 and "fqdn\-serv\-update" (0x1) for IPv6\&.
 .sp
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration\&. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests\&.
+When this property is set to the default value "none" (0x0), a global default is looked up in NetworkManager configuration\&. If that value is unset or also "none" (0x0), then the standard FQDN flags described above are sent in the DHCP requests\&.
 .sp
-Format: uint32
+Format: flags (NMDhcpHostnameFlags)
+.sp
+Valid values: none (0x0), fqdn\-serv\-update (0x1), fqdn\-encoded (0x2), fqdn\-no\-update (0x4), fqdn\-clear\-flags (0x8)
 .RE
 .PP
 \fBipv6\&.dhcp\-iaid\fR
@@ -2541,6 +3061,8 @@ Format: string
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv6\&.dhcp\-timeout\fR
@@ -2549,7 +3071,11 @@ A timeout for a DHCP transaction in seconds\&. If zero (the default), a globally
 .sp
 Set to 2147483647 (MAXINT32) for infinity\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: 0 \- 2147483647
+.sp
+Special values: default (0), infinity (2147483647)
 .RE
 .PP
 \fBipv6\&.dns\fR
@@ -2558,7 +3084,7 @@ Array of IP addresses of DNS servers\&.
 .sp
 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\&.
 .sp
-Format: array of byte array
+Format: list of IPv6 addresses
 .RE
 .PP
 \fBipv6\&.dns\-options\fR
@@ -2575,7 +3101,7 @@ When using a caching DNS plugin (dnsmasq or systemd\-resolved in NetworkManager\
 .sp
 The valid "ipv4\&.dns\-options" and "ipv6\&.dns\-options" get merged together\&.
 .sp
-Format: a comma separated list of DNS options
+Format: list of strings
 .RE
 .PP
 \fBipv6\&.dns\-priority\fR
@@ -2596,7 +3122,9 @@ When using dns=default, servers with higher priority will be on top of resolv\&.
 .sp
 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 \*(Aq~\&.\*(Aq 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\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
 .RE
 .PP
 \fBipv6\&.dns\-search\fR
@@ -2607,7 +3135,7 @@ When using a DNS plugin that supports Conditional Forwarding or Split DNS, then
 .sp
 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)\&.
 .sp
-Format: array of string
+Format: list of strings
 .RE
 .PP
 \fBipv6\&.gateway\fR
@@ -2620,7 +3148,7 @@ Setting the gateway causes NetworkManager to configure a standard default route
 .sp
 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"\&.
 .sp
-Format: string
+Format: IPv6 address
 .RE
 .PP
 \fBipv6\&.ignore\-auto\-dns\fR
@@ -2628,6 +3156,8 @@ Format: string
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv6\&.ignore\-auto\-routes\fR
@@ -2635,6 +3165,8 @@ Format: boolean
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv6\&.ip6\-privacy\fR
@@ -2647,7 +3179,9 @@ If also global configuration is unspecified or set to "\-1", fallback to read "/
 .sp
 Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr\-gen\-mode" property\*(Aqs "stable\-privacy" setting as another way of avoiding host tracking with IPv6 addresses\&.
 .sp
-Format: NMSettingIP6ConfigPrivacy (int32)
+Format: choice (NMSettingIP6ConfigPrivacy)
+.sp
+Valid values: unknown (\-1), disabled (0), prefer\-public\-addr (1), prefer\-temp\-addr (2)
 .RE
 .PP
 \fBipv6\&.may\-fail\fR
@@ -2655,6 +3189,8 @@ Format: NMSettingIP6ConfigPrivacy (int32)
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv6\&.method\fR
@@ -2749,13 +3285,17 @@ Sets the IPv6 connection method\&. You can set one of the following values:
 If you set "auto", "dhcp", "manual", "ignore", or "shared", NetworkManager assigns, in addition to the global address, an IPv6 link\-local address to the interface\&. This is compliant with RFC 4291\&.
 .sp
 Format: string
+.sp
+Valid values: ignore, auto, dhcp, link\-local, manual, shared, disabled
 .RE
 .PP
 \fBipv6\&.mtu\fR
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .PP
 \fBipv6\&.never\-default\fR
@@ -2763,6 +3303,8 @@ Format: uint32
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBipv6\&.ra\-timeout\fR
@@ -2771,14 +3313,20 @@ A timeout for waiting Router Advertisements in seconds\&. If zero (the default),
 .sp
 Set to 2147483647 (MAXINT32) for infinity\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: 0 \- 2147483647
+.sp
+Special values: default (0), infinity (2147483647)
 .RE
 .PP
 \fBipv6\&.replace\-local\-rule\fR
 .RS 4
 Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE\&.
 .sp
-Format: NMTernary (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBipv6\&.required\-timeout\fR
@@ -2791,14 +3339,20 @@ Note that if "may\-fail" is FALSE for the same address family, this property has
 .sp
 A zero value means that no required timeout is present, \-1 means the default value (either configuration ipvx\&.required\-timeout override or zero)\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-1 \- 2147483647
+.sp
+Special values: default (\-1), infinity (2147483647)
 .RE
 .PP
 \fBipv6\&.route\-metric\fR
 .RS 4
 The default metric for routes that don\*(Aqt 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\*(Aqt 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\&.
 .sp
-Format: int64
+Format: integer
+.sp
+Valid values: \-1 \- 4294967295
 .RE
 .PP
 \fBipv6\&.route\-table\fR
@@ -2811,7 +3365,11 @@ If the table setting is left at zero, it is eligible to be overwritten via globa
 .sp
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
+.sp
+Special values: unspec (0), main (254)
 .RE
 .PP
 \fBipv6\&.routes\fR
@@ -3057,7 +3615,7 @@ unicast\&.
 .sp
 For details see also `man ip\-route`\&.
 .sp
-Format: a comma separated list of routes
+Format: list of ipv6\&.routes objects
 .RE
 .PP
 \fBipv6\&.routing\-rules\fR
@@ -3069,7 +3627,7 @@ syntax and mostly compatible\&. One difference is that routing rules in NetworkM
 Example:
 priority 5 from 1:2:3::5/128 table 45
 .sp
-Format: a comma separated list of routing rules
+Format: list of ipv6\&.routing\-rules objects
 .RE
 .PP
 \fBipv6\&.token\fR
@@ -3090,28 +3648,36 @@ Properties:
 .RS 4
 How many additional levels of encapsulation are permitted to be prepended to packets\&. This property applies only to IPv6 tunnels\&. To disable this option, add 0x1 (ip6\-ign\-encap\-limit) to ip\-tunnel flags\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 255
 .RE
 .PP
 \fBip\-tunnel\&.flags\fR
 .RS 4
 Tunnel flags\&. Currently, the following values are supported: 0x1 (ip6\-ign\-encap\-limit), 0x2 (ip6\-use\-orig\-tclass), 0x4 (ip6\-use\-orig\-flowlabel), 0x8 (ip6\-mip6\-dev), 0x10 (ip6\-rcv\-dscp\-copy) and 0x20 (ip6\-use\-orig\-fwmark)\&. They are valid only for IPv6 tunnels\&.
 .sp
-Format: uint32
+Format: flags (NMIPTunnelFlags)
+.sp
+Valid values: none (0x0), ip6\-ign\-encap\-limit (0x1), ip6\-use\-orig\-tclass (0x2), ip6\-use\-orig\-flowlabel (0x4), ip6\-mip6\-dev (0x8), ip6\-rcv\-dscp\-copy (0x10), ip6\-use\-orig\-fwmark (0x20)
 .RE
 .PP
 \fBip\-tunnel\&.flow\-label\fR
 .RS 4
 The flow label to assign to tunnel packets\&. This property applies only to IPv6 tunnels\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 1048575
 .RE
 .PP
 \fBip\-tunnel\&.fwmark\fR
 .RS 4
 The fwmark value to assign to tunnel packets\&. This property can be set to a non zero value only on VTI and VTI6 tunnels\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBip\-tunnel\&.input\-key\fR
@@ -3136,14 +3702,18 @@ Alias: mode
 .sp
 The tunneling mode\&. Valid values: ipip (1), gre (2), sit (3), isatap (4), vti (5), ip6ip6 (6), ipip6 (7), ip6gre (8), vti6 (9), gretap (10) and ip6gretap (11)
 .sp
-Format: uint32
+Format: choice (NMIPTunnelMode)
+.sp
+Valid values: ipip (1), gre (2), sit (3), isatap (4), vti (5), ip6ip6 (6), ipip6 (7), ip6gre (8), vti6 (9), gretap (10), ip6gretap (11)
 .RE
 .PP
 \fBip\-tunnel\&.mtu\fR
 .RS 4
 If non\-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .PP
 \fBip\-tunnel\&.output\-key\fR
@@ -3167,6 +3737,8 @@ Format: string
 Whether to enable Path MTU Discovery on this tunnel\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBip\-tunnel\&.remote\fR
@@ -3182,14 +3754,18 @@ Format: string
 .RS 4
 The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 255
 .RE
 .PP
 \fBip\-tunnel\&.ttl\fR
 .RS 4
 The TTL to assign to tunneled packets\&. 0 is a special value meaning that packets inherit the TTL value\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 255
 .RE
 .SS "macsec setting"
 .PP
@@ -3204,6 +3780,8 @@ Alias: encrypt
 Whether the transmitted traffic must be encrypted\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBmacsec\&.mka\-cak\fR
@@ -3219,11 +3797,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "mka\-cak" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fBmacsec\&.mka\-ckn\fR
@@ -3241,7 +3817,9 @@ Alias: mode
 .sp
 Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained\&.
 .sp
-Format: int32
+Format: choice (NMSettingMacsecMode)
+.sp
+Valid values: psk (0), eap (1)
 .RE
 .PP
 \fBmacsec\&.parent\fR
@@ -3259,7 +3837,9 @@ Alias: port
 .sp
 The port component of the SCI (Secure Channel Identifier), between 1 and 65534\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: 1 \- 65534
 .RE
 .PP
 \fBmacsec\&.send\-sci\fR
@@ -3267,13 +3847,17 @@ Format: int32
 Specifies whether the SCI (Secure Channel Identifier) is included in every packet\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBmacsec\&.validation\fR
 .RS 4
 Specifies the validation mode for incoming frames\&.
 .sp
-Format: int32
+Format: choice (NMSettingMacsecValidation)
+.sp
+Valid values: disable (0), check (1), strict (2)
 .RE
 .SS "macvlan setting"
 .PP
@@ -3287,7 +3871,9 @@ Alias: mode
 .sp
 The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device\&.
 .sp
-Format: uint32
+Format: choice (NMSettingMacvlanMode)
+.sp
+Valid values: vepa (1), bridge (2), private (3), passthru (4), source (5)
 .RE
 .PP
 \fBmacvlan\&.parent\fR
@@ -3304,6 +3890,8 @@ Format: string
 Whether the interface should be put in promiscuous mode\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBmacvlan\&.tap\fR
@@ -3313,6 +3901,8 @@ Alias: tap
 Whether the interface should be a MACVTAP\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .SS "match setting"
 .PP
@@ -3326,7 +3916,7 @@ A list of driver names to match\&. Each element is a shell wildcard pattern\&.
 .sp
 See NMSettingMatch:interface\-name for how special characters \*(Aq|\*(Aq, \*(Aq&\*(Aq, \*(Aq!\*(Aq and \*(Aq\e\e\*(Aq are used for optional and mandatory matches and inverting the pattern\&.
 .sp
-Format: array of string
+Format: list of strings
 .RE
 .PP
 \fBmatch\&.interface\-name\fR
@@ -3335,7 +3925,7 @@ A list of interface names to match\&. Each element is a shell wildcard pattern\&
 .sp
 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, "&\e\e!a" is an mandatory match for literally "!a"\&.
 .sp
-Format: array of string
+Format: list of strings
 .RE
 .PP
 \fBmatch\&.kernel\-command\-line\fR
@@ -3344,7 +3934,7 @@ A list of kernel command line arguments to match\&. This may be used to check wh
 .sp
 See NMSettingMatch:interface\-name for how special characters \*(Aq|\*(Aq, \*(Aq&\*(Aq, \*(Aq!\*(Aq and \*(Aq\e\e\*(Aq are used for optional and mandatory matches and inverting the match\&.
 .sp
-Format: array of string
+Format: list of strings
 .RE
 .PP
 \fBmatch\&.path\fR
@@ -3359,7 +3949,7 @@ Each element of the list is a shell wildcard pattern\&.
 .sp
 See NMSettingMatch:interface\-name for how special characters \*(Aq|\*(Aq, \*(Aq&\*(Aq, \*(Aq!\*(Aq and \*(Aq\e\e\*(Aq are used for optional and mandatory matches and inverting the pattern\&.
 .sp
-Format: array of string
+Format: list of strings
 .RE
 .SS "802\-11\-olpc\-mesh setting"
 .PP
@@ -3375,7 +3965,9 @@ Alias: channel
 .sp
 Channel on which the mesh network to join is located\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fB802\-11\-olpc\-mesh\&.dhcp\-anycast\-address\fR
@@ -3386,7 +3978,7 @@ Anycast DHCP MAC address used when requesting an IP address via DHCP\&. The spec
 .sp
 This is currently only implemented by dhclient DHCP plugin\&.
 .sp
-Format: byte array
+Format: MAC address
 .RE
 .PP
 \fB802\-11\-olpc\-mesh\&.ssid\fR
@@ -3395,7 +3987,7 @@ Alias: ssid
 .sp
 SSID of the mesh network to join\&.
 .sp
-Format: byte array
+Format: string
 .RE
 .SS "ovs\-bridge setting"
 .PP
@@ -3408,6 +4000,8 @@ Properties:
 The data path type\&. One of "system", "netdev" or empty\&.
 .sp
 Format: string
+.sp
+Valid values: system, netdev
 .RE
 .PP
 \fBovs\-bridge\&.fail\-mode\fR
@@ -3415,6 +4009,8 @@ Format: string
 The bridge failure mode\&. One of "secure", "standalone" or empty\&.
 .sp
 Format: string
+.sp
+Valid values: secure, standalone
 .RE
 .PP
 \fBovs\-bridge\&.mcast\-snooping\-enable\fR
@@ -3422,6 +4018,8 @@ Format: string
 Enable or disable multicast snooping\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBovs\-bridge\&.rstp\-enable\fR
@@ -3429,6 +4027,8 @@ Format: boolean
 Enable or disable RSTP\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBovs\-bridge\&.stp\-enable\fR
@@ -3436,6 +4036,8 @@ Format: boolean
 Enable or disable STP\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .SS "ovs\-dpdk setting"
 .PP
@@ -3454,21 +4056,27 @@ Format: string
 .RS 4
 Open vSwitch DPDK number of rx queues\&. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBovs\-dpdk\&.n\-rxq\-desc\fR
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4096
 .RE
 .PP
 \fBovs\-dpdk\&.n\-txq\-desc\fR
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4096
 .RE
 .SS "ovs\-interface setting"
 .PP
@@ -3480,7 +4088,9 @@ Properties:
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65279
 .RE
 .PP
 \fBovs\-interface\&.type\fR
@@ -3488,6 +4098,8 @@ Format: uint32
 The interface type\&. Either "internal", "system", "patch", "dpdk", or empty\&.
 .sp
 Format: string
+.sp
+Valid values: internal, system, patch, dpdk
 .RE
 .SS "ovs\-patch setting"
 .PP
@@ -3511,7 +4123,9 @@ Properties:
 .RS 4
 The time port must be inactive in order to be considered down\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBovs\-port\&.bond\-mode\fR
@@ -3519,13 +4133,17 @@ Format: uint32
 Bonding mode\&. One of "active\-backup", "balance\-slb", or "balance\-tcp"\&.
 .sp
 Format: string
+.sp
+Valid values: active\-backup, balance\-slb, balance\-tcp
 .RE
 .PP
 \fBovs\-port\&.bond\-updelay\fR
 .RS 4
 The time port must be active before it starts forwarding traffic\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBovs\-port\&.lacp\fR
@@ -3533,13 +4151,17 @@ Format: uint32
 LACP mode\&. One of "active", "off", or "passive"\&.
 .sp
 Format: string
+.sp
+Valid values: active, off, passive
 .RE
 .PP
 \fBovs\-port\&.tag\fR
 .RS 4
 The VLAN tag in the range 0\-4095\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4095
 .RE
 .PP
 \fBovs\-port\&.trunks\fR
@@ -3548,7 +4170,7 @@ A list of VLAN ranges that this port trunks\&.
 .sp
 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\&.
 .sp
-Format: array of vardict
+Format: list of ovs\-port\&.trunks objects
 .RE
 .PP
 \fBovs\-port\&.vlan\-mode\fR
@@ -3556,6 +4178,8 @@ Format: array of vardict
 The VLAN mode\&. One of "access", "native\-tagged", "native\-untagged", "trunk", "dot1q\-tunnel" or unset\&.
 .sp
 Format: string
+.sp
+Valid values: access, native\-tagged, native\-untagged, trunk, dot1q\-tunnel
 .RE
 .SS "ppp setting"
 .PP
@@ -3567,7 +4191,9 @@ Properties:
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBppp\&.crtscts\fR
@@ -3575,20 +4201,26 @@ Format: uint32
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.lcp\-echo\-failure\fR
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBppp\&.lcp\-echo\-interval\fR
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBppp\&.mppe\-stateful\fR
@@ -3596,20 +4228,26 @@ Format: uint32
 If TRUE, stateful MPPE is used\&. See pppd documentation for more information on stateful MPPE\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.mru\fR
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 16384
 .RE
 .PP
 \fBppp\&.mtu\fR
 .RS 4
 If non\-zero, instruct pppd to send packets no larger than the specified size\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .PP
 \fBppp\&.no\-vj\-comp\fR
@@ -3617,6 +4255,8 @@ Format: uint32
 If TRUE, Van Jacobsen TCP header compression will not be requested\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.noauth\fR
@@ -3624,6 +4264,8 @@ Format: boolean
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.nobsdcomp\fR
@@ -3631,6 +4273,8 @@ Format: boolean
 If TRUE, BSD compression will not be requested\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.nodeflate\fR
@@ -3638,6 +4282,8 @@ Format: boolean
 If TRUE, "deflate" compression will not be requested\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.refuse\-chap\fR
@@ -3645,6 +4291,8 @@ Format: boolean
 If TRUE, the CHAP authentication method will not be used\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.refuse\-eap\fR
@@ -3652,6 +4300,8 @@ Format: boolean
 If TRUE, the EAP authentication method will not be used\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.refuse\-mschap\fR
@@ -3659,6 +4309,8 @@ Format: boolean
 If TRUE, the MSCHAP authentication method will not be used\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.refuse\-mschapv2\fR
@@ -3666,6 +4318,8 @@ Format: boolean
 If TRUE, the MSCHAPv2 authentication method will not be used\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.refuse\-pap\fR
@@ -3673,6 +4327,8 @@ Format: boolean
 If TRUE, the PAP authentication method will not be used\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.require\-mppe\fR
@@ -3680,6 +4336,8 @@ Format: boolean
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBppp\&.require\-mppe\-128\fR
@@ -3687,6 +4345,8 @@ Format: boolean
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .SS "pppoe setting"
 .PP
@@ -3716,11 +4376,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fBpppoe\&.service\fR
@@ -3753,15 +4411,19 @@ Alias: browser\-only
 Whether the proxy configuration is for browser only\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBproxy\&.method\fR
 .RS 4
 Alias: method
 .sp
-Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)
+Method for proxy configuration, Default is "none" (0)
+.sp
+Format: choice (NMSettingProxyMethod)
 .sp
-Format: int32
+Valid values: none (0), auto (1)
 .RE
 .PP
 \fBproxy\&.pac\-script\fR
@@ -3791,35 +4453,45 @@ Properties:
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBserial\&.bits\fR
 .RS 4
 Byte\-width of the serial communication\&. The 8 in "8n1" for example\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 5 \- 8
 .RE
 .PP
 \fBserial\&.parity\fR
 .RS 4
 Parity setting of the serial port\&.
 .sp
-Format: NMSettingSerialParity (byte)
+Format: choice (NMSettingSerialParity)
+.sp
+Valid values: none/N/n (0), even/E/e (1), odd/O/o (2)
 .RE
 .PP
 \fBserial\&.send\-delay\fR
 .RS 4
 Time to delay between each byte sent to the modem, in microseconds\&.
 .sp
-Format: uint64
+Format: integer
+.sp
+Valid values: 0 \- 18446744073709551615
 .RE
 .PP
 \fBserial\&.stopbits\fR
 .RS 4
 Number of stop bits for communication on the serial port\&. Either 1 or 2\&. The 1 in "8n1" for example\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 1 \- 2
 .RE
 .SS "sriov setting"
 .PP
@@ -3831,13 +4503,15 @@ Properties:
 .RS 4
 Whether to autoprobe virtual functions by a compatible driver\&.
 .sp
-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 "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\&.
+.sp
+If set to "false" (0), VFs will not be claimed and no network interfaces will be created for them\&.
 .sp
-If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them\&.
+When set to "default" (\-1), the global default is used; in case the global default is unspecified it is assumed to be "true" (1)\&.
 .sp
-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: ternary
 .sp
-Format: NMTernary (int32)
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBsriov\&.total\-vfs\fR
@@ -3846,7 +4520,9 @@ The total number of virtual functions to create\&.
 .sp
 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\*(Aqt add a sriov setting to the connection\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBsriov\&.vfs\fR
@@ -3871,7 +4547,7 @@ The "vlans" attribute is represented as a semicolon\-separated list of VLAN desc
 .sp
 PROTO can be either \*(Aqq\*(Aq for 802\&.1Q (the default) or \*(Aqad\*(Aq for 802\&.1ad\&.
 .sp
-Format: array of vardict
+Format: list of sriov\&.vfs objects
 .RE
 .SS "tc setting"
 .PP
@@ -4005,7 +4681,7 @@ Limit is the number of bytes that can be queued waiting for tokens to become ava
 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\&.
 .RE
 .sp
-Format: GPtrArray(NMTCQdisc)
+Format: list of tc\&.qdiscs objects
 .RE
 .PP
 \fBtc\&.tfilters\fR
@@ -4063,7 +4739,7 @@ Action for \*(Aqsimple\*(Aq:
 The actual string to print\&.
 .RE
 .sp
-Format: GPtrArray(NMTCTfilter)
+Format: list of tc\&.tfilters objects
 .RE
 .SS "team setting"
 .PP
@@ -4084,35 +4760,51 @@ Format: string
 .RS 4
 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 \*(Aqethtool\*(Aq, \*(Aqnsna_ping\*(Aq and \*(Aqarp_ping\*(Aq and it is specified in the dictionary with the key \*(Aqname\*(Aq\&. Available keys are: ethtool: \*(Aqdelay\-up\*(Aq, \*(Aqdelay\-down\*(Aq, \*(Aqinit\-wait\*(Aq; nsna_ping: \*(Aqinit\-wait\*(Aq, \*(Aqinterval\*(Aq, \*(Aqmissed\-max\*(Aq, \*(Aqtarget\-host\*(Aq; arp_ping: all the ones in nsna_ping and \*(Aqsource\-host\*(Aq, \*(Aqvalidate\-active\*(Aq, \*(Aqvalidate\-inactive\*(Aq, \*(Aqsend\-always\*(Aq\&. See teamd\&.conf man for more details\&.
 .sp
-Format: array of vardict
+Format: list of team\&.link\-watchers objects
 .RE
 .PP
 \fBteam\&.mcast\-rejoin\-count\fR
 .RS 4
 Corresponds to the teamd mcast_rejoin\&.count\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), disabled (0)
 .RE
 .PP
 \fBteam\&.mcast\-rejoin\-interval\fR
 .RS 4
 Corresponds to the teamd mcast_rejoin\&.interval\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), default (0)
 .RE
 .PP
 \fBteam\&.notify\-peers\-count\fR
 .RS 4
 Corresponds to the teamd notify_peers\&.count\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), disabled (0)
 .RE
 .PP
 \fBteam\&.notify\-peers\-interval\fR
 .RS 4
 Corresponds to the teamd notify_peers\&.interval\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), default (0)
 .RE
 .PP
 \fBteam\&.runner\fR
@@ -4120,6 +4812,8 @@ Format: int32
 Corresponds to the teamd runner\&.name\&. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random"\&.
 .sp
 Format: string
+.sp
+Valid values: broadcast, roundrobin, random, activebackup, loadbalance, lacp
 .RE
 .PP
 \fBteam\&.runner\-active\fR
@@ -4127,6 +4821,8 @@ Format: string
 Corresponds to the teamd runner\&.active\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBteam\&.runner\-agg\-select\-policy\fR
@@ -4134,6 +4830,8 @@ Format: boolean
 Corresponds to the teamd runner\&.agg_select_policy\&.
 .sp
 Format: string
+.sp
+Valid values: lacp_prio, lacp_prio_stable, bandwidth, count, port_config
 .RE
 .PP
 \fBteam\&.runner\-fast\-rate\fR
@@ -4141,6 +4839,8 @@ Format: string
 Corresponds to the teamd runner\&.fast_rate\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBteam\&.runner\-hwaddr\-policy\fR
@@ -4148,20 +4848,30 @@ Format: boolean
 Corresponds to the teamd runner\&.hwaddr_policy\&.
 .sp
 Format: string
+.sp
+Valid values: same_all, by_active, only_active
 .RE
 .PP
 \fBteam\&.runner\-min\-ports\fR
 .RS 4
 Corresponds to the teamd runner\&.min_ports\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), default (1)
 .RE
 .PP
 \fBteam\&.runner\-sys\-prio\fR
 .RS 4
 Corresponds to the teamd runner\&.sys_prio\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), default (65535)
 .RE
 .PP
 \fBteam\&.runner\-tx\-balancer\fR
@@ -4169,20 +4879,28 @@ Format: int32
 Corresponds to the teamd runner\&.tx_balancer\&.name\&.
 .sp
 Format: string
+.sp
+Valid values: basic
 .RE
 .PP
 \fBteam\&.runner\-tx\-balancer\-interval\fR
 .RS 4
 Corresponds to the teamd runner\&.tx_balancer\&.interval\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), default (50)
 .RE
 .PP
 \fBteam\&.runner\-tx\-hash\fR
 .RS 4
 Corresponds to the teamd runner\&.tx_hash\&.
 .sp
-Format: array of string
+Format: list of strings
+.sp
+Valid values: eth, vlan, ipv4, ipv6, ip, l3, tcp, udp, sctp, l4
 .RE
 .SS "team\-port setting"
 .PP
@@ -4203,35 +4921,51 @@ Format: string
 .RS 4
 Corresponds to the teamd ports\&.PORTIFNAME\&.lacp_key\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), default (0)
 .RE
 .PP
 \fBteam\-port\&.lacp\-prio\fR
 .RS 4
 Corresponds to the teamd ports\&.PORTIFNAME\&.lacp_prio\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), default (255)
 .RE
 .PP
 \fBteam\-port\&.link\-watchers\fR
 .RS 4
 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 \*(Aqethtool\*(Aq, \*(Aqnsna_ping\*(Aq and \*(Aqarp_ping\*(Aq and it is specified in the dictionary with the key \*(Aqname\*(Aq\&. Available keys are: ethtool: \*(Aqdelay\-up\*(Aq, \*(Aqdelay\-down\*(Aq, \*(Aqinit\-wait\*(Aq; nsna_ping: \*(Aqinit\-wait\*(Aq, \*(Aqinterval\*(Aq, \*(Aqmissed\-max\*(Aq, \*(Aqtarget\-host\*(Aq; arp_ping: all the ones in nsna_ping and \*(Aqsource\-host\*(Aq, \*(Aqvalidate\-active\*(Aq, \*(Aqvalidate\-inactive\*(Aq, \*(Aqsend\-always\*(Aq\&. See teamd\&.conf man for more details\&.
 .sp
-Format: array of vardict
+Format: list of team\-port\&.link\-watchers objects
 .RE
 .PP
 \fBteam\-port\&.prio\fR
 .RS 4
 Corresponds to the teamd ports\&.PORTIFNAME\&.prio\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (0), default (0)
 .RE
 .PP
 \fBteam\-port\&.queue\-id\fR
 .RS 4
 Corresponds to the teamd ports\&.PORTIFNAME\&.queue_id\&. When set to \-1 means the parameter is skipped from the json config\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.sp
+Special values: unset (\-1), default (0)
 .RE
 .PP
 \fBteam\-port\&.sticky\fR
@@ -4239,6 +4973,8 @@ Format: int32
 Corresponds to the teamd ports\&.PORTIFNAME\&.sticky\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .SS "tun setting"
 .PP
@@ -4259,9 +4995,11 @@ Format: string
 .RS 4
 Alias: mode
 .sp
-The operating mode of the virtual device\&. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet\-like layer 2 one\&.
+The operating mode of the virtual device\&. Allowed values are "tun" (1) to create a layer 3 device and "tap" (2) to create an Ethernet\-like layer 2 one\&.
+.sp
+Format: choice (NMSettingTunMode)
 .sp
-Format: uint32
+Valid values: tun (1), tap (2)
 .RE
 .PP
 \fBtun\&.multi\-queue\fR
@@ -4271,6 +5009,8 @@ 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBtun\&.owner\fR
@@ -4289,6 +5029,8 @@ Alias: pi
 If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBtun\&.vnet\-hdr\fR
@@ -4298,6 +5040,8 @@ Alias: vnet\-hdr
 If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .SS "vlan setting"
 .PP
@@ -4311,18 +5055,20 @@ Alias: egress
 .sp
 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"\&.
 .sp
-Format: array of string
+Format: list of vlan\&.egress\-priority\-map objects
 .RE
 .PP
 \fBvlan\&.flags\fR
 .RS 4
 Alias: flags
 .sp
-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\*(Aqs operating state)\&. NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol)\&.
+One or more flags which control the behavior and features of the VLAN interface\&. Flags include "reorder\-headers" (0x1) (reordering of output packet headers), "gvrp" (0x2) (use of the GVRP protocol), and "loose\-binding" (0x4) (loose binding of the interface to its master device\*(Aqs operating state)\&. "mvrp" (0x8) (use of the MVRP protocol)\&.
 .sp
 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\&.
 .sp
-Format: NMVlanFlags (uint32)
+Format: flags (NMVlanFlags)
+.sp
+Valid values: reorder\-headers (0x1), gvrp (0x2), loose\-binding (0x4), mvrp (0x8)
 .RE
 .PP
 \fBvlan\&.id\fR
@@ -4331,7 +5077,9 @@ Alias: id
 .sp
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4095
 .RE
 .PP
 \fBvlan\&.ingress\-priority\-map\fR
@@ -4340,7 +5088,7 @@ Alias: ingress
 .sp
 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"\&.
 .sp
-Format: array of string
+Format: list of vlan\&.ingress\-priority\-map objects
 .RE
 .PP
 \fBvlan\&.parent\fR
@@ -4359,6 +5107,8 @@ Specifies the VLAN protocol to use for encapsulation\&.
 Supported values are: \*(Aq802\&.1Q\*(Aq, \*(Aq802\&.1ad\*(Aq\&. If not specified the default value is \*(Aq802\&.1Q\*(Aq\&.
 .sp
 Format: string
+.sp
+Valid values: 802\&.1Q, 802\&.1ad
 .RE
 .SS "vpn setting"
 .PP
@@ -4370,7 +5120,7 @@ Properties:
 .RS 4
 Dictionary of key/value pairs of VPN plugin specific data\&. Both keys and values must be strings\&.
 .sp
-Format: dict of string to string
+Format: list of key/value options
 .RE
 .PP
 \fBvpn\&.persistent\fR
@@ -4378,13 +5128,15 @@ Format: dict of string to string
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBvpn\&.secrets\fR
 .RS 4
 Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys\&. Both keys and values must be strings\&.
 .sp
-Format: dict of string to string
+Format: list of key/value options
 .RE
 .PP
 \fBvpn\&.service\-type\fR
@@ -4400,7 +5152,9 @@ Format: string
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBvpn\&.user\-name\fR
@@ -4423,7 +5177,9 @@ Alias: table
 .sp
 The routing table for this VRF\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .SS "vxlan setting"
 .PP
@@ -4435,7 +5191,9 @@ Properties:
 .RS 4
 Specifies the lifetime in seconds of FDB entries learnt by the kernel\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBvxlan\&.destination\-port\fR
@@ -4444,7 +5202,9 @@ Alias: destination\-port
 .sp
 Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
 .RE
 .PP
 \fBvxlan\&.id\fR
@@ -4453,7 +5213,9 @@ Alias: id
 .sp
 Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 16777215
 .RE
 .PP
 \fBvxlan\&.l2\-miss\fR
@@ -4461,6 +5223,8 @@ Format: uint32
 Specifies whether netlink LL ADDR miss notifications are generated\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBvxlan\&.l3\-miss\fR
@@ -4468,6 +5232,8 @@ Format: boolean
 Specifies whether netlink IP ADDR miss notifications are generated\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBvxlan\&.learning\fR
@@ -4475,13 +5241,17 @@ Format: boolean
 Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBvxlan\&.limit\fR
 .RS 4
 Specifies the maximum number of FDB entries\&. A value of zero means that the kernel will store unlimited entries\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBvxlan\&.local\fR
@@ -4507,6 +5277,8 @@ Format: string
 Specifies whether ARP proxy is turned on\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBvxlan\&.remote\fR
@@ -4523,6 +5295,8 @@ Format: string
 Specifies whether route short circuit is turned on\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBvxlan\&.source\-port\-max\fR
@@ -4531,7 +5305,9 @@ Alias: source\-port\-max
 .sp
 Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
 .RE
 .PP
 \fBvxlan\&.source\-port\-min\fR
@@ -4540,21 +5316,27 @@ Alias: source\-port\-min
 .sp
 Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
 .RE
 .PP
 \fBvxlan\&.tos\fR
 .RS 4
 Specifies the TOS value to use in outgoing packets\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 255
 .RE
 .PP
 \fBvxlan\&.ttl\fR
 .RS 4
 Specifies the time\-to\-live value to use in outgoing packets\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 255
 .RE
 .SS "wifi\-p2p setting"
 .PP
@@ -4568,7 +5350,7 @@ Alias: peer
 .sp
 The P2P device that should be connected to\&. Currently, this is the only way to create or join a group\&.
 .sp
-Format: string
+Format: MAC address
 .RE
 .PP
 \fBwifi\-p2p\&.wfd\-ies\fR
@@ -4577,7 +5359,7 @@ The Wi\-Fi Display (WFD) Information Elements (IEs) to set\&.
 .sp
 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\&.
 .sp
-Format: byte array
+Format: bytes
 .RE
 .PP
 \fBwifi\-p2p\&.wps\-method\fR
@@ -4586,7 +5368,9 @@ Flags indicating which mode of WPS is to be used\&.
 .sp
 There\*(Aqs little point in changing the default setting as NetworkManager will automatically determine the best method to use\&.
 .sp
-Format: uint32
+Format: flags (NMSettingWirelessSecurityWpsMethod)
+.sp
+Valid values: default (0x0), disabled (0x1), auto (0x2), pbc (0x4), pin (0x8)
 .RE
 .SS "wimax setting"
 .PP
@@ -4602,7 +5386,7 @@ If specified, this connection will only apply to the WiMAX device whose MAC addr
 .sp
 This property is deprecated since version 1\&.2\&. WiMAX is no longer supported\&.
 .sp
-Format: byte array
+Format: string
 .RE
 .PP
 \fBwimax\&.network\-name\fR
@@ -4613,7 +5397,7 @@ Network Service Provider (NSP) name of the WiMAX network this connection should
 .sp
 This property is deprecated since version 1\&.2\&. WiMAX is no longer supported\&.
 .sp
-Format: string
+Format: MAC address
 .RE
 .SS "802\-3\-ethernet setting"
 .PP
@@ -4627,7 +5411,9 @@ Properties:
 .RS 4
 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\&.
 .sp
-Format: NMTernary (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fB802\-3\-ethernet\&.auto\-negotiate\fR
@@ -4635,6 +5421,8 @@ Format: NMTernary (int32)
 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fB802\-3\-ethernet\&.cloned\-mac\-address\fR
@@ -4649,7 +5437,9 @@ If unspecified, the value can be overwritten via global defaults, see manual of
 .sp
 On D\-Bus, this field is expressed as "assigned\-mac\-address" or the deprecated "cloned\-mac\-address"\&.
 .sp
-Format: byte array
+Format: MAC address
+.sp
+Special values: preserve, permanent, random, stable
 .RE
 .PP
 \fB802\-3\-ethernet\&.duplex\fR
@@ -4657,6 +5447,8 @@ Format: byte array
 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\&.
 .sp
 Format: string
+.sp
+Valid values: half, full
 .RE
 .PP
 \fB802\-3\-ethernet\&.generate\-mac\-address\-mask\fR
@@ -4680,14 +5472,14 @@ Alias: mac
 .sp
 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)\&.
 .sp
-Format: byte array
+Format: MAC address
 .RE
 .PP
 \fB802\-3\-ethernet\&.mac\-address\-blacklist\fR
 .RS 4
 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)\&.
 .sp
-Format: array of string
+Format: list of MAC addresses
 .RE
 .PP
 \fB802\-3\-ethernet\&.mtu\fR
@@ -4696,14 +5488,16 @@ Alias: mtu
 .sp
 If non\-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .PP
 \fB802\-3\-ethernet\&.port\fR
 .RS 4
 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\&.
 .sp
-Format: string
+Format: read only
 .RE
 .PP
 \fB802\-3\-ethernet\&.s390\-nettype\fR
@@ -4711,6 +5505,8 @@ Format: string
 s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems\&.
 .sp
 Format: string
+.sp
+Valid values: qeth, lcs, ctc
 .RE
 .PP
 \fB802\-3\-ethernet\&.s390\-options\fR
@@ -4719,35 +5515,39 @@ Dictionary of key/value pairs of s390\-specific device options\&. Both keys and
 .sp
 Currently, NetworkManager itself does nothing with this information\&. However, s390utils ships a udev rule which parses this information and applies it to the interface\&.
 .sp
-Format: dict of string to string
+Format: list of key/value options
 .RE
 .PP
 \fB802\-3\-ethernet\&.s390\-subchannels\fR
 .RS 4
 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\&.
 .sp
-Format: array of string
+Format: list of 802\-3\-ethernet\&.s390\-subchannels objects
 .RE
 .PP
 \fB802\-3\-ethernet\&.speed\fR
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fB802\-3\-ethernet\&.wake\-on\-lan\fR
 .RS 4
-The NMSettingWiredWakeOnLan options to enable\&. Not all devices support all options\&. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake\-on\-LAN in NetworkManager)\&.
+The NMSettingWiredWakeOnLan options to enable\&. Not all devices support all options\&. May be any combination of "phy" (0x2), "unicast" (0x4), "multicast" (0x8), "broadcast" (0x10), "arp" (0x20), "magic" (0x40) or the special values "default" (0x1) (to use global settings) and "ignore" (0x8000) (to disable management of Wake\-on\-LAN in NetworkManager)\&.
+.sp
+Format: flags (NMSettingWiredWakeOnLan)
 .sp
-Format: uint32
+Valid values: phy (0x2), unicast (0x4), multicast (0x8), broadcast (0x10), arp (0x20), magic (0x40), default (0x1), ignore (0x8000)
 .RE
 .PP
 \fB802\-3\-ethernet\&.wake\-on\-lan\-password\fR
 .RS 4
 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\&.
 .sp
-Format: string
+Format: MAC address
 .RE
 .SS "wireguard setting"
 .PP
@@ -4761,7 +5561,9 @@ The use of fwmark is optional and is by default off\&. Setting it to 0 disables
 .sp
 Note that "ip4\-auto\-default\-route" or "ip6\-auto\-default\-route" enabled, implies to automatically choose a fwmark\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fBwireguard\&.ip4\-auto\-default\-route\fR
@@ -4772,21 +5574,27 @@ Note that for this automatism to work, you usually don\*(Aqt want to set ipv4\&.
 .sp
 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\&.
 .sp
-Format: NMTernary (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBwireguard\&.ip6\-auto\-default\-route\fR
 .RS 4
 Like ip4\-auto\-default\-route, but for the IPv6 default route\&.
 .sp
-Format: NMTernary (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBwireguard\&.listen\-port\fR
 .RS 4
 The listen\-port\&. If listen\-port is not specified, the port will be chosen randomly when the interface comes up\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
 .RE
 .PP
 \fBwireguard\&.mtu\fR
@@ -4795,7 +5603,9 @@ If non\-zero, only transmit packets of the specified size or smaller, breaking l
 .sp
 If zero a default MTU is used\&. Note that contrary to wg\-quick\*(Aqs MTU setting, this does not take into account the current routes at the time of activation\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .PP
 \fBwireguard\&.peer\-routes\fR
@@ -4805,6 +5615,8 @@ Whether to automatically add routes for the AllowedIPs ranges of the peers\&. If
 Note that if the peer\*(Aqs AllowedIPs is "0\&.0\&.0\&.0/0" or "::/0" and the profile\*(Aqs ipv4\&.never\-default or ipv6\&.never\-default setting is enabled, the peer route for this peer won\*(Aqt be added automatically\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fBwireguard\&.private\-key\fR
@@ -4818,11 +5630,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "private\-key" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .SS "802\-11\-wireless setting"
 .PP
@@ -4834,15 +5644,17 @@ Properties:
 .PP
 \fB802\-11\-wireless\&.ap\-isolation\fR
 .RS 4
-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 "default" (\-1) only when the interface is configured in AP mode\&.
 .sp
-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 "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\&.
 .sp
-If set to NM_TERNARY_FALSE (0), devices can talk to each other\&.
+If set to "false" (0), devices can talk to each other\&.
 .sp
-When set to NM_TERNARY_DEFAULT (\-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0)\&.
+When set to "default" (\-1), the global default is used; in case the global default is unspecified it is assumed to be "false" (0)\&.
 .sp
-Format: NMTernary (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fB802\-11\-wireless\&.band\fR
@@ -4850,6 +5662,8 @@ Format: NMTernary (int32)
 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\*(Aqs settings are compatible\&. This setting depends on specific driver capability and may not work with all drivers\&.
 .sp
 Format: string
+.sp
+Valid values: a, bg
 .RE
 .PP
 \fB802\-11\-wireless\&.bssid\fR
@@ -4858,14 +5672,16 @@ If specified, directs the device to only associate with the given access point\&
 .sp
 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\&.
 .sp
-Format: byte array
+Format: MAC address
 .RE
 .PP
 \fB802\-11\-wireless\&.channel\fR
 .RS 4
 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 4294967295
 .RE
 .PP
 \fB802\-11\-wireless\&.cloned\-mac\-address\fR
@@ -4874,13 +5690,15 @@ Alias: cloned\-mac
 .sp
 If specified, request that the device use this MAC address instead\&. This is known as MAC cloning or spoofing\&.
 .sp
-Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random" and "stable" are supported\&. "preserve" means not to touch the MAC address on activation\&. "permanent" means to use the permanent hardware address of the device\&. "random" creates a random MAC address on each connect\&. "stable" creates a hashed MAC address based on connection\&.stable\-id and a machine dependent key\&.
+Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random", "stable" and "stable\-ssid" are supported\&. "preserve" means not to touch the MAC address on activation\&. "permanent" means to use the permanent hardware address of the device\&. "random" creates a random MAC address on each connect\&. "stable" creates a hashed MAC address based on connection\&.stable\-id and a machine dependent key\&. "stable\-ssid" creates a hashed MAC address based on the SSID, the same as setting the stable\-id to "${NETWORK_SSID}"\&.
 .sp
 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)\&.
 .sp
 On D\-Bus, this field is expressed as "assigned\-mac\-address" or the deprecated "cloned\-mac\-address"\&.
 .sp
-Format: byte array
+Format: MAC address
+.sp
+Special values: preserve, permanent, random, stable, stable\-ssid
 .RE
 .PP
 \fB802\-11\-wireless\&.generate\-mac\-address\-mask\fR
@@ -4909,6 +5727,8 @@ 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\&.
 .sp
 Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .PP
 \fB802\-11\-wireless\&.mac\-address\fR
@@ -4917,23 +5737,25 @@ Alias: mac
 .sp
 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)\&.
 .sp
-Format: byte array
+Format: MAC address
 .RE
 .PP
 \fB802\-11\-wireless\&.mac\-address\-blacklist\fR
 .RS 4
 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")\&.
 .sp
-Format: array of string
+Format: list of MAC addresses
 .RE
 .PP
 \fB802\-11\-wireless\&.mac\-address\-randomization\fR
 .RS 4
-One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address)\&.
+One of "default" (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), "never" (1) (never randomize the MAC address), or "always" (2) (always randomize the MAC address)\&.
 .sp
 This property is deprecated since version 1\&.4\&. Use the "cloned\-mac\-address" property instead\&.
 .sp
-Format: uint32
+Format: choice (NMSettingMacRandomization)
+.sp
+Valid values: default (0), never (1), always (2)
 .RE
 .PP
 \fB802\-11\-wireless\&.mode\fR
@@ -4943,6 +5765,8 @@ Alias: mode
 Wi\-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap"\&. If blank, infrastructure is assumed\&.
 .sp
 Format: string
+.sp
+Valid values: infrastructure, adhoc, ap, mesh
 .RE
 .PP
 \fB802\-11\-wireless\&.mtu\fR
@@ -4951,14 +5775,18 @@ Alias: mtu
 .sp
 If non\-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .PP
 \fB802\-11\-wireless\&.powersave\fR
 .RS 4
-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\*(Aqt touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value)\&. All other values are reserved\&.
+One of "disable" (2) (disable Wi\-Fi power saving), "enable" (3) (enable Wi\-Fi power saving), "ignore" (1) (don\*(Aqt touch currently configure setting) or "default" (0) (use the globally configured value)\&. All other values are reserved\&.
+.sp
+Format: choice (NMSettingWirelessPowersave)
 .sp
-Format: uint32
+Valid values: default (0), ignore (1), disable (2), enable (3)
 .RE
 .PP
 \fB802\-11\-wireless\&.seen\-bssids\fR
@@ -4967,7 +5795,7 @@ A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55"
 .sp
 This is not a regular property that the user would configure\&. Instead, NetworkManager automatically sets the seen BSSIDs and tracks them internally in "/var/lib/NetworkManager/seen\-bssids" file\&.
 .sp
-Format: array of string
+Format: read only
 .RE
 .PP
 \fB802\-11\-wireless\&.ssid\fR
@@ -4976,14 +5804,16 @@ Alias: ssid
 .sp
 SSID of the Wi\-Fi network\&. Must be specified\&.
 .sp
-Format: byte array
+Format: string
 .RE
 .PP
 \fB802\-11\-wireless\&.wake\-on\-wlan\fR
 .RS 4
-The NMSettingWirelessWakeOnWLan options to enable\&. Not all devices support all options\&. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake\-on\-LAN in NetworkManager)\&.
+The NMSettingWirelessWakeOnWLan options to enable\&. Not all devices support all options\&. May be any combination of "any" (0x2), "disconnect" (0x4), "magic" (0x8), "gtk\-rekey\-failure" (0x10), "eap\-identity\-request" (0x20), "4way\-handshake" (0x40), "rfkill\-release" (0x80), "tcp" (0x100) or the special values "default" (0x1) (to use global settings) and "ignore" (0x8000) (to disable management of Wake\-on\-LAN in NetworkManager)\&.
+.sp
+Format: flags (NMSettingWirelessWakeOnWLan)
 .sp
-Format: uint32
+Valid values: any (0x2), disconnect (0x4), magic (0x8), gtk\-rekey\-failure (0x10), eap\-identity\-request (0x20), 4way\-handshake (0x40), rfkill\-release (0x80), tcp (0x100), all (0x1fe), default (0x1), ignore (0x8000)
 .RE
 .SS "802\-11\-wireless\-security setting"
 .PP
@@ -4998,20 +5828,26 @@ Properties:
 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\&.
 .sp
 Format: string
+.sp
+Valid values: open, shared, leap
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.fils\fR
 .RS 4
-Indicates whether Fast Initial Link Setup (802\&.11ai) must be enabled for the connection\&. One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported)\&. When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled\&.
+Indicates whether Fast Initial Link Setup (802\&.11ai) must be enabled for the connection\&. One of "default" (0) (use global default value), "disable" (1) (disable FILS), "optional" (2) (enable FILS if the supplicant and the access point support it) or "required" (3) (enable FILS and fail if not supported)\&. When set to "default" (0) and no global default is set, FILS will be optionally enabled\&.
+.sp
+Format: choice (NMSettingWirelessSecurityFils)
 .sp
-Format: int32
+Valid values: default (0), disable (1), optional (2), required (3)
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.group\fR
 .RS 4
 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"\&.
 .sp
-Format: array of string
+Format: list of strings
+.sp
+Valid values: wep40, wep104, tkip, ccmp
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.key\-mgmt\fR
@@ -5021,6 +5857,8 @@ Key management used for the connection\&. One of "none" (WEP or no password prot
 This property must be set for any Wi\-Fi connection that uses security\&.
 .sp
 Format: string
+.sp
+Valid values: none, ieee8021x, wpa\-psk, wpa\-eap, wpa\-eap\-suite\-b\-192, sae, owe
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.leap\-password\fR
@@ -5034,11 +5872,9 @@ Format: string
 .RS 4
 Flags indicating how to handle the "leap\-password" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.leap\-username\fR
@@ -5052,21 +5888,27 @@ Format: string
 .RS 4
 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"\&.
 .sp
-Format: array of string
+Format: list of strings
+.sp
+Valid values: tkip, ccmp
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.pmf\fR
 .RS 4
-Indicates whether Protected Management Frames (802\&.11w) must be enabled for the connection\&. One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported)\&. When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled\&.
+Indicates whether Protected Management Frames (802\&.11w) must be enabled for the connection\&. One of "default" (0) (use global default value), "disable" (1) (disable PMF), "optional" (2) (enable PMF if the supplicant and the access point support it) or "required" (3) (enable PMF and fail if not supported)\&. When set to "default" (0) and no global default is set, PMF will be optionally enabled\&.
 .sp
-Format: int32
+Format: choice (NMSettingWirelessSecurityPmf)
+.sp
+Valid values: default (0), disable (1), optional (2), required (3)
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.proto\fR
 .RS 4
 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\&.
 .sp
-Format: array of string
+Format: list of strings
+.sp
+Valid values: wpa, rsn
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.psk\fR
@@ -5080,29 +5922,27 @@ Format: string
 .RS 4
 Flags indicating how to handle the "psk" property\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.wep\-key\-flags\fR
 .RS 4
 Flags indicating how to handle the "wep\-key0", "wep\-key1", "wep\-key2", and "wep\-key3" properties\&.
 .sp
-See
-the section called \(lqSecret flag types:\(rq
-for flag values\&.
+Format: flags (NMSettingSecretFlags)
 .sp
-Format: NMSettingSecretFlags (uint32)
+Valid values: none (0x0), agent\-owned (0x1), not\-saved (0x2), not\-required (0x4)
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.wep\-key\-type\fR
 .RS 4
-Controls the interpretation of WEP keys\&. Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10\- or 26\-character hexadecimal string, or a 5\- or 13\-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de\-facto MD5 method to derive the actual WEP key\&.
+Controls the interpretation of WEP keys\&. Allowed values are "key" (1), in which case the key is either a 10\- or 26\-character hexadecimal string, or a 5\- or 13\-character ASCII password; or "passphrase" (2), in which case the passphrase is provided as a string and will be hashed using the de\-facto MD5 method to derive the actual WEP key\&.
 .sp
-Format: NMWepKeyType (uint32)
+Format: choice (NMWepKeyType)
+.sp
+Valid values: unknown (0), key (1), passphrase (2)
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.wep\-key0\fR
@@ -5137,7 +5977,9 @@ Format: string
 .RS 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\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 3
 .RE
 .PP
 \fB802\-11\-wireless\-security\&.wps\-method\fR
@@ -5148,7 +5990,9 @@ There\*(Aqs little point in changing the default setting as NetworkManager will
 .sp
 WPS can be disabled by setting this property to a value of 1\&.
 .sp
-Format: uint32
+Format: flags (NMSettingWirelessSecurityWpsMethod)
+.sp
+Valid values: default (0x0), disabled (0x1), auto (0x2), pbc (0x4), pin (0x8)
 .RE
 .SS "wpan setting"
 .PP
@@ -5162,7 +6006,11 @@ Alias: channel
 .sp
 IEEE 802\&.15\&.4 channel\&. A positive integer or \-1, meaning "do not set, use whatever the device is already set to"\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-32768 \- 32767
+.sp
+Special values: default (\-1)
 .RE
 .PP
 \fBwpan\&.mac\-address\fR
@@ -5171,7 +6019,7 @@ Alias: mac
 .sp
 If specified, this connection will only apply to the IEEE 802\&.15\&.4 (WPAN) MAC layer device whose permanent MAC address matches\&.
 .sp
-Format: string
+Format: WPAN MAC address
 .RE
 .PP
 \fBwpan\&.page\fR
@@ -5180,7 +6028,11 @@ Alias: page
 .sp
 IEEE 802\&.15\&.4 channel page\&. A positive integer or \-1, meaning "do not set, use whatever the device is already set to"\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-32768 \- 32767
+.sp
+Special values: default (\-1)
 .RE
 .PP
 \fBwpan\&.pan\-id\fR
@@ -5189,7 +6041,11 @@ Alias: pan\-id
 .sp
 IEEE 802\&.15\&.4 Personal Area Network (PAN) identifier\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
+.sp
+Special values: unset (0xffff)
 .RE
 .PP
 \fBwpan\&.short\-address\fR
@@ -5198,7 +6054,11 @@ Alias: short\-addr
 .sp
 Short IEEE 802\&.15\&.4 address to be used within a restricted environment\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
+.sp
+Special values: unset (0xffff)
 .RE
 .SS "bond\-port setting"
 .PP
@@ -5212,7 +6072,9 @@ Alias: prio
 .sp
 The port priority for bond active port re\-selection during failover\&. A higher number means a higher priority in selection\&. The primary port has the highest priority\&. This option is only compatible with active\-backup, balance\-tlb and balance\-alb modes\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
 .RE
 .PP
 \fBbond\-port\&.queue\-id\fR
@@ -5221,7 +6083,9 @@ Alias: queue\-id
 .sp
 The queue ID of this bond port\&. The maximum value of queue ID is the number of TX queues currently active in device\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Valid values: 0 \- 65535
 .RE
 .SS "hostname setting"
 .PP
@@ -5233,29 +6097,35 @@ Properties:
 .RS 4
 Whether the system hostname can be determined from DHCP on this connection\&.
 .sp
-When set to NM_TERNARY_DEFAULT (\-1), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1)\&.
+When set to "default" (\-1), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be "true" (1)\&.
+.sp
+Format: ternary
 .sp
-Format: NMTernary (int32)
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBhostname\&.from\-dns\-lookup\fR
 .RS 4
 Whether the system hostname can be determined from reverse DNS lookup of addresses on this device\&.
 .sp
-When set to NM_TERNARY_DEFAULT (\-1), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1)\&.
+When set to "default" (\-1), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be "true" (1)\&.
 .sp
-Format: NMTernary (int32)
+Format: ternary
+.sp
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBhostname\&.only\-from\-default\fR
 .RS 4
-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 "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)\&.
+.sp
+If set to "false" (0), the hostname can be set from this device even if it doesn\*(Aqt have the default route\&.
 .sp
-If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn\*(Aqt have the default route\&.
+When set to "default" (\-1), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be "false" (0)\&.
 .sp
-When set to NM_TERNARY_DEFAULT (\-1), the value from global configuration is used\&. If the property doesn\*(Aqt have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0)\&.
+Format: ternary
 .sp
-Format: NMTernary (int32)
+Valid values: true/yes/on, false/no/off, default/unknown
 .RE
 .PP
 \fBhostname\&.priority\fR
@@ -5266,7 +6136,52 @@ If the value is zero, it can be overridden by a global value from NetworkManager
 .sp
 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\&.
 .sp
-Format: int32
+Format: integer
+.sp
+Valid values: \-2147483648 \- 2147483647
+.RE
+.SS "hsr setting"
+.PP
+HSR/PRP Settings\&.
+.PP
+Properties:
+.PP
+\fBhsr\&.multicast\-spec\fR
+.RS 4
+Alias: multicast\-spec
+.sp
+The last byte of supervision address\&.
+.sp
+Format: integer
+.sp
+Valid values: 0 \- 255
+.RE
+.PP
+\fBhsr\&.port1\fR
+.RS 4
+Alias: port1
+.sp
+The port1 interface name of the HSR\&. This property is mandatory\&.
+.sp
+Format: string
+.RE
+.PP
+\fBhsr\&.port2\fR
+.RS 4
+Alias: port2
+.sp
+The port2 interface name of the HSR\&. This property is mandatory\&.
+.sp
+Format: string
+.RE
+.PP
+\fBhsr\&.prp\fR
+.RS 4
+The protocol used by the interface, whether it is PRP or HSR\&.
+.sp
+Format: boolean
+.sp
+Valid values: true/yes/on, false/no/off
 .RE
 .SS "link setting"
 .PP
@@ -5278,28 +6193,44 @@ Properties:
 .RS 4
 The maximum size of a packet built by the Generic Receive Offload stack for this device\&. The value must be between 0 and 4294967295\&. When set to \-1, the existing value is preserved\&.
 .sp
-Format: int64
+Format: integer
+.sp
+Valid values: \-1 \- 4294967295
+.sp
+Special values: default (\-1)
 .RE
 .PP
 \fBlink\&.gso\-max\-segments\fR
 .RS 4
 The maximum segments of a Generic Segment Offload packet the device should accept\&. The value must be between 0 and 4294967295\&. When set to \-1, the existing value is preserved\&.
 .sp
-Format: int64
+Format: integer
+.sp
+Valid values: \-1 \- 4294967295
+.sp
+Special values: default (\-1)
 .RE
 .PP
 \fBlink\&.gso\-max\-size\fR
 .RS 4
 The maximum size of a Generic Segment Offload packet the device should accept\&. The value must be between 0 and 4294967295\&. When set to \-1, the existing value is preserved\&.
 .sp
-Format: int64
+Format: integer
+.sp
+Valid values: \-1 \- 4294967295
+.sp
+Special values: default (\-1)
 .RE
 .PP
 \fBlink\&.tx\-queue\-length\fR
 .RS 4
 The size of the transmit queue for the device, in number of packets\&. The value must be between 0 and 4294967295\&. When set to \-1, the existing value is preserved\&.
 .sp
-Format: int64
+Format: integer
+.sp
+Valid values: \-1 \- 4294967295
+.sp
+Special values: default (\-1)
 .RE
 .SS "loopback setting"
 .PP
@@ -5313,7 +6244,9 @@ Alias: mtu
 .sp
 If non\-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames\&.
 .sp
-Format: uint32
+Format: integer
+.sp
+Special values: auto
 .RE
 .SS "veth setting"
 .PP
diff --git a/man/nm-settings-nmcli.xml b/man/nm-settings-nmcli.xml
index b0a03a3b..a5475e71 100644
--- a/man/nm-settings-nmcli.xml
+++ b/man/nm-settings-nmcli.xml
@@ -1,6 +1,6 @@
 
 
-nm-settings-nmcliNetworkManager developersnm-settings-nmcli5NetworkManagerConfiguration1.44.2nm-settings-nmcliDescription of settings and properties of NetworkManager connection profiles for nmcliDescription
+nm-settings-nmcliNetworkManager developersnm-settings-nmcli5NetworkManagerConfiguration1.45.90nm-settings-nmcliDescription of settings and properties of NetworkManager connection profiles for nmcliDescription
           NetworkManager is based on a concept of connection profiles, sometimes referred to as
           connections only. These connection profiles contain a network configuration. When
           NetworkManager activates a connection profile on a network device the configuration will
@@ -34,38 +34,61 @@
         connection settingGeneral Connection Profile Settings.
         Properties:
         The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection.Currently, this only applies to 802-1x authentication.
-            Format: int32
+            Format: integer
+            Valid values: -1 - 2147483647
             Alias: autoconnectWhether 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: booleanThe 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: int32The 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: int32Whether 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)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: int32If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.
-            Format: uint32
+            Format: boolean
+            Valid values: true/yes/on, false/no/offThe 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: integer
+            Valid values: -999 - 999The 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: integer
+            Valid values: -1 - 2147483647
+            Special values: default (-1), forever (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: choice (NMSettingConnectionAutoconnectSlaves)
+            Valid values: default (-1), no (0), yes (1)
+            Alias: controllerInterface name of the controller device or UUID of the controller connection.
+            Format: stringWhether 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: choice (NMSettingConnectionDnsOverTls)
+            Valid values: default (-1), no (0), opportunistic (1), yes (2)If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.
+            Format: integer
+            Valid values: 0 - 600
             Alias: con-nameA human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".
             Format: string
             Alias: ifnameThe 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: stringWhether LLDP is enabled for the connection.
-            Format: int32Whether 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: masterInterface name of the master device or UUID of the master connection.
+            Format: choice (NMSettingConnectionLldp)
+            Valid values: default (-1), disable (0), enable-rx/enable (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.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: choice (NMSettingConnectionLlmnr)
+            Valid values: default (-1), no (0), resolve (1), yes (2)
+            Alias: masterInterface name of the master device or UUID of the master connection.Deprecated 1.46. Use "controller" instead, this is just an alias.
             Format: stringWhether 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: int32Whether the connection is metered.When updating this property on a currently activated connection, the change takes effect immediately.
-            Format: NMMetered (int32)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: uint32If 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: choice (NMSettingConnectionMdns)
+            Valid values: default (-1), no (0), resolve (1), yes (2)Whether the connection is metered.When updating this property on a currently activated connection, the change takes effect immediately.
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownWhether 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: flags (NMMptcpFlags)
+            Valid values: none/default (0x0), disabled (0x1), enabled (0x2), also-without-sysctl (0x4), also-without-default-route (0x8), signal (0x10), subflow (0x20), backup (0x40), fullmesh (0x80)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: stringSpecifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.
-            Format: int32An 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 stringList 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-typeSetting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.
-            Format: stringThis represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used to derive the DHCP client identifier with ipv4.dhcp-client-id=stable, the DHCPv6 DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid] and the DHCP IAID with ipv4.iaid=stable and ipv6.iaid=stable.Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-boot, or every time. The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$".  For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.If the value is unset, a global connection default is consulted. If the value is still unset, the default is "default${CONNECTION}" go generate an ID unique per connection profile.
+            Format: choice (NMConnectionMultiConnect)
+            Valid values: default (0), single (1), manual-multiple (2), multiple (3)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: list of strings
+            Alias: port-typeSetting name of the device type of this port's controller connection (eg, "bond"), or NULL if this connection is not a port.
+            Format: string
+            Valid values: bond, bridge, ovs-bridge, ovs-port, team, vrfList of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.
+            Format: list of strings
+            Alias: slave-typeSetting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.Deprecated 1.46. Use "port-type" instead, this is just an alias.
+            Format: string
+            Valid values: bond, bridge, ovs-bridge, ovs-port, team, vrfThis represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used to derive the DHCP client identifier with ipv4.dhcp-client-id=stable, the DHCPv6 DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid] and the DHCP IAID with ipv4.iaid=stable and ipv6.iaid=stable.Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-SSID, per-boot, or every time.  The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. "${NETWORK_SSID}" uses the SSID for Wi-Fi networks and falls back to "${CONNECTION}" on other networks. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$".  For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.If the value is unset, a global connection default is consulted. If the value is still unset, the default is "default${CONNECTION}" go generate an ID unique per connection profile.
             Format: stringThe time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).
-            Format: uint64
+            Format: read only
             Alias: typeBase 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: stringThe connection.uuid is the real identifier of a profile. It cannot change and it must be unique. It is therefore often best to refer to a profile by UUID, for example with `nmcli connection up uuid $UUID`.The UUID cannot be changed, except in offline mode. In that case, the special values "new", "generate" and "" are allowed to generate a new random UUID.
-            Format: a valid RFC4122 universally unique identifier (UUID).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: int32Timeout 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: int32The 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
+            Valid values: 6lowpan, 802-11-olpc-mesh, 802-11-wireless, 802-3-ethernet, adsl, bluetooth, bond, bridge, cdma, dummy, generic, gsm, hsr, infiniband, ip-tunnel, loopback, macsec, macvlan, ovs-bridge, ovs-dpdk, ovs-interface, ovs-patch, ovs-port, pppoe, team, tun, veth, vlan, vpn, vrf, vxlan, wifi-p2p, wimax, wireguard, wpanThe connection.uuid is the real identifier of a profile. It cannot change and it must be unique. It is therefore often best to refer to a profile by UUID, for example with `nmcli connection up uuid $UUID`.The UUID cannot be changed, except in offline mode. In that case, the special values "new", "generate" and "" are allowed to generate a new random UUID.
+            Format: stringTime 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: integer
+            Valid values: -1 - 2147483647Timeout 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: integer
+            Valid values: -1 - 2147483647The 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: string6lowpan setting6LoWPAN Settings.
         Properties:
         
@@ -73,201 +96,437 @@
             Format: string802-1x settingIEEE 802.1x Authentication Settings.
         Properties:
         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 stringAnonymous identity string for EAP authentication methods.  Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.
+            Format: list of stringsAnonymous identity string for EAP authentication methods.  Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.
             Format: stringA timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.
-            Format: int32Contains 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 arrayThe 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: integer
+            Valid values: 0 - 2147483647Contains 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: filesystem pathThe 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: stringFlags indicating how to handle the "ca-cert-password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: stringContains 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 arrayThe 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: filesystem pathThe 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: stringFlags indicating how to handle the "client-cert-password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: stringConstraint 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: stringThe 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 stringIdentity string for EAP authentication methods.  Often the user's user or login name.
+            Format: list of strings
+            Valid values: leap, md5, tls, peap, ttls, sim, fast, pwdIdentity string for EAP authentication methods.  Often the user's user or login name.
             Format: stringWhether 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: booleanUTF-8 encoded file path containing PAC for EAP-FAST.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offUTF-8 encoded file path containing PAC for EAP-FAST.
             Format: stringUTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.
             Format: stringFlags indicating how to handle the "password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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 arrayFlags indicating how to handle the "password-raw" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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: uint32Enables 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: stringForces 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: stringForces 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: stringList 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 stringSpecifies 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: stringSpecifies 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: stringContains 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 arrayThe 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: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: bytesFlags indicating how to handle the "password-raw" property.
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: flags (NMSetting8021xAuthFlags)
+            Valid values: none (0x0), tls-1-0-disable (0x1), tls-1-1-disable (0x2), tls-1-2-disable (0x4), tls-disable-time-checks (0x8), tls-1-3-disable (0x10), tls-1-0-enable (0x20), tls-1-1-enable (0x40), tls-1-2-enable (0x80), tls-1-3-enable (0x100), all (0x1ff)Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning).  See the wpa_supplicant documentation for more details.
+            Format: string
+            Valid values: 0, 1, 2, 3Forces use of the new PEAP label during key derivation.  Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1.  Set to "1" to force use of the new PEAP label.  See the wpa_supplicant documentation for more details.
+            Format: string
+            Valid values: 0, 1Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property.  When unset, the version reported by the server will be used.  Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version.  To do so, this property may be set to "0" or "1" to force that specific PEAP version.
+            Format: string
+            Valid values: 0, 1List 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: list of stringsSpecifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property.  For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method.  For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.
+            Format: string
+            Valid values: pap, chap, mschap, mschapv2, gtc, otp, md5, tlsSpecifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property.  Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.
+            Format: string
+            Valid values: md5, mschapv2, otp, gtc, tlsContains 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: filesystem pathThe 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: stringFlags indicating how to handle the "phase2-ca-cert-password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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: stringContains 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 arrayThe 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: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: filesystem pathContains 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: filesystem pathThe 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: stringFlags indicating how to handle the "phase2-client-cert-password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: stringConstraint 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: stringContains 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 arrayThe 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: filesystem pathThe 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: stringFlags indicating how to handle the "phase2-private-key-password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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.
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: stringPIN used for EAP authentication methods.
             Format: stringFlags indicating how to handle the "pin" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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 arrayThe 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: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: filesystem pathThe 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: stringFlags indicating how to handle the "private-key-password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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.
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: stringWhen 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: booleanadsl settingADSL Settings.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offadsl settingADSL Settings.
         Properties:
         
             Alias: encapsulationEncapsulation of ADSL connection.  Can be "vcmux" or "llc".
-            Format: string
+            Format: string
+            Valid values: vcmux, llc
             Alias: passwordPassword used to authenticate with the ADSL service.
             Format: stringFlags indicating how to handle the "password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)
             Alias: protocolADSL connection protocol.  Can be "pppoa", "pppoe" or "ipoatm".
-            Format: string
+            Format: string
+            Valid values: pppoa, pppoe, ipoatm
             Alias: usernameUsername used to authenticate with the ADSL service.
             Format: stringVCI of ADSL connection
-            Format: uint32VPI of ADSL connection
-            Format: uint32bluetooth settingBluetooth Settings.
+            Format: integer
+            Valid values: 0 - 65536VPI of ADSL connection
+            Format: integer
+            Valid values: 0 - 65536bluetooth settingBluetooth Settings.
         Properties:
         
             Alias: addrThe Bluetooth address of the device.
-            Format: byte array
+            Format: MAC address
             Alias: bt-typeEither "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.
-            Format: stringbond settingBonding Settings.
+            Format: string
+            Valid values: dun, panu, napbond settingBonding Settings.
         Properties:
         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 stringbridge settingBridging Settings.
+            Format: list of key/value optionsbridge settingBridging Settings.
         Properties:
         
             Alias: ageing-timeThe Ethernet MAC address aging time, in seconds.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 1000000
             Alias: forward-delayThe Spanning Tree Protocol (STP) forwarding delay, in seconds.
-            Format: uint32If specified, The MAC address of the multicast group this bridge uses for STP.The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.
-            Format: byte array
+            Format: integer
+            Valid values: 0 - 30If 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: MAC address
             Alias: group-forward-maskA mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 65535
             Alias: hello-timeThe Spanning Tree Protocol (STP) hello time, in seconds.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 10
             Alias: macIf 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
+            Format: MAC address
             Alias: max-ageThe Spanning Tree Protocol (STP) maximum message age, in seconds.
-            Format: uint32Set maximum size of multicast hash table (value must be a power of 2).
-            Format: uint32Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.
-            Format: uint32Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.
-            Format: uint64Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.
-            Format: uint64Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.
-            Format: booleanIf no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.
-            Format: uint64Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.
-            Format: uint64Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.
-            Format: uint64If 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: booleanSets 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
+            Format: integer
+            Valid values: 0 - 40Set maximum size of multicast hash table (value must be a power of 2).
+            Format: integer
+            Valid values: 1 - 4294967295Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.
+            Format: integer
+            Valid values: 0 - 4294967295Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.
+            Format: integer
+            Valid values: 0 - 18446744073709551615Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.
+            Format: integer
+            Valid values: 0 - 18446744073709551615Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.
+            Format: integer
+            Valid values: 0 - 18446744073709551615Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.
+            Format: integer
+            Valid values: 0 - 18446744073709551615Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.
+            Format: integer
+            Valid values: 0 - 18446744073709551615If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offSets 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
+            Valid values: auto, disabled, enabled
             Alias: multicast-snoopingControls 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: booleanSet the number of IGMP queries to send during startup phase.
-            Format: uint32Sets the time (in deciseconds) between queries sent out at startup to determine membership information.
-            Format: uint64
+            Format: boolean
+            Valid values: true/yes/on, false/no/offSet the number of IGMP queries to send during startup phase.
+            Format: integer
+            Valid values: 0 - 4294967295Sets the time (in deciseconds) between queries sent out at startup to determine membership information.
+            Format: integer
+            Valid values: 0 - 18446744073709551615
             Alias: prioritySets the Spanning Tree Protocol (STP) priority for this bridge.  Lower values are "better"; the lowest priority bridge will be elected the root bridge.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 65535
             Alias: stpControls whether Spanning Tree Protocol (STP) is enabled for this bridge.
-            Format: booleanThe default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.
-            Format: uint32Control whether VLAN filtering is enabled on the bridge.
-            Format: booleanIf specified, the protocol used for VLAN filtering.Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.
-            Format: stringControls whether per-VLAN stats accounting is enabled.
-            Format: booleanArray 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 vardictbridge-port settingBridge Port Settings.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offThe default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.
+            Format: integer
+            Valid values: 0 - 4094Control whether VLAN filtering is enabled on the bridge.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf 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
+            Valid values: 802.1Q, 802.1adControls whether per-VLAN stats accounting is enabled.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offArray 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: list of bridge.vlans objectsbridge-port settingBridge Port Settings.
         Properties:
         
             Alias: hairpinEnables 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
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: path-costThe Spanning Tree Protocol (STP) port cost for destinations via this port.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 65535
             Alias: priorityThe Spanning Tree Protocol (STP) priority of this bridge port.
-            Format: uint32Array 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 vardictcdma settingCDMA-based Mobile Broadband Settings.
+            Format: integer
+            Valid values: 0 - 63Array 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: list of bridge-port.vlans objectscdma settingCDMA-based Mobile Broadband Settings.
         Properties:
         If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
-            Format: uint32The 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: integer
+            Special values: autoThe 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: passwordThe 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: stringFlags indicating how to handle the "password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)
             Alias: userThe 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: stringdcb settingData Center Bridging Settings.
         Properties:
-        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)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: stringThe 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: int32Specifies 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)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: int32Specifies 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)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: int32An 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 uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.
-            Format: array of uint32Specifies 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)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 uint32Specifies 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)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 uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.
-            Format: array of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.
-            Format: array of uint32ethtool settingEthtool Ethernet Settings.
+        Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).
+            Format: flags (NMSettingDcbFlags)
+            Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)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
+            Valid values: fabric, vn2vnThe highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the "enable" (0x1) flag.
+            Format: integer
+            Valid values: -1 - 7
+            Special values: unset (-1)Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).
+            Format: flags (NMSettingDcbFlags)
+            Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the "enable" (0x1) flag.
+            Format: integer
+            Valid values: -1 - 7
+            Special values: unset (-1)Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).
+            Format: flags (NMSettingDcbFlags)
+            Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the "enable" (0x1) flag.
+            Format: integer
+            Valid values: -1 - 7
+            Special values: unset (-1)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: list of integers
+            Valid values: 0 - 100An 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: list of booleans
+            Valid values: true/yes/on, false/no/offSpecifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).
+            Format: flags (NMSettingDcbFlags)
+            Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)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: list of integers
+            Valid values: 0 - 100Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of "enable" (0x1), "advertise" (0x2), and "willing" (0x4).
+            Format: flags (NMSettingDcbFlags)
+            Valid values: none (0x0), enable (0x1), advertise (0x2), willing (0x4)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: list of integers
+            Valid values: 0 - 7, 15An 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: list of booleans
+            Valid values: true/yes/on, false/no/offAn 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: list of integers
+            Valid values: 0 - 7ethtool settingEthtool Ethernet Settings.
         Properties:
-        gsm settingGSM-based Mobile Broadband Settings.
+        
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: ternary
+            Valid values: on, off, ignore
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295
+            Format: integer
+            Valid values: 0 - 4294967295gsm settingGSM-based Mobile Broadband Settings.
         Properties:
         
-            Alias: apnThe 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.
+            Alias: apnThe GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network.  The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.If the APN is unset (the default) then it may be detected based on "auto-config" setting. The property can be explicitly set to the empty string to prevent that and use no APN.
             Format: stringWhen 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: booleanThe 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: boolean
+            Valid values: true/yes/on, false/no/offThe 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: stringWhen TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.
-            Format: booleanFor LTE modems, this sets the APN for the initial EPS bearer that is set up when attaching to the network.  Setting this parameter implies initial-eps-bearer-configure to be TRUE.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offFor LTE modems, this sets the APN for the initial EPS bearer that is set up when attaching to the network.  Setting this parameter implies initial-eps-bearer-configure to be TRUE.
             Format: stringFor LTE modems, this setting determines whether the initial EPS bearer shall be configured when bringing up the connection.  It is inferred TRUE if initial-eps-bearer-apn is set.
-            Format: booleanIf non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
-            Format: uint32The 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: boolean
+            Valid values: true/yes/on, false/no/offIf non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
+            Format: integer
+            Special values: autoThe 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: stringLegacy 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: passwordThe 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: stringFlags indicating how to handle the "password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: stringFlags indicating how to handle the "pin" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)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: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)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: stringA 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: userThe 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.
@@ -275,40 +534,57 @@
         Properties:
         
             Alias: macIf specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).
-            Format: byte array
+            Format: Infiniband MAC address
             Alias: mtuIf non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
-            Format: uint32
+            Format: integer
+            Special values: auto
             Alias: p-keyThe 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 0x8000 is set if it is a "full membership" p-key. The values 0 and 0x8000 are not allowed.With the p-key set, the interface name is always "$parent.$p_key". Setting "connection.interface-name" to another name is not supported.Note that kernel will internally always set the full membership bit, although the interface name does not reflect that. Usually the user would want to configure a full membership p-key with 0x8000 flag set.
-            Format: int32
+            Format: integer
+            Valid values: -1 - 65535
+            Special values: default (-1)
             Alias: parentThe 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-modeThe IP-over-InfiniBand transport mode. Either "datagram" or "connected".
-            Format: stringipv4 settingIPv4 Settings.
+            Format: string
+            Valid values: datagram, connectedipv4 settingIPv4 Settings.
         Properties:
         
             Alias: ip4A list of IPv4 addresses and their prefix length. Multiple addresses can be separated by comma. For example "192.168.1.5/24, 10.1.0.5/24". The addresses are listed in decreasing priority, meaning the first address will be the primary address.
-            Format: a comma separated list of addressesVPN 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)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: int32A 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: stringIf 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: list of ipv4.addresses objectsVPN 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: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownMaximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.
+            Format: integer
+            Valid values: -1 - 30000
+            Special values: default (-1), off (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 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.The special value "none" prevents any client identifier from being sent. Note that this is normally not recommended.If unset, a globally configured default from NetworkManager.conf is used. If still unset, the default depends on the DHCP plugin. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won't sent any client-id otherwise.
+            Format: string
+            Special values: mac, perm-mac, duid, ipv6-duid, stable, noneIf 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: stringIf 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: stringFlags 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: uint32A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address.The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.
+            Format: stringFlags 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 "fqdn-serv-update" (0x1), "fqdn-encoded" (0x2) and "fqdn-no-update" (0x4).  When no FQDN flag is set and "fqdn-clear-flags" (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and "fqdn-clear-flags" (0x8) is not set, the standard FQDN flags are set in the request: "fqdn-serv-update" (0x1), "fqdn-encoded" (0x2) for IPv4 and "fqdn-serv-update" (0x1) for IPv6.When this property is set to the default value "none" (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also "none" (0x0), then the standard FQDN flags described above are sent in the DHCP requests.
+            Format: flags (NMDhcpHostnameFlags)
+            Valid values: none (0x0), fqdn-serv-update (0x1), fqdn-encoded (0x2), fqdn-no-update (0x4), fqdn-clear-flags (0x8)A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address.The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.
             Format: stringArray 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 stringIf 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: booleanA 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: int32The 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: list of IPv4 addressesIf TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offA 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: integer
+            Valid values: 0 - 2147483647
+            Special values: default (0), infinity (2147483647)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: stringArray 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 uint32DNS options for /etc/resolv.conf as described in resolv.conf(5) manual.The currently supported options are "attempts", "debug", "edns0", "ndots", "no-aaaa", "no-check-names", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) manual.Note that there is a distinction between an unset (default) list and an empty list. In nmcli, to unset the list set the value to "". To set an empty list, set it to " ". Currently, an unset list has the same meaning as an empty list. That might change in the future.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.The valid "ipv4.dns-options" and "ipv6.dns-options" get merged together.
-            Format: a comma separated list of DNS optionsDNS 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: int32List 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
+            Format: list of IPv4 addressesDNS options for /etc/resolv.conf as described in resolv.conf(5) manual.The currently supported options are "attempts", "debug", "edns0", "ndots", "no-aaaa", "no-check-names", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) manual.Note that there is a distinction between an unset (default) list and an empty list. In nmcli, to unset the list set the value to "". To set an empty list, set it to " ". Currently, an unset list has the same meaning as an empty list. That might change in the future.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.The valid "ipv4.dns-options" and "ipv6.dns-options" get merged together.
+            Format: list of stringsDNS 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: integer
+            Valid values: -2147483648 - 2147483647List 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: list of strings
             Alias: gw4The 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: stringWhen "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: booleanWhen "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: booleanEnable 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: int32If 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
+            Format: IPv4 addressWhen "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offWhen "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offEnable 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: choice (NMSettingIP4LinkLocal)
+            Valid values: default (0), auto (1), disabled (2), enabled (3)If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out.  Note that at least one IP configuration must succeed or overall network configuration will still fail.  For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
   Sets the IPv4 connection method. You can set one of the following values:
 
   
@@ -329,12 +605,20 @@
      
   
 
-            Format: stringIf 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: booleanConnections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.
-            Format: NMTernary (int32)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: int32The 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: int64Enable 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
+            Format: string
+            Valid values: auto, link-local, manual, shared, disabledIf TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offConnections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownThe 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: integer
+            Valid values: -1 - 2147483647
+            Special values: default (-1), infinity (2147483647)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: integer
+            Valid values: -1 - 4294967295Enable 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: integer
+            Valid values: 0 - 4294967295
+            Special values: unspec (0), main (254)
   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]...]".
@@ -424,7 +708,7 @@
 
 For details see also `man ip-route`.
 
-            Format: a comma separated list of routes
+            Format: list of ipv4.routes objects
 A comma separated list of routing rules for policy routing. The format
 is based on ip rule add syntax and mostly compatible.
 One difference is that routing rules in NetworkManager always need a
@@ -432,30 +716,41 @@ fixed priority.
 
 Example: priority 5 from 192.167.4.0/24 table 45
 
-            Format: a comma separated list of routing rulesipv6 settingIPv6 Settings.
+            Format: list of ipv4.routing-rules objectsipv6 settingIPv6 Settings.
         Properties:
         Configure method for creating the IPv6 interface identifer of addresses with RFC4862 IPv6 Stateless Address Autoconfiguration and Link Local addresses.The permitted values are: "eui64" (0), "stable-privacy" (1), "default" (3) or "default-or-eui64" (2).If the property is set to "eui64", the addresses will be generated using the interface token derived from hardware address. This makes the host part of the address to stay constant, making it possible to track the host's presence when it changes networks. The address changes when the interface hardware is replaced. If a duplicate address is detected, there is also no fallback to generate another address. When configured, the "ipv6.token" is used instead of the MAC address to generate addresses for stateless autoconfiguration.If the property is set to "stable-privacy", the interface identifier is generated as specified by RFC7217. This works by hashing a host specific key (see NetworkManager(8) manual), the interface name, the connection's "connection.stable-id" property and the address prefix.  This improves privacy by making it harder to use the address to track the host's presence and the address is stable when the network interface hardware is replaced.The special values "default" and "default-or-eui64" will fallback to the global connection default as documented in the NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively.If not specified, when creating a new profile the default is "default".Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.
-            Format: one of "eui64" (0), "stable-privacy" (1), "default" (3) or "default-or-eui64" (2)
+            Format: choice (NMSettingIP6ConfigAddrGenMode)
+            Valid values: eui64 (0), stable-privacy (1), default-or-eui64 (2), default (3)
             Alias: ip6A list of IPv6 addresses and their prefix length. Multiple addresses can be separated by comma. For example "2001:db8:85a3::8a2e:370:7334/64, 2001:db8:85a3::5/64". The addresses are listed in decreasing priority, meaning the first address will be the primary address. This can make a difference with IPv6 source address selection (RFC 6724, section 5).
-            Format: a comma separated list of addressesVPN 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)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: list of ipv6.addresses objectsVPN 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: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownA 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: stringIf 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: stringFlags 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: uint32A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address.The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.
+            Format: stringFlags 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 "fqdn-serv-update" (0x1), "fqdn-encoded" (0x2) and "fqdn-no-update" (0x4).  When no FQDN flag is set and "fqdn-clear-flags" (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and "fqdn-clear-flags" (0x8) is not set, the standard FQDN flags are set in the request: "fqdn-serv-update" (0x1), "fqdn-encoded" (0x2) for IPv4 and "fqdn-serv-update" (0x1) for IPv6.When this property is set to the default value "none" (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also "none" (0x0), then the standard FQDN flags described above are sent in the DHCP requests.
+            Format: flags (NMDhcpHostnameFlags)
+            Valid values: none (0x0), fqdn-serv-update (0x1), fqdn-encoded (0x2), fqdn-no-update (0x4), fqdn-clear-flags (0x8)A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "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".For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address.The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.
             Format: stringA IPv6 address followed by a slash and a prefix length. If set, the value is sent to the DHCPv6 server as hint indicating the prefix delegation (IA_PD) we want to receive. To only hint a prefix length without prefix, set the address part to the zero address (for example "::/60").
             Format: stringIf 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: booleanA 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: int32Array 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 arrayDNS options for /etc/resolv.conf as described in resolv.conf(5) manual.The currently supported options are "attempts", "debug", "edns0", "ndots", "no-aaaa", "no-check-names", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc" and "inet6", "ip6-bytestring", "ip6-dotint", "no-ip6-dotint". See the resolv.conf(5) manual.Note that there is a distinction between an unset (default) list and an empty list. In nmcli, to unset the list set the value to "". To set an empty list, set it to " ". Currently, an unset list has the same meaning as an empty list. That might change in the future.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.The valid "ipv4.dns-options" and "ipv6.dns-options" get merged together.
-            Format: a comma separated list of DNS optionsDNS 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: int32List 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
+            Format: boolean
+            Valid values: true/yes/on, false/no/offA 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: integer
+            Valid values: 0 - 2147483647
+            Special values: default (0), infinity (2147483647)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: list of IPv6 addressesDNS options for /etc/resolv.conf as described in resolv.conf(5) manual.The currently supported options are "attempts", "debug", "edns0", "ndots", "no-aaaa", "no-check-names", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc" and "inet6", "ip6-bytestring", "ip6-dotint", "no-ip6-dotint". See the resolv.conf(5) manual.Note that there is a distinction between an unset (default) list and an empty list. In nmcli, to unset the list set the value to "". To set an empty list, set it to " ". Currently, an unset list has the same meaning as an empty list. That might change in the future.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.The valid "ipv4.dns-options" and "ipv6.dns-options" get merged together.
+            Format: list of stringsDNS 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: integer
+            Valid values: -2147483648 - 2147483647List 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: list of strings
             Alias: gw6The 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: stringWhen "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: booleanWhen "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: booleanConfigure 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)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
+            Format: IPv6 addressWhen "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offWhen "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offConfigure 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: choice (NMSettingIP6ConfigPrivacy)
+            Valid values: unknown (-1), disabled (0), prefer-public-addr (1), prefer-temp-addr (2)If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out.  Note that at least one IP configuration must succeed or overall network configuration will still fail.  For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
   Sets the IPv6 connection method. You can set one of the following values:
 
   
@@ -485,14 +780,25 @@ Example: priority 5 from 192.167.4.0/24 table 45
     If you set "auto", "dhcp", "manual", "ignore", or "shared", NetworkManager assigns, in addition to the global address, an IPv6 link-local address to the interface. This is compliant with RFC 4291.
   
 
-            Format: stringMaximum 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: uint32If 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: booleanA 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: int32Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.
-            Format: NMTernary (int32)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: int32The 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: int64Enable 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
+            Format: string
+            Valid values: ignore, auto, dhcp, link-local, manual, shared, disabledMaximum 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: integer
+            Special values: autoIf TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offA 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: integer
+            Valid values: 0 - 2147483647
+            Special values: default (0), infinity (2147483647)Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownThe 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: integer
+            Valid values: -1 - 2147483647
+            Special values: default (-1), infinity (2147483647)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: integer
+            Valid values: -1 - 4294967295Enable 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: integer
+            Valid values: 0 - 4294967295
+            Special values: unspec (0), main (254)
   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]...]".
@@ -563,7 +869,7 @@ Example: priority 5 from 192.167.4.0/24 table 45
 
 For details see also `man ip-route`.
 
-            Format: a comma separated list of routes
+            Format: list of ipv6.routes objects
 A comma separated list of routing rules for policy routing. The format
 is based on ip rule add syntax and mostly compatible.
 One difference is that routing rules in NetworkManager always need a
@@ -571,129 +877,179 @@ fixed priority.
 
 Example: priority 5 from 1:2:3::5/128 table 45
 
-            Format: a comma separated list of routing rulesConfigure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.When set, the token is used as IPv6 interface identifier instead of the hardware address. This only applies to addresses from stateless autoconfiguration, not to IPv6 link local addresses.
+            Format: list of ipv6.routing-rules objectsConfigure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.When set, the token is used as IPv6 interface identifier instead of the hardware address. This only applies to addresses from stateless autoconfiguration, not to IPv6 link local addresses.
             Format: stringip-tunnel settingIP Tunneling Settings.
         Properties:
         How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add 0x1 (ip6-ign-encap-limit) to ip-tunnel flags.
-            Format: uint32Tunnel flags. Currently, the following values are supported: 0x1 (ip6-ign-encap-limit), 0x2 (ip6-use-orig-tclass), 0x4 (ip6-use-orig-flowlabel), 0x8 (ip6-mip6-dev), 0x10 (ip6-rcv-dscp-copy) and 0x20 (ip6-use-orig-fwmark). They are valid only for IPv6 tunnels.
-            Format: uint32The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.
-            Format: uint32The fwmark value to assign to tunnel packets. This property can be set to a non zero value only on VTI and VTI6 tunnels.
-            Format: uint32The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.
+            Format: integer
+            Valid values: 0 - 255Tunnel flags. Currently, the following values are supported: 0x1 (ip6-ign-encap-limit), 0x2 (ip6-use-orig-tclass), 0x4 (ip6-use-orig-flowlabel), 0x8 (ip6-mip6-dev), 0x10 (ip6-rcv-dscp-copy) and 0x20 (ip6-use-orig-fwmark). They are valid only for IPv6 tunnels.
+            Format: flags (NMIPTunnelFlags)
+            Valid values: none (0x0), ip6-ign-encap-limit (0x1), ip6-use-orig-tclass (0x2), ip6-use-orig-flowlabel (0x4), ip6-mip6-dev (0x8), ip6-rcv-dscp-copy (0x10), ip6-use-orig-fwmark (0x20)The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.
+            Format: integer
+            Valid values: 0 - 1048575The fwmark value to assign to tunnel packets. This property can be set to a non zero value only on VTI and VTI6 tunnels.
+            Format: integer
+            Valid values: 0 - 4294967295The 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: localThe local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.
             Format: string
             Alias: modeThe tunneling mode. Valid values: ipip (1), gre (2), sit (3), isatap (4), vti (5), ip6ip6 (6), ipip6 (7), ip6gre (8), vti6 (9), gretap (10) and ip6gretap (11)
-            Format: uint32If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.
-            Format: uint32The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.
+            Format: choice (NMIPTunnelMode)
+            Valid values: ipip (1), gre (2), sit (3), isatap (4), vti (5), ip6ip6 (6), ipip6 (7), ip6gre (8), vti6 (9), gretap (10), ip6gretap (11)If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.
+            Format: integer
+            Special values: autoThe 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: devIf 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: stringWhether to enable Path MTU Discovery on this tunnel.
-            Format: boolean
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: remoteThe remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.
             Format: stringThe type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.
-            Format: uint32The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.
-            Format: uint32macsec settingMACSec Settings.
+            Format: integer
+            Valid values: 0 - 255The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.
+            Format: integer
+            Valid values: 0 - 255macsec settingMACSec Settings.
         Properties:
         
             Alias: encryptWhether the transmitted traffic must be encrypted.
-            Format: boolean
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: cakThe pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.
             Format: stringFlags indicating how to handle the "mka-cak" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)
             Alias: cknThe 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: modeSpecifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.
-            Format: int32
+            Format: choice (NMSettingMacsecMode)
+            Valid values: psk (0), eap (1)
             Alias: devIf 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: portThe port component of the SCI (Secure Channel Identifier), between 1 and 65534.
-            Format: int32Specifies whether the SCI (Secure Channel Identifier) is included in every packet.
-            Format: booleanSpecifies the validation mode for incoming frames.
-            Format: int32macvlan settingMAC VLAN Settings.
+            Format: integer
+            Valid values: 1 - 65534Specifies whether the SCI (Secure Channel Identifier) is included in every packet.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offSpecifies the validation mode for incoming frames.
+            Format: choice (NMSettingMacsecValidation)
+            Valid values: disable (0), check (1), strict (2)macvlan settingMAC VLAN Settings.
         Properties:
         
             Alias: modeThe macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.
-            Format: uint32
+            Format: choice (NMSettingMacvlanMode)
+            Valid values: vepa (1), bridge (2), private (3), passthru (4), source (5)
             Alias: devIf 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: stringWhether the interface should be put in promiscuous mode.
-            Format: boolean
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: tapWhether the interface should be a MACVTAP.
-            Format: booleanmatch settingMatch settings.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offmatch settingMatch settings.
         Properties:
         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 stringA 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 stringA 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 stringA 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 string802-11-olpc-mesh setting
+            Format: list of stringsA 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: list of stringsA 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: list of stringsA 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: list of strings802-11-olpc-mesh setting
           Alias: olpc-meshOLPC Wireless Mesh Settings.
         Properties:
         
             Alias: channelChannel on which the mesh network to join is located.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 4294967295
             Alias: dhcp-anycastAnycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request.This is currently only implemented by dhclient DHCP plugin.
-            Format: byte array
+            Format: MAC address
             Alias: ssidSSID of the mesh network to join.
-            Format: byte arrayovs-bridge settingOvsBridge Link Settings.
+            Format: stringovs-bridge settingOvsBridge Link Settings.
         Properties:
         The data path type. One of "system", "netdev" or empty.
-            Format: stringThe bridge failure mode. One of "secure", "standalone" or empty.
-            Format: stringEnable or disable multicast snooping.
-            Format: booleanEnable or disable RSTP.
-            Format: booleanEnable or disable STP.
-            Format: booleanovs-dpdk settingOvsDpdk Link Settings.
+            Format: string
+            Valid values: system, netdevThe bridge failure mode. One of "secure", "standalone" or empty.
+            Format: string
+            Valid values: secure, standaloneEnable or disable multicast snooping.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offEnable or disable RSTP.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offEnable or disable STP.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offovs-dpdk settingOvsDpdk Link Settings.
         Properties:
         Open vSwitch DPDK device arguments.
             Format: stringOpen vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.
-            Format: uint32The 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: uint32The 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: uint32ovs-interface settingOpen vSwitch Interface Settings.
+            Format: integer
+            Valid values: 0 - 4294967295The 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: integer
+            Valid values: 0 - 4096The 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: integer
+            Valid values: 0 - 4096ovs-interface settingOpen vSwitch Interface Settings.
         Properties:
         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: uint32The interface type. Either "internal", "system", "patch", "dpdk", or empty.
-            Format: stringovs-patch settingOvsPatch Link Settings.
+            Format: integer
+            Valid values: 0 - 65279The interface type. Either "internal", "system", "patch", "dpdk", or empty.
+            Format: string
+            Valid values: internal, system, patch, dpdkovs-patch settingOvsPatch Link Settings.
         Properties:
         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: stringovs-port settingOvsPort Link Settings.
         Properties:
         The time port must be inactive in order to be considered down.
-            Format: uint32Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".
-            Format: stringThe time port must be active before it starts forwarding traffic.
-            Format: uint32LACP mode. One of "active", "off", or "passive".
-            Format: stringThe VLAN tag in the range 0-4095.
-            Format: uint32A 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 vardictThe VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk", "dot1q-tunnel" or unset.
-            Format: stringppp settingPoint-to-Point Protocol Settings.
+            Format: integer
+            Valid values: 0 - 4294967295Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".
+            Format: string
+            Valid values: active-backup, balance-slb, balance-tcpThe time port must be active before it starts forwarding traffic.
+            Format: integer
+            Valid values: 0 - 4294967295LACP mode. One of "active", "off", or "passive".
+            Format: string
+            Valid values: active, off, passiveThe VLAN tag in the range 0-4095.
+            Format: integer
+            Valid values: 0 - 4095A 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: list of ovs-port.trunks objectsThe VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk", "dot1q-tunnel" or unset.
+            Format: string
+            Valid values: access, native-tagged, native-untagged, trunk, dot1q-tunnelppp settingPoint-to-Point Protocol Settings.
         Properties:
         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: uint32If 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: booleanIf 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: uint32If 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: uint32If TRUE, stateful MPPE is used.  See pppd documentation for more information on stateful MPPE.
-            Format: booleanIf 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: uint32If non-zero, instruct pppd to send packets no larger than the specified size.
-            Format: uint32If TRUE, Van Jacobsen TCP header compression will not be requested.
-            Format: booleanIf 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: booleanIf TRUE, BSD compression will not be requested.
-            Format: booleanIf TRUE, "deflate" compression will not be requested.
-            Format: booleanIf TRUE, the CHAP authentication method will not be used.
-            Format: booleanIf TRUE, the EAP authentication method will not be used.
-            Format: booleanIf TRUE, the MSCHAP authentication method will not be used.
-            Format: booleanIf TRUE, the MSCHAPv2 authentication method will not be used.
-            Format: booleanIf TRUE, the PAP authentication method will not be used.
-            Format: booleanIf 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: booleanIf 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: booleanpppoe settingPPP-over-Ethernet Settings.
+            Format: integer
+            Valid values: 0 - 4294967295If TRUE, specify that pppd should set the serial port to use hardware flow control with RTS and CTS signals.  This value should normally be set to FALSE.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf 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: integer
+            Valid values: 0 - 4294967295If 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: integer
+            Valid values: 0 - 4294967295If TRUE, stateful MPPE is used.  See pppd documentation for more information on stateful MPPE.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf 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: integer
+            Valid values: 0 - 16384If non-zero, instruct pppd to send packets no larger than the specified size.
+            Format: integer
+            Special values: autoIf TRUE, Van Jacobsen TCP header compression will not be requested.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, do not require the other side (usually the PPP server) to authenticate itself to the client.  If FALSE, require authentication from the remote side.  In almost all cases, this should be TRUE.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, BSD compression will not be requested.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, "deflate" compression will not be requested.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, the CHAP authentication method will not be used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, the EAP authentication method will not be used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, the MSCHAP authentication method will not be used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, the MSCHAPv2 authentication method will not be used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, the PAP authentication method will not be used.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session.  If either 64-bit or 128-bit MPPE is not available the session will fail.  Note that MPPE is not used on mobile broadband connections.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offIf TRUE, 128-bit MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session, and the "require-mppe" property must also be set to TRUE.  If 128-bit MPPE is not available the session will fail.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offpppoe settingPPP-over-Ethernet Settings.
         Properties:
         
             Alias: parentIf 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
             Alias: passwordPassword used to authenticate with the PPPoE service.
             Format: stringFlags indicating how to handle the "password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)
             Alias: serviceIf 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
             Alias: usernameUsername used to authenticate with the PPPoE service.
@@ -701,25 +1057,34 @@ Example: priority 5 from 1:2:3::5/128 table 45
         Properties:
         
             Alias: browser-onlyWhether the proxy configuration is for browser only.
-            Format: boolean
-            Alias: methodMethod for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)
-            Format: int32
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
+            Alias: methodMethod for proxy configuration, Default is "none" (0)
+            Format: choice (NMSettingProxyMethod)
+            Valid values: none (0), auto (1)
             Alias: pac-scriptThe PAC script. In the profile this must be an UTF-8 encoded javascript code that defines a FindProxyForURL() function. When setting the property in nmcli, a filename is accepted too. In that case, nmcli will read the content of the file and set the script. The prefixes "file://" and "js://" are supported to explicitly differentiate between the two.
             Format: string
             Alias: pac-urlPAC URL for obtaining PAC file.
             Format: stringserial settingSerial Link Settings.
         Properties:
         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: uint32Byte-width of the serial communication. The 8 in "8n1" for example.
-            Format: uint32Parity setting of the serial port.
-            Format: NMSettingSerialParity (byte)Time to delay between each byte sent to the modem, in microseconds.
-            Format: uint64Number of stop bits for communication on the serial port.  Either 1 or 2. The 1 in "8n1" for example.
-            Format: uint32sriov settingSR-IOV settings.
+            Format: integer
+            Valid values: 0 - 4294967295Byte-width of the serial communication. The 8 in "8n1" for example.
+            Format: integer
+            Valid values: 5 - 8Parity setting of the serial port.
+            Format: choice (NMSettingSerialParity)
+            Valid values: none/N/n (0), even/E/e (1), odd/O/o (2)Time to delay between each byte sent to the modem, in microseconds.
+            Format: integer
+            Valid values: 0 - 18446744073709551615Number of stop bits for communication on the serial port.  Either 1 or 2. The 1 in "8n1" for example.
+            Format: integer
+            Valid values: 1 - 2sriov settingSR-IOV settings.
         Properties:
-        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)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: uint32Array 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 vardicttc settingLinux Traffic Control Settings.
+        Whether to autoprobe virtual functions by a compatible driver.If set to "true" (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.If set to "false" (0), VFs will not be claimed and no network interfaces will be created for them.When set to "default" (-1), the global default is used; in case the global default is unspecified it is assumed to be "true" (1).
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownThe 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: integer
+            Valid values: 0 - 4294967295Array 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: list of sriov.vfs objectstc settingLinux Traffic Control Settings.
         Properties:
         
 Array of TC queueing disciplines. qdisc is a basic block in the
@@ -983,7 +1348,7 @@ Linux traffic control subsystem
     
   
 
-            Format: GPtrArray(NMTCQdisc)
+            Format: list of tc.qdiscs objects
  Array of TC traffic filters. Traffic control can manage the packet content during
  classification by using filters.
 
@@ -1074,240 +1439,358 @@ Linux traffic control subsystem
     
 
 
-            Format: GPtrArray(NMTCTfilter)team settingTeaming Settings.
+            Format: list of tc.tfilters objectsteam settingTeaming Settings.
         Properties:
         
             Alias: configThe 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: stringLink 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 vardictCorresponds to the teamd mcast_rejoin.count.
-            Format: int32Corresponds to the teamd mcast_rejoin.interval.
-            Format: int32Corresponds to the teamd notify_peers.count.
-            Format: int32Corresponds to the teamd notify_peers.interval.
-            Format: int32Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".
-            Format: stringCorresponds to the teamd runner.active.
-            Format: booleanCorresponds to the teamd runner.agg_select_policy.
-            Format: stringCorresponds to the teamd runner.fast_rate.
-            Format: booleanCorresponds to the teamd runner.hwaddr_policy.
-            Format: stringCorresponds to the teamd runner.min_ports.
-            Format: int32Corresponds to the teamd runner.sys_prio.
-            Format: int32Corresponds to the teamd runner.tx_balancer.name.
-            Format: stringCorresponds to the teamd runner.tx_balancer.interval.
-            Format: int32Corresponds to the teamd runner.tx_hash.
-            Format: array of stringteam-port settingTeam Port Settings.
+            Format: list of team.link-watchers objectsCorresponds to the teamd mcast_rejoin.count.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), disabled (0)Corresponds to the teamd mcast_rejoin.interval.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), default (0)Corresponds to the teamd notify_peers.count.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), disabled (0)Corresponds to the teamd notify_peers.interval.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), default (0)Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".
+            Format: string
+            Valid values: broadcast, roundrobin, random, activebackup, loadbalance, lacpCorresponds to the teamd runner.active.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offCorresponds to the teamd runner.agg_select_policy.
+            Format: string
+            Valid values: lacp_prio, lacp_prio_stable, bandwidth, count, port_configCorresponds to the teamd runner.fast_rate.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offCorresponds to the teamd runner.hwaddr_policy.
+            Format: string
+            Valid values: same_all, by_active, only_activeCorresponds to the teamd runner.min_ports.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), default (1)Corresponds to the teamd runner.sys_prio.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), default (65535)Corresponds to the teamd runner.tx_balancer.name.
+            Format: string
+            Valid values: basicCorresponds to the teamd runner.tx_balancer.interval.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), default (50)Corresponds to the teamd runner.tx_hash.
+            Format: list of strings
+            Valid values: eth, vlan, ipv4, ipv6, ip, l3, tcp, udp, sctp, l4team-port settingTeam Port Settings.
         Properties:
         
             Alias: configThe 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: stringCorresponds to the teamd ports.PORTIFNAME.lacp_key.
-            Format: int32Corresponds to the teamd ports.PORTIFNAME.lacp_prio.
-            Format: int32Link 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 vardictCorresponds to the teamd ports.PORTIFNAME.prio.
-            Format: int32Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.
-            Format: int32Corresponds to the teamd ports.PORTIFNAME.sticky.
-            Format: booleantun settingTunnel Settings.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), default (0)Corresponds to the teamd ports.PORTIFNAME.lacp_prio.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), default (255)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: list of team-port.link-watchers objectsCorresponds to the teamd ports.PORTIFNAME.prio.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (0), default (0)Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.
+            Format: integer
+            Valid values: -2147483648 - 2147483647
+            Special values: unset (-1), default (0)Corresponds to the teamd ports.PORTIFNAME.sticky.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offtun settingTunnel Settings.
         Properties:
         
             Alias: groupThe group ID which will own the device. If set to NULL everyone will be able to use the device.
             Format: string
-            Alias: modeThe 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
+            Alias: modeThe operating mode of the virtual device. Allowed values are "tun" (1) to create a layer 3 device and "tap" (2) to create an Ethernet-like layer 2 one.
+            Format: choice (NMSettingTunMode)
+            Valid values: tun (1), tap (2)
             Alias: multi-queueIf 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
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: ownerThe user ID which will own the device. If set to NULL everyone will be able to use the device.
             Format: string
             Alias: piIf TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.
-            Format: boolean
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: vnet-hdrIf TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.
-            Format: booleanvlan settingVLAN Settings.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offvlan settingVLAN Settings.
         Properties:
         
             Alias: egressFor 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
-            Alias: flagsOne 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)
+            Format: list of vlan.egress-priority-map objects
+            Alias: flagsOne or more flags which control the behavior and features of the VLAN interface.  Flags include "reorder-headers" (0x1) (reordering of output packet headers), "gvrp" (0x2) (use of the GVRP protocol), and "loose-binding" (0x4) (loose binding of the interface to its master device's operating state). "mvrp" (0x8) (use of the MVRP protocol).The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.
+            Format: flags (NMVlanFlags)
+            Valid values: reorder-headers (0x1), gvrp (0x2), loose-binding (0x4), mvrp (0x8)
             Alias: idThe VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 4095
             Alias: ingressFor incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities.  The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".
-            Format: array of string
+            Format: list of vlan.ingress-priority-map objects
             Alias: devIf 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: stringSpecifies the VLAN protocol to use for encapsulation.Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.
-            Format: stringvpn settingVPN Settings.
+            Format: string
+            Valid values: 802.1Q, 802.1advpn settingVPN Settings.
         Properties:
         Dictionary of key/value pairs of VPN plugin specific data.  Both keys and values must be strings.
-            Format: dict of string to stringIf 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: booleanDictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys.  Both keys and values must be strings.
-            Format: dict of string to string
+            Format: list of key/value optionsIf the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offDictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys.  Both keys and values must be strings.
+            Format: list of key/value options
             Alias: vpn-typeD-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: stringTimeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 4294967295
             Alias: userIf 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: stringvrf settingVRF settings.
         Properties:
         
             Alias: tableThe routing table for this VRF.
-            Format: uint32vxlan settingVXLAN Settings.
+            Format: integer
+            Valid values: 0 - 4294967295vxlan settingVXLAN Settings.
         Properties:
         Specifies the lifetime in seconds of FDB entries learnt by the kernel.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 4294967295
             Alias: destination-portSpecifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 65535
             Alias: idSpecifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.
-            Format: uint32Specifies whether netlink LL ADDR miss notifications are generated.
-            Format: booleanSpecifies whether netlink IP ADDR miss notifications are generated.
-            Format: booleanSpecifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.
-            Format: booleanSpecifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 16777215Specifies whether netlink LL ADDR miss notifications are generated.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offSpecifies whether netlink IP ADDR miss notifications are generated.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offSpecifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offSpecifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.
+            Format: integer
+            Valid values: 0 - 4294967295
             Alias: localIf given, specifies the source IP address to use in outgoing packets.
             Format: string
             Alias: devIf given, specifies the parent interface name or parent connection UUID.
             Format: stringSpecifies whether ARP proxy is turned on.
-            Format: boolean
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: remoteSpecifies 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: stringSpecifies whether route short circuit is turned on.
-            Format: boolean
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: source-port-maxSpecifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 65535
             Alias: source-port-minSpecifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.
-            Format: uint32Specifies the TOS value to use in outgoing packets.
-            Format: uint32Specifies the time-to-live value to use in outgoing packets.
-            Format: uint32wifi-p2p settingWi-Fi P2P Settings.
+            Format: integer
+            Valid values: 0 - 65535Specifies the TOS value to use in outgoing packets.
+            Format: integer
+            Valid values: 0 - 255Specifies the time-to-live value to use in outgoing packets.
+            Format: integer
+            Valid values: 0 - 255wifi-p2p settingWi-Fi P2P Settings.
         Properties:
         
             Alias: peerThe P2P device that should be connected to. Currently, this is the only way to create or join a group.
-            Format: stringThe 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 arrayFlags 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: uint32wimax settingWiMax Settings.
+            Format: MAC addressThe 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: bytesFlags 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: flags (NMSettingWirelessSecurityWpsMethod)
+            Valid values: default (0x0), disabled (0x1), auto (0x2), pbc (0x4), pin (0x8)wimax settingWiMax Settings.
         Properties:
         
             Alias: macIf 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
+            Format: string
             Alias: nspNetwork 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: string802-3-ethernet setting
+            Format: MAC address802-3-ethernet setting
           Alias: ethernetWired Ethernet Settings.
         Properties:
         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)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
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownWhen TRUE, enforce auto-negotiation of speed and duplex mode. If "speed" and "duplex" properties are both specified, only that single mode will be advertised and accepted during the link auto-negotiation process: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. When FALSE, "speed" and "duplex" properties should be both set or link configuration will be skipped.
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: cloned-macIf 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 arrayWhen 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: stringWith "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: MAC address
+            Special values: preserve, permanent, random, stableWhen a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.
+            Format: string
+            Valid values: half, fullWith "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
             Alias: macIf 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 arrayIf specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
-            Format: array of string
+            Format: MAC addressIf specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
+            Format: list of MAC addresses
             Alias: mtuIf non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.
-            Format: uint32Specific 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: strings390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.
-            Format: stringDictionary 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 stringIdentifies specific subchannels that this network device uses for communication with z/VM or s390 host.  Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels.  The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.
-            Format: array of stringWhen 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: uint32The 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: uint32If 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: stringwireguard settingWireGuard Settings.
+            Format: integer
+            Special values: autoSpecific 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: read onlys390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.
+            Format: string
+            Valid values: qeth, lcs, ctcDictionary 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: list of key/value optionsIdentifies 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: list of 802-3-ethernet.s390-subchannels objectsWhen 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: integer
+            Valid values: 0 - 4294967295The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of "phy" (0x2), "unicast" (0x4), "multicast" (0x8), "broadcast" (0x10), "arp" (0x20), "magic" (0x40) or the special values "default" (0x1) (to use global settings) and "ignore" (0x8000) (to disable management of Wake-on-LAN in NetworkManager).
+            Format: flags (NMSettingWiredWakeOnLan)
+            Valid values: phy (0x2), unicast (0x4), multicast (0x8), broadcast (0x10), arp (0x20), magic (0x40), default (0x1), ignore (0x8000)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: MAC addresswireguard settingWireGuard Settings.
         Properties:
         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: uint32Whether 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)Like ip4-auto-default-route, but for the IPv6 default route.
-            Format: NMTernary (int32)The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.
-            Format: uint32If 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: uint32Whether 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: booleanThe 256 bit private-key in base64 encoding.
+            Format: integer
+            Valid values: 0 - 4294967295Whether 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: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownLike ip4-auto-default-route, but for the IPv6 default route.
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownThe listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.
+            Format: integer
+            Valid values: 0 - 65535If 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: integer
+            Special values: autoWhether 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
+            Valid values: true/yes/on, false/no/offThe 256 bit private-key in base64 encoding.
             Format: stringFlags indicating how to handle the "private-key" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)802-11-wireless setting
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)802-11-wireless setting
           Alias: wifiWi-Fi Settings.
         Properties:
-        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)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: stringIf 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 arrayWireless 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
-            Alias: cloned-macIf 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 arrayWith "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.
+        Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from "default" (-1) only when the interface is configured in AP mode.If set to "true" (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.If set to "false" (0), devices can talk to each other.When set to "default" (-1), the global default is used; in case the global default is unspecified it is assumed to be "false" (0).
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknown802.11 frequency band of the network.  One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11.  This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible.  This setting depends on specific driver capability and may not work with all drivers.
+            Format: string
+            Valid values: a, bgIf 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: MAC addressWireless 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: integer
+            Valid values: 0 - 4294967295
+            Alias: cloned-macIf 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", "stable" and "stable-ssid" are supported. "preserve" means not to touch the MAC address on activation. "permanent" means to use the permanent hardware address of the device. "random" creates a random MAC address on each connect. "stable" creates a hashed MAC address based on connection.stable-id and a machine dependent key. "stable-ssid" creates a hashed MAC address based on the SSID, the same as setting the stable-id to "${NETWORK_SSID}".If unspecified, the value can be overwritten via global defaults, see manual of NetworkManager.conf. If still unspecified, it defaults to "preserve" (older versions of NetworkManager may use a different default value).On D-Bus, this field is expressed as "assigned-mac-address" or the deprecated "cloned-mac-address".
+            Format: MAC address
+            Special values: preserve, permanent, random, stable, stable-ssidWith "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: stringIf 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
+            Format: boolean
+            Valid values: true/yes/on, false/no/off
             Alias: macIf 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 arrayA 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 stringOne 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).
+            Format: MAC addressA list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply.  Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").
+            Format: list of MAC addressesOne of "default" (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  "never" (1) (never randomize the MAC address), or "always" (2) (always randomize the MAC address).
             This property is deprecated since version 1.4.
             Use the "cloned-mac-address" property instead.
-            Format: uint32
+            Format: choice (NMSettingMacRandomization)
+            Valid values: default (0), never (1), always (2)
             Alias: modeWi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.
-            Format: string
+            Format: string
+            Valid values: infrastructure, adhoc, ap, mesh
             Alias: mtuIf non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.
-            Format: uint32One 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: uint32A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network.  NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.This is not a regular property that the user would configure. Instead, NetworkManager automatically sets the seen BSSIDs and tracks them internally in "/var/lib/NetworkManager/seen-bssids" file.
-            Format: array of string
+            Format: integer
+            Special values: autoOne of "disable" (2) (disable Wi-Fi power saving), "enable" (3) (enable Wi-Fi power saving), "ignore" (1) (don't touch currently configure setting) or "default" (0) (use the globally configured value). All other values are reserved.
+            Format: choice (NMSettingWirelessPowersave)
+            Valid values: default (0), ignore (1), disable (2), enable (3)A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network.  NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.This is not a regular property that the user would configure. Instead, NetworkManager automatically sets the seen BSSIDs and tracks them internally in "/var/lib/NetworkManager/seen-bssids" file.
+            Format: read only
             Alias: ssidSSID of the Wi-Fi network. Must be specified.
-            Format: byte arrayThe 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: uint32802-11-wireless-security setting
+            Format: stringThe NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of "any" (0x2), "disconnect" (0x4), "magic" (0x8), "gtk-rekey-failure" (0x10), "eap-identity-request" (0x20), "4way-handshake" (0x40), "rfkill-release" (0x80), "tcp" (0x100) or the special values "default" (0x1) (to use global settings) and "ignore" (0x8000) (to disable management of Wake-on-LAN in NetworkManager).
+            Format: flags (NMSettingWirelessWakeOnWLan)
+            Valid values: any (0x2), disconnect (0x4), magic (0x8), gtk-rekey-failure (0x10), eap-identity-request (0x20), 4way-handshake (0x40), rfkill-release (0x80), tcp (0x100), all (0x1fe), default (0x1), ignore (0x8000)802-11-wireless-security setting
           Alias: wifi-secWi-Fi Security Settings.
         Properties:
         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: stringIndicates 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: int32A 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 stringKey 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: stringThe login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").
+            Format: string
+            Valid values: open, shared, leapIndicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection.  One of "default" (0) (use global default value), "disable" (1) (disable FILS), "optional" (2) (enable FILS if the supplicant and the access point support it) or "required" (3) (enable FILS and fail if not supported).  When set to "default" (0) and no global default is set, FILS will be optionally enabled.
+            Format: choice (NMSettingWirelessSecurityFils)
+            Valid values: default (0), disable (1), optional (2), required (3)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: list of strings
+            Valid values: wep40, wep104, tkip, ccmpKey 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
+            Valid values: none, ieee8021x, wpa-psk, wpa-eap, wpa-eap-suite-b-192, sae, oweThe login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").
             Format: stringFlags indicating how to handle the "leap-password" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").
             Format: stringA list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty.  Each list element may be one of "tkip" or "ccmp".
-            Format: array of stringIndicates 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: int32List 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 stringPre-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: list of strings
+            Valid values: tkip, ccmpIndicates whether Protected Management Frames (802.11w) must be enabled for the connection.  One of "default" (0) (use global default value), "disable" (1) (disable PMF), "optional" (2) (enable PMF if the supplicant and the access point support it) or "required" (3) (enable PMF and fail if not supported).  When set to "default" (0) and no global default is set, PMF will be optionally enabled.
+            Format: choice (NMSettingWirelessSecurityPmf)
+            Valid values: default (0), disable (1), optional (2), required (3)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: list of strings
+            Valid values: wpa, rsnPre-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: stringFlags indicating how to handle the "psk" property.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (uint32)Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.
-            See  for flag values.
-          
-            Format: NMSettingSecretFlags (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.
-            Format: NMWepKeyType (uint32)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: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.
+            Format: flags (NMSettingSecretFlags)
+            Valid values: none (0x0), agent-owned (0x1), not-saved (0x2), not-required (0x4)Controls the interpretation of WEP keys.  Allowed values are "key" (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or "passphrase" (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.
+            Format: choice (NMWepKeyType)
+            Valid values: unknown (0), key (1), passphrase (2)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: stringIndex 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: stringIndex 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: stringIndex 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: stringWhen 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: uint32Flags 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: uint32wpan settingIEEE 802.15.4 (WPAN) MAC Settings.
+            Format: integer
+            Valid values: 0 - 3Flags 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: flags (NMSettingWirelessSecurityWpsMethod)
+            Valid values: default (0x0), disabled (0x1), auto (0x2), pbc (0x4), pin (0x8)wpan settingIEEE 802.15.4 (WPAN) MAC Settings.
         Properties:
         
             Alias: channelIEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".
-            Format: int32
+            Format: integer
+            Valid values: -32768 - 32767
+            Special values: default (-1)
             Alias: macIf specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.
-            Format: string
+            Format: WPAN MAC address
             Alias: pageIEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".
-            Format: int32
+            Format: integer
+            Valid values: -32768 - 32767
+            Special values: default (-1)
             Alias: pan-idIEEE 802.15.4 Personal Area Network (PAN) identifier.
-            Format: uint32
+            Format: integer
+            Valid values: 0 - 65535
+            Special values: unset (0xffff)
             Alias: short-addrShort IEEE 802.15.4 address to be used within a restricted environment.
-            Format: uint32bond-port settingBond Port Settings.
+            Format: integer
+            Valid values: 0 - 65535
+            Special values: unset (0xffff)bond-port settingBond Port Settings.
         Properties:
         
             Alias: prioThe port priority for bond active port re-selection during failover. A higher number means a higher priority in selection. The primary port has the highest priority. This option is only compatible with active-backup, balance-tlb and balance-alb modes.
-            Format: int32
+            Format: integer
+            Valid values: -2147483648 - 2147483647
             Alias: queue-idThe queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.
-            Format: uint32hostname settingHostname settings.
+            Format: integer
+            Valid values: 0 - 65535hostname settingHostname settings.
         Properties:
-        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)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)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)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: int32link settingLink settings.
+        Whether the system hostname can be determined from DHCP on this connection.When set to "default" (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be "true" (1).
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownWhether the system hostname can be determined from reverse DNS lookup of addresses on this device.When set to "default" (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be "true" (1).
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownIf set to "true" (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).If set to "false" (0), the hostname can be set from this device even if it doesn't have the default route.When set to "default" (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be "false" (0).
+            Format: ternary
+            Valid values: true/yes/on, false/no/off, default/unknownThe 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: integer
+            Valid values: -2147483648 - 2147483647hsr settingHSR/PRP Settings.
+        Properties:
+        
+            Alias: multicast-specThe last byte of supervision address.
+            Format: integer
+            Valid values: 0 - 255
+            Alias: port1The port1 interface name of the HSR. This property is mandatory.
+            Format: string
+            Alias: port2The port2 interface name of the HSR. This property is mandatory.
+            Format: stringThe protocol used by the interface, whether it is PRP or HSR.
+            Format: boolean
+            Valid values: true/yes/on, false/no/offlink settingLink settings.
         Properties:
         The maximum size of a packet built by the Generic Receive Offload stack for this device. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.
-            Format: int64The maximum segments of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.
-            Format: int64The maximum size of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.
-            Format: int64The size of the transmit queue for the device, in number of packets. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.
-            Format: int64loopback settingLoopback Link Settings.
+            Format: integer
+            Valid values: -1 - 4294967295
+            Special values: default (-1)The maximum segments of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.
+            Format: integer
+            Valid values: -1 - 4294967295
+            Special values: default (-1)The maximum size of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.
+            Format: integer
+            Valid values: -1 - 4294967295
+            Special values: default (-1)The size of the transmit queue for the device, in number of packets. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.
+            Format: integer
+            Valid values: -1 - 4294967295
+            Special values: default (-1)loopback settingLoopback Link Settings.
         Properties:
         
             Alias: mtuIf non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.
-            Format: uint32veth settingVeth Settings.
+            Format: integer
+            Special values: autoveth settingVeth Settings.
         Properties:
         
             Alias: peerThis property specifies the peer interface name of the veth. This property is mandatory.
diff --git a/man/nm-settings-nmcli.xsl b/man/nm-settings-nmcli.xsl
index 5817e8e2..794ee507 100644
--- a/man/nm-settings-nmcli.xsl
+++ b/man/nm-settings-nmcli.xsl
@@ -176,6 +176,16 @@
             Format: 
           
         
+        
+          
+            Valid values: 
+          
+        
+        
+          
+            Special values: 
+          
+        
       
     
   
diff --git a/man/nmcli-examples.7 b/man/nmcli-examples.7
index a7dc8642..76b64fe4 100644
--- a/man/nmcli-examples.7
+++ b/man/nmcli-examples.7
@@ -2,12 +2,12 @@
 .\"     Title: nmcli-examples
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: Examples
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NMCLI\-EXAMPLES" "7" "" "NetworkManager 1\&.44\&.2" "Examples"
+.TH "NMCLI\-EXAMPLES" "7" "" "NetworkManager 1\&.45\&.90" "Examples"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -237,7 +237,7 @@ $ \fBnmcli \-\-ask con up my\-vpn\-con\fR
 This command activates a VPN connection profile enabling nmcli to interact with the user (\*(Aq\-\-ask\*(Aq): this will allow nmcli to prompt for the VPN password on the command line when the
 \fIpassword\-flags\fR
 are set to \*(Aq0x02\*(Aq (\*(Aqalways ask\*(Aq, see
-\fBnm-settings\fR(5)
+\fBnm-settings-nmcli\fR(5)
 )\&. This is particularly useful for OTP based VPNs, as the user needs to be prompted for the password each time the connection is activated\&.
 .PP
 \fBExample\ \&8.\ \&Adding a bonding master and two slave connection profiles\fR
@@ -829,7 +829,7 @@ Type "Yes" to commit the changes: \fBYes\fR
 \fBnmcli\fR(1),
 \fBNetworkManager\fR(8),
 \fBNetworkManager.conf\fR(5),
-\fBnm-settings\fR(5),
+\fBnm-settings-nmcli\fR(5),
 \fBnm-online\fR(1),
 \fBnm-applet\fR(1),
 \fBnm-connection-editor\fR(1)
diff --git a/man/nmcli-examples.xml b/man/nmcli-examples.xml
index 1fd7b766..2c7e16ab 100644
--- a/man/nmcli-examples.xml
+++ b/man/nmcli-examples.xml
@@ -7,20 +7,11 @@
 ]>
 
 
 
 
@@ -189,7 +180,7 @@ B,DISPATCH
         This command activates a VPN connection profile enabling nmcli to interact with the user
         ('--ask'): this will allow nmcli to prompt for the VPN password on the command line when
         the password-flags are set to '0x02' ('always ask', see
-        nm-settings5
+        nm-settings-nmcli5
         ).
         This is particularly useful for OTP based VPNs, as the user needs to be prompted for the
         password each time the connection is activated.
@@ -675,7 +666,7 @@ Type "Yes" to commit the changes: Yes
       nmcli1,
       NetworkManager8,
       NetworkManager.conf5,
-      nm-settings5,
+      nm-settings-nmcli5,
       nm-online1,
       nm-applet1,
       nm-connection-editor1
diff --git a/man/nmcli.1 b/man/nmcli.1
index b5df1750..10775351 100644
--- a/man/nmcli.1
+++ b/man/nmcli.1
@@ -2,12 +2,12 @@
 .\"     Title: nmcli
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: General Commands Manual
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NMCLI" "1" "" "NetworkManager 1\&.44\&.2" "General Commands Manual"
+.TH "NMCLI" "1" "" "NetworkManager 1\&.45\&.90" "General Commands Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
diff --git a/man/nmcli.xml b/man/nmcli.xml
index 9bda9db0..6b3054c3 100644
--- a/man/nmcli.xml
+++ b/man/nmcli.xml
@@ -7,20 +7,11 @@
 ]>
 
 
 
 
diff --git a/man/nmtui.1 b/man/nmtui.1
index 287488c8..d6e89157 100644
--- a/man/nmtui.1
+++ b/man/nmtui.1
@@ -2,12 +2,12 @@
 .\"     Title: nmtui
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets vsnapshot 
-.\"      Date: 10/03/2023
+.\"      Date: 01/25/2024
 .\"    Manual: General Commands Manual
-.\"    Source: NetworkManager 1.44.2
+.\"    Source: NetworkManager 1.45.90
 .\"  Language: English
 .\"
-.TH "NMTUI" "1" "" "NetworkManager 1\&.44\&.2" "General Commands Manual"
+.TH "NMTUI" "1" "" "NetworkManager 1\&.45\&.90" "General Commands Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
diff --git a/man/nmtui.xml b/man/nmtui.xml
index 8bf6dd58..f610be9d 100644
--- a/man/nmtui.xml
+++ b/man/nmtui.xml
@@ -7,20 +7,11 @@
 ]>
 
 
 
 
diff --git a/meson.build b/meson.build
index 9c61de7e..86c983b8 100644
--- a/meson.build
+++ b/meson.build
@@ -6,7 +6,7 @@ project(
 #  - add corresponding NM_VERSION_x_y_z macros in
 #    "src/libnm-core-public/nm-version-macros.h.in"
 #  - update number in configure.ac
-  version: '1.44.2',
+  version: '1.45.90',
   license: 'GPL2+',
   default_options: [
     'buildtype=debugoptimized',
@@ -273,9 +273,8 @@ libsystemd_login_dep = dependency('libsystemd-login', version: '>= 183', require
 config_h.set10('HAVE_LIBSYSTEMD', libsystemd_dep.found())
 
 systemd_dep = dependency('systemd', required: false)
-have_systemd_200 = systemd_dep.found() and systemd_dep.version().version_compare('>= 200')
 
-gio_unix_dep = dependency('gio-unix-2.0', version: '>= 2.40')
+gio_unix_dep = dependency('gio-unix-2.0', version: '>= 2.42')
 
 glib_dep = declare_dependency(
   dependencies: [
@@ -283,8 +282,8 @@ glib_dep = declare_dependency(
     dependency('gmodule-2.0'),
   ],
   compile_args: [
-    '-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_40',
-    '-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_40',
+    '-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_42',
+    '-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_42',
   ]
 )
 
@@ -979,9 +978,13 @@ endif
 
 if enable_docs
   assert(enable_introspection, '-Ddocs=true requires -Dintrospection=true')
-  assert(meson.version().version_compare('>= 0.46.0'), '-Ddocs requires meson >= 0.46')
+  assert(meson.version().version_compare('>= 0.49.0'), '-Ddocs requires meson >= 0.49')
   subdir('man')
   subdir('docs')
+  meson.add_dist_script(
+    'tools/meson-dist-data.sh',
+    '--build-root', build_root
+  )
 endif
 
 configure_file(
diff --git a/po/NetworkManager.pot b/po/NetworkManager.pot
index a1725fb0..8c75c02d 100644
--- a/po/NetworkManager.pot
+++ b/po/NetworkManager.pot
@@ -6,10 +6,10 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: NetworkManager 1.44.2\n"
+"Project-Id-Version: NetworkManager 1.45.90\n"
 "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/"
 "NetworkManager/issues\n"
-"POT-Creation-Date: 2023-10-03 16:28+0200\n"
+"POT-Creation-Date: 2024-01-25 01:18+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME \n"
 "Language-Team: LANGUAGE \n"
@@ -172,7 +172,7 @@ msgid "%s %u"
 msgstr ""
 
 #: src/core/devices/adsl/nm-device-adsl.c:118
-#: src/libnmc-setting/nm-meta-setting-desc.c:8463
+#: src/libnmc-setting/nm-meta-setting-desc.c:8647
 msgid "ADSL connection"
 msgstr ""
 
@@ -249,7 +249,7 @@ msgid "Wired connection %d"
 msgstr ""
 
 #: src/core/devices/nm-device-ethernet.c:1641
-#: src/libnmc-setting/nm-meta-setting-desc.c:8504
+#: src/libnmc-setting/nm-meta-setting-desc.c:8689
 msgid "Veth connection"
 msgstr ""
 
@@ -262,7 +262,7 @@ msgid "Wired connection"
 msgstr ""
 
 #: src/core/devices/nm-device-infiniband.c:160
-#: src/libnmc-setting/nm-meta-setting-desc.c:8477
+#: src/libnmc-setting/nm-meta-setting-desc.c:8662
 msgid "InfiniBand connection"
 msgstr ""
 
@@ -283,17 +283,17 @@ msgid "TUN connection"
 msgstr ""
 
 #: src/core/devices/nm-device-vlan.c:380
-#: src/libnmc-setting/nm-meta-setting-desc.c:8505
+#: src/libnmc-setting/nm-meta-setting-desc.c:8690
 msgid "VLAN connection"
 msgstr ""
 
 #: src/core/devices/nm-device-vrf.c:185
-#: src/libnmc-setting/nm-meta-setting-desc.c:8507
+#: src/libnmc-setting/nm-meta-setting-desc.c:8692
 msgid "VRF connection"
 msgstr ""
 
 #: src/core/devices/nm-device-vxlan.c:385
-#: src/libnmc-setting/nm-meta-setting-desc.c:8508
+#: src/libnmc-setting/nm-meta-setting-desc.c:8693
 msgid "VXLAN connection"
 msgstr ""
 
@@ -305,7 +305,7 @@ msgstr ""
 msgid "Team connection"
 msgstr ""
 
-#: src/core/devices/wifi/nm-device-olpc-mesh.c:112 src/nmcli/devices.c:1400
+#: src/core/devices/wifi/nm-device-olpc-mesh.c:112 src/nmcli/devices.c:1415
 msgid "Mesh"
 msgstr ""
 
@@ -451,11 +451,11 @@ msgstr ""
 msgid "Failed to determine AP security information"
 msgstr ""
 
-#: src/core/dhcp/nm-dhcp-dhclient-utils.c:319
+#: src/core/dhcp/nm-dhcp-dhclient-utils.c:323
 msgid "# Created by NetworkManager\n"
 msgstr ""
 
-#: src/core/dhcp/nm-dhcp-dhclient-utils.c:332
+#: src/core/dhcp/nm-dhcp-dhclient-utils.c:336
 #, c-format
 msgid ""
 "# Merged from %s\n"
@@ -472,11 +472,12 @@ msgstr ""
 msgid "Cannot create '%s': %s"
 msgstr ""
 
-#: src/core/main-utils.c:196
-msgid "%s is already running (pid %"
+#: src/core/main-utils.c:195
+#, c-format
+msgid "%s is already running (pid %lld)\n"
 msgstr ""
 
-#: src/core/main-utils.c:266 src/core/main.c:368
+#: src/core/main-utils.c:263 src/core/main.c:368
 #, c-format
 msgid "%s.  Please use --help to see a list of valid options.\n"
 msgstr ""
@@ -530,8 +531,8 @@ msgid "Could not daemonize: %s [error %u]\n"
 msgstr ""
 
 #: src/core/nm-config.c:544 src/libnm-core-impl/nm-setting-ovs-bridge.c:187
-#: src/libnmc-setting/nm-meta-setting-desc.c:2200
-#: src/libnmc-setting/nm-meta-setting-desc.c:4346
+#: src/libnmc-setting/nm-meta-setting-desc.c:2188
+#: src/libnmc-setting/nm-meta-setting-desc.c:4334
 #, c-format
 msgid "'%s' is not valid"
 msgstr ""
@@ -597,39 +598,39 @@ msgstr ""
 msgid "Show NetworkManager options"
 msgstr ""
 
-#: src/core/nm-manager.c:6920 src/libnmc-setting/nm-meta-setting-desc.c:8506
+#: src/core/nm-manager.c:6886 src/libnmc-setting/nm-meta-setting-desc.c:8691
 msgid "VPN connection"
 msgstr ""
 
 #: src/core/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:5650
-#: src/libnm-client-impl/nm-device.c:1780
-#: src/libnm-core-impl/nm-connection.c:3244 src/nmtui/nm-editor-utils.c:196
+#: src/libnm-client-impl/nm-device.c:1781
+#: src/libnm-core-impl/nm-connection.c:3237 src/nmtui/nm-editor-utils.c:196
 msgid "Bond"
 msgstr ""
 
 #: src/core/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:5721
-#: src/libnm-client-impl/nm-device.c:1782
-#: src/libnm-core-impl/nm-connection.c:3246 src/nmtui/nm-editor-utils.c:214
+#: src/libnm-client-impl/nm-device.c:1783
+#: src/libnm-core-impl/nm-connection.c:3239 src/nmtui/nm-editor-utils.c:214
 msgid "Team"
 msgstr ""
 
 #: src/core/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:6058
-#: src/libnm-client-impl/nm-device.c:1784
-#: src/libnm-core-impl/nm-connection.c:3248 src/nmtui/nm-editor-utils.c:205
+#: src/libnm-client-impl/nm-device.c:1785
+#: src/libnm-core-impl/nm-connection.c:3241 src/nmtui/nm-editor-utils.c:205
 msgid "Bridge"
 msgstr ""
 
-#: src/core/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh.c:9021
+#: src/core/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh.c:9024
 #: src/libnm-core-impl/nm-team-utils.c:2391
 msgid "invalid json"
 msgstr ""
 
-#: src/libnm-client-impl/nm-client.c:3815
+#: src/libnm-client-impl/nm-client.c:3816
 #, c-format
 msgid "request succeeded with %s but object is in an unsuitable state"
 msgstr ""
 
-#: src/libnm-client-impl/nm-client.c:3907
+#: src/libnm-client-impl/nm-client.c:3908
 #, c-format
 msgid "operation succeeded but object %s does not exist"
 msgstr ""
@@ -756,7 +757,7 @@ msgstr ""
 msgid "The MACs of the device and the connection didn't match."
 msgstr ""
 
-#: src/libnm-client-impl/nm-device-ip-tunnel.c:266
+#: src/libnm-client-impl/nm-device-ip-tunnel.c:285
 msgid "The connection was not an IP tunnel connection."
 msgstr ""
 
@@ -856,133 +857,137 @@ msgstr ""
 msgid "The connection was not a wpan connection."
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1760 src/nmtui/nm-editor-utils.c:144
+#: src/libnm-client-impl/nm-device.c:1761 src/nmtui/nm-editor-utils.c:144
 msgid "Ethernet"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1762 src/nmtui/nm-editor-utils.c:160
+#: src/libnm-client-impl/nm-device.c:1763 src/nmtui/nm-editor-utils.c:160
 #: src/nmtui/nmtui-radio.c:58
 msgid "Wi-Fi"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1764
+#: src/libnm-client-impl/nm-device.c:1765
 msgid "Bluetooth"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1766
+#: src/libnm-client-impl/nm-device.c:1767
 msgid "OLPC Mesh"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1768
+#: src/libnm-client-impl/nm-device.c:1769
 msgid "Open vSwitch Interface"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1770
+#: src/libnm-client-impl/nm-device.c:1771
 msgid "Open vSwitch Port"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1772
+#: src/libnm-client-impl/nm-device.c:1773
 msgid "Open vSwitch Bridge"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1774
+#: src/libnm-client-impl/nm-device.c:1775
 msgid "WiMAX"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1776 src/nmtui/nm-editor-utils.c:178
+#: src/libnm-client-impl/nm-device.c:1777 src/nmtui/nm-editor-utils.c:178
 msgid "Mobile Broadband"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1778
-#: src/libnm-core-impl/nm-connection.c:3252 src/nmtui/nm-editor-utils.c:169
+#: src/libnm-client-impl/nm-device.c:1779
+#: src/libnm-core-impl/nm-connection.c:3245 src/nmtui/nm-editor-utils.c:169
 msgid "InfiniBand"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1786
-#: src/libnm-core-impl/nm-connection.c:3250 src/nmtui/nm-editor-utils.c:223
+#: src/libnm-client-impl/nm-device.c:1787
+#: src/libnm-core-impl/nm-connection.c:3243 src/nmtui/nm-editor-utils.c:223
 #: src/nmtui/nmt-page-vlan.c:57
 msgid "VLAN"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1788
+#: src/libnm-client-impl/nm-device.c:1789
 msgid "ADSL"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1790
+#: src/libnm-client-impl/nm-device.c:1791
 msgid "MACVLAN"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1792
+#: src/libnm-client-impl/nm-device.c:1793
 msgid "VXLAN"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1794
+#: src/libnm-client-impl/nm-device.c:1795
 msgid "IPTunnel"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1796
+#: src/libnm-client-impl/nm-device.c:1797
 msgid "Tun"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1798 src/nmtui/nm-editor-utils.c:152
+#: src/libnm-client-impl/nm-device.c:1799 src/nmtui/nm-editor-utils.c:152
 msgid "Veth"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1800 src/nmtui/nm-editor-utils.c:239
+#: src/libnm-client-impl/nm-device.c:1801 src/nmtui/nm-editor-utils.c:239
 #: src/nmtui/nmt-page-macsec.c:99
 msgid "MACsec"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1802
+#: src/libnm-client-impl/nm-device.c:1803
 msgid "Dummy"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1804
+#: src/libnm-client-impl/nm-device.c:1805
 msgid "PPP"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1806
+#: src/libnm-client-impl/nm-device.c:1807
 msgid "IEEE 802.15.4"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1808
+#: src/libnm-client-impl/nm-device.c:1809
 msgid "6LoWPAN"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1810
-#: src/libnm-core-impl/nm-connection.c:3258 src/nmtui/nm-editor-utils.c:271
+#: src/libnm-client-impl/nm-device.c:1811
+#: src/libnm-core-impl/nm-connection.c:3251 src/nmtui/nm-editor-utils.c:271
 #: src/nmtui/nmt-page-wireguard.c:57
 msgid "WireGuard"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1812
+#: src/libnm-client-impl/nm-device.c:1813
 msgid "Wi-Fi P2P"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1814
+#: src/libnm-client-impl/nm-device.c:1815
 msgid "VRF"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1816
+#: src/libnm-client-impl/nm-device.c:1817
 msgid "Loopback"
 msgstr ""
 
+#: src/libnm-client-impl/nm-device.c:1819
+msgid "HSR"
+msgstr ""
+
 #. TRANSLATORS: Unknown reason for a device state change (NMDeviceStateReason)
 #. TRANSLATORS: Unknown reason for a connection state change (NMActiveConnectionStateReason)
-#: src/libnm-client-impl/nm-device.c:1823 src/libnmc-base/nm-client-utils.c:352
-#: src/libnmc-base/nm-client-utils.c:473 src/nmcli/utils.c:1838
+#: src/libnm-client-impl/nm-device.c:1826 src/libnmc-base/nm-client-utils.c:352
+#: src/libnmc-base/nm-client-utils.c:473 src/nmcli/utils.c:1841
 msgid "Unknown"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1848
+#: src/libnm-client-impl/nm-device.c:1851
 msgid "Wired"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1880
+#: src/libnm-client-impl/nm-device.c:1883
 msgid "PCI"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:1882
+#: src/libnm-client-impl/nm-device.c:1885
 msgid "USB"
 msgstr ""
 
@@ -992,19 +997,19 @@ msgstr ""
 #. * "%2$s (%1$s)" if there's no grammatical way to combine
 #. * the strings otherwise.
 #.
-#: src/libnm-client-impl/nm-device.c:2181
-#: src/libnm-client-impl/nm-device.c:2200
+#: src/libnm-client-impl/nm-device.c:2184
+#: src/libnm-client-impl/nm-device.c:2203
 #, c-format
 msgctxt "long device name"
 msgid "%s %s"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:2860
+#: src/libnm-client-impl/nm-device.c:2863
 #, c-format
 msgid "The connection was not valid: %s"
 msgstr ""
 
-#: src/libnm-client-impl/nm-device.c:2872
+#: src/libnm-client-impl/nm-device.c:2875
 msgid "The interface names of the device and the connection didn't match"
 msgstr ""
 
@@ -1139,66 +1144,66 @@ msgstr ""
 msgid "has duplicate UUIDs"
 msgstr ""
 
-#: src/libnm-core-impl/nm-connection.c:1846
+#: src/libnm-core-impl/nm-connection.c:1839
 msgid "setting not found"
 msgstr ""
 
-#: src/libnm-core-impl/nm-connection.c:1900
-#: src/libnm-core-impl/nm-connection.c:1925
-#: src/libnm-core-impl/nm-connection.c:1950
+#: src/libnm-core-impl/nm-connection.c:1893
+#: src/libnm-core-impl/nm-connection.c:1918
+#: src/libnm-core-impl/nm-connection.c:1943
 msgid "setting is required for non-slave connections"
 msgstr ""
 
-#: src/libnm-core-impl/nm-connection.c:1913
-#: src/libnm-core-impl/nm-connection.c:1938
-#: src/libnm-core-impl/nm-connection.c:1963
+#: src/libnm-core-impl/nm-connection.c:1906
+#: src/libnm-core-impl/nm-connection.c:1931
+#: src/libnm-core-impl/nm-connection.c:1956
 msgid "setting not allowed in slave connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-connection.c:2076
+#: src/libnm-core-impl/nm-connection.c:2068
 msgid "Unexpected failure to normalize the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-connection.c:2137
+#: src/libnm-core-impl/nm-connection.c:2129
 msgid "Unexpected failure to verify the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-connection.c:2174
+#: src/libnm-core-impl/nm-connection.c:2166
 #, c-format
 msgid "unexpected uuid %s instead of %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-connection.c:3103
-#: src/libnm-core-impl/nm-setting-8021x.c:2623
-#: src/libnm-core-impl/nm-setting-8021x.c:2660
-#: src/libnm-core-impl/nm-setting-8021x.c:2678
-#: src/libnm-core-impl/nm-setting-8021x.c:2816
-#: src/libnm-core-impl/nm-setting-adsl.c:173
-#: src/libnm-core-impl/nm-setting-bluetooth.c:128
-#: src/libnm-core-impl/nm-setting-bluetooth.c:192
-#: src/libnm-core-impl/nm-setting-bluetooth.c:209
-#: src/libnm-core-impl/nm-setting-cdma.c:144
-#: src/libnm-core-impl/nm-setting-connection.c:1151
-#: src/libnm-core-impl/nm-setting-connection.c:1189
-#: src/libnm-core-impl/nm-setting-connection.c:1518
-#: src/libnm-core-impl/nm-setting-ip-config.c:5500
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:407
-#: src/libnm-core-impl/nm-setting-olpc-mesh.c:99
+#: src/libnm-core-impl/nm-connection.c:3095
+#: src/libnm-core-impl/nm-setting-8021x.c:2621
+#: src/libnm-core-impl/nm-setting-8021x.c:2658
+#: src/libnm-core-impl/nm-setting-8021x.c:2676
+#: src/libnm-core-impl/nm-setting-8021x.c:2814
+#: src/libnm-core-impl/nm-setting-adsl.c:171
+#: src/libnm-core-impl/nm-setting-bluetooth.c:126
+#: src/libnm-core-impl/nm-setting-bluetooth.c:190
+#: src/libnm-core-impl/nm-setting-bluetooth.c:207
+#: src/libnm-core-impl/nm-setting-cdma.c:142
+#: src/libnm-core-impl/nm-setting-connection.c:1210
+#: src/libnm-core-impl/nm-setting-connection.c:1248
+#: src/libnm-core-impl/nm-setting-connection.c:1577
+#: src/libnm-core-impl/nm-setting-ip-config.c:5480
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:405
+#: src/libnm-core-impl/nm-setting-olpc-mesh.c:97
 #: src/libnm-core-impl/nm-setting-ovs-patch.c:75
-#: src/libnm-core-impl/nm-setting-pppoe.c:146
-#: src/libnm-core-impl/nm-setting-vpn.c:548
+#: src/libnm-core-impl/nm-setting-pppoe.c:144
+#: src/libnm-core-impl/nm-setting-vpn.c:545
 #: src/libnm-core-impl/nm-setting-wifi-p2p.c:119
-#: src/libnm-core-impl/nm-setting-wimax.c:108
-#: src/libnm-core-impl/nm-setting-wireless-security.c:916
-#: src/libnm-core-impl/nm-setting-wireless.c:845
+#: src/libnm-core-impl/nm-setting-wimax.c:106
+#: src/libnm-core-impl/nm-setting-wireless-security.c:912
+#: src/libnm-core-impl/nm-setting-wireless.c:895
 msgid "property is missing"
 msgstr ""
 
-#: src/libnm-core-impl/nm-connection.c:3256
+#: src/libnm-core-impl/nm-connection.c:3249
 msgid "IP Tunnel"
 msgstr ""
 
-#: src/libnm-core-impl/nm-connection.c:3260
+#: src/libnm-core-impl/nm-connection.c:3253
 msgid "TUN/TAP"
 msgstr ""
 
@@ -1284,458 +1289,459 @@ msgid "ignoring invalid DNS server IPv%c address '%s'"
 msgstr ""
 
 #: src/libnm-core-impl/nm-keyfile.c:1177
-#: src/libnmc-setting/nm-meta-setting-desc.c:1663
+#: src/libnmc-setting/nm-meta-setting-desc.c:1678
 #, c-format
 msgid "invalid option '%s', use one of [%s]"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1252
+#: src/libnm-core-impl/nm-keyfile.c:1257
 msgid "ignoring invalid MAC address"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1328
+#: src/libnm-core-impl/nm-keyfile.c:1333
 #, c-format
 msgid "ignoring invalid bond option %s%s%s = %s%s%s: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1518
+#: src/libnm-core-impl/nm-keyfile.c:1523
 msgid "ignoring invalid SSID"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1536
+#: src/libnm-core-impl/nm-keyfile.c:1541
 msgid "ignoring invalid raw password"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1681
+#: src/libnm-core-impl/nm-keyfile.c:1686
 msgid "invalid key/cert value"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1696
+#: src/libnm-core-impl/nm-keyfile.c:1701
 #, c-format
 msgid "invalid key/cert value path \"%s\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1721 src/libnm-core-impl/nm-keyfile.c:1818
+#: src/libnm-core-impl/nm-keyfile.c:1726 src/libnm-core-impl/nm-keyfile.c:1823
 #, c-format
 msgid "certificate or key file '%s' does not exist"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1734
+#: src/libnm-core-impl/nm-keyfile.c:1739
 #, c-format
 msgid "invalid PKCS#11 URI \"%s\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1780
+#: src/libnm-core-impl/nm-keyfile.c:1785
 msgid "invalid key/cert value data:;base64, is not base64"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1793
+#: src/libnm-core-impl/nm-keyfile.c:1798
 msgid "invalid key/cert value data:;base64,file://"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1834
+#: src/libnm-core-impl/nm-keyfile.c:1839
 msgid "invalid key/cert value is not a valid blob"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1936
+#: src/libnm-core-impl/nm-keyfile.c:1941
 #, c-format
 msgid "invalid parity value '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1958 src/libnm-core-impl/nm-keyfile.c:3540
+#: src/libnm-core-impl/nm-keyfile.c:1963 src/libnm-core-impl/nm-keyfile.c:3545
 #, c-format
 msgid "invalid setting: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:1978
+#: src/libnm-core-impl/nm-keyfile.c:1983
 #, c-format
 msgid "ignoring invalid team configuration: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:2099
+#: src/libnm-core-impl/nm-keyfile.c:2104
 #, c-format
 msgid "invalid qdisc: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:2149
+#: src/libnm-core-impl/nm-keyfile.c:2154
 #, c-format
 msgid "invalid tfilter: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3365
+#: src/libnm-core-impl/nm-keyfile.c:3370
 #, c-format
 msgid "error loading setting value: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3396 src/libnm-core-impl/nm-keyfile.c:3408
-#: src/libnm-core-impl/nm-keyfile.c:3427 src/libnm-core-impl/nm-keyfile.c:3439
-#: src/libnm-core-impl/nm-keyfile.c:3451 src/libnm-core-impl/nm-keyfile.c:3513
-#: src/libnm-core-impl/nm-keyfile.c:3525
+#: src/libnm-core-impl/nm-keyfile.c:3401 src/libnm-core-impl/nm-keyfile.c:3413
+#: src/libnm-core-impl/nm-keyfile.c:3432 src/libnm-core-impl/nm-keyfile.c:3444
+#: src/libnm-core-impl/nm-keyfile.c:3456 src/libnm-core-impl/nm-keyfile.c:3518
+#: src/libnm-core-impl/nm-keyfile.c:3530
 msgid "value cannot be interpreted as integer"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3481
+#: src/libnm-core-impl/nm-keyfile.c:3486
 #, c-format
 msgid "ignoring invalid byte element '%u' (not between 0 and 255 inclusive)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3565
+#: src/libnm-core-impl/nm-keyfile.c:3570
 #, c-format
 msgid "invalid setting name '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3612
+#: src/libnm-core-impl/nm-keyfile.c:3617
 #, c-format
 msgid "invalid key '%s.%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3628
+#: src/libnm-core-impl/nm-keyfile.c:3633
 #, c-format
 msgid "key '%s.%s' is not boolean"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3645
+#: src/libnm-core-impl/nm-keyfile.c:3650
 #, c-format
 msgid "key '%s.%s' is not a uint32"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3702
+#: src/libnm-core-impl/nm-keyfile.c:3707
 #, c-format
 msgid "invalid peer public key in section '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3717
+#: src/libnm-core-impl/nm-keyfile.c:3722
 #, c-format
 msgid "key '%s.%s' is not a valid 256 bit key in base64 encoding"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3740
+#: src/libnm-core-impl/nm-keyfile.c:3745
 #, c-format
 msgid "key '%s.%s' is not a valid secret flag"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3763
+#: src/libnm-core-impl/nm-keyfile.c:3768
 #, c-format
 msgid "key '%s.%s' is not a integer in range 0 to 2^32"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3779
+#: src/libnm-core-impl/nm-keyfile.c:3784
 #, c-format
 msgid "key '%s.%s' is not a valid endpoint"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3805
+#: src/libnm-core-impl/nm-keyfile.c:3810
 #, c-format
 msgid "key '%s.%s' has invalid allowed-ips"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:3820
+#: src/libnm-core-impl/nm-keyfile.c:3825
 #, c-format
 msgid "peer '%s' is invalid: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-keyfile.c:4348
+#: src/libnm-core-impl/nm-keyfile.c:4353
 #, c-format
 msgid "unsupported option \"%s.%s\" of variant type %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-6lowpan.c:80
+#: src/libnm-core-impl/nm-setting-6lowpan.c:81
+#: src/libnm-core-impl/nm-setting-hsr.c:131
+#: src/libnm-core-impl/nm-setting-hsr.c:149
 #: src/libnm-core-impl/nm-setting-veth.c:81
 msgid "property is not specified"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-6lowpan.c:103
-#: src/libnm-core-impl/nm-setting-macsec.c:317
-#: src/libnm-core-impl/nm-setting-vlan.c:627
+#: src/libnm-core-impl/nm-setting-6lowpan.c:104
+#: src/libnm-core-impl/nm-setting-macsec.c:315
+#: src/libnm-core-impl/nm-setting-vlan.c:625
 #, c-format
 msgid "'%s' value doesn't match '%s=%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-6lowpan.c:119
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:380
-#: src/libnm-core-impl/nm-setting-macsec.c:333
-#: src/libnm-core-impl/nm-setting-macvlan.c:140
-#: src/libnm-core-impl/nm-setting-vlan.c:643
-#: src/libnm-core-impl/nm-setting-vxlan.c:379
+#: src/libnm-core-impl/nm-setting-6lowpan.c:120
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:378
+#: src/libnm-core-impl/nm-setting-macsec.c:331
+#: src/libnm-core-impl/nm-setting-macvlan.c:138
+#: src/libnm-core-impl/nm-setting-vlan.c:641
+#: src/libnm-core-impl/nm-setting-vxlan.c:377
 #, c-format
 msgid "'%s' is neither an UUID nor an interface name"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:237
+#: src/libnm-core-impl/nm-setting-8021x.c:235
 msgid "binary data missing"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:269
+#: src/libnm-core-impl/nm-setting-8021x.c:267
 msgid "URI not NUL terminated"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:278
+#: src/libnm-core-impl/nm-setting-8021x.c:276
 msgid "URI is empty"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:286
+#: src/libnm-core-impl/nm-setting-8021x.c:284
 msgid "URI is not valid UTF-8"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:304
+#: src/libnm-core-impl/nm-setting-8021x.c:302
 msgid "data missing"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:325
-#: src/libnm-core-impl/nm-setting-8021x.c:693
+#: src/libnm-core-impl/nm-setting-8021x.c:323
+#: src/libnm-core-impl/nm-setting-8021x.c:691
 #, c-format
 msgid "certificate is invalid: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:334
+#: src/libnm-core-impl/nm-setting-8021x.c:332
 msgid "certificate detected as invalid scheme"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:560
+#: src/libnm-core-impl/nm-setting-8021x.c:558
 msgid "CA certificate must be in X.509 format"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:572
+#: src/libnm-core-impl/nm-setting-8021x.c:570
 msgid "invalid certificate format"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:704
+#: src/libnm-core-impl/nm-setting-8021x.c:702
 msgid "password is not supported when certificate is not on a PKCS#11 token"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:2628
-#: src/libnm-core-impl/nm-setting-8021x.c:2668
-#: src/libnm-core-impl/nm-setting-8021x.c:2687
-#: src/libnm-core-impl/nm-setting-8021x.c:2857
-#: src/libnm-core-impl/nm-setting-8021x.c:2877
-#: src/libnm-core-impl/nm-setting-8021x.c:2897
-#: src/libnm-core-impl/nm-setting-8021x.c:2963
-#: src/libnm-core-impl/nm-setting-8021x.c:2983
-#: src/libnm-core-impl/nm-setting-8021x.c:3037
-#: src/libnm-core-impl/nm-setting-adsl.c:181
-#: src/libnm-core-impl/nm-setting-cdma.c:149
-#: src/libnm-core-impl/nm-setting-cdma.c:159
-#: src/libnm-core-impl/nm-setting-connection.c:1161
-#: src/libnm-core-impl/nm-setting-connection.c:1204
-#: src/libnm-core-impl/nm-setting-connection.c:1456
-#: src/libnm-core-impl/nm-setting-gsm.c:399
-#: src/libnm-core-impl/nm-setting-gsm.c:414
-#: src/libnm-core-impl/nm-setting-gsm.c:457
-#: src/libnm-core-impl/nm-setting-gsm.c:466
-#: src/libnm-core-impl/nm-setting-ip-config.c:5509
-#: src/libnm-core-impl/nm-setting-ip4-config.c:286
-#: src/libnm-core-impl/nm-setting-ip4-config.c:298
-#: src/libnm-core-impl/nm-setting-pppoe.c:151
-#: src/libnm-core-impl/nm-setting-pppoe.c:161
-#: src/libnm-core-impl/nm-setting-vpn.c:556
-#: src/libnm-core-impl/nm-setting-vpn.c:566
-#: src/libnm-core-impl/nm-setting-wimax.c:109
-#: src/libnm-core-impl/nm-setting-wireless-security.c:972
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1000
-#: src/libnm-core-impl/nm-setting.c:2465
+#: src/libnm-core-impl/nm-setting-8021x.c:2626
+#: src/libnm-core-impl/nm-setting-8021x.c:2666
+#: src/libnm-core-impl/nm-setting-8021x.c:2685
+#: src/libnm-core-impl/nm-setting-8021x.c:2855
+#: src/libnm-core-impl/nm-setting-8021x.c:2875
+#: src/libnm-core-impl/nm-setting-8021x.c:2895
+#: src/libnm-core-impl/nm-setting-8021x.c:2961
+#: src/libnm-core-impl/nm-setting-8021x.c:2981
+#: src/libnm-core-impl/nm-setting-8021x.c:3035
+#: src/libnm-core-impl/nm-setting-adsl.c:179
+#: src/libnm-core-impl/nm-setting-cdma.c:147
+#: src/libnm-core-impl/nm-setting-cdma.c:157
+#: src/libnm-core-impl/nm-setting-connection.c:1220
+#: src/libnm-core-impl/nm-setting-connection.c:1263
+#: src/libnm-core-impl/nm-setting-connection.c:1515
+#: src/libnm-core-impl/nm-setting-gsm.c:396
+#: src/libnm-core-impl/nm-setting-gsm.c:411
+#: src/libnm-core-impl/nm-setting-gsm.c:454
+#: src/libnm-core-impl/nm-setting-gsm.c:463
+#: src/libnm-core-impl/nm-setting-ip-config.c:5489
+#: src/libnm-core-impl/nm-setting-ip4-config.c:284
+#: src/libnm-core-impl/nm-setting-ip4-config.c:296
+#: src/libnm-core-impl/nm-setting-pppoe.c:149
+#: src/libnm-core-impl/nm-setting-pppoe.c:159
+#: src/libnm-core-impl/nm-setting-vpn.c:553
+#: src/libnm-core-impl/nm-setting-vpn.c:563
+#: src/libnm-core-impl/nm-setting-wimax.c:107
+#: src/libnm-core-impl/nm-setting-wireless-security.c:968
+#: src/libnm-core-impl/nm-setting-wireless-security.c:996
+#: src/libnm-core-impl/nm-setting.c:2531
 msgid "property is empty"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:2701
+#: src/libnm-core-impl/nm-setting-8021x.c:2699
 #, c-format
 msgid "has to match '%s' property for PKCS#12"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:2724
+#: src/libnm-core-impl/nm-setting-8021x.c:2722
 msgid "exactly one property must be set"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:2804
+#: src/libnm-core-impl/nm-setting-8021x.c:2802
 msgid "can be enabled only on Ethernet connections"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:2825
-#: src/libnm-core-impl/nm-setting-bluetooth.c:110
-#: src/libnm-core-impl/nm-setting-infiniband.c:177
-#: src/libnm-core-impl/nm-setting-infiniband.c:189
-#: src/libnm-core-impl/nm-setting-ip4-config.c:234
-#: src/libnm-core-impl/nm-setting-ip4-config.c:250
-#: src/libnm-core-impl/nm-setting-ip6-config.c:303
-#: src/libnm-core-impl/nm-setting-ip6-config.c:319
-#: src/libnm-core-impl/nm-setting-olpc-mesh.c:137
+#: src/libnm-core-impl/nm-setting-8021x.c:2823
+#: src/libnm-core-impl/nm-setting-bluetooth.c:108
+#: src/libnm-core-impl/nm-setting-infiniband.c:175
+#: src/libnm-core-impl/nm-setting-infiniband.c:187
+#: src/libnm-core-impl/nm-setting-ip4-config.c:232
+#: src/libnm-core-impl/nm-setting-ip4-config.c:248
+#: src/libnm-core-impl/nm-setting-ip6-config.c:301
+#: src/libnm-core-impl/nm-setting-ip6-config.c:317
+#: src/libnm-core-impl/nm-setting-olpc-mesh.c:135
 #: src/libnm-core-impl/nm-setting-wifi-p2p.c:131
-#: src/libnm-core-impl/nm-setting-wimax.c:121
-#: src/libnm-core-impl/nm-setting-wired.c:837
-#: src/libnm-core-impl/nm-setting-wired.c:850
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1012
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1024
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1036
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1049
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1062
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1093
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1160
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1209
-#: src/libnm-core-impl/nm-setting-wireless.c:941
-#: src/libnm-core-impl/nm-setting-wireless.c:953
-#: src/libnm-core-impl/nm-setting-wireless.c:966
-#: src/libnm-core-impl/nm-setting-wpan.c:163
-#: src/libnm-core-impl/nm-utils.c:4151
+#: src/libnm-core-impl/nm-setting-wimax.c:119
+#: src/libnm-core-impl/nm-setting-wired.c:842
+#: src/libnm-core-impl/nm-setting-wired.c:855
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1008
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1020
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1032
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1045
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1058
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1089
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1156
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1205
+#: src/libnm-core-impl/nm-setting-wireless.c:991
+#: src/libnm-core-impl/nm-setting-wireless.c:1003
+#: src/libnm-core-impl/nm-setting-wireless.c:1016
+#: src/libnm-core-impl/nm-setting-wpan.c:164
+#: src/libnm-core-impl/nm-utils.c:4557
 msgid "property is invalid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:2851
-#: src/libnm-core-impl/nm-setting-8021x.c:2871
-#: src/libnm-core-impl/nm-setting-8021x.c:2891
-#: src/libnm-core-impl/nm-setting-8021x.c:2957
-#: src/libnm-core-impl/nm-setting-8021x.c:2977
-#: src/libnm-core-impl/nm-setting-adsl.c:193
-#: src/libnm-core-impl/nm-setting-adsl.c:206
-#: src/libnm-core-impl/nm-setting-bluetooth.c:145
-#: src/libnm-core-impl/nm-setting-wireless-security.c:928
+#: src/libnm-core-impl/nm-setting-8021x.c:2849
+#: src/libnm-core-impl/nm-setting-8021x.c:2869
+#: src/libnm-core-impl/nm-setting-8021x.c:2889
+#: src/libnm-core-impl/nm-setting-8021x.c:2955
+#: src/libnm-core-impl/nm-setting-8021x.c:2975
+#: src/libnm-core-impl/nm-setting-adsl.c:191
+#: src/libnm-core-impl/nm-setting-adsl.c:204
+#: src/libnm-core-impl/nm-setting-bluetooth.c:143
+#: src/libnm-core-impl/nm-setting-wireless-security.c:924
 #, c-format
 msgid "'%s' is not a valid value for the property"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:2910
+#: src/libnm-core-impl/nm-setting-8021x.c:2908
 #, c-format
 msgid "invalid auth flags: '%d' contains unknown flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-8021x.c:2935
+#: src/libnm-core-impl/nm-setting-8021x.c:2933
 msgid ""
 "invalid auth flags: both enable and disable are set for the same TLS version"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bluetooth.c:169
+#: src/libnm-core-impl/nm-setting-bluetooth.c:167
 #, c-format
 msgid "'%s' connection requires '%s' or '%s' setting"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bluetooth.c:221
+#: src/libnm-core-impl/nm-setting-bluetooth.c:219
 #, c-format
 msgid "'%s' connection requires '%s' setting"
 msgstr ""
 
 #: src/libnm-core-impl/nm-setting-bond-port.c:99
-#: src/libnm-core-impl/nm-setting-bridge-port.c:328
+#: src/libnm-core-impl/nm-setting-bridge-port.c:326
 #: src/libnm-core-impl/nm-setting-ovs-bridge.c:151
 #: src/libnm-core-impl/nm-setting-ovs-interface.c:306
 #: src/libnm-core-impl/nm-setting-ovs-port.c:411
-#: src/libnm-core-impl/nm-setting-team-port.c:323
+#: src/libnm-core-impl/nm-setting-team-port.c:321
 msgid "missing setting"
 msgstr ""
 
 #: src/libnm-core-impl/nm-setting-bond-port.c:109
-#: src/libnm-core-impl/nm-setting-bridge-port.c:338
+#: src/libnm-core-impl/nm-setting-bridge-port.c:336
 #: src/libnm-core-impl/nm-setting-ovs-interface.c:329
-#: src/libnm-core-impl/nm-setting-ovs-port.c:434
-#: src/libnm-core-impl/nm-setting-team-port.c:333
+#: src/libnm-core-impl/nm-setting-team-port.c:331
 #, c-format
 msgid ""
 "A connection with a '%s' setting must have the slave-type set to '%s'. "
 "Instead it is '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:526
+#: src/libnm-core-impl/nm-setting-bond.c:524
 #, c-format
 msgid "'%s' option is empty"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:539
+#: src/libnm-core-impl/nm-setting-bond.c:537
 #, c-format
 msgid "'%s' is not a valid %s address for '%s' option"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:567
+#: src/libnm-core-impl/nm-setting-bond.c:565
 msgid "missing option name"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:572
+#: src/libnm-core-impl/nm-setting-bond.c:570
 #, c-format
 msgid "invalid option '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:611
+#: src/libnm-core-impl/nm-setting-bond.c:609
 #, c-format
 msgid "invalid value '%s' for option '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:925
+#: src/libnm-core-impl/nm-setting-bond.c:923
 #, c-format
 msgid "mandatory option '%s' is missing"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:935
+#: src/libnm-core-impl/nm-setting-bond.c:933
 #, c-format
 msgid "'%s' is not a valid value for '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:948
-#: src/libnm-core-impl/nm-setting-bond.c:959
+#: src/libnm-core-impl/nm-setting-bond.c:946
+#: src/libnm-core-impl/nm-setting-bond.c:957
 #, c-format
 msgid "'%s=%s' is incompatible with '%s > 0'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:976
+#: src/libnm-core-impl/nm-setting-bond.c:974
 #, c-format
 msgid "'%s' is not valid for the '%s' option: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:988
+#: src/libnm-core-impl/nm-setting-bond.c:986
 #, c-format
 msgid "'%s' option is only valid for '%s=%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1001
+#: src/libnm-core-impl/nm-setting-bond.c:999
 #, c-format
 msgid "'%s=%s' is not a valid configuration for '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1016
-#: src/libnm-core-impl/nm-setting-bond.c:1027
-#: src/libnm-core-impl/nm-setting-bond.c:1040
+#: src/libnm-core-impl/nm-setting-bond.c:1014
+#: src/libnm-core-impl/nm-setting-bond.c:1025
+#: src/libnm-core-impl/nm-setting-bond.c:1038
 #, c-format
 msgid "'%s' option requires '%s' option to be enabled"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1057
+#: src/libnm-core-impl/nm-setting-bond.c:1055
 #, c-format
 msgid "'%s' option needs to be a value multiple of '%s' value"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1075
+#: src/libnm-core-impl/nm-setting-bond.c:1073
 #, c-format
 msgid "'%s' option requires '%s' or '%s'option to be set"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1087
-#: src/libnm-core-impl/nm-setting-bond.c:1097
+#: src/libnm-core-impl/nm-setting-bond.c:1085
+#: src/libnm-core-impl/nm-setting-bond.c:1095
 #, c-format
 msgid "'%s' option requires '%s' option to be set"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1110
-#: src/libnm-core-impl/nm-setting-bond.c:1122
+#: src/libnm-core-impl/nm-setting-bond.c:1108
+#: src/libnm-core-impl/nm-setting-bond.c:1120
 #, c-format
 msgid "'%s' option is only valid with mode '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1135
+#: src/libnm-core-impl/nm-setting-bond.c:1133
 #, c-format
 msgid "'%s' and '%s' cannot have different values"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1148
+#: src/libnm-core-impl/nm-setting-bond.c:1146
 #, c-format
 msgid "%s requires bond mode \"%s\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1161
+#: src/libnm-core-impl/nm-setting-bond.c:1159
 #, c-format
 msgid "%s requires xmit_hash_policy \"vlan+srcmac\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1184
+#: src/libnm-core-impl/nm-setting-bond.c:1182
 #, c-format
 msgid "'%s' option should be string"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1197
+#: src/libnm-core-impl/nm-setting-bond.c:1195
 #, c-format
 msgid "'%s' option is not valid with mode '%s'"
 msgstr ""
@@ -1774,646 +1780,653 @@ msgstr ""
 msgid "bridge connection should have a ethernet setting as well"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1044
+#: src/libnm-core-impl/nm-setting-connection.c:1103
 #, c-format
 msgid "setting required for connection of type '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1075
+#: src/libnm-core-impl/nm-setting-connection.c:1134
 #, c-format
 msgid "Unknown slave type '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1090
+#: src/libnm-core-impl/nm-setting-connection.c:1149
 #, c-format
 msgid "Slave connections need a valid '%s' property"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1114
+#: src/libnm-core-impl/nm-setting-connection.c:1173
 #, c-format
 msgid "Cannot set '%s' without '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1173
+#: src/libnm-core-impl/nm-setting-connection.c:1232
 #, c-format
 msgid "'%s' is not a valid UUID"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1218
+#: src/libnm-core-impl/nm-setting-connection.c:1277
 #, c-format
 msgid "connection type '%s' is not valid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1324
+#: src/libnm-core-impl/nm-setting-connection.c:1383
 #, c-format
 msgid "'%s' connections must be enslaved to '%s', not '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1339
+#: src/libnm-core-impl/nm-setting-connection.c:1398
 #, c-format
 msgid "metered value %d is not valid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1353
-#: src/libnm-core-impl/nm-setting-connection.c:1367
-#: src/libnm-core-impl/nm-setting-connection.c:1381
-#: src/libnm-core-impl/nm-setting-connection.c:1442
+#: src/libnm-core-impl/nm-setting-connection.c:1412
+#: src/libnm-core-impl/nm-setting-connection.c:1426
+#: src/libnm-core-impl/nm-setting-connection.c:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1501
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1397
+#: src/libnm-core-impl/nm-setting-connection.c:1456
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1411
+#: src/libnm-core-impl/nm-setting-connection.c:1470
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1423
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1470
+#: src/libnm-core-impl/nm-setting-connection.c:1529
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1481
+#: src/libnm-core-impl/nm-setting-connection.c:1540
 msgid "MUD URL is not a valid URL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1501
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1530
+#: src/libnm-core-impl/nm-setting-connection.c:1589
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1548
+#: src/libnm-core-impl/nm-setting-connection.c:1607
 #, c-format
-msgid "slave-type '%s' requires a '%s' setting in the connection"
+msgid "port-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1559
+#: src/libnm-core-impl/nm-setting-connection.c:1618
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
 "set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1585
+#: src/libnm-core-impl/nm-setting-connection.c:1644
 #, c-format
 msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1602
+#: src/libnm-core-impl/nm-setting-connection.c:1661
 msgid "UUID needs normalization"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1617
+#: src/libnm-core-impl/nm-setting-connection.c:1676
 msgid "read-only is deprecated and not settable for the user"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-dcb.c:499
+#: src/libnm-core-impl/nm-setting-dcb.c:496
 msgid "flags invalid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-dcb.c:508
+#: src/libnm-core-impl/nm-setting-dcb.c:505
 msgid "flags invalid - disabled"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-dcb.c:534
-#: src/libnm-core-impl/nm-setting-dcb.c:580
+#: src/libnm-core-impl/nm-setting-dcb.c:531
+#: src/libnm-core-impl/nm-setting-dcb.c:577
 msgid "property invalid (not enabled)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-dcb.c:543
+#: src/libnm-core-impl/nm-setting-dcb.c:540
 msgid "element invalid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-dcb.c:558
+#: src/libnm-core-impl/nm-setting-dcb.c:555
 msgid "sum not 100%"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-dcb.c:589
-#: src/libnm-core-impl/nm-setting-dcb.c:617
+#: src/libnm-core-impl/nm-setting-dcb.c:586
+#: src/libnm-core-impl/nm-setting-dcb.c:614
 msgid "property invalid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ethtool.c:297
+#: src/libnm-core-impl/nm-setting-ethtool.c:328
 msgid "unsupported ethtool setting"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ethtool.c:306
+#: src/libnm-core-impl/nm-setting-ethtool.c:337
 msgid "setting has invalid variant type"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ethtool.c:318
+#: src/libnm-core-impl/nm-setting-ethtool.c:349
 msgid "coalesce option must be either 0 or 1"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ethtool.c:335
+#: src/libnm-core-impl/nm-setting-ethtool.c:366
 msgid "pause-autoneg cannot be enabled when setting rx/tx options"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ethtool.c:360
+#: src/libnm-core-impl/nm-setting-ethtool.c:391
 #, c-format
 msgid "unknown ethtool option '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-gsm.c:340
+#: src/libnm-core-impl/nm-setting-gsm.c:337
 msgid "property value is empty"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-gsm.c:349
+#: src/libnm-core-impl/nm-setting-gsm.c:346
 msgid "property value is too long (>64)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-gsm.c:381
+#: src/libnm-core-impl/nm-setting-gsm.c:378
 #, c-format
 msgid "'%s' contains invalid char(s) (use [A-Za-z._-])"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-gsm.c:428
+#: src/libnm-core-impl/nm-setting-gsm.c:425
 #, c-format
 msgid "'%s' length is invalid (should be 5 or 6 digits)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-gsm.c:442
+#: src/libnm-core-impl/nm-setting-gsm.c:439
 #, c-format
 msgid "'%s' is not a number"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-gsm.c:479
+#: src/libnm-core-impl/nm-setting-gsm.c:476
 msgid "property is empty or wrong size"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-gsm.c:492
+#: src/libnm-core-impl/nm-setting-gsm.c:489
 msgid "property must contain only digits"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-gsm.c:506
+#: src/libnm-core-impl/nm-setting-gsm.c:503
 msgid "can't be enabled when manual configuration is present"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-infiniband.c:215
+#: src/libnm-core-impl/nm-setting-hsr.c:139
+#: src/libnm-core-impl/nm-setting-hsr.c:157
+#: src/libnm-core-impl/nm-setting-veth.c:90
+#, c-format
+msgid "'%s' is not a valid interface name"
+msgstr ""
+
+#: src/libnm-core-impl/nm-setting-infiniband.c:213
 msgid "Must specify a P_Key if specifying parent"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-infiniband.c:226
+#: src/libnm-core-impl/nm-setting-infiniband.c:224
 msgid "InfiniBand P_Key connection did not specify parent interface name"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-infiniband.c:234
+#: src/libnm-core-impl/nm-setting-infiniband.c:232
 msgid "the values 0 and 0x8000 are not allowed"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-infiniband.c:262
+#: src/libnm-core-impl/nm-setting-infiniband.c:260
 #, c-format
 msgid ""
 "interface name of software infiniband device must be '%s' or unset (instead "
 "it is '%s')"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-infiniband.c:270
+#: src/libnm-core-impl/nm-setting-infiniband.c:268
 #, c-format
 msgid ""
 "interface name of software infiniband device with MAC address must be unset "
 "(instead it is '%s')"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-infiniband.c:296
+#: src/libnm-core-impl/nm-setting-infiniband.c:294
 #, c-format
 msgid "mtu can be at most %u but it is %u"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:81
+#: src/libnm-core-impl/nm-setting-ip-config.c:83
 msgid "Missing IPv4 address"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:81
+#: src/libnm-core-impl/nm-setting-ip-config.c:83
 msgid "Missing IPv6 address"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:88
+#: src/libnm-core-impl/nm-setting-ip-config.c:90
 #, c-format
 msgid "Invalid IPv4 address '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:89
+#: src/libnm-core-impl/nm-setting-ip-config.c:91
 #, c-format
 msgid "Invalid IPv6 address '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:106
+#: src/libnm-core-impl/nm-setting-ip-config.c:108
 #, c-format
 msgid "Invalid IPv4 address prefix '%u'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:107
+#: src/libnm-core-impl/nm-setting-ip-config.c:109
 #, c-format
 msgid "Invalid IPv6 address prefix '%u'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:124
+#: src/libnm-core-impl/nm-setting-ip-config.c:126
 #, c-format
 msgid "Invalid routing metric '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1337
+#: src/libnm-core-impl/nm-setting-ip-config.c:1339
 #: src/libnm-core-impl/nm-setting-sriov.c:400
 msgid "unknown attribute"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1347
+#: src/libnm-core-impl/nm-setting-ip-config.c:1349
 #: src/libnm-core-impl/nm-setting-sriov.c:410
 #, c-format
 msgid "invalid attribute type '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1356
+#: src/libnm-core-impl/nm-setting-ip-config.c:1358
 msgid "attribute is not valid for a IPv4 route"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1357
+#: src/libnm-core-impl/nm-setting-ip-config.c:1359
 msgid "attribute is not valid for a IPv6 route"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1368
-#: src/libnm-core-impl/nm-setting-ip-config.c:1400
+#: src/libnm-core-impl/nm-setting-ip-config.c:1370
+#: src/libnm-core-impl/nm-setting-ip-config.c:1402
 #, c-format
 msgid "'%s' is not a valid IPv4 address"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1369
-#: src/libnm-core-impl/nm-setting-ip-config.c:1401
+#: src/libnm-core-impl/nm-setting-ip-config.c:1371
+#: src/libnm-core-impl/nm-setting-ip-config.c:1403
 #, c-format
 msgid "'%s' is not a valid IPv6 address"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1391
+#: src/libnm-core-impl/nm-setting-ip-config.c:1393
 #, c-format
 msgid "invalid prefix %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1423
+#: src/libnm-core-impl/nm-setting-ip-config.c:1425
 #, c-format
 msgid "%s is not a valid route type"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1442
+#: src/libnm-core-impl/nm-setting-ip-config.c:1444
 msgid "route weight cannot be larger than 256"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1529
+#: src/libnm-core-impl/nm-setting-ip-config.c:1531
 msgid "route scope is invalid for local route"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1541
+#: src/libnm-core-impl/nm-setting-ip-config.c:1543
 #, c-format
 msgid "a %s route cannot have a next-hop"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:1553
+#: src/libnm-core-impl/nm-setting-ip-config.c:1555
 #, c-format
 msgid "a %s route cannot have a ECMP multi-hop \"weight\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2741
+#: src/libnm-core-impl/nm-setting-ip-config.c:2743
 msgid "missing priority"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2754
+#: src/libnm-core-impl/nm-setting-ip-config.c:2756
 msgid "missing table"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2764
+#: src/libnm-core-impl/nm-setting-ip-config.c:2766
 msgid "invalid action type"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2773
+#: src/libnm-core-impl/nm-setting-ip-config.c:2775
 msgid "has from/src but the prefix-length is zero"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2781
+#: src/libnm-core-impl/nm-setting-ip-config.c:2783
 msgid "missing from/src for a non zero prefix-length"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2788
+#: src/libnm-core-impl/nm-setting-ip-config.c:2790
 msgid "invalid from/src"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2795
+#: src/libnm-core-impl/nm-setting-ip-config.c:2797
 msgid "invalid prefix length for from/src"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2804
+#: src/libnm-core-impl/nm-setting-ip-config.c:2806
 msgid "has to/dst but the prefix-length is zero"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2812
+#: src/libnm-core-impl/nm-setting-ip-config.c:2814
 msgid "missing to/dst for a non zero prefix-length"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2819
+#: src/libnm-core-impl/nm-setting-ip-config.c:2821
 msgid "invalid to/dst"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2826
+#: src/libnm-core-impl/nm-setting-ip-config.c:2828
 msgid "invalid prefix length for to/dst"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2836
+#: src/libnm-core-impl/nm-setting-ip-config.c:2838
 msgid "invalid iifname"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2846
+#: src/libnm-core-impl/nm-setting-ip-config.c:2848
 msgid "invalid oifname"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2854
+#: src/libnm-core-impl/nm-setting-ip-config.c:2856
 msgid "invalid source port range"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2862
+#: src/libnm-core-impl/nm-setting-ip-config.c:2864
 msgid "invalid destination port range"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2872
+#: src/libnm-core-impl/nm-setting-ip-config.c:2874
 msgid "suppress_prefixlength out of range"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:2880
+#: src/libnm-core-impl/nm-setting-ip-config.c:2882
 msgid "suppress_prefixlength is only allowed with the to-table action"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3023
+#: src/libnm-core-impl/nm-setting-ip-config.c:3025
 #, c-format
 msgid "invalid key \"%s\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3035
+#: src/libnm-core-impl/nm-setting-ip-config.c:3037
 #, c-format
 msgid "duplicate key %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3051
+#: src/libnm-core-impl/nm-setting-ip-config.c:3053
 #, c-format
 msgid "invalid variant type '%s' for \"%s\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3062
+#: src/libnm-core-impl/nm-setting-ip-config.c:3064
 msgid "missing \"family\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3070
+#: src/libnm-core-impl/nm-setting-ip-config.c:3072
 msgid "invalid \"family\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3127
+#: src/libnm-core-impl/nm-setting-ip-config.c:3129
 msgid "\"uid-range-start\" is greater than \"uid-range-end\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3321
+#: src/libnm-core-impl/nm-setting-ip-config.c:3323
 msgid "Unsupported to-string-flags argument"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3329
+#: src/libnm-core-impl/nm-setting-ip-config.c:3331
 msgid "Unsupported extra-argument"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3631
+#: src/libnm-core-impl/nm-setting-ip-config.c:3633
 #, c-format
 msgid "unsupported key \"%s\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3638
+#: src/libnm-core-impl/nm-setting-ip-config.c:3640
 #, c-format
 msgid "duplicate key \"%s\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3645
+#: src/libnm-core-impl/nm-setting-ip-config.c:3647
 #, c-format
 msgid "invalid value for \"%s\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3657
+#: src/libnm-core-impl/nm-setting-ip-config.c:3659
 msgid "empty text does not describe a rule"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3665
+#: src/libnm-core-impl/nm-setting-ip-config.c:3667
 #, c-format
 msgid "missing argument for \"%s\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3679
+#: src/libnm-core-impl/nm-setting-ip-config.c:3681
 msgid "invalid \"from\" part"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3695
+#: src/libnm-core-impl/nm-setting-ip-config.c:3697
 msgid "invalid \"to\" part"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3706
+#: src/libnm-core-impl/nm-setting-ip-config.c:3708
 msgid "cannot detect address family for rule"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3773
-#: src/libnm-core-impl/nm-setting-ip-config.c:3863
+#: src/libnm-core-impl/nm-setting-ip-config.c:3775
+#: src/libnm-core-impl/nm-setting-ip-config.c:3865
 #, c-format
 msgid "rule is invalid: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:3844
+#: src/libnm-core-impl/nm-setting-ip-config.c:3846
 msgid "invalid address family"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5125
+#: src/libnm-core-impl/nm-setting-ip-config.c:5108
 #, c-format
 msgid "rule #%u is invalid: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5530
+#: src/libnm-core-impl/nm-setting-ip-config.c:5510
 #, c-format
 msgid "%u. DNS server address is invalid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5550
+#: src/libnm-core-impl/nm-setting-ip-config.c:5530
 #, c-format
 msgid "%d. IP address is invalid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5565
+#: src/libnm-core-impl/nm-setting-ip-config.c:5545
 #, c-format
 msgid "%d. IP address has 'label' property with invalid type"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5577
+#: src/libnm-core-impl/nm-setting-ip-config.c:5557
 #, c-format
 msgid "%d. IP address has invalid label '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5595
+#: src/libnm-core-impl/nm-setting-ip-config.c:5575
 msgid "gateway cannot be set if there are no addresses configured"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5607
+#: src/libnm-core-impl/nm-setting-ip-config.c:5587
 msgid "gateway is invalid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5625
+#: src/libnm-core-impl/nm-setting-ip-config.c:5605
 #, c-format
 msgid "%d. route is invalid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5638
+#: src/libnm-core-impl/nm-setting-ip-config.c:5618
 #, c-format
 msgid "invalid attribute: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5658
+#: src/libnm-core-impl/nm-setting-ip-config.c:5638
 #, c-format
 msgid "%u. rule has wrong address-family"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5670
+#: src/libnm-core-impl/nm-setting-ip-config.c:5650
 #, c-format
 msgid "%u. rule is invalid: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5686
+#: src/libnm-core-impl/nm-setting-ip-config.c:5666
 #, c-format
 msgid "'%s' is not a valid IAID"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5700
+#: src/libnm-core-impl/nm-setting-ip-config.c:5680
 #, c-format
 msgid "the property cannot be set when '%s' is disabled"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5726
+#: src/libnm-core-impl/nm-setting-ip-config.c:5706
 msgid "the property is currently supported only for DHCPv4"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5743
+#: src/libnm-core-impl/nm-setting-ip-config.c:5723
 #, c-format
 msgid "'%s' is not a valid IP or subnet"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-config.c:5759
+#: src/libnm-core-impl/nm-setting-ip-config.c:5739
 #, c-format
 msgid "a gateway is incompatible with '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:366
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:364
 #, c-format
 msgid "'%d' is not a valid tunnel mode"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:393
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:419
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:391
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:417
 #, c-format
 msgid "'%s' is not a valid IPv%c address"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:440
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:438
 msgid "tunnel keys can only be specified for GRE and VTI tunnels"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:453
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:471
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:451
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:469
 #, c-format
 msgid "'%s' is not a valid tunnel key"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:485
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:483
 msgid "a fixed TTL is allowed only when path MTU discovery is enabled"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:504
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:502
 #, c-format
 msgid "some flags are invalid for the select mode: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:517
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:515
 msgid "can be set only on VTI tunnels"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip-tunnel.c:529
+#: src/libnm-core-impl/nm-setting-ip-tunnel.c:527
 #, c-format
 msgid "wired setting not allowed for mode %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip4-config.c:172
-#: src/libnm-core-impl/nm-setting-ip6-config.c:237
+#: src/libnm-core-impl/nm-setting-ip4-config.c:171
+#: src/libnm-core-impl/nm-setting-ip6-config.c:236
 #, c-format
-msgid "this property cannot be empty for '%s=%s'"
+msgid "method '%s' requires at least an address or a route"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip4-config.c:188
-#: src/libnm-core-impl/nm-setting-ip4-config.c:202
-#: src/libnm-core-impl/nm-setting-ip4-config.c:218
-#: src/libnm-core-impl/nm-setting-ip6-config.c:257
-#: src/libnm-core-impl/nm-setting-ip6-config.c:271
-#: src/libnm-core-impl/nm-setting-ip6-config.c:285
+#: src/libnm-core-impl/nm-setting-ip4-config.c:186
+#: src/libnm-core-impl/nm-setting-ip4-config.c:200
+#: src/libnm-core-impl/nm-setting-ip4-config.c:216
+#: src/libnm-core-impl/nm-setting-ip6-config.c:255
+#: src/libnm-core-impl/nm-setting-ip6-config.c:269
+#: src/libnm-core-impl/nm-setting-ip6-config.c:283
 #, c-format
 msgid "this property is not allowed for '%s=%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip4-config.c:262
+#: src/libnm-core-impl/nm-setting-ip4-config.c:260
 msgid "cannot enable ipv4.link-local with ipv4.method=disabled"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip4-config.c:274
+#: src/libnm-core-impl/nm-setting-ip4-config.c:272
 msgid "cannot disable ipv4.link-local with ipv4.method=link-local"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip4-config.c:310
+#: src/libnm-core-impl/nm-setting-ip4-config.c:308
 #, c-format
 msgid "'%s' is not a valid FQDN"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip4-config.c:323
+#: src/libnm-core-impl/nm-setting-ip4-config.c:321
 msgid "property cannot be set when dhcp-hostname is also set"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip4-config.c:338
+#: src/libnm-core-impl/nm-setting-ip4-config.c:336
 msgid "FQDN flags requires a FQDN set"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip4-config.c:357
+#: src/libnm-core-impl/nm-setting-ip4-config.c:355
 #, c-format
 msgid "multiple addresses are not allowed for '%s=%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip4-config.c:374
+#: src/libnm-core-impl/nm-setting-ip4-config.c:372
 msgid "property should be TRUE when method is set to disabled"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip6-config.c:337
+#: src/libnm-core-impl/nm-setting-ip6-config.c:335
 msgid "value is not a valid token"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip6-config.c:351
+#: src/libnm-core-impl/nm-setting-ip6-config.c:349
 msgid "only makes sense with EUI64 address generation mode"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip6-config.c:365
+#: src/libnm-core-impl/nm-setting-ip6-config.c:363
 msgid "invalid DUID"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip6-config.c:382
+#: src/libnm-core-impl/nm-setting-ip6-config.c:380
 msgid "must be a valid IPv6 address with prefix"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip6-config.c:397
+#: src/libnm-core-impl/nm-setting-ip6-config.c:395
 msgid "token is not in canonical form"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ip6-config.c:414
+#: src/libnm-core-impl/nm-setting-ip6-config.c:412
 msgid "property should be TRUE when method is set to ignore or disabled"
 msgstr ""
 
@@ -2435,61 +2448,61 @@ msgstr ""
 msgid "a loopback profile cannot be a port"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-macsec.c:251
+#: src/libnm-core-impl/nm-setting-macsec.c:249
 msgid "the key is empty"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-macsec.c:261
+#: src/libnm-core-impl/nm-setting-macsec.c:259
 #, c-format
 msgid "the key must be %d characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-macsec.c:271
+#: src/libnm-core-impl/nm-setting-macsec.c:269
 msgid "the key must have an even number of characters between 2 and 64"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-macsec.c:280
+#: src/libnm-core-impl/nm-setting-macsec.c:278
 msgid "the key contains non-hexadecimal characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-macsec.c:349
-#: src/libnm-core-impl/nm-setting-macvlan.c:156
-#: src/libnm-core-impl/nm-setting-vlan.c:656
+#: src/libnm-core-impl/nm-setting-macsec.c:347
+#: src/libnm-core-impl/nm-setting-macvlan.c:154
+#: src/libnm-core-impl/nm-setting-vlan.c:654
 #, c-format
 msgid "property is not specified and neither is '%s:%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-macsec.c:380
+#: src/libnm-core-impl/nm-setting-macsec.c:378
 #, c-format
 msgid "EAP key management requires '%s' setting presence"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-macsec.c:389
+#: src/libnm-core-impl/nm-setting-macsec.c:387
 msgid "must be either psk (0) or eap (1)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-macsec.c:400
+#: src/libnm-core-impl/nm-setting-macsec.c:398
 msgid "only valid for psk mode"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-macvlan.c:171
+#: src/libnm-core-impl/nm-setting-macvlan.c:169
 msgid "non promiscuous operation is allowed only in passthru mode"
 msgstr ""
 
+#: src/libnm-core-impl/nm-setting-match.c:644
 #: src/libnm-core-impl/nm-setting-match.c:660
 #: src/libnm-core-impl/nm-setting-match.c:676
 #: src/libnm-core-impl/nm-setting-match.c:692
-#: src/libnm-core-impl/nm-setting-match.c:708
 msgid "is empty"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-olpc-mesh.c:112
-#: src/libnm-core-impl/nm-setting-wireless.c:858
+#: src/libnm-core-impl/nm-setting-olpc-mesh.c:110
+#: src/libnm-core-impl/nm-setting-wireless.c:908
 msgid "SSID length is out of range <1-32> bytes"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-olpc-mesh.c:124
-#: src/libnm-core-impl/nm-setting-wireless.c:911
+#: src/libnm-core-impl/nm-setting-olpc-mesh.c:122
+#: src/libnm-core-impl/nm-setting-wireless.c:961
 #, c-format
 msgid "'%d' is not a valid channel"
 msgstr ""
@@ -2585,9 +2598,8 @@ msgid "Missing ovs interface type"
 msgstr ""
 
 #: src/libnm-core-impl/nm-setting-ovs-interface.c:315
-#: src/libnm-core-impl/nm-setting-ovs-port.c:420
 #, c-format
-msgid "A connection with a '%s' setting must have a master."
+msgid "A connection with a '%s' setting must have a controller."
 msgstr ""
 
 #: src/libnm-core-impl/nm-setting-ovs-port.c:347
@@ -2604,6 +2616,18 @@ msgstr ""
 msgid "VLANs %u and %u are not sorted in ascending order"
 msgstr ""
 
+#: src/libnm-core-impl/nm-setting-ovs-port.c:420
+#, c-format
+msgid "A connection with a '%s' setting must have a master."
+msgstr ""
+
+#: src/libnm-core-impl/nm-setting-ovs-port.c:434
+#, c-format
+msgid ""
+"A connection with a '%s' setting must have the port-type set to '%s'. "
+"Instead it is '%s'"
+msgstr ""
+
 #: src/libnm-core-impl/nm-setting-ovs-port.c:457
 #, c-format
 msgid "'%s' is not allowed in vlan_mode"
@@ -2624,45 +2648,45 @@ msgstr ""
 msgid "'%s' is not allowed in bond_mode"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ppp.c:353
+#: src/libnm-core-impl/nm-setting-ppp.c:350
 #, c-format
 msgid "'%d' is out of valid range <128-16384>"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-ppp.c:366
+#: src/libnm-core-impl/nm-setting-ppp.c:363
 #, c-format
 msgid "setting this property requires non-zero '%s' property"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-proxy.c:138
+#: src/libnm-core-impl/nm-setting-proxy.c:137
 msgid "invalid proxy method"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-proxy.c:148
-#: src/libnm-core-impl/nm-setting-proxy.c:160
+#: src/libnm-core-impl/nm-setting-proxy.c:147
+#: src/libnm-core-impl/nm-setting-proxy.c:159
 msgid "this property is not allowed for method none"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-proxy.c:174
+#: src/libnm-core-impl/nm-setting-proxy.c:173
 msgid "the script is too large"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-proxy.c:185
+#: src/libnm-core-impl/nm-setting-proxy.c:184
 msgid "the script is not valid utf8"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-proxy.c:196
+#: src/libnm-core-impl/nm-setting-proxy.c:195
 msgid "the script lacks FindProxyForURL function"
 msgstr ""
 
 #: src/libnm-core-impl/nm-setting-sriov.c:422
-#: src/libnm-core-impl/nm-setting-wired.c:804
-#: src/libnm-core-impl/nm-setting-wired.c:820
-#: src/libnm-core-impl/nm-setting-wired.c:894
-#: src/libnm-core-impl/nm-setting-wired.c:953
-#: src/libnm-core-impl/nm-setting-wireless.c:1001
-#: src/libnm-core-impl/nm-setting-wireless.c:1020
-#: src/libnmc-setting/nm-meta-setting-desc.c:4295
+#: src/libnm-core-impl/nm-setting-wired.c:809
+#: src/libnm-core-impl/nm-setting-wired.c:825
+#: src/libnm-core-impl/nm-setting-wired.c:899
+#: src/libnm-core-impl/nm-setting-wired.c:958
+#: src/libnm-core-impl/nm-setting-wireless.c:1051
+#: src/libnm-core-impl/nm-setting-wireless.c:1070
+#: src/libnmc-setting/nm-meta-setting-desc.c:4283
 #, c-format
 msgid "'%s' is not a valid MAC address"
 msgstr ""
@@ -2744,17 +2768,17 @@ msgstr ""
 msgid "vlanid is out of range [-1, 4094]"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-tun.c:165
+#: src/libnm-core-impl/nm-setting-tun.c:162
 #, c-format
 msgid "'%u': invalid mode"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-tun.c:176
+#: src/libnm-core-impl/nm-setting-tun.c:173
 #, c-format
 msgid "'%s': invalid user ID"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-tun.c:188
+#: src/libnm-core-impl/nm-setting-tun.c:185
 #, c-format
 msgid "'%s': invalid group ID"
 msgstr ""
@@ -2776,52 +2800,47 @@ msgstr ""
 msgid "maximum number of user data entries reached (%u instead of %u)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-veth.c:90
-#, c-format
-msgid "'%s' is not a valid interface name"
-msgstr ""
-
-#: src/libnm-core-impl/nm-setting-vlan.c:668
+#: src/libnm-core-impl/nm-setting-vlan.c:666
 #, c-format
 msgid "the vlan id must be in range 0-4094 but is %u"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vlan.c:678
+#: src/libnm-core-impl/nm-setting-vlan.c:676
 msgid "flags are invalid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vlan.c:687
+#: src/libnm-core-impl/nm-setting-vlan.c:685
 #, c-format
 msgid "invalid VLAN protocol %s: must be '802.1Q' or '802.1ad'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vlan.c:700
+#: src/libnm-core-impl/nm-setting-vlan.c:698
 msgid "vlan setting should have a ethernet setting as well"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vpn.c:576
+#: src/libnm-core-impl/nm-setting-vpn.c:573
 msgid "cannot set connection.multi-connect for VPN setting"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vpn.c:615
+#: src/libnm-core-impl/nm-setting-vpn.c:612
 msgid "setting contained a secret with an empty name"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vpn.c:654
-#: src/libnm-core-impl/nm-setting.c:3400
+#: src/libnm-core-impl/nm-setting-vpn.c:651
+#: src/libnm-core-impl/nm-setting.c:3481
 msgid "not a secret property"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vpn.c:662
+#: src/libnm-core-impl/nm-setting-vpn.c:659
 msgid "secret is not of correct type"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vpn.c:744
-#: src/libnm-core-impl/nm-setting-vpn.c:794
+#: src/libnm-core-impl/nm-setting-vpn.c:741
+#: src/libnm-core-impl/nm-setting-vpn.c:791
 msgid "secret name cannot be empty"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vpn.c:760
+#: src/libnm-core-impl/nm-setting-vpn.c:757
 msgid "secret flags property not found"
 msgstr ""
 
@@ -2829,50 +2848,50 @@ msgstr ""
 msgid "table cannot be zero"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vxlan.c:356
-#: src/libnm-core-impl/nm-setting-vxlan.c:367
+#: src/libnm-core-impl/nm-setting-vxlan.c:354
+#: src/libnm-core-impl/nm-setting-vxlan.c:365
 #, c-format
 msgid "'%s' is not a valid IP%s address"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-vxlan.c:390
+#: src/libnm-core-impl/nm-setting-vxlan.c:388
 #, c-format
 msgid "%d is greater than local port max %d"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wired.c:784
+#: src/libnm-core-impl/nm-setting-wired.c:789
 #, c-format
 msgid "'%s' is not a valid Ethernet port value"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wired.c:794
+#: src/libnm-core-impl/nm-setting-wired.c:799
 #, c-format
 msgid "'%s' is not a valid duplex value"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wired.c:867
+#: src/libnm-core-impl/nm-setting-wired.c:872
 #, c-format
 msgid "invalid key '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wired.c:879
+#: src/libnm-core-impl/nm-setting-wired.c:884
 #, c-format
 msgid "invalid value for key '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wired.c:928
+#: src/libnm-core-impl/nm-setting-wired.c:933
 msgid "Wake-on-LAN mode 'default' and 'ignore' are exclusive flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wired.c:941
+#: src/libnm-core-impl/nm-setting-wired.c:946
 msgid "Wake-on-LAN password can only be used with magic packet mode"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wired.c:972
+#: src/libnm-core-impl/nm-setting-wired.c:977
 msgid "both speed and duplex should have a valid value or both should be unset"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wired.c:973
+#: src/libnm-core-impl/nm-setting-wired.c:978
 msgid "both speed and duplex are required for static link configuration"
 msgstr ""
 
@@ -2950,128 +2969,132 @@ msgstr ""
 msgid "non-existing peer '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless-security.c:942
+#: src/libnm-core-impl/nm-setting-wireless-security.c:938
 #, c-format
 msgid "'%s' is not a valid value for '%s' mode connections"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless-security.c:958
+#: src/libnm-core-impl/nm-setting-wireless-security.c:954
 #, c-format
 msgid "'%s' security requires '%s=%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless-security.c:987
+#: src/libnm-core-impl/nm-setting-wireless-security.c:983
 #, c-format
 msgid "'%s' security requires '%s' setting presence"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1076
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1072
 #, c-format
 msgid "'%s' can only be used with '%s=%s' (WEP)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1113
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1109
 #, c-format
 msgid ""
 "'%s' can only be used with 'owe', 'wpa-psk', 'sae', 'wpa-eap' or 'wpa-eap-"
 "suite-b-192' key management"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless-security.c:1131
+#: src/libnm-core-impl/nm-setting-wireless-security.c:1127
 msgid ""
 "pmf can only be 'default' or 'required' when using 'owe', 'sae' or 'wpa-eap-"
 "suite-b-192' key management"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:870
+#: src/libnm-core-impl/nm-setting-wireless.c:920
 #, c-format
 msgid "'%s' is not a valid Wi-Fi mode"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:883
+#: src/libnm-core-impl/nm-setting-wireless.c:933
 #, c-format
 msgid "'%s' is not a valid band"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:896
+#: src/libnm-core-impl/nm-setting-wireless.c:946
 #, c-format
 msgid "'%s' requires setting '%s' property"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:926
+#: src/libnm-core-impl/nm-setting-wireless.c:976
 #, c-format
 msgid "'%s' requires '%s' and '%s' property"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:1038
+#: src/libnm-core-impl/nm-setting-wireless.c:1088
 #: src/libnm-core-impl/nm-team-utils.c:2251
 msgid "invalid value"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:1051
+#: src/libnm-core-impl/nm-setting-wireless.c:1101
 msgid "Wake-on-WLAN mode 'default' and 'ignore' are exclusive flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:1062
+#: src/libnm-core-impl/nm-setting-wireless.c:1112
 msgid "Wake-on-WLAN trying to set unknown flag"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:1075
+#: src/libnm-core-impl/nm-setting-wireless.c:1125
 msgid "AP isolation can be set only in AP mode"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:1099
+#: src/libnm-core-impl/nm-setting-wireless.c:1143
 msgid "conflicting value of mac-address-randomization and cloned-mac-address"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wireless.c:1111
+#: src/libnm-core-impl/nm-setting-wireless.c:1155
 msgid "property is deprecated and not implemented"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wpan.c:173
+#: src/libnm-core-impl/nm-setting-wpan.c:174
 msgid "page must be defined along with a channel"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wpan.c:182
+#: src/libnm-core-impl/nm-setting-wpan.c:183
 #, c-format
 msgid "page must be between %d and %d"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-wpan.c:193
+#: src/libnm-core-impl/nm-setting-wpan.c:194
 #, c-format
 msgid "channel must not be between %d and %d"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting.c:1713 src/libnm-core-impl/nm-setting.c:1753
-#: src/libnm-core-impl/nm-setting.c:2064
+#: src/libnm-core-impl/nm-setting.c:1709 src/libnm-core-impl/nm-setting.c:1749
+#: src/libnm-core-impl/nm-setting.c:2060
 #, c-format
 msgid "can't set property of type '%s' from value of type '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting.c:1729
+#: src/libnm-core-impl/nm-setting.c:1725
 #, c-format
 msgid "value of type '%s' is invalid or out of range for property '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting.c:1774
+#: src/libnm-core-impl/nm-setting.c:1770
 #, c-format
 msgid "can not set property: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting.c:2003
+#: src/libnm-core-impl/nm-setting.c:1999
 msgid "duplicate property"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting.c:2023
+#: src/libnm-core-impl/nm-setting.c:2019
 msgid "unknown property"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting.c:2097 src/libnm-core-impl/nm-setting.c:2179
+#: src/libnm-core-impl/nm-setting.c:2093 src/libnm-core-impl/nm-setting.c:2175
 #, c-format
 msgid "failed to set property: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting.c:3297
+#: src/libnm-core-impl/nm-setting.c:2444
+msgid "cannot be empty"
+msgstr ""
+
+#: src/libnm-core-impl/nm-setting.c:3378
 msgid "secret not found"
 msgstr ""
 
@@ -3140,226 +3163,316 @@ msgstr ""
 msgid "invalid link-watchers: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:2254
+#: src/libnm-core-impl/nm-utils.c:1365
+msgid "Expected value of type \"au\""
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:1508 src/libnm-core-impl/nm-utils.c:1673
+msgid "Expected value of type \"aau\""
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:1519
+msgid "Expected \"address-labels\" of type \"as\""
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:1541
+#, c-format
+msgid "Incomplete IPv4 address (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:1554 src/libnm-core-impl/nm-utils.c:1710
+#: src/libnm-core-impl/nm-utils.c:2019 src/libnm-core-impl/nm-utils.c:2216
+#: src/libnm-core-impl/nm-utils.c:2372 src/libnm-core-impl/nm-utils.c:2557
+#, c-format
+msgid "%s (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:1691
+#, c-format
+msgid "Incomplete IPv4 route (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:1819
+msgid "Expected value of type \"aay\""
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:1844
+#, c-format
+msgid "Invalid IPv6 DNS address length (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:1971
+msgid "Expected value of type \"a(ayuay)\""
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:1993
+#, c-format
+msgid "Expected value of type \"(ayuay)\" (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2006
+#, c-format
+msgid "IPv6 address with invalid length (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2036
+#, c-format
+msgid "IPv6 gateway with invalid length (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2148
+msgid "Expected value of type \"a(ayuayu)\""
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2172
+#, c-format
+msgid "Expected value of type \"(ayuayu)\" (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2185
+#, c-format
+msgid "IPv6 dest address with invalid length (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2198
+#, c-format
+msgid "IPv6 next-hop address with invalid length (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2341 src/libnm-core-impl/nm-utils.c:2520
+msgid "Expected value of type \"aa{sv}\""
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2359
+#, c-format
+msgid "IP address requires fields \"dest\" and \"prefix\" (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2538
+#, c-format
+msgid "Route requires fields \"dest\" and \"prefix\" (idx=%u)"
+msgstr ""
+
+#: src/libnm-core-impl/nm-utils.c:2660
 #, c-format
 msgid "'%s' is not a valid handle."
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:2402
+#: src/libnm-core-impl/nm-utils.c:2808
 #, c-format
 msgid "'%s' unexpected: parent already specified."
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:2420
+#: src/libnm-core-impl/nm-utils.c:2826
 #, c-format
 msgid "invalid handle: '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:2442
+#: src/libnm-core-impl/nm-utils.c:2848
 msgid "parent not specified."
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:2506
+#: src/libnm-core-impl/nm-utils.c:2912
 #, c-format
 msgid "unsupported qdisc option: '%s'."
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:2636
+#: src/libnm-core-impl/nm-utils.c:3042
 msgid "action name missing."
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:2661
+#: src/libnm-core-impl/nm-utils.c:3067
 #, c-format
 msgid "unsupported action option: '%s'."
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:2798
+#: src/libnm-core-impl/nm-utils.c:3204
 msgid "invalid action: "
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:2802
+#: src/libnm-core-impl/nm-utils.c:3208
 #, c-format
 msgid "unsupported tfilter option: '%s'."
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3102
+#: src/libnm-core-impl/nm-utils.c:3508
 #, c-format
 msgid "failed stat file %s: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3113
+#: src/libnm-core-impl/nm-utils.c:3519
 #, c-format
 msgid "not a file (%s)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3124
+#: src/libnm-core-impl/nm-utils.c:3530
 #, c-format
 msgid "invalid file owner %d for %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3136
+#: src/libnm-core-impl/nm-utils.c:3542
 #, c-format
 msgid "file permissions for %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3146
+#: src/libnm-core-impl/nm-utils.c:3552
 #, c-format
 msgid "reject %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3166
+#: src/libnm-core-impl/nm-utils.c:3572
 #, c-format
 msgid "path is not absolute (%s)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3181
+#: src/libnm-core-impl/nm-utils.c:3587
 #, c-format
 msgid "Plugin file does not exist (%s)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3190
+#: src/libnm-core-impl/nm-utils.c:3596
 #, c-format
 msgid "Plugin is not a valid file (%s)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3201
+#: src/libnm-core-impl/nm-utils.c:3607
 #, c-format
 msgid "libtool archives are not supported (%s)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:3278
+#: src/libnm-core-impl/nm-utils.c:3684
 #, c-format
 msgid "Could not find \"%s\" binary"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4102
+#: src/libnm-core-impl/nm-utils.c:4508
 msgid "unknown secret flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4112
+#: src/libnm-core-impl/nm-utils.c:4518
 msgid "conflicting secret flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4123
+#: src/libnm-core-impl/nm-utils.c:4529
 msgid "secret flags must not be \"not-required\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4131
+#: src/libnm-core-impl/nm-utils.c:4537
 msgid "unsupported secret flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4161
+#: src/libnm-core-impl/nm-utils.c:4567
 msgid "can't be simultaneously disabled and enabled"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4169
+#: src/libnm-core-impl/nm-utils.c:4575
 msgid "WPS is required"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4237
+#: src/libnm-core-impl/nm-utils.c:4643
 #, c-format
 msgid "not a valid ethernet MAC address for mask at position %lld"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4256
+#: src/libnm-core-impl/nm-utils.c:4662
 #, c-format
 msgid "not a valid ethernet MAC address #%u at position %lld"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4891
+#: src/libnm-core-impl/nm-utils.c:5319
 msgid "not valid utf-8"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4912 src/libnm-core-impl/nm-utils.c:4965
+#: src/libnm-core-impl/nm-utils.c:5340 src/libnm-core-impl/nm-utils.c:5393
 msgid "is not a JSON object"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4941
+#: src/libnm-core-impl/nm-utils.c:5369
 msgid "value is NULL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4941
+#: src/libnm-core-impl/nm-utils.c:5369
 msgid "value is empty"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:4953
+#: src/libnm-core-impl/nm-utils.c:5381
 #, c-format
 msgid "invalid JSON at position %d (%s)"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5078 src/libnm-core-impl/nm-utils.c:5098
+#: src/libnm-core-impl/nm-utils.c:5506 src/libnm-core-impl/nm-utils.c:5526
 msgid "unterminated escape sequence"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5124
+#: src/libnm-core-impl/nm-utils.c:5552
 #, c-format
 msgid "unknown attribute '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5142
+#: src/libnm-core-impl/nm-utils.c:5570
 #, c-format
 msgid "missing key-value separator '%c' after '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5162
+#: src/libnm-core-impl/nm-utils.c:5590
 #, c-format
 msgid "invalid uint32 value '%s' for attribute '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5176
+#: src/libnm-core-impl/nm-utils.c:5604
 #, c-format
 msgid "invalid int32 value '%s' for attribute '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5189
+#: src/libnm-core-impl/nm-utils.c:5617
 #, c-format
 msgid "invalid uint64 value '%s' for attribute '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5202
+#: src/libnm-core-impl/nm-utils.c:5630
 #, c-format
 msgid "invalid uint8 value '%s' for attribute '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5216
+#: src/libnm-core-impl/nm-utils.c:5644
 #, c-format
 msgid "invalid boolean value '%s' for attribute '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5230
+#: src/libnm-core-impl/nm-utils.c:5658
 #, c-format
 msgid "unsupported attribute '%s' of type '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5531
+#: src/libnm-core-impl/nm-utils.c:5959
 #, c-format
 msgid "Bridge VLANs %d and %d are not sorted by ascending vid"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5555
+#: src/libnm-core-impl/nm-utils.c:5983
 #, c-format
 msgid "duplicate bridge VLAN vid %u"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5567
+#: src/libnm-core-impl/nm-utils.c:5995
 msgid "only one VLAN can be the PVID"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5710
+#: src/libnm-core-impl/nm-utils.c:6138
 #, c-format
 msgid "unknown flags 0x%x"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5722
+#: src/libnm-core-impl/nm-utils.c:6150
 msgid ""
 "'fqdn-no-update' and 'fqdn-serv-update' flags cannot be set at the same time"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5733
+#: src/libnm-core-impl/nm-utils.c:6161
 msgid "'fqdn-clear-flags' flag is incompatible with other FQDN flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-utils.c:5741
+#: src/libnm-core-impl/nm-utils.c:6169
 msgid "DHCPv6 does not support the E (encoded) FQDN flag"
 msgstr ""
 
@@ -3732,79 +3845,79 @@ msgstr ""
 msgid "Method returned type '%s', but expected '%s'"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:2262
+#: src/libnm-glib-aux/nm-shared-utils.c:2439
 #, c-format
 msgid "object class '%s' has no property named '%s'"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:2271
+#: src/libnm-glib-aux/nm-shared-utils.c:2448
 #, c-format
 msgid "property '%s' of object class '%s' is not writable"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:2280
+#: src/libnm-glib-aux/nm-shared-utils.c:2457
 #, c-format
 msgid ""
 "construct property \"%s\" for object '%s' can't be set after construction"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:2291
+#: src/libnm-glib-aux/nm-shared-utils.c:2468
 #, c-format
 msgid "'%s::%s' is not a valid property name; '%s' is not a GObject subtype"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:2304
+#: src/libnm-glib-aux/nm-shared-utils.c:2481
 #, c-format
 msgid "unable to set property '%s' of type '%s' from value of type '%s'"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:2316
+#: src/libnm-glib-aux/nm-shared-utils.c:2493
 #, c-format
 msgid ""
 "value \"%s\" of type '%s' is invalid or out of range for property '%s' of "
 "type '%s'"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5330
+#: src/libnm-glib-aux/nm-shared-utils.c:5516
 msgid "interface name is missing"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5338
+#: src/libnm-glib-aux/nm-shared-utils.c:5524
 msgid "interface name is too short"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5346
+#: src/libnm-glib-aux/nm-shared-utils.c:5532
 msgid "interface name is reserved"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5359
+#: src/libnm-glib-aux/nm-shared-utils.c:5545
 msgid "interface name contains an invalid character"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5367
+#: src/libnm-glib-aux/nm-shared-utils.c:5553
 msgid "interface name is longer than 15 characters"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5392
+#: src/libnm-glib-aux/nm-shared-utils.c:5578
 #, c-format
 msgid "'%%' is not allowed in interface names"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5404
+#: src/libnm-glib-aux/nm-shared-utils.c:5590
 #, c-format
 msgid "'%s' is not allowed as interface name"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5426
+#: src/libnm-glib-aux/nm-shared-utils.c:5612
 msgid ""
 "interface name must be alphanumerical with no forward or backward slashes"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5443
+#: src/libnm-glib-aux/nm-shared-utils.c:5629
 msgid "interface name must not be empty"
 msgstr ""
 
-#: src/libnm-glib-aux/nm-shared-utils.c:5451
+#: src/libnm-glib-aux/nm-shared-utils.c:5637
 msgid "interface name must be UTF-8 encoded"
 msgstr ""
 
@@ -3846,21 +3959,22 @@ msgstr ""
 msgid "missing name, try one of [%s]"
 msgstr ""
 
-#: src/libnmc-base/nm-client-utils.c:248 src/nmcli/connections.c:3744
-#: src/nmcli/connections.c:3802
+#: src/libnmc-base/nm-client-utils.c:248 src/nmcli/connections.c:3771
+#: src/nmcli/connections.c:3829
 #, c-format
 msgid "'%s' not among [%s]"
 msgstr ""
 
 #: src/libnmc-base/nm-client-utils.c:291 src/libnmc-base/nm-client-utils.c:305
 #: src/libnmc-base/nm-client-utils.c:341 src/libnmc-base/nm-client-utils.c:346
-#: src/libnmc-setting/nm-meta-setting-desc.c:1854
-#: src/libnmc-setting/nm-meta-setting-desc.c:1885
-#: src/libnmc-setting/nm-meta-setting-desc.c:2894
-#: src/libnmc-setting/nm-meta-setting-desc.c:2952 src/nmcli/common.c:1611
+#: src/libnmc-setting/nm-meta-setting-desc.c:1842
+#: src/libnmc-setting/nm-meta-setting-desc.c:1873
+#: src/libnmc-setting/nm-meta-setting-desc.c:2882
+#: src/libnmc-setting/nm-meta-setting-desc.c:2940 src/nmcli/common.c:1611
 #: src/nmcli/connections.c:79 src/nmcli/connections.c:89
 #: src/nmcli/devices.c:485 src/nmcli/devices.c:592 src/nmcli/devices.c:598
-#: src/nmcli/general.c:30 src/nmcli/general.c:85 src/nmcli/general.c:91
+#: src/nmcli/devices.c:604 src/nmcli/general.c:30 src/nmcli/general.c:85
+#: src/nmcli/general.c:91
 msgid "unknown"
 msgstr ""
 
@@ -3927,20 +4041,20 @@ msgid "deactivating (externally)"
 msgstr ""
 
 #: src/libnmc-base/nm-client-utils.c:342
-#: src/libnmc-setting/nm-meta-setting-desc.c:881
-#: src/libnmc-setting/nm-meta-setting-desc.c:2886 src/nmcli/connections.c:5542
-#: src/nmcli/connections.c:7520 src/nmcli/connections.c:7521
-#: src/nmcli/devices.c:591 src/nmcli/devices.c:597 src/nmcli/devices.c:1411
-#: src/nmcli/general.c:92 src/nmcli/utils.h:315
+#: src/libnmc-setting/nm-meta-setting-desc.c:875
+#: src/libnmc-setting/nm-meta-setting-desc.c:2874 src/nmcli/connections.c:5576
+#: src/nmcli/connections.c:7554 src/nmcli/connections.c:7555
+#: src/nmcli/devices.c:591 src/nmcli/devices.c:597 src/nmcli/devices.c:603
+#: src/nmcli/devices.c:1427 src/nmcli/general.c:92 src/nmcli/utils.h:316
 msgid "yes"
 msgstr ""
 
 #: src/libnmc-base/nm-client-utils.c:343
-#: src/libnmc-setting/nm-meta-setting-desc.c:881
-#: src/libnmc-setting/nm-meta-setting-desc.c:2889 src/nmcli/connections.c:5541
-#: src/nmcli/connections.c:7520 src/nmcli/connections.c:7521
-#: src/nmcli/devices.c:591 src/nmcli/devices.c:597 src/nmcli/devices.c:1411
-#: src/nmcli/general.c:93 src/nmcli/utils.h:315
+#: src/libnmc-setting/nm-meta-setting-desc.c:875
+#: src/libnmc-setting/nm-meta-setting-desc.c:2877 src/nmcli/connections.c:5575
+#: src/nmcli/connections.c:7554 src/nmcli/connections.c:7555
+#: src/nmcli/devices.c:591 src/nmcli/devices.c:597 src/nmcli/devices.c:603
+#: src/nmcli/devices.c:1427 src/nmcli/general.c:93 src/nmcli/utils.h:316
 msgid "no"
 msgstr ""
 
@@ -3957,8 +4071,8 @@ msgid "No reason given"
 msgstr ""
 
 #. We should not really come here
-#: src/libnmc-base/nm-client-utils.c:354 src/nmcli/connections.c:3764
-#: src/nmcli/connections.c:3823
+#: src/libnmc-base/nm-client-utils.c:354 src/nmcli/connections.c:3791
+#: src/nmcli/connections.c:3850
 msgid "Unknown error"
 msgstr ""
 
@@ -4332,7 +4446,7 @@ msgstr ""
 
 #: src/libnmc-base/nm-secret-agent-simple.c:270
 #: src/libnmc-base/nm-secret-agent-simple.c:357
-#: src/libnmc-setting/nm-meta-setting-desc.c:5138
+#: src/libnmc-setting/nm-meta-setting-desc.c:5200
 #: src/nmtui/nmt-8021x-fields.c:182 src/nmtui/nmt-8021x-fields.c:353
 #: src/nmtui/nmt-8021x-fields.c:457 src/nmtui/nmt-page-dsl.c:51
 #: src/nmtui/nmt-page-wifi.c:345
@@ -4348,7 +4462,7 @@ msgstr ""
 #: src/libnmc-base/nm-secret-agent-simple.c:979
 #: src/libnmc-base/nm-vpn-helpers.c:144 src/libnmc-base/nm-vpn-helpers.c:148
 #: src/libnmc-base/nm-vpn-helpers.c:154 src/libnmc-base/nm-vpn-helpers.c:159
-#: src/nmcli/devices.c:4720 src/nmtui/nmt-8021x-fields.c:195
+#: src/nmcli/devices.c:4736 src/nmtui/nmt-8021x-fields.c:195
 #: src/nmtui/nmt-8021x-fields.c:373 src/nmtui/nmt-8021x-fields.c:477
 #: src/nmtui/nmt-page-dsl.c:64 src/nmtui/nmt-page-wifi.c:287
 #: src/nmtui/nmt-page-wifi.c:319 src/nmtui/nmt-page-wifi.c:358
@@ -4447,7 +4561,7 @@ msgid "MACsec PSK authentication"
 msgstr ""
 
 #: src/libnmc-base/nm-secret-agent-simple.c:931
-#: src/libnmc-setting/nm-meta-setting-desc.c:6744
+#: src/libnmc-setting/nm-meta-setting-desc.c:6896
 msgid "MKA CAK"
 msgstr ""
 
@@ -4540,199 +4654,199 @@ msgstr ""
 msgid "invalid field '%s%s%s%s%s'; %s%s%s"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:264
-#: src/libnmc-setting/nm-meta-setting-desc.c:332
+#: src/libnmc-setting/nm-meta-setting-desc.c:258
+#: src/libnmc-setting/nm-meta-setting-desc.c:326
 #, c-format
 msgid "invalid prefix '%s'; <0-%d> allowed"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:275
+#: src/libnmc-setting/nm-meta-setting-desc.c:269
 #, c-format
 msgid "invalid IP address: %s"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:300
+#: src/libnmc-setting/nm-meta-setting-desc.c:294
 msgid ""
 "The valid syntax is: 'ip[/prefix] [next-hop] [metric] [attribute=val]... [,"
 "ip[/prefix] ...]'"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:346
+#: src/libnmc-setting/nm-meta-setting-desc.c:340
 #, c-format
 msgid "the next hop ('%s') must be first"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:356
+#: src/libnmc-setting/nm-meta-setting-desc.c:350
 #, c-format
 msgid "the metric ('%s') must be before attributes"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:409
+#: src/libnmc-setting/nm-meta-setting-desc.c:403
 #, c-format
 msgid "invalid route: %s. %s"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:478
+#: src/libnmc-setting/nm-meta-setting-desc.c:472
 #, c-format
 msgid "cannot read pac-script from file '%s'"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:486
+#: src/libnmc-setting/nm-meta-setting-desc.c:480
 #, c-format
 msgid "file '%s' contains non-valid utf-8"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:499
+#: src/libnmc-setting/nm-meta-setting-desc.c:493
 #, c-format
 msgid "'%s' does not contain a valid PAC Script"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:502
+#: src/libnmc-setting/nm-meta-setting-desc.c:496
 msgid "Not a valid PAC Script"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:554
+#: src/libnmc-setting/nm-meta-setting-desc.c:548
 #, c-format
 msgid "cannot read team config from file '%s'"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:562
+#: src/libnmc-setting/nm-meta-setting-desc.c:556
 #, c-format
 msgid "team config file '%s' contains non-valid utf-8"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1056
+#: src/libnmc-setting/nm-meta-setting-desc.c:1050
 msgid "auto"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1221
+#: src/libnmc-setting/nm-meta-setting-desc.c:1193
 #, c-format
 msgid "%s (%s)"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1413
-#: src/libnmc-setting/nm-meta-setting-desc.c:1421
-#: src/libnmc-setting/nm-meta-setting-desc.c:4478
+#: src/libnmc-setting/nm-meta-setting-desc.c:1447
+#: src/libnmc-setting/nm-meta-setting-desc.c:1455
+#: src/libnmc-setting/nm-meta-setting-desc.c:4513
 msgid "'%s' is out of range [%"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1429
+#: src/libnmc-setting/nm-meta-setting-desc.c:1463
 #, c-format
 msgid "'%s' is not a valid number"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1485
+#: src/libnmc-setting/nm-meta-setting-desc.c:1519
 #, c-format
 msgid "'%s' is out of range [0, %u]"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1532
+#: src/libnmc-setting/nm-meta-setting-desc.c:1570
 #, c-format
 msgid "'%s' is not a valid Ethernet MAC"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1657
+#: src/libnmc-setting/nm-meta-setting-desc.c:1672
 #, c-format
 msgid "invalid option '%s', use a combination of [%s]"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1821
+#: src/libnmc-setting/nm-meta-setting-desc.c:1809
 #, c-format
 msgid "%d (key)"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1823
+#: src/libnmc-setting/nm-meta-setting-desc.c:1811
 #, c-format
 msgid "%d (passphrase)"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1826
+#: src/libnmc-setting/nm-meta-setting-desc.c:1814
 #, c-format
 msgid "%d (unknown)"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1839
+#: src/libnmc-setting/nm-meta-setting-desc.c:1827
 msgid "0 (NONE)"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1845
+#: src/libnmc-setting/nm-meta-setting-desc.c:1833
 msgid "REORDER_HEADERS, "
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1847
+#: src/libnmc-setting/nm-meta-setting-desc.c:1835
 msgid "GVRP, "
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1849
+#: src/libnmc-setting/nm-meta-setting-desc.c:1837
 msgid "LOOSE_BINDING, "
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1851
+#: src/libnmc-setting/nm-meta-setting-desc.c:1839
 msgid "MVRP, "
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1872
+#: src/libnmc-setting/nm-meta-setting-desc.c:1860
 msgid "0 (none)"
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1878
+#: src/libnmc-setting/nm-meta-setting-desc.c:1866
 msgid "agent-owned, "
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1880
+#: src/libnmc-setting/nm-meta-setting-desc.c:1868
 msgid "not saved, "
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:1882
+#: src/libnmc-setting/nm-meta-setting-desc.c:1870
 msgid "not required, "
 msgstr ""
 
-#: src/libnmc-setting/nm-meta-setting-desc.c:2087
+#: src/libnmc-setting/nm-meta-setting-desc.c:2075
 #, c-format
 msgid "'%s' is not valid; use