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't touch the qdiscs present on the interface.

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't touch the filters present on the interface.

Date: Fri, 1 Oct 2021 23:05:04 +0200 Subject: New upstream version 1.32.12 --- docs/api/html/nm-settings-nmcli.html | 148 ++++++++++++++++++++++------------- 1 file changed, 92 insertions(+), 56 deletions(-) (limited to 'docs/api/html/nm-settings-nmcli.html') diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index a869ef2b..1ce647f7 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -67,7 +67,7 @@ property.

connection setting

General Connection Profile Settings.

Properties: @@ -295,7 +295,7 @@

6lowpan setting

6LoWPAN Settings.

Properties: @@ -319,7 +319,7 @@

802-1x setting

IEEE 802.1x Authentication Settings.

Properties: @@ -729,7 +729,7 @@

adsl setting

ADSL Settings.

Properties: @@ -811,7 +811,7 @@

bluetooth setting

Bluetooth Settings.

Properties: @@ -847,7 +847,7 @@

bond setting

Bonding Settings.

Properties: @@ -869,7 +869,7 @@

bridge setting

Bridging Settings.

Properties: @@ -1119,7 +1119,7 @@

bridge-port setting

Bridge Port Settings.

Properties: @@ -1173,7 +1173,7 @@

cdma setting

CDMA-based Mobile Broadband Settings.

Properties: @@ -1235,7 +1235,7 @@

dcb setting

Data Center Bridging Settings.

Properties: @@ -1371,7 +1371,7 @@

ethtool setting

Ethtool Ethernet Settings.

Properties: @@ -1703,6 +1703,18 @@

pause-autoneg

Whether to automatically negotiate on pause frame of flow control mechanism defined by IEEE 802.3x standard.

+ + +

pause-rx

Whether RX pause should be enabled. Only valid when automatic negotiation is disabled

+ + +

pause-tx

Whether TX pause should be enabled. Only valid when automatic negotiation is disabled

+ +

ring-rx

@@ -1723,7 +1735,7 @@

gsm setting

GSM-based Mobile Broadband Settings.

Properties: @@ -1861,7 +1873,7 @@

infiniband setting

Infiniband Settings.

Properties: @@ -1927,7 +1939,7 @@

ipv4 setting

IPv4 Settings.

Properties: @@ -1943,9 +1955,9 @@

Alias: ip4

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.

- Format: array of array of uint32

+ Format: a comma separated list of addresses

@@ -2111,6 +2123,14 @@ +

required-timeout

+ +

The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).

+ Format: int32

+ + +

route-metric

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

@@ -2129,9 +2149,9 @@

routes

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

- Format: array of array of uint32

+ Format: a comma separated list of routes

@@ -2143,7 +2163,7 @@

ipv6 setting

IPv6 Settings.

Properties: @@ -2167,9 +2187,9 @@

Alias: ip6

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.

- Format: array of legacy IPv6 address struct

+ Format: a comma separated list of addresses

@@ -2319,6 +2339,14 @@ +

required-timeout

+ +

+ Format: int32

+ + +

route-metric

@@ -2359,7 +2387,7 @@

ip-tunnel setting

IP Tunneling Settings.

Properties: @@ -2487,7 +2515,7 @@

macsec setting

MACSec Settings.

Properties: @@ -2589,7 +2617,7 @@

macvlan setting

MAC VLAN Settings.

Properties: @@ -2643,7 +2671,7 @@

match setting

Match settings.

Properties: @@ -2673,7 +2701,7 @@

kernel-command-line

