From 2965dc70bb3cbfa8de2f279761812b84b87600cb Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Sun, 18 Dec 2022 21:31:39 +0100 Subject: New upstream version 1.40.8 --- man/nm-settings-docs-nmcli.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'man/nm-settings-docs-nmcli.xml') diff --git a/man/nm-settings-docs-nmcli.xml b/man/nm-settings-docs-nmcli.xml index d2b7781c..7323d72b 100644 --- a/man/nm-settings-docs-nmcli.xml +++ b/man/nm-settings-docs-nmcli.xml @@ -166,7 +166,7 @@ fixed priority. Example: priority 5 from 1:2:3::5/128 table 45 -A comma separated list of routing rules for policy routing. Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode. How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. Tunnel flags. Currently, the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20). They are valid only for IPv6 tunnels.Tunnel flags. Currently, the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20). They are valid only for IPv6 tunnels. The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels. The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used. The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address. The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2). If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments. The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used. If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface.If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface. Whether to enable Path MTU Discovery on this tunnel.Whether to enable Path MTU Discovery on this tunnel. The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address. The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets. The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value. Whether the transmitted traffic must be encrypted.Whether the transmitted traffic must be encrypted. The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement.The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Flags indicating how to handle the "mka-cak" property.Flags indicating how to handle the "mka-cak" property. The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement.The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained. If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property. The port component of the SCI (Secure Channel Identifier), between 1 and 65534.The port component of the SCI (Secure Channel Identifier), between 1 and 65534. Specifies whether the SCI (Secure Channel Identifier) is included in every packet.Specifies whether the SCI (Secure Channel Identifier) is included in every packet. Specifies the validation mode for incoming frames.Specifies the validation mode for incoming frames. The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device. If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property. Whether the interface should be put in promiscuous mode.Whether the interface should be put in promiscuous mode. Whether the interface should be a MACVTAP.Whether the interface should be a MACVTAP. A list of driver names to match. Each element is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.A list of driver names to match. Each element is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\' are used for optional and mandatory matches and inverting the pattern. A list of interface names to match. Each element is a shell wildcard pattern. An element can be prefixed with a pipe symbol (|) or an ampersand (&). The former means that the element is optional and the latter means that it is mandatory. If there are any optional elements, than the match evaluates to true if at least one of the optional element matches (logical OR). If there are any mandatory elements, then they all must match (logical AND). By default, an element is optional. This means that an element "foo" behaves the same as "|foo". An element can also be inverted with exclamation mark (!) between the pipe symbol (or the ampersand) and before the pattern. Note that "!foo" is a shortcut for the mandatory match "&!foo". Finally, a backslash can be used at the beginning of the element (after the optional special characters) to escape the start of the pattern. For example, "&\\!a" is an mandatory match for literally "!a".A list of interface names to match. Each element is a shell wildcard pattern. An element can be prefixed with a pipe symbol (|) or an ampersand (&). The former means that the element is optional and the latter means that it is mandatory. If there are any optional elements, than the match evaluates to true if at least one of the optional element matches (logical OR). If there are any mandatory elements, then they all must match (logical AND). By default, an element is optional. This means that an element "foo" behaves the same as "|foo". An element can also be inverted with exclamation mark (!) between the pipe symbol (or the ampersand) and before the pattern. Note that "!foo" is a shortcut for the mandatory match "&!foo". Finally, a backslash can be used at the beginning of the element (after the optional special characters) to escape the start of the pattern. For example, "&\!a" is an mandatory match for literally "!a". A list of kernel command line arguments to match. This may be used to check whether a specific kernel command line option is set (or unset, if prefixed with the exclamation mark). The argument must either be a single word, or an assignment (i.e. two words, joined by "="). In the former case the kernel command line is searched for the word appearing as is, or as left hand side of an assignment. In the latter case, the exact assignment is looked for with right and left hand side matching. Wildcard patterns are not supported. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the match.A list of kernel command line arguments to match. This may be used to check whether a specific kernel command line option is set (or unset, if prefixed with the exclamation mark). The argument must either be a single word, or an assignment (i.e. two words, joined by "="). In the former case the kernel command line is searched for the word appearing as is, or as left hand side of an assignment. In the latter case, the exact assignment is looked for with right and left hand side matching. Wildcard patterns are not supported. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\' are used for optional and mandatory matches and inverting the match. A list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier. For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0". The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev"). Each element of the list is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.A list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier. For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0". The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev"). Each element of the list is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\' are used for optional and mandatory matches and inverting the pattern. Channel on which the mesh network to join is located.Channel on which the mesh network to join is located. Anycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request. This is currently only implemented by dhclient DHCP plugin.Anycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request. This is currently only implemented by dhclient DHCP plugin. SSID of the mesh network to join.SSID of the mesh network to join. The data path type. One of "system", "netdev" or empty.The data path type. One of "system", "netdev" or empty. The bridge failure mode. One of "secure", "standalone" or empty.The bridge failure mode. One of "secure", "standalone" or empty. Enable or disable multicast snooping.Enable or disable multicast snooping. Enable or disable RSTP.Enable or disable RSTP. Enable or disable STP.Enable or disable STP. Open vSwitch DPDK device arguments.Open vSwitch DPDK device arguments. Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue. The interface type. Either "internal", "system", "patch", "dpdk", or empty.The interface type. Either "internal", "system", "patch", "dpdk", or empty. Specifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer.Specifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer. The time port must be inactive in order to be considered down.The time port must be inactive in order to be considered down. Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp". The time port must be active before it starts forwarding traffic.The time port must be active before it starts forwarding traffic. LACP mode. One of "active", "off", or "passive".LACP mode. One of "active", "off", or "passive". The VLAN tag in the range 0-4095.The VLAN tag in the range 0-4095. The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk" or unset.The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk" or unset. If non-zero, instruct pppd to set the serial port to the specified baudrate. This value should normally be left as 0 to automatically choose the speed.If non-zero, instruct pppd to set the serial port to the specified baudrate. This value should normally be left as 0 to automatically choose the speed. If TRUE, specify that pppd should set the serial port to use hardware flow control with RTS and CTS signals. This value should normally be set to FALSE.If TRUE, specify that pppd should set the serial port to use hardware flow control with RTS and CTS signals. This value should normally be set to FALSE. If non-zero, instruct pppd to presume the connection to the peer has failed if the specified number of LCP echo-requests go unanswered by the peer. The "lcp-echo-interval" property must also be set to a non-zero value if this property is used.If non-zero, instruct pppd to presume the connection to the peer has failed if the specified number of LCP echo-requests go unanswered by the peer. The "lcp-echo-interval" property must also be set to a non-zero value if this property is used. If non-zero, instruct pppd to send an LCP echo-request frame to the peer every n seconds (where n is the specified value). Note that some PPP peers will respond to echo requests and some will not, and it is not possible to autodetect this.If non-zero, instruct pppd to send an LCP echo-request frame to the peer every n seconds (where n is the specified value). Note that some PPP peers will respond to echo requests and some will not, and it is not possible to autodetect this. If TRUE, stateful MPPE is used. See pppd documentation for more information on stateful MPPE.If TRUE, stateful MPPE is used. See pppd documentation for more information on stateful MPPE. If non-zero, instruct pppd to request that the peer send packets no larger than the specified size. If non-zero, the MRU should be between 128 and 16384.If non-zero, instruct pppd to request that the peer send packets no larger than the specified size. If non-zero, the MRU should be between 128 and 16384. If non-zero, instruct pppd to send packets no larger than the specified size.If non-zero, instruct pppd to send packets no larger than the specified size. If TRUE, Van Jacobsen TCP header compression will not be requested.If TRUE, Van Jacobsen TCP header compression will not be requested. If TRUE, do not require the other side (usually the PPP server) to authenticate itself to the client. If FALSE, require authentication from the remote side. In almost all cases, this should be TRUE.If TRUE, do not require the other side (usually the PPP server) to authenticate itself to the client. If FALSE, require authentication from the remote side. In almost all cases, this should be TRUE. If TRUE, BSD compression will not be requested.If TRUE, BSD compression will not be requested. If TRUE, "deflate" compression will not be requested.If TRUE, "deflate" compression will not be requested. If TRUE, the CHAP authentication method will not be used.If TRUE, the CHAP authentication method will not be used. If TRUE, the EAP authentication method will not be used.If TRUE, the EAP authentication method will not be used. If TRUE, the MSCHAP authentication method will not be used.If TRUE, the MSCHAP authentication method will not be used. If TRUE, the MSCHAPv2 authentication method will not be used.If TRUE, the MSCHAPv2 authentication method will not be used. If TRUE, the PAP authentication method will not be used.If TRUE, the PAP authentication method will not be used. If TRUE, MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session. If either 64-bit or 128-bit MPPE is not available the session will fail. Note that MPPE is not used on mobile broadband connections.If TRUE, MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session. If either 64-bit or 128-bit MPPE is not available the session will fail. Note that MPPE is not used on mobile broadband connections. If TRUE, 128-bit MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session, and the "require-mppe" property must also be set to TRUE. If 128-bit MPPE is not available the session will fail.If TRUE, 128-bit MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session, and the "require-mppe" property must also be set to TRUE. If 128-bit MPPE is not available the session will fail. If given, specifies the parent interface name on which this PPPoE connection should be created. If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection.If given, specifies the parent interface name on which this PPPoE connection should be created. If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection. Password used to authenticate with the PPPoE service.Password used to authenticate with the PPPoE service. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service. For most providers, this should be left blank. It is only required if there are multiple access concentrators or a specific service is known to be required.If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service. For most providers, this should be left blank. It is only required if there are multiple access concentrators or a specific service is known to be required. Username used to authenticate with the PPPoE service.Username used to authenticate with the PPPoE service. Whether the proxy configuration is for browser only.Whether the proxy configuration is for browser only. Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0) PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.The 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. PAC URL for obtaining PAC file.PAC URL for obtaining PAC file. Speed to use for communication over the serial port. Note that this value usually has no effect for mobile broadband modems as they generally ignore speed settings and use the highest available speed.Speed to use for communication over the serial port. Note that this value usually has no effect for mobile broadband modems as they generally ignore speed settings and use the highest available speed. Byte-width of the serial communication. The 8 in "8n1" for example.Byte-width of the serial communication. The 8 in "8n1" for example. Parity setting of the serial port.Parity setting of the serial port. Time to delay between each byte sent to the modem, in microseconds.Time to delay between each byte sent to the modem, in microseconds. Number of stop bits for communication on the serial port. Either 1 or 2. The 1 in "8n1" for example.Number of stop bits for communication on the serial port. Either 1 or 2. The 1 in "8n1" for example. Whether to autoprobe virtual functions by a compatible driver. If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF. If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them. When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1).Whether to autoprobe virtual functions by a compatible driver. If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF. If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them. When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1). The total number of virtual functions to create. Note that when the sriov setting is present NetworkManager enforces the number of virtual functions on the interface (also when it is zero) during activation and resets it upon deactivation. To prevent any changes to SR-IOV parameters don't add a sriov setting to the connection.The total number of virtual functions to create. Note that when the sriov setting is present NetworkManager enforces the number of virtual functions on the interface (also when it is zero) during activation and resets it upon deactivation. To prevent any changes to SR-IOV parameters don't add a sriov setting to the connection. Array of virtual function descriptors. Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF. When represented as string a VF is in the form: "INDEX [ATTR=VALUE[ ATTR=VALUE]...]". for example: "2 mac=00:11:22:33:44:55 spoof-check=true". Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans. The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form "ID[.PRIORITY[.PROTO]]". PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.Array of virtual function descriptors. Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF. When represented as string a VF is in the form: "INDEX [ATTR=VALUE[ ATTR=VALUE]...]". for example: "2 mac=00:11:22:33:44:55 spoof-check=true". Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans. The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form "ID[.PRIORITY[.PROTO]]". PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad. +A comma separated list of routing rules for policy routing. Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode. How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. Tunnel flags. Currently, the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20). They are valid only for IPv6 tunnels.Tunnel flags. Currently, the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20). They are valid only for IPv6 tunnels. The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels. The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used. The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address. The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2). If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments. The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used. If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface.If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface. Whether to enable Path MTU Discovery on this tunnel.Whether to enable Path MTU Discovery on this tunnel. The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address. The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets. The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value. Whether the transmitted traffic must be encrypted.Whether the transmitted traffic must be encrypted. The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters. Flags indicating how to handle the "mka-cak" property.Flags indicating how to handle the "mka-cak" property. The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Must be a string of hexadecimal characters with a even length between 2 and 64.The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Must be a string of hexadecimal characters with a even length between 2 and 64. Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained. If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property. The port component of the SCI (Secure Channel Identifier), between 1 and 65534.The port component of the SCI (Secure Channel Identifier), between 1 and 65534. Specifies whether the SCI (Secure Channel Identifier) is included in every packet.Specifies whether the SCI (Secure Channel Identifier) is included in every packet. Specifies the validation mode for incoming frames.Specifies the validation mode for incoming frames. The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device. If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property. Whether the interface should be put in promiscuous mode.Whether the interface should be put in promiscuous mode. Whether the interface should be a MACVTAP.Whether the interface should be a MACVTAP. A list of driver names to match. Each element is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.A list of driver names to match. Each element is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\' are used for optional and mandatory matches and inverting the pattern. A list of interface names to match. Each element is a shell wildcard pattern. An element can be prefixed with a pipe symbol (|) or an ampersand (&). The former means that the element is optional and the latter means that it is mandatory. If there are any optional elements, than the match evaluates to true if at least one of the optional element matches (logical OR). If there are any mandatory elements, then they all must match (logical AND). By default, an element is optional. This means that an element "foo" behaves the same as "|foo". An element can also be inverted with exclamation mark (!) between the pipe symbol (or the ampersand) and before the pattern. Note that "!foo" is a shortcut for the mandatory match "&!foo". Finally, a backslash can be used at the beginning of the element (after the optional special characters) to escape the start of the pattern. For example, "&\\!a" is an mandatory match for literally "!a".A list of interface names to match. Each element is a shell wildcard pattern. An element can be prefixed with a pipe symbol (|) or an ampersand (&). The former means that the element is optional and the latter means that it is mandatory. If there are any optional elements, than the match evaluates to true if at least one of the optional element matches (logical OR). If there are any mandatory elements, then they all must match (logical AND). By default, an element is optional. This means that an element "foo" behaves the same as "|foo". An element can also be inverted with exclamation mark (!) between the pipe symbol (or the ampersand) and before the pattern. Note that "!foo" is a shortcut for the mandatory match "&!foo". Finally, a backslash can be used at the beginning of the element (after the optional special characters) to escape the start of the pattern. For example, "&\!a" is an mandatory match for literally "!a". A list of kernel command line arguments to match. This may be used to check whether a specific kernel command line option is set (or unset, if prefixed with the exclamation mark). The argument must either be a single word, or an assignment (i.e. two words, joined by "="). In the former case the kernel command line is searched for the word appearing as is, or as left hand side of an assignment. In the latter case, the exact assignment is looked for with right and left hand side matching. Wildcard patterns are not supported. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the match.A list of kernel command line arguments to match. This may be used to check whether a specific kernel command line option is set (or unset, if prefixed with the exclamation mark). The argument must either be a single word, or an assignment (i.e. two words, joined by "="). In the former case the kernel command line is searched for the word appearing as is, or as left hand side of an assignment. In the latter case, the exact assignment is looked for with right and left hand side matching. Wildcard patterns are not supported. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\' are used for optional and mandatory matches and inverting the match. A list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier. For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0". The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev"). Each element of the list is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.A list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier. For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0". The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev"). Each element of the list is a shell wildcard pattern. See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\' are used for optional and mandatory matches and inverting the pattern. Channel on which the mesh network to join is located.Channel on which the mesh network to join is located. Anycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request. This is currently only implemented by dhclient DHCP plugin.Anycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request. This is currently only implemented by dhclient DHCP plugin. SSID of the mesh network to join.SSID of the mesh network to join. The data path type. One of "system", "netdev" or empty.The data path type. One of "system", "netdev" or empty. The bridge failure mode. One of "secure", "standalone" or empty.The bridge failure mode. One of "secure", "standalone" or empty. Enable or disable multicast snooping.Enable or disable multicast snooping. Enable or disable RSTP.Enable or disable RSTP. Enable or disable STP.Enable or disable STP. Open vSwitch DPDK device arguments.Open vSwitch DPDK device arguments. Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue. The interface type. Either "internal", "system", "patch", "dpdk", or empty.The interface type. Either "internal", "system", "patch", "dpdk", or empty. Specifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer.Specifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer. The time port must be inactive in order to be considered down.The time port must be inactive in order to be considered down. Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp". The time port must be active before it starts forwarding traffic.The time port must be active before it starts forwarding traffic. LACP mode. One of "active", "off", or "passive".LACP mode. One of "active", "off", or "passive". The VLAN tag in the range 0-4095.The VLAN tag in the range 0-4095. The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk" or unset.The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk" or unset. If non-zero, instruct pppd to set the serial port to the specified baudrate. This value should normally be left as 0 to automatically choose the speed.If non-zero, instruct pppd to set the serial port to the specified baudrate. This value should normally be left as 0 to automatically choose the speed. If TRUE, specify that pppd should set the serial port to use hardware flow control with RTS and CTS signals. This value should normally be set to FALSE.If TRUE, specify that pppd should set the serial port to use hardware flow control with RTS and CTS signals. This value should normally be set to FALSE. If non-zero, instruct pppd to presume the connection to the peer has failed if the specified number of LCP echo-requests go unanswered by the peer. The "lcp-echo-interval" property must also be set to a non-zero value if this property is used.If non-zero, instruct pppd to presume the connection to the peer has failed if the specified number of LCP echo-requests go unanswered by the peer. The "lcp-echo-interval" property must also be set to a non-zero value if this property is used. If non-zero, instruct pppd to send an LCP echo-request frame to the peer every n seconds (where n is the specified value). Note that some PPP peers will respond to echo requests and some will not, and it is not possible to autodetect this.If non-zero, instruct pppd to send an LCP echo-request frame to the peer every n seconds (where n is the specified value). Note that some PPP peers will respond to echo requests and some will not, and it is not possible to autodetect this. If TRUE, stateful MPPE is used. See pppd documentation for more information on stateful MPPE.If TRUE, stateful MPPE is used. See pppd documentation for more information on stateful MPPE. If non-zero, instruct pppd to request that the peer send packets no larger than the specified size. If non-zero, the MRU should be between 128 and 16384.If non-zero, instruct pppd to request that the peer send packets no larger than the specified size. If non-zero, the MRU should be between 128 and 16384. If non-zero, instruct pppd to send packets no larger than the specified size.If non-zero, instruct pppd to send packets no larger than the specified size. If TRUE, Van Jacobsen TCP header compression will not be requested.If TRUE, Van Jacobsen TCP header compression will not be requested. If TRUE, do not require the other side (usually the PPP server) to authenticate itself to the client. If FALSE, require authentication from the remote side. In almost all cases, this should be TRUE.If TRUE, do not require the other side (usually the PPP server) to authenticate itself to the client. If FALSE, require authentication from the remote side. In almost all cases, this should be TRUE. If TRUE, BSD compression will not be requested.If TRUE, BSD compression will not be requested. If TRUE, "deflate" compression will not be requested.If TRUE, "deflate" compression will not be requested. If TRUE, the CHAP authentication method will not be used.If TRUE, the CHAP authentication method will not be used. If TRUE, the EAP authentication method will not be used.If TRUE, the EAP authentication method will not be used. If TRUE, the MSCHAP authentication method will not be used.If TRUE, the MSCHAP authentication method will not be used. If TRUE, the MSCHAPv2 authentication method will not be used.If TRUE, the MSCHAPv2 authentication method will not be used. If TRUE, the PAP authentication method will not be used.If TRUE, the PAP authentication method will not be used. If TRUE, MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session. If either 64-bit or 128-bit MPPE is not available the session will fail. Note that MPPE is not used on mobile broadband connections.If TRUE, MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session. If either 64-bit or 128-bit MPPE is not available the session will fail. Note that MPPE is not used on mobile broadband connections. If TRUE, 128-bit MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session, and the "require-mppe" property must also be set to TRUE. If 128-bit MPPE is not available the session will fail.If TRUE, 128-bit MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session, and the "require-mppe" property must also be set to TRUE. If 128-bit MPPE is not available the session will fail. If given, specifies the parent interface name on which this PPPoE connection should be created. If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection.If given, specifies the parent interface name on which this PPPoE connection should be created. If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection. Password used to authenticate with the PPPoE service.Password used to authenticate with the PPPoE service. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service. For most providers, this should be left blank. It is only required if there are multiple access concentrators or a specific service is known to be required.If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service. For most providers, this should be left blank. It is only required if there are multiple access concentrators or a specific service is known to be required. Username used to authenticate with the PPPoE service.Username used to authenticate with the PPPoE service. Whether the proxy configuration is for browser only.Whether the proxy configuration is for browser only. Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0) PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.The 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. PAC URL for obtaining PAC file.PAC URL for obtaining PAC file. Speed to use for communication over the serial port. Note that this value usually has no effect for mobile broadband modems as they generally ignore speed settings and use the highest available speed.Speed to use for communication over the serial port. Note that this value usually has no effect for mobile broadband modems as they generally ignore speed settings and use the highest available speed. Byte-width of the serial communication. The 8 in "8n1" for example.Byte-width of the serial communication. The 8 in "8n1" for example. Parity setting of the serial port.Parity setting of the serial port. Time to delay between each byte sent to the modem, in microseconds.Time to delay between each byte sent to the modem, in microseconds. Number of stop bits for communication on the serial port. Either 1 or 2. The 1 in "8n1" for example.Number of stop bits for communication on the serial port. Either 1 or 2. The 1 in "8n1" for example. Whether to autoprobe virtual functions by a compatible driver. If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF. If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them. When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1).Whether to autoprobe virtual functions by a compatible driver. If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF. If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them. When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1). The total number of virtual functions to create. Note that when the sriov setting is present NetworkManager enforces the number of virtual functions on the interface (also when it is zero) during activation and resets it upon deactivation. To prevent any changes to SR-IOV parameters don't add a sriov setting to the connection.The total number of virtual functions to create. Note that when the sriov setting is present NetworkManager enforces the number of virtual functions on the interface (also when it is zero) during activation and resets it upon deactivation. To prevent any changes to SR-IOV parameters don't add a sriov setting to the connection. Array of virtual function descriptors. Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF. When represented as string a VF is in the form: "INDEX [ATTR=VALUE[ ATTR=VALUE]...]". for example: "2 mac=00:11:22:33:44:55 spoof-check=true". Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans. The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form "ID[.PRIORITY[.PROTO]]". PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.Array of virtual function descriptors. Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF. When represented as string a VF is in the form: "INDEX [ATTR=VALUE[ ATTR=VALUE]...]". for example: "2 mac=00:11:22:33:44:55 spoof-check=true". Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans. The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form "ID[.PRIORITY[.PROTO]]". PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad. Array of TC queueing disciplines. qdisc is a basic block in the Linux traffic control subsystem -- cgit 1.3.0-6-gf8a5