From bfe522304da217296e2a61040f58e35ec5d6f3f2 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Mon, 16 Aug 2021 09:51:46 +0200 Subject: New upstream version 1.30.6 --- man/nm-settings-nmcli.5 | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'man/nm-settings-nmcli.5') diff --git a/man/nm-settings-nmcli.5 b/man/nm-settings-nmcli.5 index 89a61faf..f2065582 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: 02/18/2021 +.\" Date: 07/16/2021 .\" Manual: Configuration -.\" Source: NetworkManager 1.30.0 +.\" Source: NetworkManager 1.30.6 .\" Language: English .\" -.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.30\&.0" "Configuration" +.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.30\&.6" "Configuration" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -2703,14 +2703,14 @@ Properties: .PP \fBqdiscs\fR .RS 4 -Array of TC queueing disciplines\&. +Array of TC queueing disciplines\&. When the "tc" setting is present, qdiscs from this property are applied upon activation\&. If the property is empty, all qdiscs are removed and the device will only have the default qdisc assigned by kernel according to the "net\&.core\&.default_qdisc" sysctl\&. If the "tc" setting is not present, NetworkManager doesn\*(Aqt touch the qdiscs present on the interface\&. .sp Format: array of vardict .RE .PP \fBtfilters\fR .RS 4 -Array of TC traffic filters\&. +Array of TC traffic filters\&. When the "tc" setting is present, filters from this property are applied upon activation\&. If the property is empty, NetworkManager removes all the filters\&. If the "tc" setting is not present, NetworkManager doesn\*(Aqt touch the filters present on the interface\&. .sp Format: array of vardict .RE -- cgit 1.3.0-6-gf8a5 From e74c568b07b50b97873fb4ee1d776dedefbd54d6 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Fri, 1 Oct 2021 23:05:04 +0200 Subject: New upstream version 1.32.12 --- man/nm-settings-nmcli.5 | 60 +++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 48 insertions(+), 12 deletions(-) (limited to 'man/nm-settings-nmcli.5') diff --git a/man/nm-settings-nmcli.5 b/man/nm-settings-nmcli.5 index f2065582..f39e8f56 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: 07/16/2021 +.\" Date: 09/22/2021 .\" Manual: Configuration -.\" Source: NetworkManager 1.30.6 +.\" Source: NetworkManager 1.32.12 .\" Language: English .\" -.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.30\&.6" "Configuration" +.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.32\&.12" "Configuration" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -1452,6 +1452,21 @@ Properties: .RS 4 .RE .PP +\fBpause\-autoneg\fR +.RS 4 +Whether to automatically negotiate on pause frame of flow control mechanism defined by IEEE 802\&.3x standard\&. +.RE +.PP +\fBpause\-rx\fR +.RS 4 +Whether RX pause should be enabled\&. Only valid when automatic negotiation is disabled +.RE +.PP +\fBpause\-tx\fR +.RS 4 +Whether TX pause should be enabled\&. Only valid when automatic negotiation is disabled +.RE +.PP \fBring\-rx\fR .RS 4 .RE @@ -1640,9 +1655,9 @@ Properties: .RS 4 Alias: ip4 .sp -Array of IP addresses\&. +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: array of array of uint32 +Format: a comma separated list of addresses .RE .PP \fBdad\-timeout\fR @@ -1787,6 +1802,13 @@ If TRUE, this connection will never be the default connection for this IP type, Format: boolean .RE .PP +\fBrequired\-timeout\fR +.RS 4 +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)\&. +.sp +Format: int32 +.RE +.PP \fBroute\-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\&. @@ -1803,9 +1825,9 @@ Format: uint32 .PP \fBroutes\fR .RS 4 -Array of IP routes\&. +A list of IPv4 destination addresses, prefix length, optional IPv4 next hop addresses, optional route metric, optional attribute\&. The valid syntax is: "ip[/prefix] [next\-hop] [metric] [attribute=val]\&.\&.\&.[,ip[/prefix]\&.\&.\&.]"\&. For example "192\&.0\&.2\&.0/24 10\&.1\&.1\&.1 77, 198\&.51\&.100\&.0/24"\&. .sp -Format: array of array of uint32 +Format: a comma separated list of routes .RE .PP \fBrouting\-rules\fR @@ -1828,9 +1850,9 @@ Format: int32 .RS 4 Alias: ip6 .sp -Array of IP addresses\&. +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 increasing priority, meaning the last address will be the primary address\&. .sp -Format: array of legacy IPv6 address struct +Format: a comma separated list of addresses .RE .PP \fBdhcp\-duid\fR @@ -1961,6 +1983,13 @@ A timeout for waiting Router Advertisements in seconds\&. If zero (the default), Format: int32 .RE .PP +\fBrequired\-timeout\fR +.RS 4 +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)\&. +.sp +Format: int32 +.RE +.PP \fBroute\-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\&. @@ -2239,7 +2268,7 @@ Format: array of string .PP \fBkernel\-command\-line\fR .RS 4 -A list of kernel command line arguments to match\&. This may be used to check whether a specific kernel command line option is set (or if prefixed with the exclamation mark unset)\&. The argument must either be a single word, or an assignment (i\&.e\&. two words, separated "=")\&. 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\&. See NMSettingMatch:interface\-name for how special characters \*(Aq|\*(Aq, \*(Aq&\*(Aq, \*(Aq!\*(Aq and \*(Aq\e\*(Aq are used for optional and mandatory matches and inverting the pattern\&. +A list of kernel command line arguments to match\&. This may be used to check whether a specific kernel command line option is set (or unset, if prefixed with the exclamation mark)\&. The argument must either be a single word, or an assignment (i\&.e\&. two words, joined by "=")\&. In the former case the kernel command line is searched for the word appearing as is, or as left hand side of an assignment\&. In the latter case, the exact assignment is looked for with right and left hand side matching\&. Wildcard patterns are not supported\&. See NMSettingMatch:interface\-name for how special characters \*(Aq|\*(Aq, \*(Aq&\*(Aq, \*(Aq!\*(Aq and \*(Aq\e\*(Aq are used for optional and mandatory matches and inverting the match\&. .sp Format: array of string .RE @@ -2271,7 +2300,7 @@ Format: uint32 .RS 4 Alias: dhcp\-anycast .sp -Anycast DHCP MAC address used when requesting an IP address via DHCP\&. The specific anycast address used determines which DHCP server class answers the request\&. +Anycast DHCP MAC address used when requesting an IP address via DHCP\&. The specific anycast address used determines which DHCP server class answers the request\&. This is currently only implemented by dhclient DHCP plugin\&. .sp Format: byte array .RE @@ -3253,6 +3282,13 @@ Wired Ethernet Settings\&. .PP Properties: .PP +\fBaccept\-all\-mac\-addresses\fR +.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) +.RE +.PP \fBauto\-negotiate\fR .RS 4 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\&. @@ -3593,7 +3629,7 @@ Format: array of string .PP \fBkey\-mgmt\fR .RS 4 -Key management used for the connection\&. One of "none" (WEP), "ieee8021x" (Dynamic WEP), "wpa\-psk" (infrastructure WPA\-PSK), "sae" (SAE), "owe" (Opportunistic Wireless Encryption), "wpa\-eap" (WPA\-Enterprise) or "wpa\-eap\-suite\-b\-192" (WPA3\-Enterprise Suite B)\&. This property must be set for any Wi\-Fi connection that uses security\&. +Key management used for the connection\&. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa\-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa\-eap" (WPA2 + WPA3 enterprise) or "wpa\-eap\-suite\-b\-192" (WPA3 enterprise only)\&. This property must be set for any Wi\-Fi connection that uses security\&. .sp Format: string .RE -- cgit 1.3.0-6-gf8a5 From 88c227d90a6b7b388c5c85d72802a0ca8f05ed5c Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 13 Jan 2022 22:30:39 +0100 Subject: New upstream version 1.34.0 --- man/nm-settings-nmcli.5 | 216 +++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 205 insertions(+), 11 deletions(-) (limited to 'man/nm-settings-nmcli.5') diff --git a/man/nm-settings-nmcli.5 b/man/nm-settings-nmcli.5 index f39e8f56..b290f8a5 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: 09/22/2021 +.\" Date: 01/13/2022 .\" Manual: Configuration -.\" Source: NetworkManager 1.32.12 +.\" Source: NetworkManager 1.34.0 .\" Language: English .\" -.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.32\&.12" "Configuration" +.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.34\&.0" "Configuration" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -79,14 +79,14 @@ Format: int32 .RS 4 Alias: autoconnect .sp -Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available\&. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection\&. Note that autoconnect is not implemented for VPN profiles\&. See "secondaries" as an alternative to automatically connect VPN profiles\&. +Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available\&. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection\&. Autoconnect happens when the circumstances are suitable\&. That means for example that the device is currently managed and not active\&. Autoconnect thus never replaces or competes with an already active profile\&. Note that autoconnect is not implemented for VPN profiles\&. See "secondaries" as an alternative to automatically connect VPN profiles\&. .sp Format: boolean .RE .PP \fBautoconnect\-priority\fR .RS 4 -The autoconnect priority\&. If the connection is set to autoconnect, connections with higher priority will be preferred\&. Defaults to 0\&. The higher number means higher priority\&. +The autoconnect priority in range \-999 to 999\&. If the connection is set to autoconnect, connections with higher priority will be preferred\&. The higher number means higher priority\&. Defaults to 0\&. Note that this property only matters if there are more than one candidate profile to select for autoconnect\&. In case of equal priority, the profile used most recently is chosen\&. .sp Format: int32 .RE @@ -105,6 +105,13 @@ Whether or not slaves of this connection should be automatically brought up when Format: NMSettingConnectionAutoconnectSlaves (int32) .RE .PP +\fBdns\-over\-tls\fR +.RS 4 +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\*(Aqt 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\&. +.sp +Format: int32 +.RE +.PP \fBgateway\-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\&. @@ -1031,7 +1038,7 @@ Format: NMSettingDcbFlags (uint32) .PP \fBapp\-fcoe\-mode\fR .RS 4 -The FCoE controller mode; either "fabric" (default) or "vn2vn"\&. +The FCoE controller mode; either "fabric" or "vn2vn"\&. Since 1\&.34, NULL is the default and means "fabric"\&. Before 1\&.34, NULL was rejected as invalid and the default was "fabric"\&. .sp Format: string .RE @@ -2732,16 +2739,189 @@ Properties: .PP \fBqdiscs\fR .RS 4 -Array of TC queueing disciplines\&. When the "tc" setting is present, qdiscs from this property are applied upon activation\&. If the property is empty, all qdiscs are removed and the device will only have the default qdisc assigned by kernel according to the "net\&.core\&.default_qdisc" sysctl\&. If the "tc" setting is not present, NetworkManager doesn\*(Aqt touch the qdiscs present on the interface\&. +Array of TC queueing disciplines\&. qdisc is a basic block in the Linux traffic control subsystem .sp -Format: array of vardict +Each qdisc can be specified by the following attributes: +.PP +\fIhandle HANDLE\fR +.RS 4 +specifies the qdisc handle\&. A qdisc, which potentially can have children, gets assigned a major number, called a \*(Aqhandle\*(Aq, leaving the minor number namespace available for classes\&. The handle is expressed as \*(Aq10:\*(Aq\&. It is customary to explicitly assign a handle to qdiscs expected to have children\&. +.RE +.PP +\fIparent HANDLE\fR +.RS 4 +specifies the handle of the parent qdisc the current qdisc must be attached to\&. +.RE +.PP +\fIroot\fR +.RS 4 +specifies that the qdisc is attached to the root of device\&. +.RE +.PP +\fIKIND\fR +.RS 4 +this is the qdisc kind\&. NetworkManager currently supports the following kinds: fq_codel, sfq, tbf\&. Each qdisc kind has a different set of parameters, described below\&. There are also some kinds like pfifo, pfifo_fast, prio supported by NetworkManager but their parameters are not supported by NetworkManager\&. +.RE +.sp +Parameters for \*(Aqfq_codel\*(Aq: +.PP +\fIlimit U32\fR +.RS 4 +the hard limit on the real queue size\&. When this limit is reached, incoming packets are dropped\&. Default is 10240 packets\&. +.RE +.PP +\fImemory_limit U32\fR +.RS 4 +sets a limit on the total number of bytes that can be queued in this FQ\-CoDel instance\&. The lower of the packet limit of the limit parameter and the memory limit will be enforced\&. Default is 32 MB\&. +.RE +.PP +\fIflows U32\fR +.RS 4 +the number of flows into which the incoming packets are classified\&. Due to the stochastic nature of hashing, multiple flows may end up being hashed into the same slot\&. Newer flows have priority over older ones\&. This parameter can be set only at load time since memory has to be allocated for the hash table\&. Default value is 1024\&. +.RE +.PP +\fItarget U32\fR +.RS 4 +the acceptable minimum standing/persistent queue delay\&. This minimum delay is identified by tracking the local minimum queue delay that packets experience\&. The unit of measurement is microsecond(us)\&. Default value is 5ms\&. +.RE +.PP +\fIinterval U32\fR +.RS 4 +used to ensure that the measured minimum delay does not become too stale\&. The minimum delay must be experienced in the last epoch of length \&.B interval\&. It should be set on the order of the worst\-case RTT through the bottleneck to give endpoints sufficient time to react\&. Default value is 100ms\&. +.RE +.PP +\fIquantum U32\fR +.RS 4 +the number of bytes used as \*(Aqdeficit\*(Aq in the fair queuing algorithm\&. Default is set to 1514 bytes which corresponds to the Ethernet MTU plus the hardware header length of 14 bytes\&. +.RE +.PP +\fIecn BOOL\fR +.RS 4 +can be used to mark packets instead of dropping them\&. ecn is turned on by default\&. +.RE +.PP +\fIce_threshold U32\fR +.RS 4 +sets a threshold above which all packets are marked with ECN Congestion Experienced\&. This is useful for DCTCP\-style congestion control algorithms that require marking at very shallow queueing thresholds\&. +.RE +.sp +Parameters for \*(Aqsfq\*(Aq: +.PP +\fIdivisor U32\fR +.RS 4 +can be used to set a different hash table size, available from kernel 2\&.6\&.39 onwards\&. The specified divisor must be a power of two and cannot be larger than 65536\&. Default value: 1024\&. +.RE +.PP +\fIlimit U32\fR +.RS 4 +Upper limit of the SFQ\&. Can be used to reduce the default length of 127 packets\&. +.RE +.PP +\fIdepth U32\fR +.RS 4 +Limit of packets per flow\&. Default to 127 and can be lowered\&. +.RE +.PP +\fIperturb_period U32\fR +.RS 4 +Interval in seconds for queue algorithm perturbation\&. Defaults to 0, which means that no perturbation occurs\&. Do not set too low for each perturbation may cause some packet reordering or losses\&. Advised value: 60 This value has no effect when external flow classification is used\&. Its better to increase divisor value to lower risk of hash collisions\&. +.RE +.PP +\fIquantum U32\fR +.RS 4 +Amount of bytes a flow is allowed to dequeue during a round of the round robin process\&. Defaults to the MTU of the interface which is also the advised value and the minimum value\&. +.RE +.PP +\fIflows U32\fR +.RS 4 +Default value is 127\&. +.RE +.sp +Parameters for \*(Aqtbf\*(Aq: +.PP +\fIrate U64\fR +.RS 4 +Bandwidth or rate\&. These parameters accept a floating point number, possibly followed by either a unit (both SI and IEC units supported), or a float followed by a percent character to specify the rate as a percentage of the device\*(Aqs speed\&. +.RE +.PP +\fIburst U32\fR +.RS 4 +Also known as buffer or maxburst\&. Size of the bucket, in bytes\&. This is the maximum amount of bytes that tokens can be available for instantaneously\&. In general, larger shaping rates require a larger buffer\&. For 10mbit/s on Intel, you need at least 10kbyte buffer if you want to reach your configured rate! +.sp +If your buffer is too small, packets may be dropped because more tokens arrive per timer tick than fit in your bucket\&. The minimum buffer size can be calculated by dividing the rate by HZ\&. +.sp +Token usage calculations are performed using a table which by default has a resolution of 8 packets\&. This resolution can be changed by specifying the cell size with the burst\&. For example, to specify a 6000 byte buffer with a 16 byte cell size, set a burst of 6000/16\&. You will probably never have to set this\&. Must be an integral power of 2\&. +.RE +.PP +\fIlimit U32\fR +.RS 4 +Limit is the number of bytes that can be queued waiting for tokens to become available\&. +.RE +.PP +\fIlatency U32\fR +.RS 4 +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) .RE .PP \fBtfilters\fR .RS 4 -Array of TC traffic filters\&. When the "tc" setting is present, filters from this property are applied upon activation\&. If the property is empty, NetworkManager removes all the filters\&. If the "tc" setting is not present, NetworkManager doesn\*(Aqt touch the filters present on the interface\&. +Array of TC traffic filters\&. Traffic control can manage the packet content during classification by using filters\&. .sp -Format: array of vardict +Each tfilters can be specified by the following attributes: +.PP +\fIhandle HANDLE\fR +.RS 4 +specifies the tfilters handle\&. A filter is used by a classful qdisc to determine in which class a packet will be enqueued\&. It is important to notice that filters reside within qdiscs\&. Therefore, see qdiscs handle for detailed information\&. +.RE +.PP +\fIparent HANDLE\fR +.RS 4 +specifies the handle of the parent qdisc the current qdisc must be attached to\&. +.RE +.PP +\fIroot\fR +.RS 4 +specifies that the qdisc is attached to the root of device\&. +.RE +.PP +\fIKIND\fR +.RS 4 +this is the tfilters kind\&. NetworkManager currently supports following kinds: mirred, simple\&. Each filter kind has a different set of actions, described below\&. There are also some other kinds like matchall, basic, u32 supported by NetworkManager\&. +.RE +.sp +Actions for \*(Aqmirred\*(Aq: +.PP +\fIegress bool\fR +.RS 4 +Define whether the packet should exit from the interface\&. +.RE +.PP +\fIingress bool\fR +.RS 4 +Define whether the packet should come into the interface\&. +.RE +.PP +\fImirror bool\fR +.RS 4 +Define whether the packet should be copied to the destination space\&. +.RE +.PP +\fIredirect bool\fR +.RS 4 +Define whether the packet should be moved to the destination space\&. +.RE +.sp +Action for \*(Aqsimple\*(Aq: +.PP +\fIsdata char[32]\fR +.RS 4 +The actual string to print\&. +.RE +.sp +Format: GPtrArray(NMTCTfilter) .RE .SS "team setting" .PP @@ -3360,7 +3540,7 @@ Format: string .PP \fBs390\-options\fR .RS 4 -Dictionary of key/value pairs of s390\-specific device options\&. Both keys and values must be strings\&. Allowed keys include "portno", "layer2", "portname", "protocol", among others\&. Key names must contain only alphanumeric characters (ie, [a\-zA\-Z0\-9])\&. +Dictionary of key/value pairs of s390\-specific device options\&. Both keys and values must be strings\&. Allowed keys include "portno", "layer2", "portname", "protocol", among others\&. Key names must contain only alphanumeric characters (ie, [a\-zA\-Z0\-9])\&. Currently, NetworkManager itself does nothing with this information\&. However, s390utils ships a udev rule which parses this information and applies it to the interface\&. .sp Format: dict of string to string .RE @@ -3801,6 +3981,20 @@ Short IEEE 802\&.15\&.4 address to be used within a restricted environment\&. .sp Format: uint32 .RE +.SS "bond\-port setting" +.PP +Bond Port Settings\&. +.PP +Properties: +.PP +\fBqueue\-id\fR +.RS 4 +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 +.RE .SS "hostname setting" .PP Hostname settings\&. -- cgit 1.3.0-6-gf8a5