A list of kernel command line arguments to match. This may be used to check whether a specific kernel command line option is set (or 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 '|', '&', '!' and '\' 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 '|', '&', '!' and '\' are used for optional and mandatory matches and inverting the match.

Format: array of string

@@ -2691,7 +2719,7 @@

802-11-olpc-mesh setting

Alias: olpc-mesh

OLPC Wireless Mesh Settings.

@@ -2719,7 +2747,7 @@

Alias: dhcp-anycast

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

Anycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request. This is currently only implemented by dhclient DHCP plugin.

Format: byte array

@@ -2739,7 +2767,7 @@

ovs-bridge setting

OvsBridge Link Settings.

Properties: @@ -2795,7 +2823,7 @@

ovs-dpdk setting

OvsDpdk Link Settings.

Properties: @@ -2817,7 +2845,7 @@

ovs-interface setting

Open vSwitch Interface Settings.

Properties: @@ -2839,7 +2867,7 @@

ovs-patch setting

OvsPatch Link Settings.

Properties: @@ -2861,7 +2889,7 @@

ovs-port setting

OvsPort Link Settings.

Properties: @@ -2925,7 +2953,7 @@

ppp setting

Point-to-Point Protocol Settings.

Properties: @@ -3085,7 +3113,7 @@

pppoe setting

PPP-over-Ethernet Settings.

Properties: @@ -3151,7 +3179,7 @@

proxy setting

WWW Proxy Settings.

Properties: @@ -3207,7 +3235,7 @@

serial setting

Serial Link Settings.

Properties: @@ -3263,7 +3291,7 @@

sriov setting

SR-IOV settings.

Properties: @@ -3303,7 +3331,7 @@

tc setting

Linux Traffic Control Settings.

Properties: @@ -3335,7 +3363,7 @@

team setting

Teaming Settings.

Properties: @@ -3481,7 +3509,7 @@

team-port setting

Team Port Settings.

Properties: @@ -3555,7 +3583,7 @@

tun setting

Tunnel Settings.

Properties: @@ -3631,7 +3659,7 @@

vlan setting

VLAN Settings.

Properties: @@ -3697,7 +3725,7 @@

vpn setting

VPN Settings.

Properties: @@ -3765,7 +3793,7 @@

vrf setting

VRF settings.

Properties: @@ -3789,7 +3817,7 @@

vxlan setting

VXLAN Settings.

Properties: @@ -3947,7 +3975,7 @@

wifi-p2p setting

Wi-Fi P2P Settings.

Properties: @@ -3989,7 +4017,7 @@

wimax setting

WiMax Settings.

Properties: @@ -4025,7 +4053,7 @@

802-3-ethernet setting

Alias: ethernet

Wired Ethernet Settings.

@@ -4039,6 +4067,14 @@ +

accept-all-mac-addresses

+ +

When TRUE, setup the interface to accept packets for all MAC addresses. This is enabling the kernel interface flag IFF_PROMISC. When FALSE, the interface will only accept the packets with the interface destination mac address or broadcast.

+ Format: NMTernary (int32)

+ + +

auto-negotiate

When TRUE, enforce auto-negotiation of speed and duplex mode. If "speed" and "duplex" properties are both specified, only that single mode will be advertised and accepted during the link auto-negotiation process: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. When FALSE, "speed" and "duplex" properties should be both set or link configuration will be skipped.

@@ -4161,7 +4197,7 @@

wireguard setting

WireGuard Settings.

Properties: @@ -4243,7 +4279,7 @@

802-11-wireless setting

Alias: wifi

Wi-Fi Settings.

@@ -4415,7 +4451,7 @@

802-11-wireless-security setting

Alias: wifi-sec

Wi-Fi Security Settings.

@@ -4455,7 +4491,7 @@

key-mgmt

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.

Format: string

@@ -4599,7 +4635,7 @@

wpan setting

IEEE 802.15.4 (WPAN) MAC Settings.

Properties: @@ -4665,7 +4701,7 @@

hostname setting

Hostname settings.

Properties: @@ -4713,7 +4749,7 @@

veth setting

Veth Settings.

Properties: -- 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 --- docs/api/html/nm-settings-nmcli.html | 535 +++++++++++++++++++++++++++++++---- 1 file changed, 487 insertions(+), 48 deletions(-) (limited to 'docs/api/html/nm-settings-nmcli.html') diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index 1ce647f7..0043313f 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -91,7 +91,7 @@

Alias: autoconnect

Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.

Format: boolean

@@ -99,7 +99,7 @@

autoconnect-priority

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.

Format: int32

@@ -121,6 +121,14 @@ +

dns-over-tls

+ +

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

+ Format: int32

+ + +

gateway-ping-timeout

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

@@ -374,8 +382,8 @@

ca-cert-password-flags

Flags indicating how to handle the "ca-cert-password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -408,8 +416,8 @@

client-cert-password-flags

Flags indicating how to handle the "client-cert-password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -474,8 +482,8 @@

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -492,8 +500,8 @@

password-raw-flags

Flags indicating how to handle the "password-raw" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -574,8 +582,8 @@

phase2-ca-cert-password-flags

Flags indicating how to handle the "phase2-ca-cert-password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -608,8 +616,8 @@

phase2-client-cert-password-flags

Flags indicating how to handle the "phase2-client-cert-password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -650,8 +658,8 @@

phase2-private-key-password-flags

Flags indicating how to handle the "phase2-private-key-password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -676,8 +684,8 @@

pin-flags

Flags indicating how to handle the "pin" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -702,8 +710,8 @@

private-key-password-flags

Flags indicating how to handle the "private-key-password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -764,8 +772,8 @@

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -1214,8 +1222,8 @@

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -1257,7 +1265,7 @@

app-fcoe-mode

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

Format: string

@@ -1818,8 +1826,8 @@

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -1836,8 +1844,8 @@

pin-flags

Flags indicating how to handle the "pin" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -2550,8 +2558,8 @@

mka-cak-flags

Flags indicating how to handle the "mka-cak" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -3148,8 +3156,8 @@

password-flags

Flags indicating how to handle the "password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -3345,17 +3353,424 @@

qdiscs

- Format: array of vardict

+Array of TC queueing disciplines. qdisc is a basic block in the +Linux traffic control subsystem +

+Each qdisc can be specified by the following attributes: +

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

+`handle HANDLE` +	+specifies the qdisc handle. A qdisc, which potentially can have children, gets +assigned a major number, called a 'handle', leaving the minor number namespace +available for classes. The handle is expressed as '10:'. It is customary to +explicitly assign a handle to qdiscs expected to have children. +
+`parent HANDLE` +	+specifies the handle of the parent qdisc the current qdisc must be +attached to. +
+`root` +	+specifies that the qdisc is attached to the root of device. +
+`KIND` +	+this is the qdisc kind. NetworkManager currently supports the +following kinds: fq_codel, sfq, tbf. Each qdisc kind has a +different set of parameters, described below. There are also some +kinds like pfifo, pfifo_fast, prio supported by NetworkManager +but their parameters are not supported by NetworkManager. +

+Parameters for 'fq_codel': +

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

+`limit U32` +	+the hard limit on the real queue size. When this limit is +reached, incoming packets are dropped. Default is 10240 packets. +
+`memory_limit U32` +	+sets a limit on the total number of bytes that can be queued in +this FQ-CoDel instance. The lower of the packet limit of the +limit parameter and the memory limit will be enforced. Default is +32 MB. +
+`flows U32` +	+the number of flows into which the incoming packets are +classified. Due to the stochastic nature of hashing, multiple +flows may end up being hashed into the same slot. Newer flows +have priority over older ones. This parameter can be set only at +load time since memory has to be allocated for the hash table. +Default value is 1024. +
+`target U32` +	+the acceptable minimum standing/persistent queue delay. This minimum +delay is identified by tracking the local minimum queue delay that packets +experience. The unit of measurement is microsecond(us). Default value is 5ms. +
+`interval U32` +	+used to ensure that the measured minimum delay does not become too stale. +The minimum delay must be experienced in the last epoch of length .B +interval. It should be set on the order of the worst-case RTT +through the bottleneck to give endpoints sufficient time to +react. Default value is 100ms. +
+`quantum U32` +	+the number of bytes used as 'deficit' in the fair queuing +algorithm. Default is set to 1514 bytes which corresponds to the +Ethernet MTU plus the hardware header length of 14 bytes. +
+`ecn BOOL` +	+can be used to mark packets instead of dropping them. ecn is turned +on by default. +
+`ce_threshold U32` +	+sets a threshold above which all packets are marked with ECN +Congestion Experienced. This is useful for DCTCP-style congestion +control algorithms that require marking at very shallow queueing +thresholds. +

+Parameters for 'sfq': +

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

+`divisor U32` +	+can be used to set a different hash table size, available +from kernel 2.6.39 onwards. The specified divisor must be +a power of two and cannot be larger than 65536. Default +value: 1024. +
+`limit U32` +	+Upper limit of the SFQ. Can be used to reduce the default +length of 127 packets. +
+`depth U32` +	+Limit of packets per flow. Default to +127 and can be lowered. +
+`perturb_period U32` +	+Interval in seconds for queue algorithm perturbation. +Defaults to 0, which means that no perturbation occurs. Do +not set too low for each perturbation may cause some +packet reordering or losses. Advised value: 60 This value +has no effect when external flow classification is used. +Its better to increase divisor value to lower risk of hash +collisions. +
+`quantum U32` +	+Amount of bytes a flow is allowed to dequeue during a +round of the round robin process. Defaults to the MTU of +the interface which is also the advised value and the +minimum value. +
+`flows U32` +	+Default value is 127. +

+Parameters for 'tbf': +

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

+`rate U64` +	+Bandwidth or rate. These parameters accept a floating +point number, possibly followed by either a unit (both SI +and IEC units supported), or a float followed by a percent +character to specify the rate as a percentage of the +device's speed. +
+`burst U32` +	+ +Also known as buffer or maxburst. Size of the bucket, in +bytes. This is the maximum amount of bytes that tokens can +be available for instantaneously. In general, larger +shaping rates require a larger buffer. For 10mbit/s on +Intel, you need at least 10kbyte buffer if you want to +reach your configured rate! + + +If your buffer is too small, packets may be dropped +because more tokens arrive per timer tick than fit in your +bucket. The minimum buffer size can be calculated by +dividing the rate by HZ. + + +Token usage calculations are performed using a table which +by default has a resolution of 8 packets. This resolution +can be changed by specifying the cell size with the burst. +For example, to specify a 6000 byte buffer with a 16 byte +cell size, set a burst of 6000/16. You will probably never +have to set this. Must be an integral power of 2. + +
+`limit U32` +	+Limit is the number of bytes that can be queued waiting +for tokens to become available. +
+`latency U32` +	+specifies the maximum amount of time a packet can +sit in the TBF. The latency calculation takes into account +the size of the bucket, the rate and possibly the peakrate +(if set). The latency and limit are mutually exclusive. +

+ Format: GPtrArray(NMTCQdisc)

tfilters

- Format: array of vardict

+Array of TC traffic filters. Traffic control can manage the packet content during +classification by using filters. +

+Each tfilters can be specified by the following attributes: +

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

+`handle HANDLE` +	+specifies the tfilters handle. A filter is used by a classful qdisc to determine in which class +a packet will be enqueued. It is important to notice that filters reside within qdiscs. Therefore, +see qdiscs handle for detailed information. +
+`parent HANDLE` +	+specifies the handle of the parent qdisc the current qdisc must be +attached to. +
+`root` +	+specifies that the qdisc is attached to the root of device. +
+`KIND` +	+this is the tfilters kind. NetworkManager currently supports +following kinds: mirred, simple. Each filter kind has a +different set of actions, described below. There are also some +other kinds like matchall, basic, u32 supported by NetworkManager. +

+Actions for 'mirred': +

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

+`egress bool` +	+Define whether the packet should exit from the interface. +
+`ingress bool` +	+Define whether the packet should come into the interface. +
+`mirror bool` +	+Define whether the packet should be copied to the destination space. +
+`redirect bool` +	+Define whether the packet should be moved to the destination space. +

+Action for 'simple': +

++++ + + + + +

+sdata char[32] +

+The actual string to print. +

+ Format: GPtrArray(NMTCTfilter)

@@ -4155,7 +4570,7 @@

s390-options

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

Format: dict of string to string

@@ -4268,8 +4683,8 @@

private-key-flags

Flags indicating how to handle the "private-key" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -4508,8 +4923,8 @@

leap-password-flags

Flags indicating how to handle the "leap-password" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -4558,8 +4973,8 @@

psk-flags

Flags indicating how to handle the "psk" property. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -4568,8 +4983,8 @@

wep-key-flags

Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties. - See the section called “Secret flag types:” for flag values. -

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

Format: NMSettingSecretFlags (uint32)

@@ -4701,7 +5116,31 @@

hostname setting

bond-port setting

Bond Port Settings.

+ Properties: +

++++ + + + + +

queue-id

+ Alias: queue-id

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

+ Format: uint32

hostname setting

Hostname settings.

Properties: @@ -4749,7 +5188,7 @@

veth setting

Veth Settings.

Properties: -- cgit 1.3.0-6-gf8a5