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 --- 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 +- 34 files changed, 2743 insertions(+), 1148 deletions(-) (limited to 'man') 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 @@ ]> -- cgit 1.3.0-6-gf8a5