diff options
| author | Michael Biebl <biebl@debian.org> | 2023-03-09 20:01:53 +0100 |
|---|---|---|
| committer | Michael Biebl <biebl@debian.org> | 2023-03-09 20:01:53 +0100 |
| commit | cffb548b401e2cd3fad166aa92e0f634bbb1d4d6 (patch) | |
| tree | 6d803d8f7d0d92a1c5e5705974fff8975472af95 /docs/api/html | |
| parent | 647d6b95d5475e0a1bf3d6f299d1cb8c9041a7a4 (diff) | |
| parent | 12e1ee797bbf0b10d1fd5afd4b947484769f2b9f (diff) | |
Merge tag 'debian/1.42.4-1' into debian/bullseye-backports
network-manager Debian release 1.42.4-1
Diffstat (limited to 'docs/api/html')
96 files changed, 3994 insertions, 3122 deletions
diff --git a/docs/api/html/NetworkManager-dispatcher.html b/docs/api/html/NetworkManager-dispatcher.html index 6c899110..88ed3634 100644 --- a/docs/api/html/NetworkManager-dispatcher.html +++ b/docs/api/html/NetworkManager-dispatcher.html @@ -152,6 +152,12 @@ The network connectivity state has changed (no connectivity, went online, etc). </p></td> </tr> +<tr> +<td><p><span class="term"><code class="varname">reapply</code></span></p></td> +<td><p> + The connection was reapplied on the device. + </p></td> +</tr> </tbody> </table></div> <p> diff --git a/docs/api/html/NetworkManager-wait-online.service.html b/docs/api/html/NetworkManager-wait-online.service.html index 76b703a0..71b80e38 100644 --- a/docs/api/html/NetworkManager-wait-online.service.html +++ b/docs/api/html/NetworkManager-wait-online.service.html @@ -24,132 +24,102 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2><span class="refentrytitle">NetworkManager-wait-online.service</span></h2> -<p>NetworkManager-wait-online.service — Wait for network to come online</p> +<p>NetworkManager-wait-online.service — Wait for the network to come online</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> <a name="id-1.2.5.4"></a><h2>Description</h2> <p> - NetworkManager-wait-online.service delays network-online.target until network - is ready. + The <code class="literal">NetworkManager-wait-online</code> service is a <code class="literal">oneshot</code> + systemd service that delays reaching the <code class="literal">network-online</code> target until + NetworkManager reports that the startup is completed on the D-Bus. </p> <p> - The systemd target <code class="literal">network-online.target</code> acts as a synchronization point - for services to start after network is configured. Such services should - order themselves <code class="literal">After=network-online.target</code> - (and never <code class="literal">After=NetworkManager-wait-online.service</code>). - <code class="literal">NetworkManager-wait-online.service</code> is a one-shot service - that itself is ordered <code class="literal">Before=network-online.target</code> - and this way delays the target until the network is configured. + When the system boots, for example, remote mounts defined in <code class="literal">/etc/fstab</code>, + require that the network is up. For this, these systemd units contain the + <code class="literal">After=network-online.target</code> setting to order themselves after this + target. <code class="literal">NetworkManager-wait-online</code> ensures that the + <code class="literal">network-online</code> target is reached only after the network is available. </p> <p> - <code class="literal">NetworkManager-wait-online.service</code> itself is almost not configurable - itself. Instead the connection profiles and configuration in NetworkManager affects - the behavior. + Optimally, all services on the host react dynamically to network changes and systemd + services do not need to be configured to start after reaching the + <code class="literal">network-online</code> target. In this case, + <code class="literal">NetworkManager-wait-online.service</code> has no effect and does not delay + the boot time. On the other hand, if you encounter a long boot time due to the delay + of <code class="literal">NetworkManager-wait-online</code>, investigate the services that require + network access and fix them. </p> <p> - In the best case, all services on the system can react to networking changes dynamically and - no service orders itself after <code class="literal">network-online.target</code>. That way, - <code class="literal">NetworkManager-wait-online.service</code> has no effect and, for example, - does not delay the boot. That means, if the problem is a long boot time related to - <code class="literal">NetworkManager-wait-online.service</code>, a possible solution is to - investigate the services that claim to require network and fix those. + Except for the time out value in the <code class="literal">NetworkManager-wait-online.service</code> + unit, you cannot configure this service. Instead, settings in NetworkManager and the + connection profiles affect the behavior: </p> -<p> - For services that require network configured, - <code class="literal">NetworkManager-wait-online.service</code> is the default implementation - provided by NetworkManager to delay the target. But it does nothing magical. With - special requirements, it may be sensible to disable <code class="literal">NetworkManager-wait-online.service</code> - and replace it with a similar service that better implements the requirement. - </p> -<p> - <code class="literal">NetworkManager-wait-online.service</code> blocks until - NetworkManager logs "startup complete" and announces startup complete - on D-Bus. How long that takes depends on the network - and the NetworkManager configuration. If it takes longer than expected, then - the reasons need to be investigated in NetworkManager. - </p> -<p> - There are various reasons what affects NetworkManager reaching "startup complete" - and how long <code class="literal">NetworkManager-wait-online.service</code> blocks. - </p> <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <p> - In general, startup complete is not reached as long as NetworkManager is busy - activating a device and as long as there are profiles in activating state. - During boot, NetworkManager starts autoactivating - suitable profiles that are configured to autoconnect. If activation fails, - NetworkManager might retry right away (depending on <code class="literal">connection.autoconnect-retries</code> - setting). While trying and retrying, NetworkManager is busy until all - profiles and devices either reached an activated or disconnected state - and no further events are expected. - </p> + Startup is not complete as long as NetworkManager profiles are in an activating + state. During boot, NetworkManager starts profiles with the + <code class="literal">connection.autoconnect=yes</code> setting. If activation fails, + NetworkManager retries the activation depending on the value of the + <code class="literal">connection.autoconnect-retries</code> setting. + </p> <p> - </p> + NetworkManager reports startup complete when all profiles and devices are either + activated or in a disconnect state and no further events are expected. + </p> +</li> +<li class="listitem"> <p> - Basically, as long as there are devices and connections in <code class="literal">activating</code> - state visible with <span class="command"><strong>nmcli device</strong></span> and <span class="command"><strong>nmcli connection</strong></span>, - startup is still pending. - </p> + When a device reaches the activate state depends on its configuration. For example, + with a profile that has both IPv4 and IPv6 enabled, by default, NetworkManager + considers the device as fully activated already when only one of the address + families is ready. + </p> +<p> + The <code class="literal">ipv4.may-fail</code> and <code class="literal">ipv6.may-fail</code> settings + control this behavior. Additionally, the following settings influence when the + two address families complete: <code class="literal">ipv4.required-timeout</code>, + <code class="literal">ipv6.required-timeout</code>, <code class="literal">ipv4.dhcp-timeout</code>, + and <code class="literal">ipv6.ra-timeout</code>. For details, see + <a class="link" href="nm-settings-nmcli.html" title="nm-settings-nmcli"><span class="citerefentry"><span class="refentrytitle">nm-settings-nmcli</span>(5)</span></a>. + </p> </li> <li class="listitem"><p> - When a device reaches activated state, depends on its configuration. - For example, with a profile with both IPv4 and IPv6 addressing - enabled, the device is possibly considered fully activated when - either of the address families is ready. This can be controlled with the - <code class="literal">ipv4.may-fail</code> and <code class="literal">ipv6.may-fail</code> - settings, to indicate that the address family is required. - There are also <code class="literal">ipv4.required-timeout</code> and <code class="literal">ipv6.required-timeout</code> - settings which affect how long to wait for an address family. - Likewise, properties like <code class="literal">ipv4.dhcp-timeout</code> and - <code class="literal">ipv6.ra-timeout</code> affect how long NetworkManager - will try the IP configuration before giving up. - </p></li> -<li class="listitem"><p> - For example, a bridge or bond profile cannot do IP configuration - without ports. When booting with such profiles that autoactivate - without ports, <code class="literal">NetworkManager-wait-online.service</code> blocks until timeout. - This is a configuration error. - </p></li> + NetworkManager cannot set IP addresses on bridge and bond devices that have ports + that do not auto-activate. Because of this configuration error, + <code class="literal">NetworkManager-wait-online</code> blocks until the service reaches + its timeout value. + </p></li> <li class="listitem"><p> - Dispatcher scripts for the "pre-up" event run at a late stage during activation - of a profile. These scripts block the activation for when NetworkManager considers - the profile fully activated. - See also <a class="link" href="NetworkManager-dispatcher.html" title="NetworkManager-dispatcher"><span class="citerefentry"><span class="refentrytitle">NetworkManager-dispatcher</span>(8)</span></a> - for details. - </p></li> + Dispatcher scripts for the <code class="literal">pre-up</code> event run at a late stage + during activation of a profile. These scripts block the activation for when + NetworkManager considers the profile fully activated. For details, see + <a class="link" href="NetworkManager-dispatcher.html" title="NetworkManager-dispatcher"><span class="citerefentry"><span class="refentrytitle">NetworkManager-dispatcher</span>(8)</span></a>. + </p></li> <li class="listitem"><p> - The connection property <code class="literal">connection.wait-activation-delay</code> also - adds an additional delay during activation and delays startup complete. This is to - workaround certain cases where a device is known to not be ready for a certain - amount of time. - </p></li> + The property <code class="literal">connection.wait-activation-delay</code> adds an additional + delay during activation and delays startup complete. This setting works around + certain cases where a device is known to not be ready for a certain amount of time. + </p></li> <li class="listitem"><p> - The property <code class="literal">connection.wait-device-timeout</code> of the connection - profiles waits until the waited devices appear. This is useful if the driver - takes a longer time to detect the networking interfaces. Similar with the - <code class="literal">connection.gateway-ping-timeout</code> property. - </p></li> + The property <code class="literal">connection.wait-device-timeout</code> in the connection + profiles cause a delay until the waiting devices appear. This is useful if the + driver takes a longer time to detect the networking interfaces. This setting is + similar to the <code class="literal">connection.gateway-ping-timeout</code> property. + </p></li> <li class="listitem"><p> - With Wi-Fi devices, NetworkManager needs to wait for the first scan - result to know which networks might be available. That always adds a delay. - </p></li> + With Wi-Fi devices, NetworkManager needs to wait for the first scan result to + know which networks are available. That adds a delay. + </p></li> <li class="listitem"><p> - With ethernet devices, NetworkManager waits for carrier until the - configurable <code class="literal">[device*].carrier-timeout</code> is reached. - This is because some devices take a long time to detect carrier - and it means to boot with cable unplugged, will unnecessarily delay - <code class="literal">NetworkManager-wait-online.service</code>. - </p></li> + With Ethernet devices, NetworkManager waits for the carrier until the value in + <code class="literal">[device*].carrier-wait-timeout</code> is reached. This is because some + devices take a long time to detect the carrier. Consequently, booting with cable + unplugged, unnecessarily delays <code class="literal">NetworkManager-wait-online.service</code>. + </p></li> </ul></div> -<p> - </p> -<p> - <code class="literal">NetworkManager-wait-online.service</code> internally uses - <code class="literal">nm-online</code>. - </p> </div> <div class="refsect1"> <a name="id-1.2.5.5"></a><h2>Bugs</h2> @@ -164,6 +134,7 @@ <a class="ulink" href="https://networkmanager.dev" target="_top">NetworkManager home page</a>, <a class="link" href="NetworkManager.html" title="NetworkManager"><span class="citerefentry"><span class="refentrytitle">NetworkManager</span>(8)</span></a>, <a class="link" href="nm-online.html" title="nm-online"><span class="citerefentry"><span class="refentrytitle">nm-online</span>(1)</span></a>, + the <code class="literal">network-online.target</code> description in <span class="citerefentry"><span class="refentrytitle">systemd.special</span>(7)</span> </p> </div> </div> diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index 34063973..30d5660a 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -975,6 +975,10 @@ ipv6.ip6-privacy=0 </p></td> </tr> <tr> +<td><p><span class="term"><code class="varname">loopback.mtu</code></span></p></td> +<td><p>If configured explicitly to 0, the MTU is not reconfigured during device activation unless it is required due to IPv6 constraints. If left unspecified, a DHCP/IPv6 SLAAC provided value is used or the MTU is left unspecified on activation.</p></td> +</tr> +<tr> <td><p><span class="term"><code class="varname">sriov.autoprobe-drivers</code></span></p></td> <td><p>If left unspecified, drivers are autoprobed when the SR-IOV VF gets created.</p></td> </tr> @@ -1428,8 +1432,8 @@ managed=1 <div class="refsect1"> <a name="id-1.2.3.14"></a><h2> <code class="literal">global-dns</code> section</h2> -<p>This section specifies global DNS settings that override - connection-specific configuration.</p> +<p>This section specifies DNS settings that are applied + globally, in addition to connection-specific ones.</p> <p> </p> <div class="variablelist"><table border="0" class="variablelist"> @@ -1461,10 +1465,15 @@ managed=1 <p>Sections with a name starting with the "global-dns-domain-" prefix allow to define global DNS configuration for specific domains. The part of section name after "global-dns-domain-" - specifies the domain name a section applies to. More specific - domains have the precedence over less specific ones and the - default domain is represented by the wildcard "*". A default - domain section is mandatory. + specifies the domain name a section applies to (for example, a + section could be named "global-dns-domain-foobar.com"). More + specific domains have the precedence over less specific ones and + the default domain is represented by the wildcard "*". + + To be valid, global DNS domains must include a section for the + default domain "*". When the global DNS domains are valid, the + name servers and domains defined globally override the ones from + active connections. </p> <p> </p> diff --git a/docs/api/html/NetworkManager.devhelp2 b/docs/api/html/NetworkManager.devhelp2 index 52186b6b..33b73bdf 100644 --- a/docs/api/html/NetworkManager.devhelp2 +++ b/docs/api/html/NetworkManager.devhelp2 @@ -70,7 +70,9 @@ <sub name="" link="settings-wpan.html"/> <sub name="" link="settings-bond-port.html"/> <sub name="" link="settings-hostname.html"/> + <sub name="" link="settings-loopback.html"/> <sub name="" link="settings-ovs-external-ids.html"/> + <sub name="" link="settings-ovs-other-config.html"/> <sub name="" link="settings-veth.html"/> </sub> <sub name="Secret flag types" link="secrets-flags.html"/> @@ -102,6 +104,7 @@ <sub name="org.freedesktop.NetworkManager.Device.Generic" link="gdbus-org.freedesktop.NetworkManager.Device.Generic.html"/> <sub name="org.freedesktop.NetworkManager.Device.IPTunnel" link="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html"/> <sub name="org.freedesktop.NetworkManager.Device.Infiniband" link="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html"/> + <sub name="org.freedesktop.NetworkManager.Device.Loopback" link="gdbus-org.freedesktop.NetworkManager.Device.Loopback.html"/> <sub name="org.freedesktop.NetworkManager.Device.Lowpan" link="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html"/> <sub name="org.freedesktop.NetworkManager.Device.Macsec" link="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html"/> <sub name="org.freedesktop.NetworkManager.Device.Macvlan" link="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html"/> @@ -211,6 +214,7 @@ <keyword type="property" name="The "ActivatingConnection" property" link="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.ActivatingConnection"/> <keyword type="property" name="The "Startup" property" link="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Startup"/> <keyword type="property" name="The "Version" property" link="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Version"/> + <keyword type="property" name="The "VersionInfo" property" link="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.VersionInfo"/> <keyword type="property" name="The "Capabilities" property" link="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Capabilities"/> <keyword type="property" name="The "State" property" link="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.State"/> <keyword type="property" name="The "Connectivity" property" link="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Connectivity"/> @@ -314,6 +318,7 @@ <keyword type="property" name="The "OutputKey" property" link="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.OutputKey"/> <keyword type="property" name="The "EncapsulationLimit" property" link="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.EncapsulationLimit"/> <keyword type="property" name="The "FlowLabel" property" link="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.FlowLabel"/> + <keyword type="property" name="The "FwMark" property" link="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.FwMark"/> <keyword type="property" name="The "Flags" property" link="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.Flags"/> <keyword type="property" name="The "HwAddress" property" link="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html#gdbus-property-org-freedesktop-NetworkManager-Device-Infiniband.HwAddress"/> <keyword type="property" name="The "Carrier" property" link="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html#gdbus-property-org-freedesktop-NetworkManager-Device-Infiniband.Carrier"/> @@ -429,6 +434,7 @@ <keyword type="property" name="The "Ip6Config" property" link="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Ip6Config"/> <keyword type="property" name="The "Dhcp6Config" property" link="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Dhcp6Config"/> <keyword type="property" name="The "Vpn" property" link="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Vpn"/> + <keyword type="property" name="The "Controller" property" link="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Controller"/> <keyword type="property" name="The "Master" property" link="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Master"/> <keyword type="signal" name="The "VpnStateChanged" signal" link="gdbus-org.freedesktop.NetworkManager.VPN.Connection.html#gdbus-signal-org-freedesktop-NetworkManager-VPN-Connection.VpnStateChanged"/> <keyword type="property" name="The "VpnState" property" link="gdbus-org.freedesktop.NetworkManager.VPN.Connection.html#gdbus-property-org-freedesktop-NetworkManager-VPN-Connection.VpnState"/> @@ -481,6 +487,7 @@ <keyword type="property" name="The "Devices" property" link="gdbus-org.freedesktop.NetworkManager.Checkpoint.html#gdbus-property-org-freedesktop-NetworkManager-Checkpoint.Devices"/> <keyword type="property" name="The "Created" property" link="gdbus-org.freedesktop.NetworkManager.Checkpoint.html#gdbus-property-org-freedesktop-NetworkManager-Checkpoint.Created"/> <keyword type="property" name="The "RollbackTimeout" property" link="gdbus-org.freedesktop.NetworkManager.Checkpoint.html#gdbus-property-org-freedesktop-NetworkManager-Checkpoint.RollbackTimeout"/> + <keyword type="enum" name="enum NMVersionInfoCapability" link="nm-dbus-types.html#NMVersionInfoCapability"/> <keyword type="enum" name="enum NMCapability" link="nm-dbus-types.html#NMCapability"/> <keyword type="enum" name="enum NMState" link="nm-dbus-types.html#NMState"/> <keyword type="enum" name="enum NMConnectivityState" link="nm-dbus-types.html#NMConnectivityState"/> @@ -541,327 +548,328 @@ <keyword type="enum" name="enum NMVpnConnectionState" link="nm-vpn-dbus-types.html#NMVpnConnectionState"/> <keyword type="enum" name="enum NMVpnConnectionStateReason" link="nm-vpn-dbus-types.html#NMVpnConnectionStateReason"/> <keyword type="enum" name="enum NMVpnPluginFailure" link="nm-vpn-dbus-types.html#NMVpnPluginFailure"/> - <keyword type="constant" name="NM_CAPABILITY_TEAM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.3.4.2.1.4.1.1.1id-1.4.17.2.3.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_CAPABILITY_OVS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.3.4.2.1.4.2.1.1id-1.4.17.2.3.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_STATE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.1.1.1id-1.4.17.2.4.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_STATE_ASLEEP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.2.1.1id-1.4.17.2.4.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_STATE_DISCONNECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.3.1.1id-1.4.17.2.4.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_STATE_DISCONNECTING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.4.1.1id-1.4.17.2.4.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_STATE_CONNECTING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.5.1.1id-1.4.17.2.4.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_STATE_CONNECTED_LOCAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.6.1.1id-1.4.17.2.4.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_STATE_CONNECTED_SITE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.7.1.1id-1.4.17.2.4.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_STATE_CONNECTED_GLOBAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.8.1.1id-1.4.17.2.4.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_CONNECTIVITY_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.1.1.1id-1.4.17.2.5.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_CONNECTIVITY_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.2.1.1id-1.4.17.2.5.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_CONNECTIVITY_PORTAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.3.1.1id-1.4.17.2.5.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_CONNECTIVITY_LIMITED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.4.1.1id-1.4.17.2.5.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_CONNECTIVITY_FULL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.5.1.1id-1.4.17.2.5.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.1.1.1id-1.4.17.2.6.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_GENERIC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.2.1.1id-1.4.17.2.6.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_ETHERNET" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.3.1.1id-1.4.17.2.6.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_WIFI" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.4.1.1id-1.4.17.2.6.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_UNUSED1" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.5.1.1id-1.4.17.2.6.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_UNUSED2" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.6.1.1id-1.4.17.2.6.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_BT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.7.1.1id-1.4.17.2.6.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_OLPC_MESH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.8.1.1id-1.4.17.2.6.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_WIMAX" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.9.1.1id-1.4.17.2.6.4.2.1.4.9.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_MODEM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.10.1.1id-1.4.17.2.6.4.2.1.4.10.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_INFINIBAND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.11.1.1id-1.4.17.2.6.4.2.1.4.11.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_BOND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.12.1.1id-1.4.17.2.6.4.2.1.4.12.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_VLAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.13.1.1id-1.4.17.2.6.4.2.1.4.13.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_ADSL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.14.1.1id-1.4.17.2.6.4.2.1.4.14.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_BRIDGE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.15.1.1id-1.4.17.2.6.4.2.1.4.15.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_TEAM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.16.1.1id-1.4.17.2.6.4.2.1.4.16.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_TUN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.17.1.1id-1.4.17.2.6.4.2.1.4.17.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_IP_TUNNEL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.18.1.1id-1.4.17.2.6.4.2.1.4.18.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_MACVLAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.19.1.1id-1.4.17.2.6.4.2.1.4.19.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_VXLAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.20.1.1id-1.4.17.2.6.4.2.1.4.20.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_VETH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.21.1.1id-1.4.17.2.6.4.2.1.4.21.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_MACSEC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.22.1.1id-1.4.17.2.6.4.2.1.4.22.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_DUMMY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.23.1.1id-1.4.17.2.6.4.2.1.4.23.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_PPP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.24.1.1id-1.4.17.2.6.4.2.1.4.24.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_OVS_INTERFACE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.25.1.1id-1.4.17.2.6.4.2.1.4.25.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_OVS_PORT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.26.1.1id-1.4.17.2.6.4.2.1.4.26.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_OVS_BRIDGE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.27.1.1id-1.4.17.2.6.4.2.1.4.27.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_WPAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.28.1.1id-1.4.17.2.6.4.2.1.4.28.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_6LOWPAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.29.1.1id-1.4.17.2.6.4.2.1.4.29.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_WIREGUARD" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.30.1.1id-1.4.17.2.6.4.2.1.4.30.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_WIFI_P2P" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.31.1.1id-1.4.17.2.6.4.2.1.4.31.1.2"/> - <keyword type="constant" name="NM_DEVICE_TYPE_VRF" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.32.1.1id-1.4.17.2.6.4.2.1.4.32.1.2"/> - <keyword type="constant" name="NM_DEVICE_CAP_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.1.1.1id-1.4.17.2.7.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_DEVICE_CAP_NM_SUPPORTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.2.1.1id-1.4.17.2.7.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_DEVICE_CAP_CARRIER_DETECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.3.1.1id-1.4.17.2.7.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_DEVICE_CAP_IS_SOFTWARE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.4.1.1id-1.4.17.2.7.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_DEVICE_CAP_SRIOV" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.5.1.1id-1.4.17.2.7.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.1.1.1id-1.4.17.2.8.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_CIPHER_WEP40" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.2.1.1id-1.4.17.2.8.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_CIPHER_WEP104" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.3.1.1id-1.4.17.2.8.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_CIPHER_TKIP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.4.1.1id-1.4.17.2.8.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_CIPHER_CCMP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.5.1.1id-1.4.17.2.8.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_WPA" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.6.1.1id-1.4.17.2.8.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_RSN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.7.1.1id-1.4.17.2.8.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_AP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.8.1.1id-1.4.17.2.8.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_ADHOC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.9.1.1id-1.4.17.2.8.4.2.1.4.9.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_FREQ_VALID" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.10.1.1id-1.4.17.2.8.4.2.1.4.10.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_FREQ_2GHZ" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.11.1.1id-1.4.17.2.8.4.2.1.4.11.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_FREQ_5GHZ" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.12.1.1id-1.4.17.2.8.4.2.1.4.12.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_MESH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.13.1.1id-1.4.17.2.8.4.2.1.4.13.1.2"/> - <keyword type="constant" name="NM_WIFI_DEVICE_CAP_IBSS_RSN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.14.1.1id-1.4.17.2.8.4.2.1.4.14.1.2"/> - <keyword type="constant" name="NM_802_11_AP_FLAGS_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.1.1.1id-1.4.17.2.9.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_802_11_AP_FLAGS_PRIVACY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.2.1.1id-1.4.17.2.9.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_802_11_AP_FLAGS_WPS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.3.1.1id-1.4.17.2.9.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_802_11_AP_FLAGS_WPS_PBC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.4.1.1id-1.4.17.2.9.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_802_11_AP_FLAGS_WPS_PIN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.5.1.1id-1.4.17.2.9.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.1.1.1id-1.4.17.2.10.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_PAIR_WEP40" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.2.1.1id-1.4.17.2.10.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_PAIR_WEP104" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.3.1.1id-1.4.17.2.10.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_PAIR_TKIP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.4.1.1id-1.4.17.2.10.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_PAIR_CCMP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.5.1.1id-1.4.17.2.10.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_GROUP_WEP40" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.6.1.1id-1.4.17.2.10.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_GROUP_WEP104" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.7.1.1id-1.4.17.2.10.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_GROUP_TKIP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.8.1.1id-1.4.17.2.10.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_GROUP_CCMP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.9.1.1id-1.4.17.2.10.4.2.1.4.9.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_PSK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.10.1.1id-1.4.17.2.10.4.2.1.4.10.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_802_1X" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.11.1.1id-1.4.17.2.10.4.2.1.4.11.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_SAE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.12.1.1id-1.4.17.2.10.4.2.1.4.12.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_OWE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.13.1.1id-1.4.17.2.10.4.2.1.4.13.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_OWE_TM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.14.1.1id-1.4.17.2.10.4.2.1.4.14.1.2"/> - <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_EAP_SUITE_B_192" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.15.1.1id-1.4.17.2.10.4.2.1.4.15.1.2"/> - <keyword type="constant" name="NM_802_11_MODE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.1.1.1id-1.4.17.2.11.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_802_11_MODE_ADHOC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.2.1.1id-1.4.17.2.11.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_802_11_MODE_INFRA" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.3.1.1id-1.4.17.2.11.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_802_11_MODE_AP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.4.1.1id-1.4.17.2.11.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_802_11_MODE_MESH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.5.1.1id-1.4.17.2.11.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_BT_CAPABILITY_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.12.4.2.1.4.1.1.1id-1.4.17.2.12.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_BT_CAPABILITY_DUN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.12.4.2.1.4.2.1.1id-1.4.17.2.12.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_BT_CAPABILITY_NAP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.12.4.2.1.4.3.1.1id-1.4.17.2.12.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.13.4.2.1.4.1.1.1id-1.4.17.2.13.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_POTS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.13.4.2.1.4.2.1.1id-1.4.17.2.13.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_CDMA_EVDO" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.13.4.2.1.4.3.1.1id-1.4.17.2.13.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_GSM_UMTS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.13.4.2.1.4.4.1.1id-1.4.17.2.13.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_LTE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.13.4.2.1.4.5.1.1id-1.4.17.2.13.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_5GNR" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.13.4.2.1.4.6.1.1id-1.4.17.2.13.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_WIMAX_NSP_NETWORK_TYPE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.1.1.1id-1.4.17.2.14.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_WIMAX_NSP_NETWORK_TYPE_HOME" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.2.1.1id-1.4.17.2.14.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_WIMAX_NSP_NETWORK_TYPE_PARTNER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.3.1.1id-1.4.17.2.14.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_WIMAX_NSP_NETWORK_TYPE_ROAMING_PARTNER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.4.1.1id-1.4.17.2.14.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.1.1.1id-1.4.17.2.15.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_UNMANAGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.2.1.1id-1.4.17.2.15.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_UNAVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.3.1.1id-1.4.17.2.15.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_DISCONNECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.4.1.1id-1.4.17.2.15.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_PREPARE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.5.1.1id-1.4.17.2.15.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_CONFIG" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.6.1.1id-1.4.17.2.15.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_NEED_AUTH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.7.1.1id-1.4.17.2.15.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_IP_CONFIG" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.8.1.1id-1.4.17.2.15.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_IP_CHECK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.9.1.1id-1.4.17.2.15.4.2.1.4.9.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_SECONDARIES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.10.1.1id-1.4.17.2.15.4.2.1.4.10.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_ACTIVATED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.11.1.1id-1.4.17.2.15.4.2.1.4.11.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_DEACTIVATING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.12.1.1id-1.4.17.2.15.4.2.1.4.12.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.13.1.1id-1.4.17.2.15.4.2.1.4.13.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.1.1.1id-1.4.17.2.16.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.2.1.1id-1.4.17.2.16.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_NOW_MANAGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.3.1.1id-1.4.17.2.16.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_NOW_UNMANAGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.4.1.1id-1.4.17.2.16.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_CONFIG_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.5.1.1id-1.4.17.2.16.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_IP_CONFIG_UNAVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.6.1.1id-1.4.17.2.16.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_IP_CONFIG_EXPIRED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.7.1.1id-1.4.17.2.16.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_NO_SECRETS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.8.1.1id-1.4.17.2.16.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_DISCONNECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.9.1.1id-1.4.17.2.16.4.2.1.4.9.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_CONFIG_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.10.1.1id-1.4.17.2.16.4.2.1.4.10.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.11.1.1id-1.4.17.2.16.4.2.1.4.11.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.12.1.1id-1.4.17.2.16.4.2.1.4.12.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_PPP_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.13.1.1id-1.4.17.2.16.4.2.1.4.13.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_PPP_DISCONNECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.14.1.1id-1.4.17.2.16.4.2.1.4.14.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_PPP_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.15.1.1id-1.4.17.2.16.4.2.1.4.15.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_DHCP_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.16.1.1id-1.4.17.2.16.4.2.1.4.16.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_DHCP_ERROR" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.17.1.1id-1.4.17.2.16.4.2.1.4.17.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_DHCP_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.18.1.1id-1.4.17.2.16.4.2.1.4.18.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SHARED_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.19.1.1id-1.4.17.2.16.4.2.1.4.19.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SHARED_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.20.1.1id-1.4.17.2.16.4.2.1.4.20.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_AUTOIP_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.21.1.1id-1.4.17.2.16.4.2.1.4.21.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_AUTOIP_ERROR" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.22.1.1id-1.4.17.2.16.4.2.1.4.22.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_AUTOIP_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.23.1.1id-1.4.17.2.16.4.2.1.4.23.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_BUSY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.24.1.1id-1.4.17.2.16.4.2.1.4.24.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_NO_DIAL_TONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.25.1.1id-1.4.17.2.16.4.2.1.4.25.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_NO_CARRIER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.26.1.1id-1.4.17.2.16.4.2.1.4.26.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_DIAL_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.27.1.1id-1.4.17.2.16.4.2.1.4.27.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_DIAL_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.28.1.1id-1.4.17.2.16.4.2.1.4.28.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_INIT_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.29.1.1id-1.4.17.2.16.4.2.1.4.29.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_APN_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.30.1.1id-1.4.17.2.16.4.2.1.4.30.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_REGISTRATION_NOT_SEARCHING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.31.1.1id-1.4.17.2.16.4.2.1.4.31.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_REGISTRATION_DENIED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.32.1.1id-1.4.17.2.16.4.2.1.4.32.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_REGISTRATION_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.33.1.1id-1.4.17.2.16.4.2.1.4.33.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_REGISTRATION_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.34.1.1id-1.4.17.2.16.4.2.1.4.34.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_PIN_CHECK_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.35.1.1id-1.4.17.2.16.4.2.1.4.35.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_FIRMWARE_MISSING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.36.1.1id-1.4.17.2.16.4.2.1.4.36.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_REMOVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.37.1.1id-1.4.17.2.16.4.2.1.4.37.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SLEEPING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.38.1.1id-1.4.17.2.16.4.2.1.4.38.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_CONNECTION_REMOVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.39.1.1id-1.4.17.2.16.4.2.1.4.39.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_USER_REQUESTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.40.1.1id-1.4.17.2.16.4.2.1.4.40.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_CARRIER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.41.1.1id-1.4.17.2.16.4.2.1.4.41.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_CONNECTION_ASSUMED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.42.1.1id-1.4.17.2.16.4.2.1.4.42.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_AVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.43.1.1id-1.4.17.2.16.4.2.1.4.43.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_NOT_FOUND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.44.1.1id-1.4.17.2.16.4.2.1.4.44.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_BT_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.45.1.1id-1.4.17.2.16.4.2.1.4.45.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_SIM_NOT_INSERTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.46.1.1id-1.4.17.2.16.4.2.1.4.46.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_SIM_PIN_REQUIRED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.47.1.1id-1.4.17.2.16.4.2.1.4.47.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_SIM_PUK_REQUIRED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.48.1.1id-1.4.17.2.16.4.2.1.4.48.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_SIM_WRONG" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.49.1.1id-1.4.17.2.16.4.2.1.4.49.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_INFINIBAND_MODE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.50.1.1id-1.4.17.2.16.4.2.1.4.50.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_DEPENDENCY_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.51.1.1id-1.4.17.2.16.4.2.1.4.51.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_BR2684_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.52.1.1id-1.4.17.2.16.4.2.1.4.52.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_MANAGER_UNAVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.53.1.1id-1.4.17.2.16.4.2.1.4.53.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SSID_NOT_FOUND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.54.1.1id-1.4.17.2.16.4.2.1.4.54.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SECONDARY_CONNECTION_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.55.1.1id-1.4.17.2.16.4.2.1.4.55.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_DCB_FCOE_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.56.1.1id-1.4.17.2.16.4.2.1.4.56.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_TEAMD_CONTROL_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.57.1.1id-1.4.17.2.16.4.2.1.4.57.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.58.1.1id-1.4.17.2.16.4.2.1.4.58.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_AVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.59.1.1id-1.4.17.2.16.4.2.1.4.59.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SIM_PIN_INCORRECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.60.1.1id-1.4.17.2.16.4.2.1.4.60.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_NEW_ACTIVATION" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.61.1.1id-1.4.17.2.16.4.2.1.4.61.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_PARENT_CHANGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.62.1.1id-1.4.17.2.16.4.2.1.4.62.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_PARENT_MANAGED_CHANGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.63.1.1id-1.4.17.2.16.4.2.1.4.63.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_OVSDB_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.64.1.1id-1.4.17.2.16.4.2.1.4.64.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_IP_ADDRESS_DUPLICATE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.65.1.1id-1.4.17.2.16.4.2.1.4.65.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_IP_METHOD_UNSUPPORTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.66.1.1id-1.4.17.2.16.4.2.1.4.66.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_SRIOV_CONFIGURATION_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.67.1.1id-1.4.17.2.16.4.2.1.4.67.1.2"/> - <keyword type="constant" name="NM_DEVICE_STATE_REASON_PEER_NOT_FOUND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.68.1.1id-1.4.17.2.16.4.2.1.4.68.1.2"/> - <keyword type="constant" name="NM_METERED_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.1.1.1id-1.4.17.2.17.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_METERED_YES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.2.1.1id-1.4.17.2.17.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_METERED_NO" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.3.1.1id-1.4.17.2.17.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_METERED_GUESS_YES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.4.1.1id-1.4.17.2.17.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_METERED_GUESS_NO" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.5.1.1id-1.4.17.2.17.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_CONNECTION_MULTI_CONNECT_DEFAULT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.18.4.2.1.4.1.1.1id-1.4.17.2.18.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_CONNECTION_MULTI_CONNECT_SINGLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.18.4.2.1.4.2.1.1id-1.4.17.2.18.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_CONNECTION_MULTI_CONNECT_MANUAL_MULTIPLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.18.4.2.1.4.3.1.1id-1.4.17.2.18.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_CONNECTION_MULTI_CONNECT_MULTIPLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.18.4.2.1.4.4.1.1id-1.4.17.2.18.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.19.4.2.1.4.1.1.1id-1.4.17.2.19.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_ACTIVATING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.19.4.2.1.4.2.1.1id-1.4.17.2.19.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_ACTIVATED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.19.4.2.1.4.3.1.1id-1.4.17.2.19.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_DEACTIVATING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.19.4.2.1.4.4.1.1id-1.4.17.2.19.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_DEACTIVATED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.19.4.2.1.4.5.1.1id-1.4.17.2.19.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.1.1.1id-1.4.17.2.20.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.2.1.1id-1.4.17.2.20.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_USER_DISCONNECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.3.1.1id-1.4.17.2.20.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.4.1.1id-1.4.17.2.20.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_STOPPED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.5.1.1id-1.4.17.2.20.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_IP_CONFIG_INVALID" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.6.1.1id-1.4.17.2.20.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_CONNECT_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.7.1.1id-1.4.17.2.20.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_START_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.8.1.1id-1.4.17.2.20.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.9.1.1id-1.4.17.2.20.4.2.1.4.9.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_NO_SECRETS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.10.1.1id-1.4.17.2.20.4.2.1.4.10.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_LOGIN_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.11.1.1id-1.4.17.2.20.4.2.1.4.11.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_CONNECTION_REMOVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.12.1.1id-1.4.17.2.20.4.2.1.4.12.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_DEPENDENCY_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.13.1.1id-1.4.17.2.20.4.2.1.4.13.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_REALIZE_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.14.1.1id-1.4.17.2.20.4.2.1.4.14.1.2"/> - <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_REMOVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.15.1.1id-1.4.17.2.20.4.2.1.4.15.1.2"/> - <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.1.1.1id-1.4.17.2.21.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_ALLOW_INTERACTION" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.2.1.1id-1.4.17.2.21.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_REQUEST_NEW" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.3.1.1id-1.4.17.2.21.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_USER_REQUESTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.4.1.1id-1.4.17.2.21.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_WPS_PBC_ACTIVE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.5.1.1id-1.4.17.2.21.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_ONLY_SYSTEM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.6.1.1id-1.4.17.2.21.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_NO_ERRORS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.7.1.1id-1.4.17.2.21.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_SECRET_AGENT_CAPABILITY_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.22.4.2.1.4.1.1.1id-1.4.17.2.22.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_SECRET_AGENT_CAPABILITY_VPN_HINTS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.22.4.2.1.4.2.1.1id-1.4.17.2.22.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.1.1.1id-1.4.17.2.23.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_IPIP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.2.1.1id-1.4.17.2.23.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_GRE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.3.1.1id-1.4.17.2.23.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_SIT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.4.1.1id-1.4.17.2.23.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_ISATAP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.5.1.1id-1.4.17.2.23.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_VTI" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.6.1.1id-1.4.17.2.23.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_IP6IP6" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.7.1.1id-1.4.17.2.23.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_IPIP6" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.8.1.1id-1.4.17.2.23.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_IP6GRE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.9.1.1id-1.4.17.2.23.4.2.1.4.9.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_VTI6" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.10.1.1id-1.4.17.2.23.4.2.1.4.10.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_GRETAP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.11.1.1id-1.4.17.2.23.4.2.1.4.11.1.2"/> - <keyword type="constant" name="NM_IP_TUNNEL_MODE_IP6GRETAP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.12.1.1id-1.4.17.2.23.4.2.1.4.12.1.2"/> - <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.1.1.1id-1.4.17.2.24.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_DESTROY_ALL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.2.1.1id-1.4.17.2.24.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_DELETE_NEW_CONNECTIONS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.3.1.1id-1.4.17.2.24.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_DISCONNECT_NEW_DEVICES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.4.1.1id-1.4.17.2.24.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_ALLOW_OVERLAPPING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.5.1.1id-1.4.17.2.24.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_NO_PRESERVE_EXTERNAL_PORTS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.6.1.1id-1.4.17.2.24.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_ROLLBACK_RESULT_OK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.1.1.1id-1.4.17.2.25.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_ROLLBACK_RESULT_ERR_NO_DEVICE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.2.1.1id-1.4.17.2.25.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_ROLLBACK_RESULT_ERR_DEVICE_UNMANAGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.3.1.1id-1.4.17.2.25.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_ROLLBACK_RESULT_ERR_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.4.1.1id-1.4.17.2.25.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.26.4.2.1.4.1.1.1id-1.4.17.2.26.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_UNSAVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.26.4.2.1.4.2.1.1id-1.4.17.2.26.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_NM_GENERATED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.26.4.2.1.4.3.1.1id-1.4.17.2.26.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_VOLATILE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.26.4.2.1.4.4.1.1id-1.4.17.2.26.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_EXTERNAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.26.4.2.1.4.5.1.1id-1.4.17.2.26.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.1.1.1id-1.4.17.2.27.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_IS_MASTER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.2.1.1id-1.4.17.2.27.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_IS_SLAVE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.3.1.1id-1.4.17.2.27.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_LAYER2_READY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.4.1.1id-1.4.17.2.27.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_IP4_READY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.5.1.1id-1.4.17.2.27.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_IP6_READY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.6.1.1id-1.4.17.2.27.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_MASTER_HAS_SLAVES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.7.1.1id-1.4.17.2.27.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_LIFETIME_BOUND_TO_PROFILE_VISIBILITY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.8.1.1id-1.4.17.2.27.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_EXTERNAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.9.1.1id-1.4.17.2.27.4.2.1.4.9.1.2"/> - <keyword type="constant" name="NM_SETTINGS_ADD_CONNECTION2_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.1.1.1id-1.4.17.2.28.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_SETTINGS_ADD_CONNECTION2_FLAG_TO_DISK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.2.1.1id-1.4.17.2.28.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_SETTINGS_ADD_CONNECTION2_FLAG_IN_MEMORY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.3.1.1id-1.4.17.2.28.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_SETTINGS_ADD_CONNECTION2_FLAG_BLOCK_AUTOCONNECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.4.1.1id-1.4.17.2.28.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.1.1.1id-1.4.17.2.29.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_TO_DISK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.2.1.1id-1.4.17.2.29.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.3.1.1id-1.4.17.2.29.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.4.1.1id-1.4.17.2.29.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.5.1.1id-1.4.17.2.29.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_VOLATILE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.6.1.1id-1.4.17.2.29.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_BLOCK_AUTOCONNECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.7.1.1id-1.4.17.2.29.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_NO_REAPPLY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.8.1.1id-1.4.17.2.29.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_DEVICE_REAPPLY_FLAGS_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.1.1.1id-1.4.17.2.30.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_DEVICE_REAPPLY_FLAGS_PRESERVE_EXTERNAL_IP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.2.1.1id-1.4.17.2.30.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_TERNARY_DEFAULT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.31.4.2.1.4.1.1.1id-1.4.17.2.31.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_TERNARY_FALSE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.31.4.2.1.4.2.1.1id-1.4.17.2.31.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_TERNARY_TRUE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.31.4.2.1.4.3.1.1id-1.4.17.2.31.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.32.4.2.1.4.1.1.1id-1.4.17.2.32.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_CONF" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.32.4.2.1.4.2.1.1id-1.4.17.2.32.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_DNS_RC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.32.4.2.1.4.3.1.1id-1.4.17.2.32.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_DNS_FULL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.32.4.2.1.4.4.1.1id-1.4.17.2.32.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_ALL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.32.4.2.1.4.5.1.1id-1.4.17.2.32.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.1.1.1id-1.4.17.2.33.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_UP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.2.1.1id-1.4.17.2.33.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_LOWER_UP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.3.1.1id-1.4.17.2.33.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_PROMISC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.4.1.1id-1.4.17.2.33.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_CARRIER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.5.1.1id-1.4.17.2.33.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_LLDP_CLIENT_ENABLED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.6.1.1id-1.4.17.2.33.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.1.1.1id-1.4.17.2.34.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_NETWORK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.2.1.1id-1.4.17.2.34.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_WIFI" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.3.1.1id-1.4.17.2.34.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_WWAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.4.1.1id-1.4.17.2.34.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_WIMAX" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.5.1.1id-1.4.17.2.34.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_SLEEP_WAKE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.6.1.1id-1.4.17.2.34.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_NETWORK_CONTROL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.7.1.1id-1.4.17.2.34.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_WIFI_SHARE_PROTECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.8.1.1id-1.4.17.2.34.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_WIFI_SHARE_OPEN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.9.1.1id-1.4.17.2.34.4.2.1.4.9.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_SETTINGS_MODIFY_SYSTEM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.10.1.1id-1.4.17.2.34.4.2.1.4.10.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_SETTINGS_MODIFY_OWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.11.1.1id-1.4.17.2.34.4.2.1.4.11.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_SETTINGS_MODIFY_HOSTNAME" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.12.1.1id-1.4.17.2.34.4.2.1.4.12.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_SETTINGS_MODIFY_GLOBAL_DNS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.13.1.1id-1.4.17.2.34.4.2.1.4.13.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_RELOAD" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.14.1.1id-1.4.17.2.34.4.2.1.4.14.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_CHECKPOINT_ROLLBACK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.15.1.1id-1.4.17.2.34.4.2.1.4.15.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_STATISTICS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.16.1.1id-1.4.17.2.34.4.2.1.4.16.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_CONNECTIVITY_CHECK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.17.1.1id-1.4.17.2.34.4.2.1.4.17.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_WIFI_SCAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.18.1.1id-1.4.17.2.34.4.2.1.4.18.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_RESULT_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.1.1.1id-1.4.17.2.35.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_RESULT_YES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.2.1.1id-1.4.17.2.35.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_RESULT_AUTH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.3.1.1id-1.4.17.2.35.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_CLIENT_PERMISSION_RESULT_NO" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.4.1.1id-1.4.17.2.35.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_RADIO_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.36.4.2.1.4.1.1.1id-1.4.17.2.36.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_RADIO_FLAG_WLAN_AVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.36.4.2.1.4.2.1.1id-1.4.17.2.36.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_RADIO_FLAG_WWAN_AVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.36.4.2.1.4.3.1.1id-1.4.17.2.36.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_MPTCP_FLAGS_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.1.1.1id-1.4.17.2.37.4.2.1.4.1.1.2"/> - <keyword type="constant" name="NM_MPTCP_FLAGS_DISABLED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.2.1.1id-1.4.17.2.37.4.2.1.4.2.1.2"/> - <keyword type="constant" name="NM_MPTCP_FLAGS_ENABLED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.3.1.1id-1.4.17.2.37.4.2.1.4.3.1.2"/> - <keyword type="constant" name="NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.4.1.1id-1.4.17.2.37.4.2.1.4.4.1.2"/> - <keyword type="constant" name="NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.5.1.1id-1.4.17.2.37.4.2.1.4.5.1.2"/> - <keyword type="constant" name="NM_MPTCP_FLAGS_SIGNAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.6.1.1id-1.4.17.2.37.4.2.1.4.6.1.2"/> - <keyword type="constant" name="NM_MPTCP_FLAGS_SUBFLOW" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.7.1.1id-1.4.17.2.37.4.2.1.4.7.1.2"/> - <keyword type="constant" name="NM_MPTCP_FLAGS_BACKUP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.8.1.1id-1.4.17.2.37.4.2.1.4.8.1.2"/> - <keyword type="constant" name="NM_MPTCP_FLAGS_FULLMESH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.9.1.1id-1.4.17.2.37.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_CAPABILITY_TEAM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.1.1.1id-1.4.17.2.4.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_CAPABILITY_OVS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.4.4.2.1.4.2.1.1id-1.4.17.2.4.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_STATE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.1.1.1id-1.4.17.2.5.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_STATE_ASLEEP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.2.1.1id-1.4.17.2.5.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_STATE_DISCONNECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.3.1.1id-1.4.17.2.5.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_STATE_DISCONNECTING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.4.1.1id-1.4.17.2.5.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_STATE_CONNECTING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.5.1.1id-1.4.17.2.5.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_STATE_CONNECTED_LOCAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.6.1.1id-1.4.17.2.5.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_STATE_CONNECTED_SITE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.7.1.1id-1.4.17.2.5.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_STATE_CONNECTED_GLOBAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.5.4.2.1.4.8.1.1id-1.4.17.2.5.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_CONNECTIVITY_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.1.1.1id-1.4.17.2.6.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_CONNECTIVITY_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.2.1.1id-1.4.17.2.6.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_CONNECTIVITY_PORTAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.3.1.1id-1.4.17.2.6.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_CONNECTIVITY_LIMITED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.4.1.1id-1.4.17.2.6.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_CONNECTIVITY_FULL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.6.4.2.1.4.5.1.1id-1.4.17.2.6.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.1.1.1id-1.4.17.2.7.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_GENERIC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.2.1.1id-1.4.17.2.7.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_ETHERNET" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.3.1.1id-1.4.17.2.7.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_WIFI" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.4.1.1id-1.4.17.2.7.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_UNUSED1" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.5.1.1id-1.4.17.2.7.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_UNUSED2" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.6.1.1id-1.4.17.2.7.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_BT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.7.1.1id-1.4.17.2.7.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_OLPC_MESH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.8.1.1id-1.4.17.2.7.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_WIMAX" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.9.1.1id-1.4.17.2.7.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_MODEM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.10.1.1id-1.4.17.2.7.4.2.1.4.10.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_INFINIBAND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.11.1.1id-1.4.17.2.7.4.2.1.4.11.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_BOND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.12.1.1id-1.4.17.2.7.4.2.1.4.12.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_VLAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.13.1.1id-1.4.17.2.7.4.2.1.4.13.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_ADSL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.14.1.1id-1.4.17.2.7.4.2.1.4.14.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_BRIDGE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.15.1.1id-1.4.17.2.7.4.2.1.4.15.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_TEAM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.16.1.1id-1.4.17.2.7.4.2.1.4.16.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_TUN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.17.1.1id-1.4.17.2.7.4.2.1.4.17.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_IP_TUNNEL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.18.1.1id-1.4.17.2.7.4.2.1.4.18.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_MACVLAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.19.1.1id-1.4.17.2.7.4.2.1.4.19.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_VXLAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.20.1.1id-1.4.17.2.7.4.2.1.4.20.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_VETH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.21.1.1id-1.4.17.2.7.4.2.1.4.21.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_MACSEC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.22.1.1id-1.4.17.2.7.4.2.1.4.22.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_DUMMY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.23.1.1id-1.4.17.2.7.4.2.1.4.23.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_PPP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.24.1.1id-1.4.17.2.7.4.2.1.4.24.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_OVS_INTERFACE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.25.1.1id-1.4.17.2.7.4.2.1.4.25.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_OVS_PORT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.26.1.1id-1.4.17.2.7.4.2.1.4.26.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_OVS_BRIDGE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.27.1.1id-1.4.17.2.7.4.2.1.4.27.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_WPAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.28.1.1id-1.4.17.2.7.4.2.1.4.28.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_6LOWPAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.29.1.1id-1.4.17.2.7.4.2.1.4.29.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_WIREGUARD" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.30.1.1id-1.4.17.2.7.4.2.1.4.30.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_WIFI_P2P" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.31.1.1id-1.4.17.2.7.4.2.1.4.31.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_VRF" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.32.1.1id-1.4.17.2.7.4.2.1.4.32.1.2"/> + <keyword type="constant" name="NM_DEVICE_TYPE_LOOPBACK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.7.4.2.1.4.33.1.1id-1.4.17.2.7.4.2.1.4.33.1.2"/> + <keyword type="constant" name="NM_DEVICE_CAP_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.1.1.1id-1.4.17.2.8.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_DEVICE_CAP_NM_SUPPORTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.2.1.1id-1.4.17.2.8.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_DEVICE_CAP_CARRIER_DETECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.3.1.1id-1.4.17.2.8.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_DEVICE_CAP_IS_SOFTWARE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.4.1.1id-1.4.17.2.8.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_DEVICE_CAP_SRIOV" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.8.4.2.1.4.5.1.1id-1.4.17.2.8.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.1.1.1id-1.4.17.2.9.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_CIPHER_WEP40" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.2.1.1id-1.4.17.2.9.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_CIPHER_WEP104" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.3.1.1id-1.4.17.2.9.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_CIPHER_TKIP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.4.1.1id-1.4.17.2.9.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_CIPHER_CCMP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.5.1.1id-1.4.17.2.9.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_WPA" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.6.1.1id-1.4.17.2.9.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_RSN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.7.1.1id-1.4.17.2.9.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_AP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.8.1.1id-1.4.17.2.9.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_ADHOC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.9.1.1id-1.4.17.2.9.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_FREQ_VALID" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.10.1.1id-1.4.17.2.9.4.2.1.4.10.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_FREQ_2GHZ" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.11.1.1id-1.4.17.2.9.4.2.1.4.11.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_FREQ_5GHZ" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.12.1.1id-1.4.17.2.9.4.2.1.4.12.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_MESH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.13.1.1id-1.4.17.2.9.4.2.1.4.13.1.2"/> + <keyword type="constant" name="NM_WIFI_DEVICE_CAP_IBSS_RSN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.9.4.2.1.4.14.1.1id-1.4.17.2.9.4.2.1.4.14.1.2"/> + <keyword type="constant" name="NM_802_11_AP_FLAGS_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.1.1.1id-1.4.17.2.10.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_802_11_AP_FLAGS_PRIVACY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.2.1.1id-1.4.17.2.10.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_802_11_AP_FLAGS_WPS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.3.1.1id-1.4.17.2.10.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_802_11_AP_FLAGS_WPS_PBC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.4.1.1id-1.4.17.2.10.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_802_11_AP_FLAGS_WPS_PIN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.10.4.2.1.4.5.1.1id-1.4.17.2.10.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.1.1.1id-1.4.17.2.11.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_PAIR_WEP40" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.2.1.1id-1.4.17.2.11.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_PAIR_WEP104" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.3.1.1id-1.4.17.2.11.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_PAIR_TKIP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.4.1.1id-1.4.17.2.11.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_PAIR_CCMP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.5.1.1id-1.4.17.2.11.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_GROUP_WEP40" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.6.1.1id-1.4.17.2.11.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_GROUP_WEP104" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.7.1.1id-1.4.17.2.11.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_GROUP_TKIP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.8.1.1id-1.4.17.2.11.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_GROUP_CCMP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.9.1.1id-1.4.17.2.11.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_PSK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.10.1.1id-1.4.17.2.11.4.2.1.4.10.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_802_1X" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.11.1.1id-1.4.17.2.11.4.2.1.4.11.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_SAE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.12.1.1id-1.4.17.2.11.4.2.1.4.12.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_OWE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.13.1.1id-1.4.17.2.11.4.2.1.4.13.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_OWE_TM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.14.1.1id-1.4.17.2.11.4.2.1.4.14.1.2"/> + <keyword type="constant" name="NM_802_11_AP_SEC_KEY_MGMT_EAP_SUITE_B_192" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.11.4.2.1.4.15.1.1id-1.4.17.2.11.4.2.1.4.15.1.2"/> + <keyword type="constant" name="NM_802_11_MODE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.12.4.2.1.4.1.1.1id-1.4.17.2.12.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_802_11_MODE_ADHOC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.12.4.2.1.4.2.1.1id-1.4.17.2.12.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_802_11_MODE_INFRA" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.12.4.2.1.4.3.1.1id-1.4.17.2.12.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_802_11_MODE_AP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.12.4.2.1.4.4.1.1id-1.4.17.2.12.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_802_11_MODE_MESH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.12.4.2.1.4.5.1.1id-1.4.17.2.12.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_BT_CAPABILITY_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.13.4.2.1.4.1.1.1id-1.4.17.2.13.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_BT_CAPABILITY_DUN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.13.4.2.1.4.2.1.1id-1.4.17.2.13.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_BT_CAPABILITY_NAP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.13.4.2.1.4.3.1.1id-1.4.17.2.13.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.1.1.1id-1.4.17.2.14.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_POTS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.2.1.1id-1.4.17.2.14.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_CDMA_EVDO" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.3.1.1id-1.4.17.2.14.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_GSM_UMTS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.4.1.1id-1.4.17.2.14.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_LTE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.5.1.1id-1.4.17.2.14.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_DEVICE_MODEM_CAPABILITY_5GNR" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.14.4.2.1.4.6.1.1id-1.4.17.2.14.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_WIMAX_NSP_NETWORK_TYPE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.1.1.1id-1.4.17.2.15.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_WIMAX_NSP_NETWORK_TYPE_HOME" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.2.1.1id-1.4.17.2.15.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_WIMAX_NSP_NETWORK_TYPE_PARTNER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.3.1.1id-1.4.17.2.15.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_WIMAX_NSP_NETWORK_TYPE_ROAMING_PARTNER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.15.4.2.1.4.4.1.1id-1.4.17.2.15.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.1.1.1id-1.4.17.2.16.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_UNMANAGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.2.1.1id-1.4.17.2.16.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_UNAVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.3.1.1id-1.4.17.2.16.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_DISCONNECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.4.1.1id-1.4.17.2.16.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_PREPARE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.5.1.1id-1.4.17.2.16.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_CONFIG" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.6.1.1id-1.4.17.2.16.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_NEED_AUTH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.7.1.1id-1.4.17.2.16.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_IP_CONFIG" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.8.1.1id-1.4.17.2.16.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_IP_CHECK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.9.1.1id-1.4.17.2.16.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_SECONDARIES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.10.1.1id-1.4.17.2.16.4.2.1.4.10.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_ACTIVATED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.11.1.1id-1.4.17.2.16.4.2.1.4.11.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_DEACTIVATING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.12.1.1id-1.4.17.2.16.4.2.1.4.12.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.16.4.2.1.4.13.1.1id-1.4.17.2.16.4.2.1.4.13.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.1.1.1id-1.4.17.2.17.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.2.1.1id-1.4.17.2.17.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_NOW_MANAGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.3.1.1id-1.4.17.2.17.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_NOW_UNMANAGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.4.1.1id-1.4.17.2.17.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_CONFIG_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.5.1.1id-1.4.17.2.17.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_IP_CONFIG_UNAVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.6.1.1id-1.4.17.2.17.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_IP_CONFIG_EXPIRED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.7.1.1id-1.4.17.2.17.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_NO_SECRETS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.8.1.1id-1.4.17.2.17.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_DISCONNECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.9.1.1id-1.4.17.2.17.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_CONFIG_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.10.1.1id-1.4.17.2.17.4.2.1.4.10.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.11.1.1id-1.4.17.2.17.4.2.1.4.11.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.12.1.1id-1.4.17.2.17.4.2.1.4.12.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_PPP_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.13.1.1id-1.4.17.2.17.4.2.1.4.13.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_PPP_DISCONNECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.14.1.1id-1.4.17.2.17.4.2.1.4.14.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_PPP_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.15.1.1id-1.4.17.2.17.4.2.1.4.15.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_DHCP_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.16.1.1id-1.4.17.2.17.4.2.1.4.16.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_DHCP_ERROR" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.17.1.1id-1.4.17.2.17.4.2.1.4.17.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_DHCP_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.18.1.1id-1.4.17.2.17.4.2.1.4.18.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SHARED_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.19.1.1id-1.4.17.2.17.4.2.1.4.19.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SHARED_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.20.1.1id-1.4.17.2.17.4.2.1.4.20.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_AUTOIP_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.21.1.1id-1.4.17.2.17.4.2.1.4.21.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_AUTOIP_ERROR" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.22.1.1id-1.4.17.2.17.4.2.1.4.22.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_AUTOIP_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.23.1.1id-1.4.17.2.17.4.2.1.4.23.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_BUSY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.24.1.1id-1.4.17.2.17.4.2.1.4.24.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_NO_DIAL_TONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.25.1.1id-1.4.17.2.17.4.2.1.4.25.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_NO_CARRIER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.26.1.1id-1.4.17.2.17.4.2.1.4.26.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_DIAL_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.27.1.1id-1.4.17.2.17.4.2.1.4.27.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_DIAL_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.28.1.1id-1.4.17.2.17.4.2.1.4.28.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_INIT_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.29.1.1id-1.4.17.2.17.4.2.1.4.29.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_APN_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.30.1.1id-1.4.17.2.17.4.2.1.4.30.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_REGISTRATION_NOT_SEARCHING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.31.1.1id-1.4.17.2.17.4.2.1.4.31.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_REGISTRATION_DENIED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.32.1.1id-1.4.17.2.17.4.2.1.4.32.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_REGISTRATION_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.33.1.1id-1.4.17.2.17.4.2.1.4.33.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_REGISTRATION_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.34.1.1id-1.4.17.2.17.4.2.1.4.34.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_PIN_CHECK_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.35.1.1id-1.4.17.2.17.4.2.1.4.35.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_FIRMWARE_MISSING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.36.1.1id-1.4.17.2.17.4.2.1.4.36.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_REMOVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.37.1.1id-1.4.17.2.17.4.2.1.4.37.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SLEEPING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.38.1.1id-1.4.17.2.17.4.2.1.4.38.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_CONNECTION_REMOVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.39.1.1id-1.4.17.2.17.4.2.1.4.39.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_USER_REQUESTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.40.1.1id-1.4.17.2.17.4.2.1.4.40.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_CARRIER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.41.1.1id-1.4.17.2.17.4.2.1.4.41.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_CONNECTION_ASSUMED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.42.1.1id-1.4.17.2.17.4.2.1.4.42.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SUPPLICANT_AVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.43.1.1id-1.4.17.2.17.4.2.1.4.43.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_NOT_FOUND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.44.1.1id-1.4.17.2.17.4.2.1.4.44.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_BT_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.45.1.1id-1.4.17.2.17.4.2.1.4.45.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_SIM_NOT_INSERTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.46.1.1id-1.4.17.2.17.4.2.1.4.46.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_SIM_PIN_REQUIRED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.47.1.1id-1.4.17.2.17.4.2.1.4.47.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_SIM_PUK_REQUIRED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.48.1.1id-1.4.17.2.17.4.2.1.4.48.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_GSM_SIM_WRONG" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.49.1.1id-1.4.17.2.17.4.2.1.4.49.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_INFINIBAND_MODE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.50.1.1id-1.4.17.2.17.4.2.1.4.50.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_DEPENDENCY_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.51.1.1id-1.4.17.2.17.4.2.1.4.51.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_BR2684_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.52.1.1id-1.4.17.2.17.4.2.1.4.52.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_MANAGER_UNAVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.53.1.1id-1.4.17.2.17.4.2.1.4.53.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SSID_NOT_FOUND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.54.1.1id-1.4.17.2.17.4.2.1.4.54.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SECONDARY_CONNECTION_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.55.1.1id-1.4.17.2.17.4.2.1.4.55.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_DCB_FCOE_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.56.1.1id-1.4.17.2.17.4.2.1.4.56.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_TEAMD_CONTROL_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.57.1.1id-1.4.17.2.17.4.2.1.4.57.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.58.1.1id-1.4.17.2.17.4.2.1.4.58.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_MODEM_AVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.59.1.1id-1.4.17.2.17.4.2.1.4.59.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SIM_PIN_INCORRECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.60.1.1id-1.4.17.2.17.4.2.1.4.60.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_NEW_ACTIVATION" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.61.1.1id-1.4.17.2.17.4.2.1.4.61.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_PARENT_CHANGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.62.1.1id-1.4.17.2.17.4.2.1.4.62.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_PARENT_MANAGED_CHANGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.63.1.1id-1.4.17.2.17.4.2.1.4.63.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_OVSDB_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.64.1.1id-1.4.17.2.17.4.2.1.4.64.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_IP_ADDRESS_DUPLICATE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.65.1.1id-1.4.17.2.17.4.2.1.4.65.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_IP_METHOD_UNSUPPORTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.66.1.1id-1.4.17.2.17.4.2.1.4.66.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_SRIOV_CONFIGURATION_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.67.1.1id-1.4.17.2.17.4.2.1.4.67.1.2"/> + <keyword type="constant" name="NM_DEVICE_STATE_REASON_PEER_NOT_FOUND" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.17.4.2.1.4.68.1.1id-1.4.17.2.17.4.2.1.4.68.1.2"/> + <keyword type="constant" name="NM_METERED_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.18.4.2.1.4.1.1.1id-1.4.17.2.18.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_METERED_YES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.18.4.2.1.4.2.1.1id-1.4.17.2.18.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_METERED_NO" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.18.4.2.1.4.3.1.1id-1.4.17.2.18.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_METERED_GUESS_YES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.18.4.2.1.4.4.1.1id-1.4.17.2.18.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_METERED_GUESS_NO" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.18.4.2.1.4.5.1.1id-1.4.17.2.18.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_CONNECTION_MULTI_CONNECT_DEFAULT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.19.4.2.1.4.1.1.1id-1.4.17.2.19.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_CONNECTION_MULTI_CONNECT_SINGLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.19.4.2.1.4.2.1.1id-1.4.17.2.19.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_CONNECTION_MULTI_CONNECT_MANUAL_MULTIPLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.19.4.2.1.4.3.1.1id-1.4.17.2.19.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_CONNECTION_MULTI_CONNECT_MULTIPLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.19.4.2.1.4.4.1.1id-1.4.17.2.19.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.1.1.1id-1.4.17.2.20.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_ACTIVATING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.2.1.1id-1.4.17.2.20.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_ACTIVATED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.3.1.1id-1.4.17.2.20.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_DEACTIVATING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.4.1.1id-1.4.17.2.20.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_DEACTIVATED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.20.4.2.1.4.5.1.1id-1.4.17.2.20.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.1.1.1id-1.4.17.2.21.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.2.1.1id-1.4.17.2.21.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_USER_DISCONNECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.3.1.1id-1.4.17.2.21.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.4.1.1id-1.4.17.2.21.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_STOPPED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.5.1.1id-1.4.17.2.21.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_IP_CONFIG_INVALID" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.6.1.1id-1.4.17.2.21.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_CONNECT_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.7.1.1id-1.4.17.2.21.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_START_TIMEOUT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.8.1.1id-1.4.17.2.21.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_START_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.9.1.1id-1.4.17.2.21.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_NO_SECRETS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.10.1.1id-1.4.17.2.21.4.2.1.4.10.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_LOGIN_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.11.1.1id-1.4.17.2.21.4.2.1.4.11.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_CONNECTION_REMOVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.12.1.1id-1.4.17.2.21.4.2.1.4.12.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_DEPENDENCY_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.13.1.1id-1.4.17.2.21.4.2.1.4.13.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_REALIZE_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.14.1.1id-1.4.17.2.21.4.2.1.4.14.1.2"/> + <keyword type="constant" name="NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_REMOVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.21.4.2.1.4.15.1.1id-1.4.17.2.21.4.2.1.4.15.1.2"/> + <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.22.4.2.1.4.1.1.1id-1.4.17.2.22.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_ALLOW_INTERACTION" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.22.4.2.1.4.2.1.1id-1.4.17.2.22.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_REQUEST_NEW" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.22.4.2.1.4.3.1.1id-1.4.17.2.22.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_USER_REQUESTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.22.4.2.1.4.4.1.1id-1.4.17.2.22.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_WPS_PBC_ACTIVE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.22.4.2.1.4.5.1.1id-1.4.17.2.22.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_ONLY_SYSTEM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.22.4.2.1.4.6.1.1id-1.4.17.2.22.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_SECRET_AGENT_GET_SECRETS_FLAG_NO_ERRORS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.22.4.2.1.4.7.1.1id-1.4.17.2.22.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_SECRET_AGENT_CAPABILITY_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.1.1.1id-1.4.17.2.23.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_SECRET_AGENT_CAPABILITY_VPN_HINTS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.23.4.2.1.4.2.1.1id-1.4.17.2.23.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.1.1.1id-1.4.17.2.24.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_IPIP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.2.1.1id-1.4.17.2.24.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_GRE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.3.1.1id-1.4.17.2.24.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_SIT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.4.1.1id-1.4.17.2.24.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_ISATAP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.5.1.1id-1.4.17.2.24.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_VTI" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.6.1.1id-1.4.17.2.24.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_IP6IP6" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.7.1.1id-1.4.17.2.24.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_IPIP6" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.8.1.1id-1.4.17.2.24.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_IP6GRE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.9.1.1id-1.4.17.2.24.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_VTI6" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.10.1.1id-1.4.17.2.24.4.2.1.4.10.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_GRETAP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.11.1.1id-1.4.17.2.24.4.2.1.4.11.1.2"/> + <keyword type="constant" name="NM_IP_TUNNEL_MODE_IP6GRETAP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.24.4.2.1.4.12.1.1id-1.4.17.2.24.4.2.1.4.12.1.2"/> + <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.1.1.1id-1.4.17.2.25.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_DESTROY_ALL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.2.1.1id-1.4.17.2.25.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_DELETE_NEW_CONNECTIONS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.3.1.1id-1.4.17.2.25.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_DISCONNECT_NEW_DEVICES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.4.1.1id-1.4.17.2.25.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_ALLOW_OVERLAPPING" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.5.1.1id-1.4.17.2.25.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_CHECKPOINT_CREATE_FLAG_NO_PRESERVE_EXTERNAL_PORTS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.25.4.2.1.4.6.1.1id-1.4.17.2.25.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_ROLLBACK_RESULT_OK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.26.4.2.1.4.1.1.1id-1.4.17.2.26.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_ROLLBACK_RESULT_ERR_NO_DEVICE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.26.4.2.1.4.2.1.1id-1.4.17.2.26.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_ROLLBACK_RESULT_ERR_DEVICE_UNMANAGED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.26.4.2.1.4.3.1.1id-1.4.17.2.26.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_ROLLBACK_RESULT_ERR_FAILED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.26.4.2.1.4.4.1.1id-1.4.17.2.26.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.1.1.1id-1.4.17.2.27.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_UNSAVED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.2.1.1id-1.4.17.2.27.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_NM_GENERATED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.3.1.1id-1.4.17.2.27.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_VOLATILE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.4.1.1id-1.4.17.2.27.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_SETTINGS_CONNECTION_FLAG_EXTERNAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.27.4.2.1.4.5.1.1id-1.4.17.2.27.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.1.1.1id-1.4.17.2.28.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_IS_MASTER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.2.1.1id-1.4.17.2.28.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_IS_SLAVE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.3.1.1id-1.4.17.2.28.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_LAYER2_READY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.4.1.1id-1.4.17.2.28.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_IP4_READY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.5.1.1id-1.4.17.2.28.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_IP6_READY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.6.1.1id-1.4.17.2.28.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_MASTER_HAS_SLAVES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.7.1.1id-1.4.17.2.28.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_LIFETIME_BOUND_TO_PROFILE_VISIBILITY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.8.1.1id-1.4.17.2.28.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_ACTIVATION_STATE_FLAG_EXTERNAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.28.4.2.1.4.9.1.1id-1.4.17.2.28.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_SETTINGS_ADD_CONNECTION2_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.1.1.1id-1.4.17.2.29.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_SETTINGS_ADD_CONNECTION2_FLAG_TO_DISK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.2.1.1id-1.4.17.2.29.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_SETTINGS_ADD_CONNECTION2_FLAG_IN_MEMORY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.3.1.1id-1.4.17.2.29.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_SETTINGS_ADD_CONNECTION2_FLAG_BLOCK_AUTOCONNECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.29.4.2.1.4.4.1.1id-1.4.17.2.29.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.1.1.1id-1.4.17.2.30.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_TO_DISK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.2.1.1id-1.4.17.2.30.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.3.1.1id-1.4.17.2.30.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.4.1.1id-1.4.17.2.30.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.5.1.1id-1.4.17.2.30.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_VOLATILE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.6.1.1id-1.4.17.2.30.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_BLOCK_AUTOCONNECT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.7.1.1id-1.4.17.2.30.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_SETTINGS_UPDATE2_FLAG_NO_REAPPLY" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.30.4.2.1.4.8.1.1id-1.4.17.2.30.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_DEVICE_REAPPLY_FLAGS_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.31.4.2.1.4.1.1.1id-1.4.17.2.31.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_DEVICE_REAPPLY_FLAGS_PRESERVE_EXTERNAL_IP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.31.4.2.1.4.2.1.1id-1.4.17.2.31.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_TERNARY_DEFAULT" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.32.4.2.1.4.1.1.1id-1.4.17.2.32.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_TERNARY_FALSE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.32.4.2.1.4.2.1.1id-1.4.17.2.32.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_TERNARY_TRUE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.32.4.2.1.4.3.1.1id-1.4.17.2.32.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.1.1.1id-1.4.17.2.33.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_CONF" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.2.1.1id-1.4.17.2.33.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_DNS_RC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.3.1.1id-1.4.17.2.33.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_DNS_FULL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.4.1.1id-1.4.17.2.33.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_MANAGER_RELOAD_FLAG_ALL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.33.4.2.1.4.5.1.1id-1.4.17.2.33.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.1.1.1id-1.4.17.2.34.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_UP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.2.1.1id-1.4.17.2.34.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_LOWER_UP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.3.1.1id-1.4.17.2.34.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_PROMISC" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.4.1.1id-1.4.17.2.34.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_CARRIER" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.5.1.1id-1.4.17.2.34.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_DEVICE_INTERFACE_FLAG_LLDP_CLIENT_ENABLED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.34.4.2.1.4.6.1.1id-1.4.17.2.34.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.1.1.1id-1.4.17.2.35.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_NETWORK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.2.1.1id-1.4.17.2.35.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_WIFI" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.3.1.1id-1.4.17.2.35.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_WWAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.4.1.1id-1.4.17.2.35.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_WIMAX" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.5.1.1id-1.4.17.2.35.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_SLEEP_WAKE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.6.1.1id-1.4.17.2.35.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_NETWORK_CONTROL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.7.1.1id-1.4.17.2.35.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_WIFI_SHARE_PROTECTED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.8.1.1id-1.4.17.2.35.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_WIFI_SHARE_OPEN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.9.1.1id-1.4.17.2.35.4.2.1.4.9.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_SETTINGS_MODIFY_SYSTEM" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.10.1.1id-1.4.17.2.35.4.2.1.4.10.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_SETTINGS_MODIFY_OWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.11.1.1id-1.4.17.2.35.4.2.1.4.11.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_SETTINGS_MODIFY_HOSTNAME" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.12.1.1id-1.4.17.2.35.4.2.1.4.12.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_SETTINGS_MODIFY_GLOBAL_DNS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.13.1.1id-1.4.17.2.35.4.2.1.4.13.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_RELOAD" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.14.1.1id-1.4.17.2.35.4.2.1.4.14.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_CHECKPOINT_ROLLBACK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.15.1.1id-1.4.17.2.35.4.2.1.4.15.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_STATISTICS" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.16.1.1id-1.4.17.2.35.4.2.1.4.16.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_ENABLE_DISABLE_CONNECTIVITY_CHECK" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.17.1.1id-1.4.17.2.35.4.2.1.4.17.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_WIFI_SCAN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.35.4.2.1.4.18.1.1id-1.4.17.2.35.4.2.1.4.18.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_RESULT_UNKNOWN" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.36.4.2.1.4.1.1.1id-1.4.17.2.36.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_RESULT_YES" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.36.4.2.1.4.2.1.1id-1.4.17.2.36.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_RESULT_AUTH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.36.4.2.1.4.3.1.1id-1.4.17.2.36.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_CLIENT_PERMISSION_RESULT_NO" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.36.4.2.1.4.4.1.1id-1.4.17.2.36.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_RADIO_FLAG_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.1.1.1id-1.4.17.2.37.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_RADIO_FLAG_WLAN_AVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.2.1.1id-1.4.17.2.37.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_RADIO_FLAG_WWAN_AVAILABLE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.37.4.2.1.4.3.1.1id-1.4.17.2.37.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_MPTCP_FLAGS_NONE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.38.4.2.1.4.1.1.1id-1.4.17.2.38.4.2.1.4.1.1.2"/> + <keyword type="constant" name="NM_MPTCP_FLAGS_DISABLED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.38.4.2.1.4.2.1.1id-1.4.17.2.38.4.2.1.4.2.1.2"/> + <keyword type="constant" name="NM_MPTCP_FLAGS_ENABLED" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.38.4.2.1.4.3.1.1id-1.4.17.2.38.4.2.1.4.3.1.2"/> + <keyword type="constant" name="NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.38.4.2.1.4.4.1.1id-1.4.17.2.38.4.2.1.4.4.1.2"/> + <keyword type="constant" name="NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.38.4.2.1.4.5.1.1id-1.4.17.2.38.4.2.1.4.5.1.2"/> + <keyword type="constant" name="NM_MPTCP_FLAGS_SIGNAL" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.38.4.2.1.4.6.1.1id-1.4.17.2.38.4.2.1.4.6.1.2"/> + <keyword type="constant" name="NM_MPTCP_FLAGS_SUBFLOW" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.38.4.2.1.4.7.1.1id-1.4.17.2.38.4.2.1.4.7.1.2"/> + <keyword type="constant" name="NM_MPTCP_FLAGS_BACKUP" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.38.4.2.1.4.8.1.1id-1.4.17.2.38.4.2.1.4.8.1.2"/> + <keyword type="constant" name="NM_MPTCP_FLAGS_FULLMESH" link="nm-dbus-types.htmlnm-dbus-types.html#id-1.4.17.2.38.4.2.1.4.9.1.1id-1.4.17.2.38.4.2.1.4.9.1.2"/> <keyword type="constant" name="NM_VPN_SERVICE_STATE_UNKNOWN" link="nm-vpn-dbus-types.htmlnm-vpn-dbus-types.html#id-1.6.3.2.3.4.2.1.4.1.1.1id-1.6.3.2.3.4.2.1.4.1.1.2"/> <keyword type="constant" name="NM_VPN_SERVICE_STATE_INIT" link="nm-vpn-dbus-types.htmlnm-vpn-dbus-types.html#id-1.6.3.2.3.4.2.1.4.2.1.1id-1.6.3.2.3.4.2.1.4.2.1.2"/> <keyword type="constant" name="NM_VPN_SERVICE_STATE_SHUTDOWN" link="nm-vpn-dbus-types.htmlnm-vpn-dbus-types.html#id-1.6.3.2.3.4.2.1.4.3.1.1id-1.6.3.2.3.4.2.1.4.3.1.2"/> diff --git a/docs/api/html/NetworkManager.html b/docs/api/html/NetworkManager.html index 1ce88b40..678e9f1c 100644 --- a/docs/api/html/NetworkManager.html +++ b/docs/api/html/NetworkManager.html @@ -150,9 +150,17 @@ </tr> <tr> <td><p><span class="term"><code class="option">--print-config</code></span></p></td> -<td><p> - Print the NetworkManager configuration to stdout and exit. - </p></td> +<td> +<p> + Print the NetworkManager configuration to stdout and exit. See + <a class="link" href="NetworkManager.conf.html" title="NetworkManager.conf"><span class="citerefentry"><span class="refentrytitle">NetworkManager.conf</span>(5)</span></a>. + This does not include connection profiles. View them with <span class="command"><strong>nmcli connection</strong></span>. + </p> +<p> + This reads configuration files from disk. If NetworkManager is currently running, + make sure that it has the same configuration loaded. + </p> +</td> </tr> </tbody> </table></div> diff --git a/docs/api/html/ch01.html b/docs/api/html/ch01.html index 56eda1b0..4a43e068 100644 --- a/docs/api/html/ch01.html +++ b/docs/api/html/ch01.html @@ -24,160 +24,166 @@ <a name="id-1.3.3"></a>Configuration Settings</h2></div></div></div> <div class="toc"><dl class="toc"> <dt> -<span class="refentrytitle"><a href="settings-connection.html">connection</a></span><span class="refpurpose"> — General Connection Profile Settings</span> +<span class="refentrytitle"><a href="settings-connection.html">connection</a></span><span class="refpurpose"> — General Connection Profile Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-6lowpan.html">6lowpan</a></span><span class="refpurpose"> — 6LoWPAN Settings</span> +<span class="refentrytitle"><a href="settings-6lowpan.html">6lowpan</a></span><span class="refpurpose"> — 6LoWPAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-1x.html">802-1x</a></span><span class="refpurpose"> — IEEE 802.1x Authentication Settings</span> +<span class="refentrytitle"><a href="settings-802-1x.html">802-1x</a></span><span class="refpurpose"> — IEEE 802.1x Authentication Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-adsl.html">adsl</a></span><span class="refpurpose"> — ADSL Settings</span> +<span class="refentrytitle"><a href="settings-adsl.html">adsl</a></span><span class="refpurpose"> — ADSL Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bluetooth.html">bluetooth</a></span><span class="refpurpose"> — Bluetooth Settings</span> +<span class="refentrytitle"><a href="settings-bluetooth.html">bluetooth</a></span><span class="refpurpose"> — Bluetooth Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bond.html">bond</a></span><span class="refpurpose"> — Bonding Settings</span> +<span class="refentrytitle"><a href="settings-bond.html">bond</a></span><span class="refpurpose"> — Bonding Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bridge.html">bridge</a></span><span class="refpurpose"> — Bridging Settings</span> +<span class="refentrytitle"><a href="settings-bridge.html">bridge</a></span><span class="refpurpose"> — Bridging Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bridge-port.html">bridge-port</a></span><span class="refpurpose"> — Bridge Port Settings</span> +<span class="refentrytitle"><a href="settings-bridge-port.html">bridge-port</a></span><span class="refpurpose"> — Bridge Port Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-cdma.html">cdma</a></span><span class="refpurpose"> — CDMA-based Mobile Broadband Settings</span> +<span class="refentrytitle"><a href="settings-cdma.html">cdma</a></span><span class="refpurpose"> — CDMA-based Mobile Broadband Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-dcb.html">dcb</a></span><span class="refpurpose"> — Data Center Bridging Settings</span> +<span class="refentrytitle"><a href="settings-dcb.html">dcb</a></span><span class="refpurpose"> — Data Center Bridging Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-dummy.html">dummy</a></span><span class="refpurpose"> — Dummy Link Settings</span> +<span class="refentrytitle"><a href="settings-dummy.html">dummy</a></span><span class="refpurpose"> — Dummy Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ethtool.html">ethtool</a></span><span class="refpurpose"> — Ethtool Ethernet Settings</span> +<span class="refentrytitle"><a href="settings-ethtool.html">ethtool</a></span><span class="refpurpose"> — Ethtool Ethernet Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-generic.html">generic</a></span><span class="refpurpose"> — Generic Link Settings</span> +<span class="refentrytitle"><a href="settings-generic.html">generic</a></span><span class="refpurpose"> — Generic Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-gsm.html">gsm</a></span><span class="refpurpose"> — GSM-based Mobile Broadband Settings</span> +<span class="refentrytitle"><a href="settings-gsm.html">gsm</a></span><span class="refpurpose"> — GSM-based Mobile Broadband Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-infiniband.html">infiniband</a></span><span class="refpurpose"> — Infiniband Settings</span> +<span class="refentrytitle"><a href="settings-infiniband.html">infiniband</a></span><span class="refpurpose"> — Infiniband Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ipv4.html">ipv4</a></span><span class="refpurpose"> — IPv4 Settings</span> +<span class="refentrytitle"><a href="settings-ipv4.html">ipv4</a></span><span class="refpurpose"> — IPv4 Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ipv6.html">ipv6</a></span><span class="refpurpose"> — IPv6 Settings</span> +<span class="refentrytitle"><a href="settings-ipv6.html">ipv6</a></span><span class="refpurpose"> — IPv6 Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ip-tunnel.html">ip-tunnel</a></span><span class="refpurpose"> — IP Tunneling Settings</span> +<span class="refentrytitle"><a href="settings-ip-tunnel.html">ip-tunnel</a></span><span class="refpurpose"> — IP Tunneling Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-macsec.html">macsec</a></span><span class="refpurpose"> — MACSec Settings</span> +<span class="refentrytitle"><a href="settings-macsec.html">macsec</a></span><span class="refpurpose"> — MACSec Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-macvlan.html">macvlan</a></span><span class="refpurpose"> — MAC VLAN Settings</span> +<span class="refentrytitle"><a href="settings-macvlan.html">macvlan</a></span><span class="refpurpose"> — MAC VLAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-match.html">match</a></span><span class="refpurpose"> — Match settings</span> +<span class="refentrytitle"><a href="settings-match.html">match</a></span><span class="refpurpose"> — Match settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-11-olpc-mesh.html">802-11-olpc-mesh</a></span><span class="refpurpose"> — OLPC Wireless Mesh Settings</span> +<span class="refentrytitle"><a href="settings-802-11-olpc-mesh.html">802-11-olpc-mesh</a></span><span class="refpurpose"> — OLPC Wireless Mesh Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-bridge.html">ovs-bridge</a></span><span class="refpurpose"> — OvsBridge Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-bridge.html">ovs-bridge</a></span><span class="refpurpose"> — OvsBridge Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-dpdk.html">ovs-dpdk</a></span><span class="refpurpose"> — OvsDpdk Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-dpdk.html">ovs-dpdk</a></span><span class="refpurpose"> — OvsDpdk Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-interface.html">ovs-interface</a></span><span class="refpurpose"> — Open vSwitch Interface Settings</span> +<span class="refentrytitle"><a href="settings-ovs-interface.html">ovs-interface</a></span><span class="refpurpose"> — Open vSwitch Interface Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-patch.html">ovs-patch</a></span><span class="refpurpose"> — OvsPatch Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-patch.html">ovs-patch</a></span><span class="refpurpose"> — OvsPatch Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-port.html">ovs-port</a></span><span class="refpurpose"> — OvsPort Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-port.html">ovs-port</a></span><span class="refpurpose"> — OvsPort Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ppp.html">ppp</a></span><span class="refpurpose"> — Point-to-Point Protocol Settings</span> +<span class="refentrytitle"><a href="settings-ppp.html">ppp</a></span><span class="refpurpose"> — Point-to-Point Protocol Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-pppoe.html">pppoe</a></span><span class="refpurpose"> — PPP-over-Ethernet Settings</span> +<span class="refentrytitle"><a href="settings-pppoe.html">pppoe</a></span><span class="refpurpose"> — PPP-over-Ethernet Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-proxy.html">proxy</a></span><span class="refpurpose"> — WWW Proxy Settings</span> +<span class="refentrytitle"><a href="settings-proxy.html">proxy</a></span><span class="refpurpose"> — WWW Proxy Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-serial.html">serial</a></span><span class="refpurpose"> — Serial Link Settings</span> +<span class="refentrytitle"><a href="settings-serial.html">serial</a></span><span class="refpurpose"> — Serial Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-sriov.html">sriov</a></span><span class="refpurpose"> — SR-IOV settings</span> +<span class="refentrytitle"><a href="settings-sriov.html">sriov</a></span><span class="refpurpose"> — SR-IOV settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-tc.html">tc</a></span><span class="refpurpose"> — Linux Traffic Control Settings</span> +<span class="refentrytitle"><a href="settings-tc.html">tc</a></span><span class="refpurpose"> — Linux Traffic Control Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-team.html">team</a></span><span class="refpurpose"> — Teaming Settings</span> +<span class="refentrytitle"><a href="settings-team.html">team</a></span><span class="refpurpose"> — Teaming Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-team-port.html">team-port</a></span><span class="refpurpose"> — Team Port Settings</span> +<span class="refentrytitle"><a href="settings-team-port.html">team-port</a></span><span class="refpurpose"> — Team Port Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-tun.html">tun</a></span><span class="refpurpose"> — Tunnel Settings</span> +<span class="refentrytitle"><a href="settings-tun.html">tun</a></span><span class="refpurpose"> — Tunnel Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-user.html">user</a></span><span class="refpurpose"> — General User Profile Settings</span> +<span class="refentrytitle"><a href="settings-user.html">user</a></span><span class="refpurpose"> — General User Profile Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vlan.html">vlan</a></span><span class="refpurpose"> — VLAN Settings</span> +<span class="refentrytitle"><a href="settings-vlan.html">vlan</a></span><span class="refpurpose"> — VLAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vpn.html">vpn</a></span><span class="refpurpose"> — VPN Settings</span> +<span class="refentrytitle"><a href="settings-vpn.html">vpn</a></span><span class="refpurpose"> — VPN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vrf.html">vrf</a></span><span class="refpurpose"> — VRF settings</span> +<span class="refentrytitle"><a href="settings-vrf.html">vrf</a></span><span class="refpurpose"> — VRF settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vxlan.html">vxlan</a></span><span class="refpurpose"> — VXLAN Settings</span> +<span class="refentrytitle"><a href="settings-vxlan.html">vxlan</a></span><span class="refpurpose"> — VXLAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wifi-p2p.html">wifi-p2p</a></span><span class="refpurpose"> — Wi-Fi P2P Settings</span> +<span class="refentrytitle"><a href="settings-wifi-p2p.html">wifi-p2p</a></span><span class="refpurpose"> — Wi-Fi P2P Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wimax.html">wimax</a></span><span class="refpurpose"> — WiMax Settings</span> +<span class="refentrytitle"><a href="settings-wimax.html">wimax</a></span><span class="refpurpose"> — WiMax Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-3-ethernet.html">802-3-ethernet</a></span><span class="refpurpose"> — Wired Ethernet Settings</span> +<span class="refentrytitle"><a href="settings-802-3-ethernet.html">802-3-ethernet</a></span><span class="refpurpose"> — Wired Ethernet Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wireguard.html">wireguard</a></span><span class="refpurpose"> — WireGuard Settings</span> +<span class="refentrytitle"><a href="settings-wireguard.html">wireguard</a></span><span class="refpurpose"> — WireGuard Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-11-wireless.html">802-11-wireless</a></span><span class="refpurpose"> — Wi-Fi Settings</span> +<span class="refentrytitle"><a href="settings-802-11-wireless.html">802-11-wireless</a></span><span class="refpurpose"> — Wi-Fi Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-11-wireless-security.html">802-11-wireless-security</a></span><span class="refpurpose"> — Wi-Fi Security Settings</span> +<span class="refentrytitle"><a href="settings-802-11-wireless-security.html">802-11-wireless-security</a></span><span class="refpurpose"> — Wi-Fi Security Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wpan.html">wpan</a></span><span class="refpurpose"> — IEEE 802.15.4 (WPAN) MAC Settings</span> +<span class="refentrytitle"><a href="settings-wpan.html">wpan</a></span><span class="refpurpose"> — IEEE 802.15.4 (WPAN) MAC Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bond-port.html">bond-port</a></span><span class="refpurpose"> — Bond Port Settings</span> +<span class="refentrytitle"><a href="settings-bond-port.html">bond-port</a></span><span class="refpurpose"> — Bond Port Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-hostname.html">hostname</a></span><span class="refpurpose"> — Hostname settings</span> +<span class="refentrytitle"><a href="settings-hostname.html">hostname</a></span><span class="refpurpose"> — Hostname settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-external-ids.html">ovs-external-ids</a></span><span class="refpurpose"> — OVS External IDs Settings</span> +<span class="refentrytitle"><a href="settings-loopback.html">loopback</a></span><span class="refpurpose"> — Loopback Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-veth.html">veth</a></span><span class="refpurpose"> — Veth Settings</span> +<span class="refentrytitle"><a href="settings-ovs-external-ids.html">ovs-external-ids</a></span><span class="refpurpose"> — OVS External IDs Settings</span> +</dt> +<dt> +<span class="refentrytitle"><a href="settings-ovs-other-config.html">ovs-other-config</a></span><span class="refpurpose"> — OVS Other Config Settings</span> +</dt> +<dt> +<span class="refentrytitle"><a href="settings-veth.html">veth</a></span><span class="refpurpose"> — Veth Settings</span> </dt> </dl></div> </div> diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Connection.Active.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Connection.Active.html index f6e96ea6..afd8aea2 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Connection.Active.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Connection.Active.html @@ -58,6 +58,7 @@ <a class="link" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Ip6Config" title='The "Ip6Config" property'>Ip6Config</a> readable o <a class="link" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Dhcp6Config" title='The "Dhcp6Config" property'>Dhcp6Config</a> readable o <a class="link" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Vpn" title='The "Vpn" property'>Vpn</a> readable b +<a class="link" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Controller" title='The "Controller" property'>Controller</a> readable o <a class="link" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Master" title='The "Master" property'>Master</a> readable o </pre> </div> @@ -289,12 +290,27 @@ Whether this active connection is also a VPN connection. </div> <hr> <div class="refsect2"> +<a name="gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Controller"></a><h3>The "Controller" property</h3> +<pre class="programlisting"> +Controller readable o +</pre> +<p> +The path to the controller device if the connection is a port. This +property replaces the deprecated 'Master' property. +</p> +</div> +<hr> +<div class="refsect2"> <a name="gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Master"></a><h3>The "Master" property</h3> <pre class="programlisting"> Master readable o </pre> <p> -The path to the master device if the connection is a slave. +The path to the controller device if the connection is a port. +</p> +<p> +This property is deprecated in favor of the 'Controller' +property since 1.44 and 1.42.2. </p> </div> </div> diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html index cdf6a946..19b57766 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html @@ -46,6 +46,7 @@ <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.OutputKey" title='The "OutputKey" property'>OutputKey</a> readable s <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.EncapsulationLimit" title='The "EncapsulationLimit" property'>EncapsulationLimit</a> readable y <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.FlowLabel" title='The "FlowLabel" property'>FlowLabel</a> readable u +<a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.FwMark" title='The "FwMark" property'>FwMark</a> readable u <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.Flags" title='The "Flags" property'>Flags</a> readable u </pre> </div> @@ -173,6 +174,17 @@ IPv6 tunnels. </div> <hr> <div class="refsect2"> +<a name="gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.FwMark"></a><h3>The "FwMark" property</h3> +<pre class="programlisting"> +FwMark readable u +</pre> +<p> +The fwmark value to assign to tunnel packets. This property applies only to +VTI tunnels. +</p> +</div> +<hr> +<div class="refsect2"> <a name="gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.Flags"></a><h3>The "Flags" property</h3> <pre class="programlisting"> Flags readable u diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html index c706d1ff..2aef5cdb 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html @@ -7,7 +7,7 @@ <link rel="home" href="index.html" title="NetworkManager Reference Manual"> <link rel="up" href="ref-dbus-devices.html" title="The /org/freedesktop/NetworkManager/Devices/* objects"> <link rel="prev" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html" title="org.freedesktop.NetworkManager.Device.IPTunnel"> -<link rel="next" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html" title="org.freedesktop.NetworkManager.Device.Lowpan"> +<link rel="next" href="gdbus-org.freedesktop.NetworkManager.Device.Loopback.html" title="org.freedesktop.NetworkManager.Device.Loopback"> <meta name="generator" content="GTK-Doc V1.33.1 (XML mode)"> <link rel="stylesheet" href="style.css" type="text/css"> </head> @@ -21,7 +21,7 @@ <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> <td><a accesskey="u" href="ref-dbus-devices.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> <td><a accesskey="p" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> -<td><a accesskey="n" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> +<td><a accesskey="n" href="gdbus-org.freedesktop.NetworkManager.Device.Loopback.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> </tr></table> <div class="refentry"> <a name="gdbus-org.freedesktop.NetworkManager.Device.Infiniband"></a><div class="titlepage"></div> diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Loopback.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Loopback.html new file mode 100644 index 00000000..c522f1f7 --- /dev/null +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Loopback.html @@ -0,0 +1,45 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> +<title>org.freedesktop.NetworkManager.Device.Loopback: NetworkManager Reference Manual</title> +<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"> +<link rel="home" href="index.html" title="NetworkManager Reference Manual"> +<link rel="up" href="ref-dbus-devices.html" title="The /org/freedesktop/NetworkManager/Devices/* objects"> +<link rel="prev" href="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html" title="org.freedesktop.NetworkManager.Device.Infiniband"> +<link rel="next" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html" title="org.freedesktop.NetworkManager.Device.Lowpan"> +<meta name="generator" content="GTK-Doc V1.33.1 (XML mode)"> +<link rel="stylesheet" href="style.css" type="text/css"> +</head> +<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> +<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle"> +<td width="100%" align="left" class="shortcuts"> +<a href="#" class="shortcut">Top</a><span id="nav_description"> <span class="dim">|</span> + <a href="#gdbus-org.freedesktop.NetworkManager.Device.Loopback.description" class="shortcut">Description</a></span> +</td> +<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> +<td><a accesskey="u" href="ref-dbus-devices.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> +<td><a accesskey="p" href="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> +<td><a accesskey="n" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> +</tr></table> +<div class="refentry"> +<a name="gdbus-org.freedesktop.NetworkManager.Device.Loopback"></a><div class="titlepage"></div> +<div class="refnamediv"><table width="100%"><tr> +<td valign="top"> +<h2><span class="refentrytitle"><a name="gdbus-interface-org-freedesktop-NetworkManager-Device-Loopback.top_of_page"></a>org.freedesktop.NetworkManager.Device.Loopback</span></h2> +<p>org.freedesktop.NetworkManager.Device.Loopback — Loopback Device.</p> +</td> +<td class="gallery_image" valign="top" align="right"></td> +</tr></table></div> +<div class="refsect1"> +<a name="gdbus-interface-org-freedesktop-NetworkManager-Device-Loopback"></a><h2>Description</h2> +<p> +</p> +<p> +</p> +</div> +</div> +<div class="footer"> +<hr>Generated by GTK-Doc V1.33.1</div> +</body> +</html> \ No newline at end of file diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html index 8d85d33a..68e709aa 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html @@ -6,7 +6,7 @@ <meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"> <link rel="home" href="index.html" title="NetworkManager Reference Manual"> <link rel="up" href="ref-dbus-devices.html" title="The /org/freedesktop/NetworkManager/Devices/* objects"> -<link rel="prev" href="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html" title="org.freedesktop.NetworkManager.Device.Infiniband"> +<link rel="prev" href="gdbus-org.freedesktop.NetworkManager.Device.Loopback.html" title="org.freedesktop.NetworkManager.Device.Loopback"> <link rel="next" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html" title="org.freedesktop.NetworkManager.Device.Macsec"> <meta name="generator" content="GTK-Doc V1.33.1 (XML mode)"> <link rel="stylesheet" href="style.css" type="text/css"> @@ -20,7 +20,7 @@ </td> <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> <td><a accesskey="u" href="ref-dbus-devices.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> -<td><a accesskey="p" href="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> +<td><a accesskey="p" href="gdbus-org.freedesktop.NetworkManager.Device.Loopback.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> <td><a accesskey="n" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> </tr></table> <div class="refentry"> @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.12.3"></a><h2>Properties</h2> +<a name="id-1.4.8.13.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Lowpan.HwAddress" title='The "HwAddress" property'>HwAddress</a> readable s <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Lowpan.Parent" title='The "Parent" property'>Parent</a> readable o diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html index 795aee21..9f868062 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.13.3"></a><h2>Properties</h2> +<a name="id-1.4.8.14.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Parent" title='The "Parent" property'>Parent</a> readable o <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Sci" title='The "Sci" property'>Sci</a> readable t diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html index fcbb003c..b7ffeaf3 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.14.3"></a><h2>Properties</h2> +<a name="id-1.4.8.15.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.Parent" title='The "Parent" property'>Parent</a> readable o <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.Mode" title='The "Mode" property'>Mode</a> readable s diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html index 4b6cc204..b55163c1 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.15.3"></a><h2>Properties</h2> +<a name="id-1.4.8.16.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.ModemCapabilities" title='The "ModemCapabilities" property'>ModemCapabilities</a> readable u <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.CurrentCapabilities" title='The "CurrentCapabilities" property'>CurrentCapabilities</a> readable u diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html index 2f71abd8..631e01b3 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.16.3"></a><h2>Properties</h2> +<a name="id-1.4.8.17.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-property-org-freedesktop-NetworkManager-Device-OlpcMesh.HwAddress" title='The "HwAddress" property'>HwAddress</a> readable s <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-property-org-freedesktop-NetworkManager-Device-OlpcMesh.Companion" title='The "Companion" property'>Companion</a> readable o diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html index 46b3fbd4..571a45e6 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.17.3"></a><h2>Properties</h2> +<a name="id-1.4.8.18.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html#gdbus-property-org-freedesktop-NetworkManager-Device-OvsBridge.Slaves" title='The "Slaves" property'>Slaves</a> readable ao </pre> diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html index 08cf13ba..4dcf9283 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.19.3"></a><h2>Properties</h2> +<a name="id-1.4.8.20.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html#gdbus-property-org-freedesktop-NetworkManager-Device-OvsPort.Slaves" title='The "Slaves" property'>Slaves</a> readable ao </pre> diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html index 5864fd40..8340f542 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.21.3"></a><h2>Properties</h2> +<a name="id-1.4.8.22.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.HwAddress" title='The "HwAddress" property'>HwAddress</a> readable s <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.Carrier" title='The "Carrier" property'>Carrier</a> readable b diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html index 8c05cf5c..4ff42e7a 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.22.3"></a><h2>Properties</h2> +<a name="id-1.4.8.23.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.Owner" title='The "Owner" property'>Owner</a> readable x <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.Group" title='The "Group" property'>Group</a> readable x diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html index 46b788f2..d2ba1876 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.23.3"></a><h2>Properties</h2> +<a name="id-1.4.8.24.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Veth.html#gdbus-property-org-freedesktop-NetworkManager-Device-Veth.Peer" title='The "Peer" property'>Peer</a> readable o </pre> diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html index a55b8250..0a17c6ef 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.24.3"></a><h2>Properties</h2> +<a name="id-1.4.8.25.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.HwAddress" title='The "HwAddress" property'>HwAddress</a> readable s <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.Carrier" title='The "Carrier" property'>Carrier</a> readable b diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html index 88e848a0..a37962e2 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.25.3"></a><h2>Properties</h2> +<a name="id-1.4.8.26.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Vrf.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vrf.Table" title='The "Table" property'>Table</a> readable u </pre> diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html index 9349aa4c..38f938f8 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.26.3"></a><h2>Properties</h2> +<a name="id-1.4.8.27.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Parent" title='The "Parent" property'>Parent</a> readable o <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.HwAddress" title='The "HwAddress" property'>HwAddress</a> readable s diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html index 2ef395cf..4f99d38e 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html @@ -41,14 +41,14 @@ </pre> </div> <div class="refsect1"> -<a name="id-1.4.8.27.4"></a><h2>Signals</h2> +<a name="id-1.4.8.28.4"></a><h2>Signals</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-signal-org-freedesktop-NetworkManager-Device-WifiP2P.PeerAdded" title='The "PeerAdded" signal'>PeerAdded</a> (o peer); <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-signal-org-freedesktop-NetworkManager-Device-WifiP2P.PeerRemoved" title='The "PeerRemoved" signal'>PeerRemoved</a> (o peer); </pre> </div> <div class="refsect1"> -<a name="id-1.4.8.27.5"></a><h2>Properties</h2> +<a name="id-1.4.8.28.5"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-property-org-freedesktop-NetworkManager-Device-WifiP2P.HwAddress" title='The "HwAddress" property'>HwAddress</a> readable s <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-property-org-freedesktop-NetworkManager-Device-WifiP2P.Peers" title='The "Peers" property'>Peers</a> readable ao diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html index 60ad16dc..ab48943e 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.28.3"></a><h2>Properties</h2> +<a name="id-1.4.8.29.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-property-org-freedesktop-NetworkManager-Device-WireGuard.PublicKey" title='The "PublicKey" property'>PublicKey</a> readable ay <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-property-org-freedesktop-NetworkManager-Device-WireGuard.ListenPort" title='The "ListenPort" property'>ListenPort</a> readable q diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html index e62fe697..94fcf349 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.29.3"></a><h2>Properties</h2> +<a name="id-1.4.8.30.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.HwAddress" title='The "HwAddress" property'>HwAddress</a> readable s <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.PermHwAddress" title='The "PermHwAddress" property'>PermHwAddress</a> readable s diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html index 39d0305d..ba1206a8 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html @@ -42,14 +42,14 @@ </pre> </div> <div class="refsect1"> -<a name="id-1.4.8.30.4"></a><h2>Signals</h2> +<a name="id-1.4.8.31.4"></a><h2>Signals</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-signal-org-freedesktop-NetworkManager-Device-Wireless.AccessPointAdded" title='The "AccessPointAdded" signal'>AccessPointAdded</a> (o access_point); <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-signal-org-freedesktop-NetworkManager-Device-Wireless.AccessPointRemoved" title='The "AccessPointRemoved" signal'>AccessPointRemoved</a> (o access_point); </pre> </div> <div class="refsect1"> -<a name="id-1.4.8.30.5"></a><h2>Properties</h2> +<a name="id-1.4.8.31.5"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.HwAddress" title='The "HwAddress" property'>HwAddress</a> readable s <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.PermHwAddress" title='The "PermHwAddress" property'>PermHwAddress</a> readable s diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html index 4415fe36..28bba258 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html @@ -33,7 +33,7 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.4.8.31.3"></a><h2>Properties</h2> +<a name="id-1.4.8.32.3"></a><h2>Properties</h2> <pre class="synopsis"> <a class="link" href="gdbus-org.freedesktop.NetworkManager.Device.Wpan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wpan.HwAddress" title='The "HwAddress" property'>HwAddress</a> readable s </pre> diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html index f5026a1f..8da3cea1 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html @@ -130,8 +130,8 @@ settings-connection, just like updating the settings-connection can make them different. </p> <p> -Since 1.42, 1.40.10, "preserve-external-ip" flag (0x1) is supported to not -remove externally added IP addresses and routes on the device during reapply. +Since 1.42, "preserve-external-ip" flag (0x1) is supported to not remove +externally added IP addresses and routes on the device during reapply. </p> <div class="variablelist"><table border="0" class="variablelist"> <colgroup> diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.html index 96ae6b68..57560d60 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.html @@ -108,6 +108,7 @@ <a class="link" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.ActivatingConnection" title='The "ActivatingConnection" property'>ActivatingConnection</a> readable o <a class="link" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Startup" title='The "Startup" property'>Startup</a> readable b <a class="link" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Version" title='The "Version" property'>Version</a> readable s +<a class="link" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.VersionInfo" title='The "VersionInfo" property'>VersionInfo</a> readable au <a class="link" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Capabilities" title='The "Capabilities" property'>Capabilities</a> readable au <a class="link" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.State" title='The "State" property'>State</a> readable u <a class="link" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Connectivity" title='The "Connectivity" property'>Connectivity</a> readable u @@ -1057,6 +1058,28 @@ NetworkManager version. </div> <hr> <div class="refsect2"> +<a name="gdbus-property-org-freedesktop-NetworkManager.VersionInfo"></a><h3>The "VersionInfo" property</h3> +<pre class="programlisting"> +VersionInfo readable au +</pre> +<p> +NetworkManager version and capabilities. +</p> +<p> +The first element in the array is the NM_VERSION of the daemon. It is a binary representation +of the "Version" and can be compared numerically. The version is encoded as +"(major << 16 | minor << 8 | micro)". +</p> +<p> +The following elements are a bitfield of static capabilities of the daemon. See +#NMVersionInfoCapability for the available capability numbers. +</p> +<p> +Since: 1.42 +</p> +</div> +<hr> +<div class="refsect2"> <a name="gdbus-property-org-freedesktop-NetworkManager.Capabilities"></a><h3>The "Capabilities" property</h3> <pre class="programlisting"> Capabilities readable au diff --git a/docs/api/html/index.html b/docs/api/html/index.html index d4b84edd..b8815102 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@ <div> <div><table class="navigation" id="top" width="100%" cellpadding="2" cellspacing="0"><tr><th valign="middle"><p class="title">NetworkManager Reference Manual</p></th></tr></table></div> <div><p class="releaseinfo"> - for NetworkManager 1.40.12 + for NetworkManager 1.42.4 The latest version of this documentation can be found on-line at <a class="ulink" href="https://networkmanager.dev/docs/api/latest/" target="_top">https://networkmanager.dev/docs/api/latest/</a>. @@ -79,7 +79,7 @@ <span class="refentrytitle"><a href="NetworkManager-dispatcher.html">NetworkManager-dispatcher</a></span><span class="refpurpose"> — Dispatch user scripts for NetworkManager</span> </dt> <dt> -<span class="refentrytitle"><a href="NetworkManager-wait-online.service.html">NetworkManager-wait-online.service</a></span><span class="refpurpose"> — Wait for network to come online</span> +<span class="refentrytitle"><a href="NetworkManager-wait-online.service.html">NetworkManager-wait-online.service</a></span><span class="refpurpose"> — Wait for the network to come online</span> </dt> <dt> <span class="refentrytitle"><a href="nmcli.html">nmcli</a></span><span class="refpurpose"> — command-line tool for controlling NetworkManager</span> @@ -120,160 +120,166 @@ <dt><span class="chapter"><a href="ch01.html">Configuration Settings</a></span></dt> <dd><dl> <dt> -<span class="refentrytitle"><a href="settings-connection.html">connection</a></span><span class="refpurpose"> — General Connection Profile Settings</span> +<span class="refentrytitle"><a href="settings-connection.html">connection</a></span><span class="refpurpose"> — General Connection Profile Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-6lowpan.html">6lowpan</a></span><span class="refpurpose"> — 6LoWPAN Settings</span> +<span class="refentrytitle"><a href="settings-6lowpan.html">6lowpan</a></span><span class="refpurpose"> — 6LoWPAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-1x.html">802-1x</a></span><span class="refpurpose"> — IEEE 802.1x Authentication Settings</span> +<span class="refentrytitle"><a href="settings-802-1x.html">802-1x</a></span><span class="refpurpose"> — IEEE 802.1x Authentication Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-adsl.html">adsl</a></span><span class="refpurpose"> — ADSL Settings</span> +<span class="refentrytitle"><a href="settings-adsl.html">adsl</a></span><span class="refpurpose"> — ADSL Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bluetooth.html">bluetooth</a></span><span class="refpurpose"> — Bluetooth Settings</span> +<span class="refentrytitle"><a href="settings-bluetooth.html">bluetooth</a></span><span class="refpurpose"> — Bluetooth Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bond.html">bond</a></span><span class="refpurpose"> — Bonding Settings</span> +<span class="refentrytitle"><a href="settings-bond.html">bond</a></span><span class="refpurpose"> — Bonding Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bridge.html">bridge</a></span><span class="refpurpose"> — Bridging Settings</span> +<span class="refentrytitle"><a href="settings-bridge.html">bridge</a></span><span class="refpurpose"> — Bridging Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bridge-port.html">bridge-port</a></span><span class="refpurpose"> — Bridge Port Settings</span> +<span class="refentrytitle"><a href="settings-bridge-port.html">bridge-port</a></span><span class="refpurpose"> — Bridge Port Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-cdma.html">cdma</a></span><span class="refpurpose"> — CDMA-based Mobile Broadband Settings</span> +<span class="refentrytitle"><a href="settings-cdma.html">cdma</a></span><span class="refpurpose"> — CDMA-based Mobile Broadband Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-dcb.html">dcb</a></span><span class="refpurpose"> — Data Center Bridging Settings</span> +<span class="refentrytitle"><a href="settings-dcb.html">dcb</a></span><span class="refpurpose"> — Data Center Bridging Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-dummy.html">dummy</a></span><span class="refpurpose"> — Dummy Link Settings</span> +<span class="refentrytitle"><a href="settings-dummy.html">dummy</a></span><span class="refpurpose"> — Dummy Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ethtool.html">ethtool</a></span><span class="refpurpose"> — Ethtool Ethernet Settings</span> +<span class="refentrytitle"><a href="settings-ethtool.html">ethtool</a></span><span class="refpurpose"> — Ethtool Ethernet Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-generic.html">generic</a></span><span class="refpurpose"> — Generic Link Settings</span> +<span class="refentrytitle"><a href="settings-generic.html">generic</a></span><span class="refpurpose"> — Generic Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-gsm.html">gsm</a></span><span class="refpurpose"> — GSM-based Mobile Broadband Settings</span> +<span class="refentrytitle"><a href="settings-gsm.html">gsm</a></span><span class="refpurpose"> — GSM-based Mobile Broadband Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-infiniband.html">infiniband</a></span><span class="refpurpose"> — Infiniband Settings</span> +<span class="refentrytitle"><a href="settings-infiniband.html">infiniband</a></span><span class="refpurpose"> — Infiniband Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ipv4.html">ipv4</a></span><span class="refpurpose"> — IPv4 Settings</span> +<span class="refentrytitle"><a href="settings-ipv4.html">ipv4</a></span><span class="refpurpose"> — IPv4 Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ipv6.html">ipv6</a></span><span class="refpurpose"> — IPv6 Settings</span> +<span class="refentrytitle"><a href="settings-ipv6.html">ipv6</a></span><span class="refpurpose"> — IPv6 Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ip-tunnel.html">ip-tunnel</a></span><span class="refpurpose"> — IP Tunneling Settings</span> +<span class="refentrytitle"><a href="settings-ip-tunnel.html">ip-tunnel</a></span><span class="refpurpose"> — IP Tunneling Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-macsec.html">macsec</a></span><span class="refpurpose"> — MACSec Settings</span> +<span class="refentrytitle"><a href="settings-macsec.html">macsec</a></span><span class="refpurpose"> — MACSec Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-macvlan.html">macvlan</a></span><span class="refpurpose"> — MAC VLAN Settings</span> +<span class="refentrytitle"><a href="settings-macvlan.html">macvlan</a></span><span class="refpurpose"> — MAC VLAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-match.html">match</a></span><span class="refpurpose"> — Match settings</span> +<span class="refentrytitle"><a href="settings-match.html">match</a></span><span class="refpurpose"> — Match settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-11-olpc-mesh.html">802-11-olpc-mesh</a></span><span class="refpurpose"> — OLPC Wireless Mesh Settings</span> +<span class="refentrytitle"><a href="settings-802-11-olpc-mesh.html">802-11-olpc-mesh</a></span><span class="refpurpose"> — OLPC Wireless Mesh Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-bridge.html">ovs-bridge</a></span><span class="refpurpose"> — OvsBridge Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-bridge.html">ovs-bridge</a></span><span class="refpurpose"> — OvsBridge Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-dpdk.html">ovs-dpdk</a></span><span class="refpurpose"> — OvsDpdk Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-dpdk.html">ovs-dpdk</a></span><span class="refpurpose"> — OvsDpdk Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-interface.html">ovs-interface</a></span><span class="refpurpose"> — Open vSwitch Interface Settings</span> +<span class="refentrytitle"><a href="settings-ovs-interface.html">ovs-interface</a></span><span class="refpurpose"> — Open vSwitch Interface Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-patch.html">ovs-patch</a></span><span class="refpurpose"> — OvsPatch Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-patch.html">ovs-patch</a></span><span class="refpurpose"> — OvsPatch Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-port.html">ovs-port</a></span><span class="refpurpose"> — OvsPort Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-port.html">ovs-port</a></span><span class="refpurpose"> — OvsPort Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ppp.html">ppp</a></span><span class="refpurpose"> — Point-to-Point Protocol Settings</span> +<span class="refentrytitle"><a href="settings-ppp.html">ppp</a></span><span class="refpurpose"> — Point-to-Point Protocol Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-pppoe.html">pppoe</a></span><span class="refpurpose"> — PPP-over-Ethernet Settings</span> +<span class="refentrytitle"><a href="settings-pppoe.html">pppoe</a></span><span class="refpurpose"> — PPP-over-Ethernet Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-proxy.html">proxy</a></span><span class="refpurpose"> — WWW Proxy Settings</span> +<span class="refentrytitle"><a href="settings-proxy.html">proxy</a></span><span class="refpurpose"> — WWW Proxy Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-serial.html">serial</a></span><span class="refpurpose"> — Serial Link Settings</span> +<span class="refentrytitle"><a href="settings-serial.html">serial</a></span><span class="refpurpose"> — Serial Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-sriov.html">sriov</a></span><span class="refpurpose"> — SR-IOV settings</span> +<span class="refentrytitle"><a href="settings-sriov.html">sriov</a></span><span class="refpurpose"> — SR-IOV settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-tc.html">tc</a></span><span class="refpurpose"> — Linux Traffic Control Settings</span> +<span class="refentrytitle"><a href="settings-tc.html">tc</a></span><span class="refpurpose"> — Linux Traffic Control Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-team.html">team</a></span><span class="refpurpose"> — Teaming Settings</span> +<span class="refentrytitle"><a href="settings-team.html">team</a></span><span class="refpurpose"> — Teaming Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-team-port.html">team-port</a></span><span class="refpurpose"> — Team Port Settings</span> +<span class="refentrytitle"><a href="settings-team-port.html">team-port</a></span><span class="refpurpose"> — Team Port Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-tun.html">tun</a></span><span class="refpurpose"> — Tunnel Settings</span> +<span class="refentrytitle"><a href="settings-tun.html">tun</a></span><span class="refpurpose"> — Tunnel Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-user.html">user</a></span><span class="refpurpose"> — General User Profile Settings</span> +<span class="refentrytitle"><a href="settings-user.html">user</a></span><span class="refpurpose"> — General User Profile Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vlan.html">vlan</a></span><span class="refpurpose"> — VLAN Settings</span> +<span class="refentrytitle"><a href="settings-vlan.html">vlan</a></span><span class="refpurpose"> — VLAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vpn.html">vpn</a></span><span class="refpurpose"> — VPN Settings</span> +<span class="refentrytitle"><a href="settings-vpn.html">vpn</a></span><span class="refpurpose"> — VPN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vrf.html">vrf</a></span><span class="refpurpose"> — VRF settings</span> +<span class="refentrytitle"><a href="settings-vrf.html">vrf</a></span><span class="refpurpose"> — VRF settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vxlan.html">vxlan</a></span><span class="refpurpose"> — VXLAN Settings</span> +<span class="refentrytitle"><a href="settings-vxlan.html">vxlan</a></span><span class="refpurpose"> — VXLAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wifi-p2p.html">wifi-p2p</a></span><span class="refpurpose"> — Wi-Fi P2P Settings</span> +<span class="refentrytitle"><a href="settings-wifi-p2p.html">wifi-p2p</a></span><span class="refpurpose"> — Wi-Fi P2P Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wimax.html">wimax</a></span><span class="refpurpose"> — WiMax Settings</span> +<span class="refentrytitle"><a href="settings-wimax.html">wimax</a></span><span class="refpurpose"> — WiMax Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-3-ethernet.html">802-3-ethernet</a></span><span class="refpurpose"> — Wired Ethernet Settings</span> +<span class="refentrytitle"><a href="settings-802-3-ethernet.html">802-3-ethernet</a></span><span class="refpurpose"> — Wired Ethernet Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wireguard.html">wireguard</a></span><span class="refpurpose"> — WireGuard Settings</span> +<span class="refentrytitle"><a href="settings-wireguard.html">wireguard</a></span><span class="refpurpose"> — WireGuard Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-11-wireless.html">802-11-wireless</a></span><span class="refpurpose"> — Wi-Fi Settings</span> +<span class="refentrytitle"><a href="settings-802-11-wireless.html">802-11-wireless</a></span><span class="refpurpose"> — Wi-Fi Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-11-wireless-security.html">802-11-wireless-security</a></span><span class="refpurpose"> — Wi-Fi Security Settings</span> +<span class="refentrytitle"><a href="settings-802-11-wireless-security.html">802-11-wireless-security</a></span><span class="refpurpose"> — Wi-Fi Security Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wpan.html">wpan</a></span><span class="refpurpose"> — IEEE 802.15.4 (WPAN) MAC Settings</span> +<span class="refentrytitle"><a href="settings-wpan.html">wpan</a></span><span class="refpurpose"> — IEEE 802.15.4 (WPAN) MAC Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bond-port.html">bond-port</a></span><span class="refpurpose"> — Bond Port Settings</span> +<span class="refentrytitle"><a href="settings-bond-port.html">bond-port</a></span><span class="refpurpose"> — Bond Port Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-hostname.html">hostname</a></span><span class="refpurpose"> — Hostname settings</span> +<span class="refentrytitle"><a href="settings-hostname.html">hostname</a></span><span class="refpurpose"> — Hostname settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-external-ids.html">ovs-external-ids</a></span><span class="refpurpose"> — OVS External IDs Settings</span> +<span class="refentrytitle"><a href="settings-loopback.html">loopback</a></span><span class="refpurpose"> — Loopback Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-veth.html">veth</a></span><span class="refpurpose"> — Veth Settings</span> +<span class="refentrytitle"><a href="settings-ovs-external-ids.html">ovs-external-ids</a></span><span class="refpurpose"> — OVS External IDs Settings</span> +</dt> +<dt> +<span class="refentrytitle"><a href="settings-ovs-other-config.html">ovs-other-config</a></span><span class="refpurpose"> — OVS Other Config Settings</span> +</dt> +<dt> +<span class="refentrytitle"><a href="settings-veth.html">veth</a></span><span class="refpurpose"> — Veth Settings</span> </dt> </dl></dd> <dt><span class="chapter"><a href="secrets-flags.html">Secret flag types</a></span></dt> @@ -333,6 +339,9 @@ <span class="refentrytitle"><a href="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html">org.freedesktop.NetworkManager.Device.Infiniband</a></span><span class="refpurpose"> — Infiniband Device.</span> </dt> <dt> +<span class="refentrytitle"><a href="gdbus-org.freedesktop.NetworkManager.Device.Loopback.html">org.freedesktop.NetworkManager.Device.Loopback</a></span><span class="refpurpose"> — Loopback Device.</span> +</dt> +<dt> <span class="refentrytitle"><a href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html">org.freedesktop.NetworkManager.Device.Lowpan</a></span><span class="refpurpose"> — 6LoWPAN Device.</span> </dt> <dt> diff --git a/docs/api/html/ix01.html b/docs/api/html/ix01.html index d1897057..e087c18a 100644 --- a/docs/api/html/ix01.html +++ b/docs/api/html/ix01.html @@ -112,10 +112,12 @@ </dt> <dt id="ientry-id-1.4.8.10.5.11.2">org.freedesktop.NetworkManager.Device.IPTunnel:EncapsulationLimit, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.EncapsulationLimit">The "EncapsulationLimit" property</a> </dt> -<dt id="ientry-id-1.4.8.10.5.13.2">org.freedesktop.NetworkManager.Device.IPTunnel:Flags, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.Flags">The "Flags" property</a> +<dt id="ientry-id-1.4.8.10.5.14.2">org.freedesktop.NetworkManager.Device.IPTunnel:Flags, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.Flags">The "Flags" property</a> </dt> <dt id="ientry-id-1.4.8.10.5.12.2">org.freedesktop.NetworkManager.Device.IPTunnel:FlowLabel, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.FlowLabel">The "FlowLabel" property</a> </dt> +<dt id="ientry-id-1.4.8.10.5.13.2">org.freedesktop.NetworkManager.Device.IPTunnel:FwMark, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.FwMark">The "FwMark" property</a> +</dt> <dt id="ientry-id-1.4.8.10.5.9.2">org.freedesktop.NetworkManager.Device.IPTunnel:InputKey, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.InputKey">The "InputKey" property</a> </dt> <dt id="ientry-id-1.4.8.10.5.4.2">org.freedesktop.NetworkManager.Device.IPTunnel:Local, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.Local">The "Local" property</a> @@ -134,81 +136,83 @@ </dt> <dt id="ientry-id-1.4.8.10.5.6.2">org.freedesktop.NetworkManager.Device.IPTunnel:Ttl, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.IPTunnel.html#gdbus-property-org-freedesktop-NetworkManager-Device-IPTunnel.Ttl">The "Ttl" property</a> </dt> -<dt id="ientry-id-1.4.8.12.1.2">org.freedesktop.NetworkManager.Device.Lowpan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Lowpan.top_of_page">org.freedesktop.NetworkManager.Device.Lowpan</a> +<dt id="ientry-id-1.4.8.12.1.2">org.freedesktop.NetworkManager.Device.Loopback, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Loopback.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Loopback.top_of_page">org.freedesktop.NetworkManager.Device.Loopback</a> +</dt> +<dt id="ientry-id-1.4.8.13.1.2">org.freedesktop.NetworkManager.Device.Lowpan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Lowpan.top_of_page">org.freedesktop.NetworkManager.Device.Lowpan</a> </dt> -<dt id="ientry-id-1.4.8.12.5.2.2">org.freedesktop.NetworkManager.Device.Lowpan:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Lowpan.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.13.5.2.2">org.freedesktop.NetworkManager.Device.Lowpan:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Lowpan.HwAddress">The "HwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.12.5.3.2">org.freedesktop.NetworkManager.Device.Lowpan:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Lowpan.Parent">The "Parent" property</a> +<dt id="ientry-id-1.4.8.13.5.3.2">org.freedesktop.NetworkManager.Device.Lowpan:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Lowpan.Parent">The "Parent" property</a> </dt> -<dt id="ientry-id-1.4.8.13.1.2">org.freedesktop.NetworkManager.Device.Macsec, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Macsec.top_of_page">org.freedesktop.NetworkManager.Device.Macsec</a> +<dt id="ientry-id-1.4.8.14.1.2">org.freedesktop.NetworkManager.Device.Macsec, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Macsec.top_of_page">org.freedesktop.NetworkManager.Device.Macsec</a> </dt> -<dt id="ientry-id-1.4.8.13.5.5.2">org.freedesktop.NetworkManager.Device.Macsec:CipherSuite, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.CipherSuite">The "CipherSuite" property</a> +<dt id="ientry-id-1.4.8.14.5.5.2">org.freedesktop.NetworkManager.Device.Macsec:CipherSuite, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.CipherSuite">The "CipherSuite" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.7.2">org.freedesktop.NetworkManager.Device.Macsec:EncodingSa, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.EncodingSa">The "EncodingSa" property</a> +<dt id="ientry-id-1.4.8.14.5.7.2">org.freedesktop.NetworkManager.Device.Macsec:EncodingSa, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.EncodingSa">The "EncodingSa" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.9.2">org.freedesktop.NetworkManager.Device.Macsec:Encrypt, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Encrypt">The "Encrypt" property</a> +<dt id="ientry-id-1.4.8.14.5.9.2">org.freedesktop.NetworkManager.Device.Macsec:Encrypt, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Encrypt">The "Encrypt" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.12.2">org.freedesktop.NetworkManager.Device.Macsec:Es, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Es">The "Es" property</a> +<dt id="ientry-id-1.4.8.14.5.12.2">org.freedesktop.NetworkManager.Device.Macsec:Es, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Es">The "Es" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.4.2">org.freedesktop.NetworkManager.Device.Macsec:IcvLength, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.IcvLength">The "IcvLength" property</a> +<dt id="ientry-id-1.4.8.14.5.4.2">org.freedesktop.NetworkManager.Device.Macsec:IcvLength, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.IcvLength">The "IcvLength" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.11.2">org.freedesktop.NetworkManager.Device.Macsec:IncludeSci, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.IncludeSci">The "IncludeSci" property</a> +<dt id="ientry-id-1.4.8.14.5.11.2">org.freedesktop.NetworkManager.Device.Macsec:IncludeSci, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.IncludeSci">The "IncludeSci" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.2.2">org.freedesktop.NetworkManager.Device.Macsec:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Parent">The "Parent" property</a> +<dt id="ientry-id-1.4.8.14.5.2.2">org.freedesktop.NetworkManager.Device.Macsec:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Parent">The "Parent" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.10.2">org.freedesktop.NetworkManager.Device.Macsec:Protect, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Protect">The "Protect" property</a> +<dt id="ientry-id-1.4.8.14.5.10.2">org.freedesktop.NetworkManager.Device.Macsec:Protect, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Protect">The "Protect" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.14.2">org.freedesktop.NetworkManager.Device.Macsec:ReplayProtect, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.ReplayProtect">The "ReplayProtect" property</a> +<dt id="ientry-id-1.4.8.14.5.14.2">org.freedesktop.NetworkManager.Device.Macsec:ReplayProtect, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.ReplayProtect">The "ReplayProtect" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.13.2">org.freedesktop.NetworkManager.Device.Macsec:Scb, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Scb">The "Scb" property</a> +<dt id="ientry-id-1.4.8.14.5.13.2">org.freedesktop.NetworkManager.Device.Macsec:Scb, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Scb">The "Scb" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.3.2">org.freedesktop.NetworkManager.Device.Macsec:Sci, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Sci">The "Sci" property</a> +<dt id="ientry-id-1.4.8.14.5.3.2">org.freedesktop.NetworkManager.Device.Macsec:Sci, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Sci">The "Sci" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.8.2">org.freedesktop.NetworkManager.Device.Macsec:Validation, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Validation">The "Validation" property</a> +<dt id="ientry-id-1.4.8.14.5.8.2">org.freedesktop.NetworkManager.Device.Macsec:Validation, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Validation">The "Validation" property</a> </dt> -<dt id="ientry-id-1.4.8.13.5.6.2">org.freedesktop.NetworkManager.Device.Macsec:Window, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Window">The "Window" property</a> +<dt id="ientry-id-1.4.8.14.5.6.2">org.freedesktop.NetworkManager.Device.Macsec:Window, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macsec.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macsec.Window">The "Window" property</a> </dt> -<dt id="ientry-id-1.4.8.14.1.2">org.freedesktop.NetworkManager.Device.Macvlan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Macvlan.top_of_page">org.freedesktop.NetworkManager.Device.Macvlan</a> +<dt id="ientry-id-1.4.8.15.1.2">org.freedesktop.NetworkManager.Device.Macvlan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Macvlan.top_of_page">org.freedesktop.NetworkManager.Device.Macvlan</a> </dt> -<dt id="ientry-id-1.4.8.14.5.3.2">org.freedesktop.NetworkManager.Device.Macvlan:Mode, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.Mode">The "Mode" property</a> +<dt id="ientry-id-1.4.8.15.5.3.2">org.freedesktop.NetworkManager.Device.Macvlan:Mode, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.Mode">The "Mode" property</a> </dt> -<dt id="ientry-id-1.4.8.14.5.4.2">org.freedesktop.NetworkManager.Device.Macvlan:NoPromisc, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.NoPromisc">The "NoPromisc" property</a> +<dt id="ientry-id-1.4.8.15.5.4.2">org.freedesktop.NetworkManager.Device.Macvlan:NoPromisc, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.NoPromisc">The "NoPromisc" property</a> </dt> -<dt id="ientry-id-1.4.8.14.5.2.2">org.freedesktop.NetworkManager.Device.Macvlan:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.Parent">The "Parent" property</a> +<dt id="ientry-id-1.4.8.15.5.2.2">org.freedesktop.NetworkManager.Device.Macvlan:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.Parent">The "Parent" property</a> </dt> -<dt id="ientry-id-1.4.8.14.5.5.2">org.freedesktop.NetworkManager.Device.Macvlan:Tap, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.Tap">The "Tap" property</a> +<dt id="ientry-id-1.4.8.15.5.5.2">org.freedesktop.NetworkManager.Device.Macvlan:Tap, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Macvlan.Tap">The "Tap" property</a> </dt> -<dt id="ientry-id-1.4.8.15.1.2">org.freedesktop.NetworkManager.Device.Modem, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Modem.top_of_page">org.freedesktop.NetworkManager.Device.Modem</a> +<dt id="ientry-id-1.4.8.16.1.2">org.freedesktop.NetworkManager.Device.Modem, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Modem.top_of_page">org.freedesktop.NetworkManager.Device.Modem</a> </dt> -<dt id="ientry-id-1.4.8.15.5.6.2">org.freedesktop.NetworkManager.Device.Modem:Apn, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.Apn">The "Apn" property</a> +<dt id="ientry-id-1.4.8.16.5.6.2">org.freedesktop.NetworkManager.Device.Modem:Apn, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.Apn">The "Apn" property</a> </dt> -<dt id="ientry-id-1.4.8.15.5.3.2">org.freedesktop.NetworkManager.Device.Modem:CurrentCapabilities, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.CurrentCapabilities">The "CurrentCapabilities" property</a> +<dt id="ientry-id-1.4.8.16.5.3.2">org.freedesktop.NetworkManager.Device.Modem:CurrentCapabilities, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.CurrentCapabilities">The "CurrentCapabilities" property</a> </dt> -<dt id="ientry-id-1.4.8.15.5.4.2">org.freedesktop.NetworkManager.Device.Modem:DeviceId, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.DeviceId">The "DeviceId" property</a> +<dt id="ientry-id-1.4.8.16.5.4.2">org.freedesktop.NetworkManager.Device.Modem:DeviceId, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.DeviceId">The "DeviceId" property</a> </dt> -<dt id="ientry-id-1.4.8.15.5.2.2">org.freedesktop.NetworkManager.Device.Modem:ModemCapabilities, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.ModemCapabilities">The "ModemCapabilities" property</a> +<dt id="ientry-id-1.4.8.16.5.2.2">org.freedesktop.NetworkManager.Device.Modem:ModemCapabilities, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.ModemCapabilities">The "ModemCapabilities" property</a> </dt> -<dt id="ientry-id-1.4.8.15.5.5.2">org.freedesktop.NetworkManager.Device.Modem:OperatorCode, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.OperatorCode">The "OperatorCode" property</a> +<dt id="ientry-id-1.4.8.16.5.5.2">org.freedesktop.NetworkManager.Device.Modem:OperatorCode, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Modem.html#gdbus-property-org-freedesktop-NetworkManager-Device-Modem.OperatorCode">The "OperatorCode" property</a> </dt> -<dt id="ientry-id-1.4.8.16.1.2">org.freedesktop.NetworkManager.Device.OlpcMesh, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-interface-org-freedesktop-NetworkManager-Device-OlpcMesh.top_of_page">org.freedesktop.NetworkManager.Device.OlpcMesh</a> +<dt id="ientry-id-1.4.8.17.1.2">org.freedesktop.NetworkManager.Device.OlpcMesh, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-interface-org-freedesktop-NetworkManager-Device-OlpcMesh.top_of_page">org.freedesktop.NetworkManager.Device.OlpcMesh</a> </dt> -<dt id="ientry-id-1.4.8.16.5.4.2">org.freedesktop.NetworkManager.Device.OlpcMesh:ActiveChannel, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-property-org-freedesktop-NetworkManager-Device-OlpcMesh.ActiveChannel">The "ActiveChannel" property</a> +<dt id="ientry-id-1.4.8.17.5.4.2">org.freedesktop.NetworkManager.Device.OlpcMesh:ActiveChannel, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-property-org-freedesktop-NetworkManager-Device-OlpcMesh.ActiveChannel">The "ActiveChannel" property</a> </dt> -<dt id="ientry-id-1.4.8.16.5.3.2">org.freedesktop.NetworkManager.Device.OlpcMesh:Companion, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-property-org-freedesktop-NetworkManager-Device-OlpcMesh.Companion">The "Companion" property</a> +<dt id="ientry-id-1.4.8.17.5.3.2">org.freedesktop.NetworkManager.Device.OlpcMesh:Companion, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-property-org-freedesktop-NetworkManager-Device-OlpcMesh.Companion">The "Companion" property</a> </dt> -<dt id="ientry-id-1.4.8.16.5.2.2">org.freedesktop.NetworkManager.Device.OlpcMesh:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-property-org-freedesktop-NetworkManager-Device-OlpcMesh.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.17.5.2.2">org.freedesktop.NetworkManager.Device.OlpcMesh:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html#gdbus-property-org-freedesktop-NetworkManager-Device-OlpcMesh.HwAddress">The "HwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.17.1.2">org.freedesktop.NetworkManager.Device.OvsBridge, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html#gdbus-interface-org-freedesktop-NetworkManager-Device-OvsBridge.top_of_page">org.freedesktop.NetworkManager.Device.OvsBridge</a> +<dt id="ientry-id-1.4.8.18.1.2">org.freedesktop.NetworkManager.Device.OvsBridge, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html#gdbus-interface-org-freedesktop-NetworkManager-Device-OvsBridge.top_of_page">org.freedesktop.NetworkManager.Device.OvsBridge</a> </dt> -<dt id="ientry-id-1.4.8.17.5.2.2">org.freedesktop.NetworkManager.Device.OvsBridge:Slaves, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html#gdbus-property-org-freedesktop-NetworkManager-Device-OvsBridge.Slaves">The "Slaves" property</a> +<dt id="ientry-id-1.4.8.18.5.2.2">org.freedesktop.NetworkManager.Device.OvsBridge:Slaves, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html#gdbus-property-org-freedesktop-NetworkManager-Device-OvsBridge.Slaves">The "Slaves" property</a> </dt> -<dt id="ientry-id-1.4.8.18.1.2">org.freedesktop.NetworkManager.Device.OvsInterface, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsInterface.html#gdbus-interface-org-freedesktop-NetworkManager-Device-OvsInterface.top_of_page">org.freedesktop.NetworkManager.Device.OvsInterface</a> +<dt id="ientry-id-1.4.8.19.1.2">org.freedesktop.NetworkManager.Device.OvsInterface, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsInterface.html#gdbus-interface-org-freedesktop-NetworkManager-Device-OvsInterface.top_of_page">org.freedesktop.NetworkManager.Device.OvsInterface</a> </dt> -<dt id="ientry-id-1.4.8.19.1.2">org.freedesktop.NetworkManager.Device.OvsPort, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html#gdbus-interface-org-freedesktop-NetworkManager-Device-OvsPort.top_of_page">org.freedesktop.NetworkManager.Device.OvsPort</a> +<dt id="ientry-id-1.4.8.20.1.2">org.freedesktop.NetworkManager.Device.OvsPort, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html#gdbus-interface-org-freedesktop-NetworkManager-Device-OvsPort.top_of_page">org.freedesktop.NetworkManager.Device.OvsPort</a> </dt> -<dt id="ientry-id-1.4.8.19.5.2.2">org.freedesktop.NetworkManager.Device.OvsPort:Slaves, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html#gdbus-property-org-freedesktop-NetworkManager-Device-OvsPort.Slaves">The "Slaves" property</a> +<dt id="ientry-id-1.4.8.20.5.2.2">org.freedesktop.NetworkManager.Device.OvsPort:Slaves, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html#gdbus-property-org-freedesktop-NetworkManager-Device-OvsPort.Slaves">The "Slaves" property</a> </dt> -<dt id="ientry-id-1.4.8.20.1.2">org.freedesktop.NetworkManager.Device.Ppp, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Ppp.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Ppp.top_of_page">org.freedesktop.NetworkManager.Device.Ppp</a> +<dt id="ientry-id-1.4.8.21.1.2">org.freedesktop.NetworkManager.Device.Ppp, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Ppp.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Ppp.top_of_page">org.freedesktop.NetworkManager.Device.Ppp</a> </dt> <dt id="ientry-id-1.4.8.2.7.2.2">org.freedesktop.NetworkManager.Device.Reapply(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.html#gdbus-method-org-freedesktop-NetworkManager-Device.Reapply">The Reapply() method</a> </dt> @@ -220,97 +224,97 @@ </dt> <dt id="ientry-id-1.4.8.3.5.3.2">org.freedesktop.NetworkManager.Device.Statistics:TxBytes, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Statistics.html#gdbus-property-org-freedesktop-NetworkManager-Device-Statistics.TxBytes">The "TxBytes" property</a> </dt> -<dt id="ientry-id-1.4.8.21.1.2">org.freedesktop.NetworkManager.Device.Team, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Team.top_of_page">org.freedesktop.NetworkManager.Device.Team</a> +<dt id="ientry-id-1.4.8.22.1.2">org.freedesktop.NetworkManager.Device.Team, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Team.top_of_page">org.freedesktop.NetworkManager.Device.Team</a> </dt> -<dt id="ientry-id-1.4.8.21.5.3.2">org.freedesktop.NetworkManager.Device.Team:Carrier, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.Carrier">The "Carrier" property</a> +<dt id="ientry-id-1.4.8.22.5.3.2">org.freedesktop.NetworkManager.Device.Team:Carrier, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.Carrier">The "Carrier" property</a> </dt> -<dt id="ientry-id-1.4.8.21.5.5.2">org.freedesktop.NetworkManager.Device.Team:Config, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.Config">The "Config" property</a> +<dt id="ientry-id-1.4.8.22.5.5.2">org.freedesktop.NetworkManager.Device.Team:Config, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.Config">The "Config" property</a> </dt> -<dt id="ientry-id-1.4.8.21.5.2.2">org.freedesktop.NetworkManager.Device.Team:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.22.5.2.2">org.freedesktop.NetworkManager.Device.Team:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.HwAddress">The "HwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.21.5.4.2">org.freedesktop.NetworkManager.Device.Team:Slaves, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.Slaves">The "Slaves" property</a> +<dt id="ientry-id-1.4.8.22.5.4.2">org.freedesktop.NetworkManager.Device.Team:Slaves, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Team.html#gdbus-property-org-freedesktop-NetworkManager-Device-Team.Slaves">The "Slaves" property</a> </dt> -<dt id="ientry-id-1.4.8.22.1.2">org.freedesktop.NetworkManager.Device.Tun, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Tun.top_of_page">org.freedesktop.NetworkManager.Device.Tun</a> +<dt id="ientry-id-1.4.8.23.1.2">org.freedesktop.NetworkManager.Device.Tun, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Tun.top_of_page">org.freedesktop.NetworkManager.Device.Tun</a> </dt> -<dt id="ientry-id-1.4.8.22.5.3.2">org.freedesktop.NetworkManager.Device.Tun:Group, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.Group">The "Group" property</a> +<dt id="ientry-id-1.4.8.23.5.3.2">org.freedesktop.NetworkManager.Device.Tun:Group, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.Group">The "Group" property</a> </dt> -<dt id="ientry-id-1.4.8.22.5.8.2">org.freedesktop.NetworkManager.Device.Tun:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.23.5.8.2">org.freedesktop.NetworkManager.Device.Tun:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.HwAddress">The "HwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.22.5.4.2">org.freedesktop.NetworkManager.Device.Tun:Mode, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.Mode">The "Mode" property</a> +<dt id="ientry-id-1.4.8.23.5.4.2">org.freedesktop.NetworkManager.Device.Tun:Mode, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.Mode">The "Mode" property</a> </dt> -<dt id="ientry-id-1.4.8.22.5.7.2">org.freedesktop.NetworkManager.Device.Tun:MultiQueue, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.MultiQueue">The "MultiQueue" property</a> +<dt id="ientry-id-1.4.8.23.5.7.2">org.freedesktop.NetworkManager.Device.Tun:MultiQueue, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.MultiQueue">The "MultiQueue" property</a> </dt> -<dt id="ientry-id-1.4.8.22.5.5.2">org.freedesktop.NetworkManager.Device.Tun:NoPi, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.NoPi">The "NoPi" property</a> +<dt id="ientry-id-1.4.8.23.5.5.2">org.freedesktop.NetworkManager.Device.Tun:NoPi, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.NoPi">The "NoPi" property</a> </dt> -<dt id="ientry-id-1.4.8.22.5.2.2">org.freedesktop.NetworkManager.Device.Tun:Owner, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.Owner">The "Owner" property</a> +<dt id="ientry-id-1.4.8.23.5.2.2">org.freedesktop.NetworkManager.Device.Tun:Owner, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.Owner">The "Owner" property</a> </dt> -<dt id="ientry-id-1.4.8.22.5.6.2">org.freedesktop.NetworkManager.Device.Tun:VnetHdr, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.VnetHdr">The "VnetHdr" property</a> +<dt id="ientry-id-1.4.8.23.5.6.2">org.freedesktop.NetworkManager.Device.Tun:VnetHdr, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Tun.html#gdbus-property-org-freedesktop-NetworkManager-Device-Tun.VnetHdr">The "VnetHdr" property</a> </dt> -<dt id="ientry-id-1.4.8.23.1.2">org.freedesktop.NetworkManager.Device.Veth, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Veth.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Veth.top_of_page">org.freedesktop.NetworkManager.Device.Veth</a> +<dt id="ientry-id-1.4.8.24.1.2">org.freedesktop.NetworkManager.Device.Veth, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Veth.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Veth.top_of_page">org.freedesktop.NetworkManager.Device.Veth</a> </dt> -<dt id="ientry-id-1.4.8.23.5.2.2">org.freedesktop.NetworkManager.Device.Veth:Peer, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Veth.html#gdbus-property-org-freedesktop-NetworkManager-Device-Veth.Peer">The "Peer" property</a> +<dt id="ientry-id-1.4.8.24.5.2.2">org.freedesktop.NetworkManager.Device.Veth:Peer, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Veth.html#gdbus-property-org-freedesktop-NetworkManager-Device-Veth.Peer">The "Peer" property</a> </dt> -<dt id="ientry-id-1.4.8.24.1.2">org.freedesktop.NetworkManager.Device.Vlan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Vlan.top_of_page">org.freedesktop.NetworkManager.Device.Vlan</a> +<dt id="ientry-id-1.4.8.25.1.2">org.freedesktop.NetworkManager.Device.Vlan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Vlan.top_of_page">org.freedesktop.NetworkManager.Device.Vlan</a> </dt> -<dt id="ientry-id-1.4.8.24.5.3.2">org.freedesktop.NetworkManager.Device.Vlan:Carrier, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.Carrier">The "Carrier" property</a> +<dt id="ientry-id-1.4.8.25.5.3.2">org.freedesktop.NetworkManager.Device.Vlan:Carrier, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.Carrier">The "Carrier" property</a> </dt> -<dt id="ientry-id-1.4.8.24.5.2.2">org.freedesktop.NetworkManager.Device.Vlan:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.25.5.2.2">org.freedesktop.NetworkManager.Device.Vlan:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.HwAddress">The "HwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.24.5.4.2">org.freedesktop.NetworkManager.Device.Vlan:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.Parent">The "Parent" property</a> +<dt id="ientry-id-1.4.8.25.5.4.2">org.freedesktop.NetworkManager.Device.Vlan:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.Parent">The "Parent" property</a> </dt> -<dt id="ientry-id-1.4.8.24.5.5.2">org.freedesktop.NetworkManager.Device.Vlan:VlanId, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.VlanId">The "VlanId" property</a> +<dt id="ientry-id-1.4.8.25.5.5.2">org.freedesktop.NetworkManager.Device.Vlan:VlanId, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vlan.VlanId">The "VlanId" property</a> </dt> -<dt id="ientry-id-1.4.8.25.1.2">org.freedesktop.NetworkManager.Device.Vrf, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vrf.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Vrf.top_of_page">org.freedesktop.NetworkManager.Device.Vrf</a> +<dt id="ientry-id-1.4.8.26.1.2">org.freedesktop.NetworkManager.Device.Vrf, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vrf.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Vrf.top_of_page">org.freedesktop.NetworkManager.Device.Vrf</a> </dt> -<dt id="ientry-id-1.4.8.25.5.2.2">org.freedesktop.NetworkManager.Device.Vrf:Table, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vrf.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vrf.Table">The "Table" property</a> +<dt id="ientry-id-1.4.8.26.5.2.2">org.freedesktop.NetworkManager.Device.Vrf:Table, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vrf.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vrf.Table">The "Table" property</a> </dt> -<dt id="ientry-id-1.4.8.26.1.2">org.freedesktop.NetworkManager.Device.Vxlan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Vxlan.top_of_page">org.freedesktop.NetworkManager.Device.Vxlan</a> +<dt id="ientry-id-1.4.8.27.1.2">org.freedesktop.NetworkManager.Device.Vxlan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Vxlan.top_of_page">org.freedesktop.NetworkManager.Device.Vxlan</a> </dt> -<dt id="ientry-id-1.4.8.26.5.10.2">org.freedesktop.NetworkManager.Device.Vxlan:Ageing, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Ageing">The "Ageing" property</a> +<dt id="ientry-id-1.4.8.27.5.10.2">org.freedesktop.NetworkManager.Device.Vxlan:Ageing, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Ageing">The "Ageing" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.12.2">org.freedesktop.NetworkManager.Device.Vxlan:DstPort, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.DstPort">The "DstPort" property</a> +<dt id="ientry-id-1.4.8.27.5.12.2">org.freedesktop.NetworkManager.Device.Vxlan:DstPort, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.DstPort">The "DstPort" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.5.2">org.freedesktop.NetworkManager.Device.Vxlan:Group, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Group">The "Group" property</a> +<dt id="ientry-id-1.4.8.27.5.5.2">org.freedesktop.NetworkManager.Device.Vxlan:Group, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Group">The "Group" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.3.2">org.freedesktop.NetworkManager.Device.Vxlan:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.27.5.3.2">org.freedesktop.NetworkManager.Device.Vxlan:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.HwAddress">The "HwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.4.2">org.freedesktop.NetworkManager.Device.Vxlan:Id, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Id">The "Id" property</a> +<dt id="ientry-id-1.4.8.27.5.4.2">org.freedesktop.NetworkManager.Device.Vxlan:Id, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Id">The "Id" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.17.2">org.freedesktop.NetworkManager.Device.Vxlan:L2miss, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.L2miss">The "L2miss" property</a> +<dt id="ientry-id-1.4.8.27.5.17.2">org.freedesktop.NetworkManager.Device.Vxlan:L2miss, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.L2miss">The "L2miss" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.18.2">org.freedesktop.NetworkManager.Device.Vxlan:L3miss, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.L3miss">The "L3miss" property</a> +<dt id="ientry-id-1.4.8.27.5.18.2">org.freedesktop.NetworkManager.Device.Vxlan:L3miss, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.L3miss">The "L3miss" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.9.2">org.freedesktop.NetworkManager.Device.Vxlan:Learning, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Learning">The "Learning" property</a> +<dt id="ientry-id-1.4.8.27.5.9.2">org.freedesktop.NetworkManager.Device.Vxlan:Learning, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Learning">The "Learning" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.11.2">org.freedesktop.NetworkManager.Device.Vxlan:Limit, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Limit">The "Limit" property</a> +<dt id="ientry-id-1.4.8.27.5.11.2">org.freedesktop.NetworkManager.Device.Vxlan:Limit, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Limit">The "Limit" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.6.2">org.freedesktop.NetworkManager.Device.Vxlan:Local, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Local">The "Local" property</a> +<dt id="ientry-id-1.4.8.27.5.6.2">org.freedesktop.NetworkManager.Device.Vxlan:Local, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Local">The "Local" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.2.2">org.freedesktop.NetworkManager.Device.Vxlan:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Parent">The "Parent" property</a> +<dt id="ientry-id-1.4.8.27.5.2.2">org.freedesktop.NetworkManager.Device.Vxlan:Parent, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Parent">The "Parent" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.15.2">org.freedesktop.NetworkManager.Device.Vxlan:Proxy, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Proxy">The "Proxy" property</a> +<dt id="ientry-id-1.4.8.27.5.15.2">org.freedesktop.NetworkManager.Device.Vxlan:Proxy, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Proxy">The "Proxy" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.16.2">org.freedesktop.NetworkManager.Device.Vxlan:Rsc, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Rsc">The "Rsc" property</a> +<dt id="ientry-id-1.4.8.27.5.16.2">org.freedesktop.NetworkManager.Device.Vxlan:Rsc, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Rsc">The "Rsc" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.14.2">org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMax, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.SrcPortMax">The "SrcPortMax" property</a> +<dt id="ientry-id-1.4.8.27.5.14.2">org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMax, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.SrcPortMax">The "SrcPortMax" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.13.2">org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMin, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.SrcPortMin">The "SrcPortMin" property</a> +<dt id="ientry-id-1.4.8.27.5.13.2">org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMin, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.SrcPortMin">The "SrcPortMin" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.7.2">org.freedesktop.NetworkManager.Device.Vxlan:Tos, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Tos">The "Tos" property</a> +<dt id="ientry-id-1.4.8.27.5.7.2">org.freedesktop.NetworkManager.Device.Vxlan:Tos, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Tos">The "Tos" property</a> </dt> -<dt id="ientry-id-1.4.8.26.5.8.2">org.freedesktop.NetworkManager.Device.Vxlan:Ttl, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Ttl">The "Ttl" property</a> +<dt id="ientry-id-1.4.8.27.5.8.2">org.freedesktop.NetworkManager.Device.Vxlan:Ttl, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Vxlan.Ttl">The "Ttl" property</a> </dt> -<dt id="ientry-id-1.4.8.28.1.2">org.freedesktop.NetworkManager.Device.WireGuard, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-interface-org-freedesktop-NetworkManager-Device-WireGuard.top_of_page">org.freedesktop.NetworkManager.Device.WireGuard</a> +<dt id="ientry-id-1.4.8.29.1.2">org.freedesktop.NetworkManager.Device.WireGuard, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-interface-org-freedesktop-NetworkManager-Device-WireGuard.top_of_page">org.freedesktop.NetworkManager.Device.WireGuard</a> </dt> -<dt id="ientry-id-1.4.8.28.5.4.2">org.freedesktop.NetworkManager.Device.WireGuard:FwMark, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-property-org-freedesktop-NetworkManager-Device-WireGuard.FwMark">The "FwMark" property</a> +<dt id="ientry-id-1.4.8.29.5.4.2">org.freedesktop.NetworkManager.Device.WireGuard:FwMark, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-property-org-freedesktop-NetworkManager-Device-WireGuard.FwMark">The "FwMark" property</a> </dt> -<dt id="ientry-id-1.4.8.28.5.3.2">org.freedesktop.NetworkManager.Device.WireGuard:ListenPort, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-property-org-freedesktop-NetworkManager-Device-WireGuard.ListenPort">The "ListenPort" property</a> +<dt id="ientry-id-1.4.8.29.5.3.2">org.freedesktop.NetworkManager.Device.WireGuard:ListenPort, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-property-org-freedesktop-NetworkManager-Device-WireGuard.ListenPort">The "ListenPort" property</a> </dt> -<dt id="ientry-id-1.4.8.28.5.2.2">org.freedesktop.NetworkManager.Device.WireGuard:PublicKey, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-property-org-freedesktop-NetworkManager-Device-WireGuard.PublicKey">The "PublicKey" property</a> +<dt id="ientry-id-1.4.8.29.5.2.2">org.freedesktop.NetworkManager.Device.WireGuard:PublicKey, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html#gdbus-property-org-freedesktop-NetworkManager-Device-WireGuard.PublicKey">The "PublicKey" property</a> </dt> -<dt id="ientry-id-1.4.8.31.1.2">org.freedesktop.NetworkManager.Device.Wpan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wpan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Wpan.top_of_page">org.freedesktop.NetworkManager.Device.Wpan</a> +<dt id="ientry-id-1.4.8.32.1.2">org.freedesktop.NetworkManager.Device.Wpan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wpan.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Wpan.top_of_page">org.freedesktop.NetworkManager.Device.Wpan</a> </dt> -<dt id="ientry-id-1.4.8.31.5.2.2">org.freedesktop.NetworkManager.Device.Wpan:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wpan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wpan.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.32.5.2.2">org.freedesktop.NetworkManager.Device.Wpan:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wpan.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wpan.HwAddress">The "HwAddress" property</a> </dt> <dt id="ientry-id-1.4.8.2.8.2.2">org.freedesktop.NetworkManager.Device::StateChanged, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.html#gdbus-signal-org-freedesktop-NetworkManager-Device.StateChanged">The "StateChanged" signal</a> </dt> @@ -515,6 +519,8 @@ </dt> <dt id="ientry-id-1.4.9.2.7.2.2">org.freedesktop.NetworkManager.Connection.Active:Connection, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Connection">The "Connection" property</a> </dt> +<dt id="ientry-id-1.4.9.2.7.17.2">org.freedesktop.NetworkManager.Connection.Active:Controller, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Controller">The "Controller" property</a> +</dt> <dt id="ientry-id-1.4.9.2.7.10.2">org.freedesktop.NetworkManager.Connection.Active:Default, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Default">The "Default" property</a> </dt> <dt id="ientry-id-1.4.9.2.7.13.2">org.freedesktop.NetworkManager.Connection.Active:Default6, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Default6">The "Default6" property</a> @@ -531,7 +537,7 @@ </dt> <dt id="ientry-id-1.4.9.2.7.14.2">org.freedesktop.NetworkManager.Connection.Active:Ip6Config, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Ip6Config">The "Ip6Config" property</a> </dt> -<dt id="ientry-id-1.4.9.2.7.17.2">org.freedesktop.NetworkManager.Connection.Active:Master, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Master">The "Master" property</a> +<dt id="ientry-id-1.4.9.2.7.18.2">org.freedesktop.NetworkManager.Connection.Active:Master, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.Master">The "Master" property</a> </dt> <dt id="ientry-id-1.4.9.2.7.3.2">org.freedesktop.NetworkManager.Connection.Active:SpecificObject, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Connection.Active.html#gdbus-property-org-freedesktop-NetworkManager-Connection-Active.SpecificObject">The "SpecificObject" property</a> </dt> @@ -589,6 +595,8 @@ </dt> <dt id="ientry-id-1.3.3.45.2.2.1.1.2.3.1.1.1">auto-negotiate, <a class="indexterm" href="settings-802-3-ethernet.html">802-3-ethernet</a> </dt> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.3.1.1.1">auto-route-ext-gw, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +</dt> <dt id="ientry-id-1.3.3.2.2.2.1.1.2.2.1.1.1">autoconnect, <a class="indexterm" href="settings-connection.html">connection</a> </dt> <dt id="ientry-id-1.3.3.2.2.2.1.1.2.3.1.1.1">autoconnect-priority, <a class="indexterm" href="settings-connection.html">connection</a> @@ -662,9 +670,9 @@ <div class="indexdiv"> <h3>D</h3> <dl> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.3.1.1.1">dad-timeout, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.4.1.1.1">dad-timeout, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.38.2.2.1.1.2.1.1.1.1">data, <a class="indexterm" href="settings-user.html">user</a>, <a class="indexterm" href="settings-vpn.html">vpn</a>, <a class="indexterm" href="settings-ovs-external-ids.html">ovs-external-ids</a> +<dt id="ientry-id-1.3.3.38.2.2.1.1.2.1.1.1.1">data, <a class="indexterm" href="settings-user.html">user</a>, <a class="indexterm" href="settings-vpn.html">vpn</a>, <a class="indexterm" href="settings-ovs-external-ids.html">ovs-external-ids</a>, <a class="indexterm" href="settings-ovs-other-config.html">ovs-other-config</a> </dt> <dt id="ientry-id-1.3.3.24.2.2.1.1.2.1.1.1.1">datapath-type, <a class="indexterm" href="settings-ovs-bridge.html">ovs-bridge</a> </dt> @@ -674,81 +682,81 @@ </dt> <dt id="ientry-id-1.3.3.15.2.2.1.1.2.3.1.1.1">device-id, <a class="indexterm" href="settings-gsm.html">gsm</a> </dt> -<dt id="ientry-id-1.4.8.29.1.2">org.freedesktop.NetworkManager.Device.Wired, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Wired.top_of_page">org.freedesktop.NetworkManager.Device.Wired</a> +<dt id="ientry-id-1.4.8.30.1.2">org.freedesktop.NetworkManager.Device.Wired, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Wired.top_of_page">org.freedesktop.NetworkManager.Device.Wired</a> </dt> -<dt id="ientry-id-1.4.8.29.5.6.2">org.freedesktop.NetworkManager.Device.Wired:Carrier, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.Carrier">The "Carrier" property</a> +<dt id="ientry-id-1.4.8.30.5.6.2">org.freedesktop.NetworkManager.Device.Wired:Carrier, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.Carrier">The "Carrier" property</a> </dt> -<dt id="ientry-id-1.4.8.29.5.2.2">org.freedesktop.NetworkManager.Device.Wired:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.30.5.2.2">org.freedesktop.NetworkManager.Device.Wired:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.HwAddress">The "HwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.29.5.3.2">org.freedesktop.NetworkManager.Device.Wired:PermHwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.PermHwAddress">The "PermHwAddress" property</a> +<dt id="ientry-id-1.4.8.30.5.3.2">org.freedesktop.NetworkManager.Device.Wired:PermHwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.PermHwAddress">The "PermHwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.29.5.5.2">org.freedesktop.NetworkManager.Device.Wired:S390Subchannels, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.S390Subchannels">The "S390Subchannels" property</a> +<dt id="ientry-id-1.4.8.30.5.5.2">org.freedesktop.NetworkManager.Device.Wired:S390Subchannels, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.S390Subchannels">The "S390Subchannels" property</a> </dt> -<dt id="ientry-id-1.4.8.29.5.4.2">org.freedesktop.NetworkManager.Device.Wired:Speed, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.Speed">The "Speed" property</a> +<dt id="ientry-id-1.4.8.30.5.4.2">org.freedesktop.NetworkManager.Device.Wired:Speed, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wired.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wired.Speed">The "Speed" property</a> </dt> -<dt id="ientry-id-1.4.8.30.1.2">org.freedesktop.NetworkManager.Device.Wireless, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Wireless.top_of_page">org.freedesktop.NetworkManager.Device.Wireless</a> +<dt id="ientry-id-1.4.8.31.1.2">org.freedesktop.NetworkManager.Device.Wireless, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-interface-org-freedesktop-NetworkManager-Device-Wireless.top_of_page">org.freedesktop.NetworkManager.Device.Wireless</a> </dt> -<dt id="ientry-id-1.4.8.30.7.2.2">org.freedesktop.NetworkManager.Device.Wireless.GetAccessPoints(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-method-org-freedesktop-NetworkManager-Device-Wireless.GetAccessPoints">The GetAccessPoints() method</a> +<dt id="ientry-id-1.4.8.31.7.2.2">org.freedesktop.NetworkManager.Device.Wireless.GetAccessPoints(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-method-org-freedesktop-NetworkManager-Device-Wireless.GetAccessPoints">The GetAccessPoints() method</a> </dt> -<dt id="ientry-id-1.4.8.30.7.3.2">org.freedesktop.NetworkManager.Device.Wireless.GetAllAccessPoints(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-method-org-freedesktop-NetworkManager-Device-Wireless.GetAllAccessPoints">The GetAllAccessPoints() method</a> +<dt id="ientry-id-1.4.8.31.7.3.2">org.freedesktop.NetworkManager.Device.Wireless.GetAllAccessPoints(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-method-org-freedesktop-NetworkManager-Device-Wireless.GetAllAccessPoints">The GetAllAccessPoints() method</a> </dt> -<dt id="ientry-id-1.4.8.30.7.4.2">org.freedesktop.NetworkManager.Device.Wireless.RequestScan(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-method-org-freedesktop-NetworkManager-Device-Wireless.RequestScan">The RequestScan() method</a> +<dt id="ientry-id-1.4.8.31.7.4.2">org.freedesktop.NetworkManager.Device.Wireless.RequestScan(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-method-org-freedesktop-NetworkManager-Device-Wireless.RequestScan">The RequestScan() method</a> </dt> -<dt id="ientry-id-1.4.8.30.8.2.2">org.freedesktop.NetworkManager.Device.Wireless::AccessPointAdded, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-signal-org-freedesktop-NetworkManager-Device-Wireless.AccessPointAdded">The "AccessPointAdded" signal</a> +<dt id="ientry-id-1.4.8.31.8.2.2">org.freedesktop.NetworkManager.Device.Wireless::AccessPointAdded, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-signal-org-freedesktop-NetworkManager-Device-Wireless.AccessPointAdded">The "AccessPointAdded" signal</a> </dt> -<dt id="ientry-id-1.4.8.30.8.3.2">org.freedesktop.NetworkManager.Device.Wireless::AccessPointRemoved, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-signal-org-freedesktop-NetworkManager-Device-Wireless.AccessPointRemoved">The "AccessPointRemoved" signal</a> +<dt id="ientry-id-1.4.8.31.8.3.2">org.freedesktop.NetworkManager.Device.Wireless::AccessPointRemoved, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-signal-org-freedesktop-NetworkManager-Device-Wireless.AccessPointRemoved">The "AccessPointRemoved" signal</a> </dt> -<dt id="ientry-id-1.4.8.30.9.6.2">org.freedesktop.NetworkManager.Device.Wireless:AccessPoints, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.AccessPoints">The "AccessPoints" property</a> +<dt id="ientry-id-1.4.8.31.9.6.2">org.freedesktop.NetworkManager.Device.Wireless:AccessPoints, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.AccessPoints">The "AccessPoints" property</a> </dt> -<dt id="ientry-id-1.4.8.30.9.7.2">org.freedesktop.NetworkManager.Device.Wireless:ActiveAccessPoint, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.ActiveAccessPoint">The "ActiveAccessPoint" property</a> +<dt id="ientry-id-1.4.8.31.9.7.2">org.freedesktop.NetworkManager.Device.Wireless:ActiveAccessPoint, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.ActiveAccessPoint">The "ActiveAccessPoint" property</a> </dt> -<dt id="ientry-id-1.4.8.30.9.5.2">org.freedesktop.NetworkManager.Device.Wireless:Bitrate, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.Bitrate">The "Bitrate" property</a> +<dt id="ientry-id-1.4.8.31.9.5.2">org.freedesktop.NetworkManager.Device.Wireless:Bitrate, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.Bitrate">The "Bitrate" property</a> </dt> -<dt id="ientry-id-1.4.8.30.9.2.2">org.freedesktop.NetworkManager.Device.Wireless:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.31.9.2.2">org.freedesktop.NetworkManager.Device.Wireless:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.HwAddress">The "HwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.30.9.9.2">org.freedesktop.NetworkManager.Device.Wireless:LastScan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.LastScan">The "LastScan" property</a> +<dt id="ientry-id-1.4.8.31.9.9.2">org.freedesktop.NetworkManager.Device.Wireless:LastScan, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.LastScan">The "LastScan" property</a> </dt> -<dt id="ientry-id-1.4.8.30.9.4.2">org.freedesktop.NetworkManager.Device.Wireless:Mode, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.Mode">The "Mode" property</a> +<dt id="ientry-id-1.4.8.31.9.4.2">org.freedesktop.NetworkManager.Device.Wireless:Mode, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.Mode">The "Mode" property</a> </dt> -<dt id="ientry-id-1.4.8.30.9.3.2">org.freedesktop.NetworkManager.Device.Wireless:PermHwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.PermHwAddress">The "PermHwAddress" property</a> +<dt id="ientry-id-1.4.8.31.9.3.2">org.freedesktop.NetworkManager.Device.Wireless:PermHwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.PermHwAddress">The "PermHwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.30.9.8.2">org.freedesktop.NetworkManager.Device.Wireless:WirelessCapabilities, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.WirelessCapabilities">The "WirelessCapabilities" property</a> +<dt id="ientry-id-1.4.8.31.9.8.2">org.freedesktop.NetworkManager.Device.Wireless:WirelessCapabilities, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.Wireless.html#gdbus-property-org-freedesktop-NetworkManager-Device-Wireless.WirelessCapabilities">The "WirelessCapabilities" property</a> </dt> -<dt id="ientry-id-1.4.8.27.1.2">org.freedesktop.NetworkManager.Device.WifiP2P, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-interface-org-freedesktop-NetworkManager-Device-WifiP2P.top_of_page">org.freedesktop.NetworkManager.Device.WifiP2P</a> +<dt id="ientry-id-1.4.8.28.1.2">org.freedesktop.NetworkManager.Device.WifiP2P, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-interface-org-freedesktop-NetworkManager-Device-WifiP2P.top_of_page">org.freedesktop.NetworkManager.Device.WifiP2P</a> </dt> -<dt id="ientry-id-1.4.8.27.7.2.2">org.freedesktop.NetworkManager.Device.WifiP2P.StartFind(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-method-org-freedesktop-NetworkManager-Device-WifiP2P.StartFind">The StartFind() method</a> +<dt id="ientry-id-1.4.8.28.7.2.2">org.freedesktop.NetworkManager.Device.WifiP2P.StartFind(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-method-org-freedesktop-NetworkManager-Device-WifiP2P.StartFind">The StartFind() method</a> </dt> -<dt id="ientry-id-1.4.8.27.7.3.2">org.freedesktop.NetworkManager.Device.WifiP2P.StopFind(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-method-org-freedesktop-NetworkManager-Device-WifiP2P.StopFind">The StopFind() method</a> +<dt id="ientry-id-1.4.8.28.7.3.2">org.freedesktop.NetworkManager.Device.WifiP2P.StopFind(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-method-org-freedesktop-NetworkManager-Device-WifiP2P.StopFind">The StopFind() method</a> </dt> -<dt id="ientry-id-1.4.8.27.8.2.2">org.freedesktop.NetworkManager.Device.WifiP2P::PeerAdded, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-signal-org-freedesktop-NetworkManager-Device-WifiP2P.PeerAdded">The "PeerAdded" signal</a> +<dt id="ientry-id-1.4.8.28.8.2.2">org.freedesktop.NetworkManager.Device.WifiP2P::PeerAdded, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-signal-org-freedesktop-NetworkManager-Device-WifiP2P.PeerAdded">The "PeerAdded" signal</a> </dt> -<dt id="ientry-id-1.4.8.27.8.3.2">org.freedesktop.NetworkManager.Device.WifiP2P::PeerRemoved, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-signal-org-freedesktop-NetworkManager-Device-WifiP2P.PeerRemoved">The "PeerRemoved" signal</a> +<dt id="ientry-id-1.4.8.28.8.3.2">org.freedesktop.NetworkManager.Device.WifiP2P::PeerRemoved, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-signal-org-freedesktop-NetworkManager-Device-WifiP2P.PeerRemoved">The "PeerRemoved" signal</a> </dt> -<dt id="ientry-id-1.4.8.27.9.2.2">org.freedesktop.NetworkManager.Device.WifiP2P:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-property-org-freedesktop-NetworkManager-Device-WifiP2P.HwAddress">The "HwAddress" property</a> +<dt id="ientry-id-1.4.8.28.9.2.2">org.freedesktop.NetworkManager.Device.WifiP2P:HwAddress, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-property-org-freedesktop-NetworkManager-Device-WifiP2P.HwAddress">The "HwAddress" property</a> </dt> -<dt id="ientry-id-1.4.8.27.9.3.2">org.freedesktop.NetworkManager.Device.WifiP2P:Peers, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-property-org-freedesktop-NetworkManager-Device-WifiP2P.Peers">The "Peers" property</a> +<dt id="ientry-id-1.4.8.28.9.3.2">org.freedesktop.NetworkManager.Device.WifiP2P:Peers, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html#gdbus-property-org-freedesktop-NetworkManager-Device-WifiP2P.Peers">The "Peers" property</a> </dt> <dt id="ientry-id-1.3.3.23.2.2.1.1.2.2.1.1.1">dhcp-anycast-address, <a class="indexterm" href="settings-802-11-olpc-mesh.html">802-11-olpc-mesh</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.4.1.1.1">dhcp-client-id, <a class="indexterm" href="settings-ipv4.html">ipv4</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.5.1.1.1">dhcp-client-id, <a class="indexterm" href="settings-ipv4.html">ipv4</a> </dt> -<dt id="ientry-id-1.3.3.18.2.2.1.1.2.5.1.1.1">dhcp-duid, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.18.2.2.1.1.2.6.1.1.1">dhcp-duid, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.5.1.1.1">dhcp-fqdn, <a class="indexterm" href="settings-ipv4.html">ipv4</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.6.1.1.1">dhcp-fqdn, <a class="indexterm" href="settings-ipv4.html">ipv4</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.6.1.1.1">dhcp-hostname, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.7.1.1.1">dhcp-hostname, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.7.1.1.1">dhcp-hostname-flags, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.8.1.1.1">dhcp-hostname-flags, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.8.1.1.1">dhcp-iaid, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.9.1.1.1">dhcp-iaid, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.9.1.1.1">dhcp-reject-servers, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.10.1.1.1">dhcp-reject-servers, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.10.1.1.1">dhcp-send-hostname, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.11.1.1.1">dhcp-send-hostname, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.11.1.1.1">dhcp-timeout, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.12.1.1.1">dhcp-timeout, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.12.1.1.1">dhcp-vendor-class-identifier, <a class="indexterm" href="settings-ipv4.html">ipv4</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.13.1.1.1">dhcp-vendor-class-identifier, <a class="indexterm" href="settings-ipv4.html">ipv4</a> </dt> <dt id="ientry-id-1.4.12.2.1.2">org.freedesktop.NetworkManager.DHCP4Config, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.DHCP4Config.html#gdbus-interface-org-freedesktop-NetworkManager-DHCP4Config.top_of_page">org.freedesktop.NetworkManager.DHCP4Config</a> </dt> @@ -758,15 +766,17 @@ </dt> <dt id="ientry-id-1.4.13.2.5.2.2">org.freedesktop.NetworkManager.DHCP6Config:Options, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.DHCP6Config.html#gdbus-property-org-freedesktop-NetworkManager-DHCP6Config.Options">The "Options" property</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.13.1.1.1">dns, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.14.1.1.1">dns, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.14.1.1.1">dns-options, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.15.1.1.1">dns-data, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +</dt> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.16.1.1.1">dns-options, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> <dt id="ientry-id-1.3.3.2.2.2.1.1.2.6.1.1.1">dns-over-tls, <a class="indexterm" href="settings-connection.html">connection</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.15.1.1.1">dns-priority, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.17.1.1.1">dns-priority, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.16.1.1.1">dns-search, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.18.1.1.1">dns-search, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> <dt id="ientry-id-1.3.3.4.2.2.1.1.2.11.1.1.1">domain-match, <a class="indexterm" href="settings-802-1x.html">802-1x</a> </dt> @@ -810,14 +820,14 @@ </dt> <dt id="ientry-id-1.3.3.51.2.2.1.1.2.2.1.1.1">from-dns-lookup, <a class="indexterm" href="settings-hostname.html">hostname</a> </dt> -<dt id="ientry-id-1.3.3.46.2.2.1.1.2.1.1.1.1">fwmark, <a class="indexterm" href="settings-wireguard.html">wireguard</a> +<dt id="ientry-id-1.3.3.19.2.2.1.1.2.4.1.1.1">fwmark, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-wireguard.html">wireguard</a> </dt> </dl> </div> <div class="indexdiv"> <h3>G</h3> <dl> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.17.1.1.1">gateway, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.19.1.1.1">gateway, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> <dt id="ientry-id-1.3.3.2.2.2.1.1.2.7.1.1.1">gateway-ping-timeout, <a class="indexterm" href="settings-connection.html">connection</a> </dt> @@ -851,13 +861,13 @@ </dt> <dt id="ientry-id-1.3.3.4.2.2.1.1.2.14.1.1.1">identity, <a class="indexterm" href="settings-802-1x.html">802-1x</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.18.1.1.1">ignore-auto-dns, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.20.1.1.1">ignore-auto-dns, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.19.1.1.1">ignore-auto-routes, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.21.1.1.1">ignore-auto-routes, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> <dt id="ientry-id-1.3.3.39.2.2.1.1.2.4.1.1.1">ingress-priority-map, <a class="indexterm" href="settings-vlan.html">vlan</a> </dt> -<dt id="ientry-id-1.3.3.19.2.2.1.1.2.4.1.1.1">input-key, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a> +<dt id="ientry-id-1.3.3.19.2.2.1.1.2.5.1.1.1">input-key, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a> </dt> <dt id="ientry-id-1.3.3.2.2.2.1.1.2.9.1.1.1">interface-name, <a class="indexterm" href="settings-connection.html">connection</a>, <a class="indexterm" href="settings-bond.html">bond</a>, <a class="indexterm" href="settings-bridge.html">bridge</a>, <a class="indexterm" href="settings-match.html">match</a>, <a class="indexterm" href="settings-team.html">team</a>, <a class="indexterm" href="settings-vlan.html">vlan</a> </dt> @@ -865,7 +875,7 @@ </dt> <dt id="ientry-id-1.3.3.46.2.2.1.1.2.3.1.1.1">ip6-auto-default-route, <a class="indexterm" href="settings-wireguard.html">wireguard</a> </dt> -<dt id="ientry-id-1.3.3.18.2.2.1.1.2.19.1.1.1">ip6-privacy, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.18.2.2.1.1.2.21.1.1.1">ip6-privacy, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> </dl> </div> @@ -905,7 +915,7 @@ </dt> <dt id="ientry-id-1.3.3.42.2.2.1.1.2.7.1.1.1">limit, <a class="indexterm" href="settings-vxlan.html">vxlan</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.20.1.1.1">link-local, <a class="indexterm" href="settings-ipv4.html">ipv4</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.22.1.1.1">link-local, <a class="indexterm" href="settings-ipv4.html">ipv4</a> </dt> <dt id="ientry-id-1.3.3.35.2.2.1.1.2.3.1.1.1">link-watchers, <a class="indexterm" href="settings-team.html">team</a>, <a class="indexterm" href="settings-team-port.html">team-port</a> </dt> @@ -915,7 +925,7 @@ </dt> <dt id="ientry-id-1.3.3.2.2.2.1.1.2.11.1.1.1">llmnr, <a class="indexterm" href="settings-connection.html">connection</a> </dt> -<dt id="ientry-id-1.3.3.19.2.2.1.1.2.5.1.1.1">local, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-vxlan.html">vxlan</a> +<dt id="ientry-id-1.3.3.19.2.2.1.1.2.6.1.1.1">local, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-vxlan.html">vxlan</a> </dt> </dl> </div> @@ -982,21 +992,21 @@ </dt> <dt id="ientry-id-1.4.3.2.9.3.2">org.freedesktop.NetworkManager:AllDevices, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.AllDevices">The "AllDevices" property</a> </dt> -<dt id="ientry-id-1.4.3.2.9.20.2">org.freedesktop.NetworkManager:Capabilities, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Capabilities">The "Capabilities" property</a> +<dt id="ientry-id-1.4.3.2.9.21.2">org.freedesktop.NetworkManager:Capabilities, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Capabilities">The "Capabilities" property</a> </dt> <dt id="ientry-id-1.4.3.2.9.4.2">org.freedesktop.NetworkManager:Checkpoints, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Checkpoints">The "Checkpoints" property</a> </dt> -<dt id="ientry-id-1.4.3.2.9.22.2">org.freedesktop.NetworkManager:Connectivity, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Connectivity">The "Connectivity" property</a> +<dt id="ientry-id-1.4.3.2.9.23.2">org.freedesktop.NetworkManager:Connectivity, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Connectivity">The "Connectivity" property</a> </dt> -<dt id="ientry-id-1.4.3.2.9.23.2">org.freedesktop.NetworkManager:ConnectivityCheckAvailable, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.ConnectivityCheckAvailable">The "ConnectivityCheckAvailable" property</a> +<dt id="ientry-id-1.4.3.2.9.24.2">org.freedesktop.NetworkManager:ConnectivityCheckAvailable, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.ConnectivityCheckAvailable">The "ConnectivityCheckAvailable" property</a> </dt> -<dt id="ientry-id-1.4.3.2.9.24.2">org.freedesktop.NetworkManager:ConnectivityCheckEnabled, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.ConnectivityCheckEnabled">The "ConnectivityCheckEnabled" property</a> +<dt id="ientry-id-1.4.3.2.9.25.2">org.freedesktop.NetworkManager:ConnectivityCheckEnabled, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.ConnectivityCheckEnabled">The "ConnectivityCheckEnabled" property</a> </dt> -<dt id="ientry-id-1.4.3.2.9.25.2">org.freedesktop.NetworkManager:ConnectivityCheckUri, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.ConnectivityCheckUri">The "ConnectivityCheckUri" property</a> +<dt id="ientry-id-1.4.3.2.9.26.2">org.freedesktop.NetworkManager:ConnectivityCheckUri, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.ConnectivityCheckUri">The "ConnectivityCheckUri" property</a> </dt> <dt id="ientry-id-1.4.3.2.9.2.2">org.freedesktop.NetworkManager:Devices, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Devices">The "Devices" property</a> </dt> -<dt id="ientry-id-1.4.3.2.9.26.2">org.freedesktop.NetworkManager:GlobalDnsConfiguration, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.GlobalDnsConfiguration">The "GlobalDnsConfiguration" property</a> +<dt id="ientry-id-1.4.3.2.9.27.2">org.freedesktop.NetworkManager:GlobalDnsConfiguration, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.GlobalDnsConfiguration">The "GlobalDnsConfiguration" property</a> </dt> <dt id="ientry-id-1.4.3.2.9.16.2">org.freedesktop.NetworkManager:Metered, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Metered">The "Metered" property</a> </dt> @@ -1010,10 +1020,12 @@ </dt> <dt id="ientry-id-1.4.3.2.9.18.2">org.freedesktop.NetworkManager:Startup, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Startup">The "Startup" property</a> </dt> -<dt id="ientry-id-1.4.3.2.9.21.2">org.freedesktop.NetworkManager:State, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.State">The "State" property</a> +<dt id="ientry-id-1.4.3.2.9.22.2">org.freedesktop.NetworkManager:State, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.State">The "State" property</a> </dt> <dt id="ientry-id-1.4.3.2.9.19.2">org.freedesktop.NetworkManager:Version, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.Version">The "Version" property</a> </dt> +<dt id="ientry-id-1.4.3.2.9.20.2">org.freedesktop.NetworkManager:VersionInfo, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.VersionInfo">The "VersionInfo" property</a> +</dt> <dt id="ientry-id-1.4.3.2.9.10.2">org.freedesktop.NetworkManager:WimaxEnabled, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.WimaxEnabled">The "WimaxEnabled" property</a> </dt> <dt id="ientry-id-1.4.3.2.9.11.2">org.freedesktop.NetworkManager:WimaxHardwareEnabled, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.html#gdbus-property-org-freedesktop-NetworkManager.WimaxHardwareEnabled">The "WimaxHardwareEnabled" property</a> @@ -1030,7 +1042,7 @@ </dt> <dt id="ientry-id-1.3.3.8.2.2.1.1.2.8.1.1.1">max-age, <a class="indexterm" href="settings-bridge.html">bridge</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.21.1.1.1">may-fail, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.23.1.1.1">may-fail, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> <dt id="ientry-id-1.3.3.35.2.2.1.1.2.4.1.1.1">mcast-rejoin-count, <a class="indexterm" href="settings-team.html">team</a> </dt> @@ -1042,7 +1054,7 @@ </dt> <dt id="ientry-id-1.3.3.2.2.2.1.1.2.14.1.1.1">metered, <a class="indexterm" href="settings-connection.html">connection</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.22.1.1.1">method, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a>, <a class="indexterm" href="settings-proxy.html">proxy</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.24.1.1.1">method, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a>, <a class="indexterm" href="settings-proxy.html">proxy</a> </dt> <dt id="ientry-id-1.3.3.20.2.2.1.1.2.2.1.1.1">mka-cak, <a class="indexterm" href="settings-macsec.html">macsec</a> </dt> @@ -1050,7 +1062,7 @@ </dt> <dt id="ientry-id-1.3.3.20.2.2.1.1.2.4.1.1.1">mka-ckn, <a class="indexterm" href="settings-macsec.html">macsec</a> </dt> -<dt id="ientry-id-1.3.3.19.2.2.1.1.2.6.1.1.1">mode, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-macsec.html">macsec</a>, <a class="indexterm" href="settings-macvlan.html">macvlan</a>, <a class="indexterm" href="settings-tun.html">tun</a>, <a class="indexterm" href="settings-802-11-wireless.html">802-11-wireless</a> +<dt id="ientry-id-1.3.3.19.2.2.1.1.2.7.1.1.1">mode, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-macsec.html">macsec</a>, <a class="indexterm" href="settings-macvlan.html">macvlan</a>, <a class="indexterm" href="settings-tun.html">tun</a>, <a class="indexterm" href="settings-802-11-wireless.html">802-11-wireless</a> </dt> <dt id="ientry-id-1.3.3.29.2.2.1.1.2.5.1.1.1">mppe-stateful, <a class="indexterm" href="settings-ppp.html">ppp</a> </dt> @@ -1058,7 +1070,7 @@ </dt> <dt id="ientry-id-1.3.3.29.2.2.1.1.2.6.1.1.1">mru, <a class="indexterm" href="settings-ppp.html">ppp</a> </dt> -<dt id="ientry-id-1.3.3.10.2.2.1.1.2.1.1.1.1">mtu, <a class="indexterm" href="settings-cdma.html">cdma</a>, <a class="indexterm" href="settings-gsm.html">gsm</a>, <a class="indexterm" href="settings-infiniband.html">infiniband</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a>, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-ppp.html">ppp</a>, <a class="indexterm" href="settings-802-3-ethernet.html">802-3-ethernet</a>, <a class="indexterm" href="settings-wireguard.html">wireguard</a>, <a class="indexterm" href="settings-802-11-wireless.html">802-11-wireless</a> +<dt id="ientry-id-1.3.3.10.2.2.1.1.2.1.1.1.1">mtu, <a class="indexterm" href="settings-cdma.html">cdma</a>, <a class="indexterm" href="settings-gsm.html">gsm</a>, <a class="indexterm" href="settings-infiniband.html">infiniband</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a>, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-ppp.html">ppp</a>, <a class="indexterm" href="settings-802-3-ethernet.html">802-3-ethernet</a>, <a class="indexterm" href="settings-wireguard.html">wireguard</a>, <a class="indexterm" href="settings-802-11-wireless.html">802-11-wireless</a>, <a class="indexterm" href="settings-loopback.html">loopback</a> </dt> <dt id="ientry-id-1.3.3.2.2.2.1.1.2.16.1.1.1">mud-url, <a class="indexterm" href="settings-connection.html">connection</a> </dt> @@ -1099,79 +1111,85 @@ <dl> <dt id="ientry-id-1.3.3.25.2.2.1.1.2.2.1.1.1">n-rxq, <a class="indexterm" href="settings-ovs-dpdk.html">ovs-dpdk</a> </dt> +<dt id="ientry-id-1.3.3.25.2.2.1.1.2.3.1.1.1">n-rxq-desc, <a class="indexterm" href="settings-ovs-dpdk.html">ovs-dpdk</a> +</dt> +<dt id="ientry-id-1.3.3.25.2.2.1.1.2.4.1.1.1">n-txq-desc, <a class="indexterm" href="settings-ovs-dpdk.html">ovs-dpdk</a> +</dt> <dt id="ientry-id-1.3.3.15.2.2.1.1.2.6.1.1.1">network-id, <a class="indexterm" href="settings-gsm.html">gsm</a> </dt> <dt id="ientry-id-1.3.3.44.2.2.1.1.2.2.1.1.1">network-name, <a class="indexterm" href="settings-wimax.html">wimax</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.23.1.1.1">never-default, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.25.1.1.1">never-default, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +</dt> +<dt id="ientry-id-1.4.17.2.10.2">NM80211ApFlags, <a class="indexterm" href="nm-dbus-types.html#NM80211ApFlags">enum NM80211ApFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.9.2">NM80211ApFlags, <a class="indexterm" href="nm-dbus-types.html#NM80211ApFlags">enum NM80211ApFlags</a> +<dt id="ientry-id-1.4.17.2.11.2">NM80211ApSecurityFlags, <a class="indexterm" href="nm-dbus-types.html#NM80211ApSecurityFlags">enum NM80211ApSecurityFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.10.2">NM80211ApSecurityFlags, <a class="indexterm" href="nm-dbus-types.html#NM80211ApSecurityFlags">enum NM80211ApSecurityFlags</a> +<dt id="ientry-id-1.4.17.2.12.2">NM80211Mode, <a class="indexterm" href="nm-dbus-types.html#NM80211Mode">enum NM80211Mode</a> </dt> -<dt id="ientry-id-1.4.17.2.11.2">NM80211Mode, <a class="indexterm" href="nm-dbus-types.html#NM80211Mode">enum NM80211Mode</a> +<dt id="ientry-id-1.4.17.2.28.2">NMActivationStateFlags, <a class="indexterm" href="nm-dbus-types.html#NMActivationStateFlags">enum NMActivationStateFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.27.2">NMActivationStateFlags, <a class="indexterm" href="nm-dbus-types.html#NMActivationStateFlags">enum NMActivationStateFlags</a> +<dt id="ientry-id-1.4.17.2.20.2">NMActiveConnectionState, <a class="indexterm" href="nm-dbus-types.html#NMActiveConnectionState">enum NMActiveConnectionState</a> </dt> -<dt id="ientry-id-1.4.17.2.19.2">NMActiveConnectionState, <a class="indexterm" href="nm-dbus-types.html#NMActiveConnectionState">enum NMActiveConnectionState</a> +<dt id="ientry-id-1.4.17.2.21.2">NMActiveConnectionStateReason, <a class="indexterm" href="nm-dbus-types.html#NMActiveConnectionStateReason">enum NMActiveConnectionStateReason</a> </dt> -<dt id="ientry-id-1.4.17.2.20.2">NMActiveConnectionStateReason, <a class="indexterm" href="nm-dbus-types.html#NMActiveConnectionStateReason">enum NMActiveConnectionStateReason</a> +<dt id="ientry-id-1.4.17.2.13.2">NMBluetoothCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMBluetoothCapabilities">enum NMBluetoothCapabilities</a> </dt> -<dt id="ientry-id-1.4.17.2.12.2">NMBluetoothCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMBluetoothCapabilities">enum NMBluetoothCapabilities</a> +<dt id="ientry-id-1.4.17.2.4.2">NMCapability, <a class="indexterm" href="nm-dbus-types.html#NMCapability">enum NMCapability</a> </dt> -<dt id="ientry-id-1.4.17.2.3.2">NMCapability, <a class="indexterm" href="nm-dbus-types.html#NMCapability">enum NMCapability</a> +<dt id="ientry-id-1.4.17.2.25.2">NMCheckpointCreateFlags, <a class="indexterm" href="nm-dbus-types.html#NMCheckpointCreateFlags">enum NMCheckpointCreateFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.24.2">NMCheckpointCreateFlags, <a class="indexterm" href="nm-dbus-types.html#NMCheckpointCreateFlags">enum NMCheckpointCreateFlags</a> +<dt id="ientry-id-1.4.17.2.35.2">NMClientPermission, <a class="indexterm" href="nm-dbus-types.html#NMClientPermission">enum NMClientPermission</a> </dt> -<dt id="ientry-id-1.4.17.2.34.2">NMClientPermission, <a class="indexterm" href="nm-dbus-types.html#NMClientPermission">enum NMClientPermission</a> +<dt id="ientry-id-1.4.17.2.36.2">NMClientPermissionResult, <a class="indexterm" href="nm-dbus-types.html#NMClientPermissionResult">enum NMClientPermissionResult</a> </dt> -<dt id="ientry-id-1.4.17.2.35.2">NMClientPermissionResult, <a class="indexterm" href="nm-dbus-types.html#NMClientPermissionResult">enum NMClientPermissionResult</a> +<dt id="ientry-id-1.4.17.2.19.2">NMConnectionMultiConnect, <a class="indexterm" href="nm-dbus-types.html#NMConnectionMultiConnect">enum NMConnectionMultiConnect</a> </dt> -<dt id="ientry-id-1.4.17.2.18.2">NMConnectionMultiConnect, <a class="indexterm" href="nm-dbus-types.html#NMConnectionMultiConnect">enum NMConnectionMultiConnect</a> +<dt id="ientry-id-1.4.17.2.6.2">NMConnectivityState, <a class="indexterm" href="nm-dbus-types.html#NMConnectivityState">enum NMConnectivityState</a> </dt> -<dt id="ientry-id-1.4.17.2.5.2">NMConnectivityState, <a class="indexterm" href="nm-dbus-types.html#NMConnectivityState">enum NMConnectivityState</a> +<dt id="ientry-id-1.4.17.2.8.2">NMDeviceCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMDeviceCapabilities">enum NMDeviceCapabilities</a> </dt> -<dt id="ientry-id-1.4.17.2.7.2">NMDeviceCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMDeviceCapabilities">enum NMDeviceCapabilities</a> +<dt id="ientry-id-1.4.17.2.34.2">NMDeviceInterfaceFlags, <a class="indexterm" href="nm-dbus-types.html#NMDeviceInterfaceFlags">enum NMDeviceInterfaceFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.33.2">NMDeviceInterfaceFlags, <a class="indexterm" href="nm-dbus-types.html#NMDeviceInterfaceFlags">enum NMDeviceInterfaceFlags</a> +<dt id="ientry-id-1.4.17.2.14.2">NMDeviceModemCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMDeviceModemCapabilities">enum NMDeviceModemCapabilities</a> </dt> -<dt id="ientry-id-1.4.17.2.13.2">NMDeviceModemCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMDeviceModemCapabilities">enum NMDeviceModemCapabilities</a> +<dt id="ientry-id-1.4.17.2.31.2">NMDeviceReapplyFlags, <a class="indexterm" href="nm-dbus-types.html#NMDeviceReapplyFlags">enum NMDeviceReapplyFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.30.2">NMDeviceReapplyFlags, <a class="indexterm" href="nm-dbus-types.html#NMDeviceReapplyFlags">enum NMDeviceReapplyFlags</a> +<dt id="ientry-id-1.4.17.2.16.2">NMDeviceState, <a class="indexterm" href="nm-dbus-types.html#NMDeviceState">enum NMDeviceState</a> </dt> -<dt id="ientry-id-1.4.17.2.15.2">NMDeviceState, <a class="indexterm" href="nm-dbus-types.html#NMDeviceState">enum NMDeviceState</a> +<dt id="ientry-id-1.4.17.2.17.2">NMDeviceStateReason, <a class="indexterm" href="nm-dbus-types.html#NMDeviceStateReason">enum NMDeviceStateReason</a> </dt> -<dt id="ientry-id-1.4.17.2.16.2">NMDeviceStateReason, <a class="indexterm" href="nm-dbus-types.html#NMDeviceStateReason">enum NMDeviceStateReason</a> +<dt id="ientry-id-1.4.17.2.7.2">NMDeviceType, <a class="indexterm" href="nm-dbus-types.html#NMDeviceType">enum NMDeviceType</a> </dt> -<dt id="ientry-id-1.4.17.2.6.2">NMDeviceType, <a class="indexterm" href="nm-dbus-types.html#NMDeviceType">enum NMDeviceType</a> +<dt id="ientry-id-1.4.17.2.9.2">NMDeviceWifiCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMDeviceWifiCapabilities">enum NMDeviceWifiCapabilities</a> </dt> -<dt id="ientry-id-1.4.17.2.8.2">NMDeviceWifiCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMDeviceWifiCapabilities">enum NMDeviceWifiCapabilities</a> +<dt id="ientry-id-1.4.17.2.24.2">NMIPTunnelMode, <a class="indexterm" href="nm-dbus-types.html#NMIPTunnelMode">enum NMIPTunnelMode</a> </dt> -<dt id="ientry-id-1.4.17.2.23.2">NMIPTunnelMode, <a class="indexterm" href="nm-dbus-types.html#NMIPTunnelMode">enum NMIPTunnelMode</a> +<dt id="ientry-id-1.4.17.2.33.2">NMManagerReloadFlags, <a class="indexterm" href="nm-dbus-types.html#NMManagerReloadFlags">enum NMManagerReloadFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.32.2">NMManagerReloadFlags, <a class="indexterm" href="nm-dbus-types.html#NMManagerReloadFlags">enum NMManagerReloadFlags</a> +<dt id="ientry-id-1.4.17.2.18.2">NMMetered, <a class="indexterm" href="nm-dbus-types.html#NMMetered">enum NMMetered</a> </dt> -<dt id="ientry-id-1.4.17.2.17.2">NMMetered, <a class="indexterm" href="nm-dbus-types.html#NMMetered">enum NMMetered</a> +<dt id="ientry-id-1.4.17.2.38.2">NMMptcpFlags, <a class="indexterm" href="nm-dbus-types.html#NMMptcpFlags">enum NMMptcpFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.37.2">NMMptcpFlags, <a class="indexterm" href="nm-dbus-types.html#NMMptcpFlags">enum NMMptcpFlags</a> +<dt id="ientry-id-1.4.17.2.37.2">NMRadioFlags, <a class="indexterm" href="nm-dbus-types.html#NMRadioFlags">enum NMRadioFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.36.2">NMRadioFlags, <a class="indexterm" href="nm-dbus-types.html#NMRadioFlags">enum NMRadioFlags</a> +<dt id="ientry-id-1.4.17.2.26.2">NMRollbackResult, <a class="indexterm" href="nm-dbus-types.html#NMRollbackResult">enum NMRollbackResult</a> </dt> -<dt id="ientry-id-1.4.17.2.25.2">NMRollbackResult, <a class="indexterm" href="nm-dbus-types.html#NMRollbackResult">enum NMRollbackResult</a> +<dt id="ientry-id-1.4.17.2.23.2">NMSecretAgentCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMSecretAgentCapabilities">enum NMSecretAgentCapabilities</a> </dt> -<dt id="ientry-id-1.4.17.2.22.2">NMSecretAgentCapabilities, <a class="indexterm" href="nm-dbus-types.html#NMSecretAgentCapabilities">enum NMSecretAgentCapabilities</a> +<dt id="ientry-id-1.4.17.2.22.2">NMSecretAgentGetSecretsFlags, <a class="indexterm" href="nm-dbus-types.html#NMSecretAgentGetSecretsFlags">enum NMSecretAgentGetSecretsFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.21.2">NMSecretAgentGetSecretsFlags, <a class="indexterm" href="nm-dbus-types.html#NMSecretAgentGetSecretsFlags">enum NMSecretAgentGetSecretsFlags</a> +<dt id="ientry-id-1.4.17.2.29.2">NMSettingsAddConnection2Flags, <a class="indexterm" href="nm-dbus-types.html#NMSettingsAddConnection2Flags">enum NMSettingsAddConnection2Flags</a> </dt> -<dt id="ientry-id-1.4.17.2.28.2">NMSettingsAddConnection2Flags, <a class="indexterm" href="nm-dbus-types.html#NMSettingsAddConnection2Flags">enum NMSettingsAddConnection2Flags</a> +<dt id="ientry-id-1.4.17.2.27.2">NMSettingsConnectionFlags, <a class="indexterm" href="nm-dbus-types.html#NMSettingsConnectionFlags">enum NMSettingsConnectionFlags</a> </dt> -<dt id="ientry-id-1.4.17.2.26.2">NMSettingsConnectionFlags, <a class="indexterm" href="nm-dbus-types.html#NMSettingsConnectionFlags">enum NMSettingsConnectionFlags</a> +<dt id="ientry-id-1.4.17.2.30.2">NMSettingsUpdate2Flags, <a class="indexterm" href="nm-dbus-types.html#NMSettingsUpdate2Flags">enum NMSettingsUpdate2Flags</a> </dt> -<dt id="ientry-id-1.4.17.2.29.2">NMSettingsUpdate2Flags, <a class="indexterm" href="nm-dbus-types.html#NMSettingsUpdate2Flags">enum NMSettingsUpdate2Flags</a> +<dt id="ientry-id-1.4.17.2.5.2">NMState, <a class="indexterm" href="nm-dbus-types.html#NMState">enum NMState</a> </dt> -<dt id="ientry-id-1.4.17.2.4.2">NMState, <a class="indexterm" href="nm-dbus-types.html#NMState">enum NMState</a> +<dt id="ientry-id-1.4.17.2.32.2">NMTernary, <a class="indexterm" href="nm-dbus-types.html#NMTernary">enum NMTernary</a> </dt> -<dt id="ientry-id-1.4.17.2.31.2">NMTernary, <a class="indexterm" href="nm-dbus-types.html#NMTernary">enum NMTernary</a> +<dt id="ientry-id-1.4.17.2.3.2">NMVersionInfoCapability, <a class="indexterm" href="nm-dbus-types.html#NMVersionInfoCapability">enum NMVersionInfoCapability</a> </dt> <dt id="ientry-id-1.6.3.2.4.2">NMVpnConnectionState, <a class="indexterm" href="nm-vpn-dbus-types.html#NMVpnConnectionState">enum NMVpnConnectionState</a> </dt> @@ -1181,7 +1199,7 @@ </dt> <dt id="ientry-id-1.6.3.2.3.2">NMVpnServiceState, <a class="indexterm" href="nm-vpn-dbus-types.html#NMVpnServiceState">enum NMVpnServiceState</a> </dt> -<dt id="ientry-id-1.4.17.2.14.2">NMWimaxNspNetworkType, <a class="indexterm" href="nm-dbus-types.html#NMWimaxNspNetworkType">enum NMWimaxNspNetworkType</a> +<dt id="ientry-id-1.4.17.2.15.2">NMWimaxNspNetworkType, <a class="indexterm" href="nm-dbus-types.html#NMWimaxNspNetworkType">enum NMWimaxNspNetworkType</a> </dt> <dt id="ientry-id-1.3.3.29.2.2.1.1.2.8.1.1.1">no-vj-comp, <a class="indexterm" href="settings-ppp.html">ppp</a> </dt> @@ -1202,13 +1220,15 @@ <div class="indexdiv"> <h3>O</h3> <dl> +<dt id="ientry-id-1.3.3.26.2.2.1.1.2.1.1.1.1">ofport-request, <a class="indexterm" href="settings-ovs-interface.html">ovs-interface</a> +</dt> <dt id="ientry-id-1.3.3.51.2.2.1.1.2.3.1.1.1">only-from-default, <a class="indexterm" href="settings-hostname.html">hostname</a> </dt> <dt id="ientry-id-1.3.3.4.2.2.1.1.2.15.1.1.1">optional, <a class="indexterm" href="settings-802-1x.html">802-1x</a> </dt> <dt id="ientry-id-1.3.3.7.2.2.1.1.2.2.1.1.1">options, <a class="indexterm" href="settings-bond.html">bond</a> </dt> -<dt id="ientry-id-1.3.3.19.2.2.1.1.2.8.1.1.1">output-key, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a> +<dt id="ientry-id-1.3.3.19.2.2.1.1.2.9.1.1.1">output-key, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a> </dt> <dt id="ientry-id-1.3.3.37.2.2.1.1.2.4.1.1.1">owner, <a class="indexterm" href="settings-tun.html">tun</a> </dt> @@ -1247,7 +1267,7 @@ </dt> <dt id="ientry-id-1.3.3.9.2.2.1.1.2.2.1.1.1">path-cost, <a class="indexterm" href="settings-bridge-port.html">bridge-port</a> </dt> -<dt id="ientry-id-1.3.3.19.2.2.1.1.2.10.1.1.1">path-mtu-discovery, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a> +<dt id="ientry-id-1.3.3.19.2.2.1.1.2.11.1.1.1">path-mtu-discovery, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a> </dt> <dt id="ientry-id-1.3.3.27.2.2.1.1.2.1.1.1.1">peer, <a class="indexterm" href="settings-ovs-patch.html">ovs-patch</a>, <a class="indexterm" href="settings-wifi-p2p.html">wifi-p2p</a>, <a class="indexterm" href="settings-veth.html">veth</a> </dt> @@ -1311,17 +1331,17 @@ </dt> <dt id="ientry-id-1.3.3.47.2.2.1.1.2.14.1.1.1">powersave, <a class="indexterm" href="settings-802-11-wireless.html">802-11-wireless</a> </dt> -<dt id="ientry-id-1.4.8.32.1.2">org.freedesktop.NetworkManager.PPP, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-interface-org-freedesktop-NetworkManager-PPP.top_of_page">org.freedesktop.NetworkManager.PPP</a> +<dt id="ientry-id-1.4.8.33.1.2">org.freedesktop.NetworkManager.PPP, <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-interface-org-freedesktop-NetworkManager-PPP.top_of_page">org.freedesktop.NetworkManager.PPP</a> </dt> -<dt id="ientry-id-1.4.8.32.5.2.2">org.freedesktop.NetworkManager.PPP.NeedSecrets(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.NeedSecrets">The NeedSecrets() method</a> +<dt id="ientry-id-1.4.8.33.5.2.2">org.freedesktop.NetworkManager.PPP.NeedSecrets(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.NeedSecrets">The NeedSecrets() method</a> </dt> -<dt id="ientry-id-1.4.8.32.5.6.2">org.freedesktop.NetworkManager.PPP.SetIfindex(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.SetIfindex">The SetIfindex() method</a> +<dt id="ientry-id-1.4.8.33.5.6.2">org.freedesktop.NetworkManager.PPP.SetIfindex(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.SetIfindex">The SetIfindex() method</a> </dt> -<dt id="ientry-id-1.4.8.32.5.3.2">org.freedesktop.NetworkManager.PPP.SetIp4Config(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.SetIp4Config">The SetIp4Config() method</a> +<dt id="ientry-id-1.4.8.33.5.3.2">org.freedesktop.NetworkManager.PPP.SetIp4Config(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.SetIp4Config">The SetIp4Config() method</a> </dt> -<dt id="ientry-id-1.4.8.32.5.4.2">org.freedesktop.NetworkManager.PPP.SetIp6Config(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.SetIp6Config">The SetIp6Config() method</a> +<dt id="ientry-id-1.4.8.33.5.4.2">org.freedesktop.NetworkManager.PPP.SetIp6Config(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.SetIp6Config">The SetIp6Config() method</a> </dt> -<dt id="ientry-id-1.4.8.32.5.5.2">org.freedesktop.NetworkManager.PPP.SetState(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.SetState">The SetState() method</a> +<dt id="ientry-id-1.4.8.33.5.5.2">org.freedesktop.NetworkManager.PPP.SetState(), <a class="indexterm" href="gdbus-org.freedesktop.NetworkManager.PPP.html#gdbus-method-org-freedesktop-NetworkManager-PPP.SetState">The SetState() method</a> </dt> <dt id="ientry-id-1.3.3.36.2.2.1.1.2.5.1.1.1">prio, <a class="indexterm" href="settings-team-port.html">team-port</a> </dt> @@ -1355,7 +1375,7 @@ </dt> <dt id="ientry-id-1.3.3.48.2.2.1.1.2.10.1.1.1">proto, <a class="indexterm" href="settings-802-11-wireless-security.html">802-11-wireless-security</a> </dt> -<dt id="ientry-id-1.3.3.5.2.2.1.1.2.4.1.1.1">protocol, <a class="indexterm" href="settings-adsl.html">adsl</a> +<dt id="ientry-id-1.3.3.5.2.2.1.1.2.4.1.1.1">protocol, <a class="indexterm" href="settings-adsl.html">adsl</a>, <a class="indexterm" href="settings-vlan.html">vlan</a> </dt> <dt id="ientry-id-1.3.3.42.2.2.1.1.2.10.1.1.1">proxy, <a class="indexterm" href="settings-vxlan.html">vxlan</a> </dt> @@ -1377,7 +1397,7 @@ <div class="indexdiv"> <h3>R</h3> <dl> -<dt id="ientry-id-1.3.3.18.2.2.1.1.2.24.1.1.1">ra-timeout, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.18.2.2.1.1.2.26.1.1.1">ra-timeout, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> <dt id="ientry-id-1.3.3.47.2.2.1.1.2.15.1.1.1">rate, <a class="indexterm" href="settings-802-11-wireless.html">802-11-wireless</a> </dt> @@ -1393,21 +1413,25 @@ </dt> <dt id="ientry-id-1.3.3.29.2.2.1.1.2.16.1.1.1">refuse-pap, <a class="indexterm" href="settings-ppp.html">ppp</a> </dt> -<dt id="ientry-id-1.3.3.19.2.2.1.1.2.11.1.1.1">remote, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-vxlan.html">vxlan</a> +<dt id="ientry-id-1.3.3.19.2.2.1.1.2.12.1.1.1">remote, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-vxlan.html">vxlan</a> +</dt> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.26.1.1.1">replace-local-rule, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> <dt id="ientry-id-1.3.3.29.2.2.1.1.2.17.1.1.1">require-mppe, <a class="indexterm" href="settings-ppp.html">ppp</a> </dt> <dt id="ientry-id-1.3.3.29.2.2.1.1.2.18.1.1.1">require-mppe-128, <a class="indexterm" href="settings-ppp.html">ppp</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.24.1.1.1">required-timeout, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.27.1.1.1">required-timeout, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +</dt> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.28.1.1.1">route-data, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.25.1.1.1">route-data, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.29.1.1.1">route-metric, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.26.1.1.1">route-metric, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.30.1.1.1">route-table, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.27.1.1.1">route-table, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.31.1.1.1">routes, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.17.2.2.1.1.2.28.1.1.1">routes, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.17.2.2.1.1.2.32.1.1.1">routing-rules, <a class="indexterm" href="settings-ipv4.html">ipv4</a>, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> <dt id="ientry-id-1.3.3.42.2.2.1.1.2.12.1.1.1">rsc, <a class="indexterm" href="settings-vxlan.html">vxlan</a> </dt> @@ -1507,15 +1531,17 @@ </dt> <dt id="ientry-id-1.3.3.2.2.2.1.1.2.23.1.1.1">timestamp, <a class="indexterm" href="settings-connection.html">connection</a> </dt> -<dt id="ientry-id-1.3.3.18.2.2.1.1.2.30.1.1.1">token, <a class="indexterm" href="settings-ipv6.html">ipv6</a> +<dt id="ientry-id-1.3.3.18.2.2.1.1.2.34.1.1.1">token, <a class="indexterm" href="settings-ipv6.html">ipv6</a> </dt> -<dt id="ientry-id-1.3.3.19.2.2.1.1.2.12.1.1.1">tos, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-vxlan.html">vxlan</a> +<dt id="ientry-id-1.3.3.19.2.2.1.1.2.13.1.1.1">tos, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-vxlan.html">vxlan</a> </dt> <dt id="ientry-id-1.3.3.33.2.2.1.1.2.2.1.1.1">total-vfs, <a class="indexterm" href="settings-sriov.html">sriov</a> </dt> <dt id="ientry-id-1.3.3.16.2.2.1.1.2.5.1.1.1">transport-mode, <a class="indexterm" href="settings-infiniband.html">infiniband</a> </dt> -<dt id="ientry-id-1.3.3.19.2.2.1.1.2.13.1.1.1">ttl, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-vxlan.html">vxlan</a> +<dt id="ientry-id-1.3.3.28.2.2.1.1.2.6.1.1.1">trunks, <a class="indexterm" href="settings-ovs-port.html">ovs-port</a> +</dt> +<dt id="ientry-id-1.3.3.19.2.2.1.1.2.14.1.1.1">ttl, <a class="indexterm" href="settings-ip-tunnel.html">ip-tunnel</a>, <a class="indexterm" href="settings-vxlan.html">vxlan</a> </dt> <dt id="ientry-id-1.3.3.47.2.2.1.1.2.19.1.1.1">tx-power, <a class="indexterm" href="settings-802-11-wireless.html">802-11-wireless</a> </dt> @@ -1547,7 +1573,7 @@ </dt> <dt id="ientry-id-1.3.3.8.2.2.1.1.2.25.1.1.1">vlan-filtering, <a class="indexterm" href="settings-bridge.html">bridge</a> </dt> -<dt id="ientry-id-1.3.3.28.2.2.1.1.2.6.1.1.1">vlan-mode, <a class="indexterm" href="settings-ovs-port.html">ovs-port</a> +<dt id="ientry-id-1.3.3.28.2.2.1.1.2.7.1.1.1">vlan-mode, <a class="indexterm" href="settings-ovs-port.html">ovs-port</a> </dt> <dt id="ientry-id-1.3.3.8.2.2.1.1.2.26.1.1.1">vlan-protocol, <a class="indexterm" href="settings-bridge.html">bridge</a> </dt> diff --git a/docs/api/html/manpages.html b/docs/api/html/manpages.html index 4ce24258..b3befb31 100644 --- a/docs/api/html/manpages.html +++ b/docs/api/html/manpages.html @@ -35,7 +35,7 @@ <span class="refentrytitle"><a href="NetworkManager-dispatcher.html">NetworkManager-dispatcher</a></span><span class="refpurpose"> — Dispatch user scripts for NetworkManager</span> </dt> <dt> -<span class="refentrytitle"><a href="NetworkManager-wait-online.service.html">NetworkManager-wait-online.service</a></span><span class="refpurpose"> — Wait for network to come online</span> +<span class="refentrytitle"><a href="NetworkManager-wait-online.service.html">NetworkManager-wait-online.service</a></span><span class="refpurpose"> — Wait for the network to come online</span> </dt> <dt> <span class="refentrytitle"><a href="nmcli.html">nmcli</a></span><span class="refpurpose"> — command-line tool for controlling NetworkManager</span> diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html index 892a1924..5d7db24a 100644 --- a/docs/api/html/nm-dbus-types.html +++ b/docs/api/html/nm-dbus-types.html @@ -29,13 +29,33 @@ <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect2"> +<a name="NMVersionInfoCapability"></a><h3>enum NMVersionInfoCapability</h3> +<p>%_NM_VERSION_INFO_CAPABILITY_UNUSED: a dummy capability. It has no meaning, don't use it.</p> +<p>Currently no enum values are defined. These capabilities are exposed on D-Bus in the "VersionInfo" bit field.</p> +<p>Since: 1.42</p> +<p></p> +<div class="refsect3"> +<a name="id-1.4.17.2.3.4"></a><h4>Values</h4> +<div class="informaltable"><table class="informaltable" width="100%" border="0"> +<colgroup> +<col width="300px" class="enum_members_name"> +<col width="100px" class="enum_members_value"> +<col class="enum_members_description"> +<col> +</colgroup> +<tbody></tbody> +</table></div> +</div> +</div> +<hr> +<div class="refsect2"> <a name="NMCapability"></a><h3>enum NMCapability</h3> <p><a class="link" href="nm-dbus-types.html#NMCapability" title="enum NMCapability">NMCapability</a> names the numbers in the Capabilities property. Capabilities are positive numbers. They are part of stable API and a certain capability number is guaranteed not to change.</p> <p>The range 0x7000 - 0x7FFF of capabilities is guaranteed not to be used by upstream NetworkManager. It could thus be used for downstream extensions.</p> <p>Since: 1.6</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.3.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.4.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -84,7 +104,7 @@ <p><a class="link" href="nm-dbus-types.html#NMState" title="enum NMState">NMState</a> values indicate the current overall networking state.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.4.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.5.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -222,7 +242,7 @@ <a name="NMConnectivityState"></a><h3>enum NMConnectivityState</h3> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.5.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.6.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -316,7 +336,7 @@ <p><a class="link" href="nm-dbus-types.html#NMDeviceType" title="enum NMDeviceType">NMDeviceType</a> values indicate the type of hardware represented by a device object.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.6.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.7.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -805,6 +825,21 @@ </td> <td class="auto-generated"> </td> </tr> +<tr> +<td class="enum_member_name"> +<p>NM_DEVICE_TYPE_LOOPBACK</p> +<p></p> +</td> +<td class="enum_member_value"> +<p>= <code class="literal">32</code></p> +<p></p> +</td> +<td class="enum_member_description"> +<p>a loopback interface. Since: 1.42.</p> +<p></p> +</td> +<td class="auto-generated"> </td> +</tr> </tbody> </table></div> </div> @@ -815,7 +850,7 @@ <p>General device capability flags.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.7.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.8.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -909,7 +944,7 @@ <p>802.11 specific device encryption and authentication capabilities.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.8.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.9.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -1138,7 +1173,7 @@ <p>802.11 access point flags.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.9.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.10.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -1232,7 +1267,7 @@ <p>802.11 access point security and authentication flags. These flags describe the current security requirements of an access point as determined from the access point's beacon.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.10.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.11.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -1476,7 +1511,7 @@ <p>Indicates the 802.11 mode an access point or device is currently in.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.11.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.12.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -1570,7 +1605,7 @@ <p><a class="link" href="nm-dbus-types.html#NMBluetoothCapabilities" title="enum NMBluetoothCapabilities">NMBluetoothCapabilities</a> values indicate the usable capabilities of a Bluetooth device.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.12.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.13.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -1634,7 +1669,7 @@ <p><a class="link" href="nm-dbus-types.html#NMDeviceModemCapabilities" title="enum NMDeviceModemCapabilities">NMDeviceModemCapabilities</a> values indicate the generic radio access technology families a modem device supports. For more information on the specific access technologies the device supports use the ModemManager D-Bus API.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.13.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.14.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -1743,7 +1778,7 @@ <p>WiMAX network type.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.14.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.15.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -1821,7 +1856,7 @@ <a name="NMDeviceState"></a><h3>enum NMDeviceState</h3> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.15.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.16.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -2035,7 +2070,7 @@ <p>Device state change reason codes</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.16.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.17.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -3079,7 +3114,7 @@ <p>Since: 1.2</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.17.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.18.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -3173,7 +3208,7 @@ <p>Since: 1.14</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.18.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.19.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -3252,7 +3287,7 @@ <p><a class="link" href="nm-dbus-types.html#NMActiveConnectionState" title="enum NMActiveConnectionState">NMActiveConnectionState</a> values indicate the state of a connection to a specific network while it is starting, connected, or disconnecting from that network.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.19.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.20.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -3347,7 +3382,7 @@ <p>Since: 1.8</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.20.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.21.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -3591,7 +3626,7 @@ <p><a class="link" href="nm-dbus-types.html#NMSecretAgentGetSecretsFlags" title="enum NMSecretAgentGetSecretsFlags">NMSecretAgentGetSecretsFlags</a> values modify the behavior of a GetSecrets request.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.21.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.22.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -3715,7 +3750,7 @@ <p><a class="link" href="nm-dbus-types.html#NMSecretAgentCapabilities" title="enum NMSecretAgentCapabilities">NMSecretAgentCapabilities</a> indicate various capabilities of the agent.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.22.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.23.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -3765,7 +3800,7 @@ <p>Since: 1.2</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.23.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.24.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -3965,7 +4000,7 @@ <p>Since: 1.12 (public since 1.4, g-ir since 1.12)</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.24.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.25.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4075,7 +4110,7 @@ <p>Since: 1.4</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.25.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.26.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4155,7 +4190,7 @@ <p>Since: 1.12</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.26.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.27.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4250,7 +4285,7 @@ <p>Since: 1.10</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.27.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.28.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4405,7 +4440,7 @@ <p>Since: 1.20</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.28.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.29.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4484,7 +4519,7 @@ <p>Since: 1.12</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.29.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.30.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4621,11 +4656,10 @@ <div class="refsect2"> <a name="NMDeviceReapplyFlags"></a><h3>enum NMDeviceReapplyFlags</h3> <p>Flags for the Reapply() D-Bus call of a device and nm_device_reapply_async().</p> -<p>Since: 1.42, 1.40.10</p> -<p>On 1.40.10+, no GFlags type is created.</p> +<p>Since: 1.42</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.30.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.31.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4675,7 +4709,7 @@ <p>Since: 1.14</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.31.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.32.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4740,7 +4774,7 @@ <p>Since: 1.22</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.32.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.33.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4835,7 +4869,7 @@ <p>Since: 1.22</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.33.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.34.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -4944,7 +4978,7 @@ <p><a class="link" href="nm-dbus-types.html#NMClientPermission" title="enum NMClientPermission">NMClientPermission</a> values indicate various permissions that NetworkManager clients can obtain to perform certain tasks on behalf of the current user.</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.34.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.35.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -5233,7 +5267,7 @@ <p><a class="link" href="nm-dbus-types.html#NMClientPermissionResult" title="enum NMClientPermissionResult">NMClientPermissionResult</a> values indicate what authorizations and permissions the user requires to obtain a given <a class="link" href="nm-dbus-types.html#NMClientPermission" title="enum NMClientPermission">NMClientPermission</a></p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.35.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.36.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -5313,7 +5347,7 @@ <p>Since: 1.38</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.36.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.37.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> @@ -5377,7 +5411,7 @@ <p>Since: 1.40</p> <p></p> <div class="refsect3"> -<a name="id-1.4.17.2.37.4"></a><h4>Values</h4> +<a name="id-1.4.17.2.38.4"></a><h4>Values</h4> <div class="informaltable"><table class="informaltable" width="100%" border="0"> <colgroup> <col width="300px" class="enum_members_name"> diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index fd1f0892..1ce7840d 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -95,7 +95,7 @@ </div> <div class="refsect2"> <a name="id-1.2.9.4.3"></a><h3>connection setting</h3> -<p> General Connection Profile Settings.</p> +<p>General Connection Profile Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -115,264 +115,264 @@ <a name="nm-settings-dbus.property.connection.auth-retries"></a>auth-retries</td> <td align="left">int32</td> <td align="left">-1</td> -<td> The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. +<td>The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. - Currently, this only applies to 802-1x authentication.</td> +Currently, this only applies to 802-1x authentication.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.autoconnect"></a>autoconnect</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> 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. +<td>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. +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. +Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles. - If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined. +If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined. - Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.</td> +Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.autoconnect-priority"></a>autoconnect-priority</td> <td align="left">int32</td> <td align="left">0</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.autoconnect-retries"></a>autoconnect-retries</td> <td align="left">int32</td> <td align="left">-1</td> -<td> The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.</td> +<td>The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.autoconnect-slaves"></a>autoconnect-slaves</td> <td align="left">NMSettingConnectionAutoconnectSlaves (int32)</td> <td align="left"> </td> -<td> Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.</td> +<td>Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.dns-over-tls"></a>dns-over-tls</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. +<td>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. +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.</td> +This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.gateway-ping-timeout"></a>gateway-ping-timeout</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.</td> +<td>If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.id"></a>id</td> <td align="left">string</td> <td align="left"> </td> -<td> A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".</td> +<td>A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.interface-name"></a>interface-name</td> <td align="left">string</td> <td align="left"> </td> -<td> The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). +<td>The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). - For software devices this specifies the name of the created device. +For software devices this specifies the name of the created device. - For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.</td> +For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.lldp"></a>lldp</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Whether LLDP is enabled for the connection.</td> +<td>Whether LLDP is enabled for the connection.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.llmnr"></a>llmnr</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. +<td>Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. - The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes"). +The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes"). - This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</td> +This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.master"></a>master</td> <td align="left">string</td> <td align="left"> </td> -<td> Interface name of the master device or UUID of the master connection.</td> +<td>Interface name of the master device or UUID of the master connection.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.mdns"></a>mdns</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Whether mDNS is enabled for the connection. +<td>Whether mDNS is enabled for the connection. - The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). +The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). - This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</td> +This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.metered"></a>metered</td> <td align="left">NMMetered (int32)</td> <td align="left"> </td> -<td> Whether the connection is metered. +<td>Whether the connection is metered. - When updating this property on a currently activated connection, the change takes effect immediately.</td> +When updating this property on a currently activated connection, the change takes effect immediately.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.mptcp-flags"></a>mptcp-flags</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. +<td>Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. - If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. +If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. - The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. +The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. - Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. +Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. - Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. +Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. - When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. +When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. - If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. +If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. - NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. +NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. - Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).</td> +Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.mud-url"></a>mud-url</td> <td align="left">string</td> <td align="left"> </td> -<td> If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". +<td>If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". - The special value "none" is allowed to indicate that no MUD URL is used. +The special value "none" is allowed to indicate that no MUD URL is used. - If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".</td> +If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.multi-connect"></a>multi-connect</td> <td align="left">int32</td> <td align="left">0</td> -<td> Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.</td> +<td>Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.permissions"></a>permissions</td> <td align="left">array of string</td> <td align="left"> </td> -<td> An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". +<td>An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". - At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.</td> +At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.read-only"></a>read-only</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.</td> +<td>FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.secondaries"></a>secondaries</td> <td align="left">array of string</td> <td align="left"> </td> -<td> List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.</td> +<td>List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.slave-type"></a>slave-type</td> <td align="left">string</td> <td align="left"> </td> -<td> Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.</td> +<td>Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.stable-id"></a>stable-id</td> <td align="left">string</td> <td align="left"> </td> -<td> This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. +<td>This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. - The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. +The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. - Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity. +Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity. - The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. +The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. - If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.</td> +If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.timestamp"></a>timestamp</td> <td align="left">uint64</td> <td align="left">0</td> -<td> The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. +<td>The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. - NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).</td> +NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.type"></a>type</td> <td align="left">string</td> <td align="left"> </td> -<td> Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).</td> +<td>Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.uuid"></a>uuid</td> <td align="left">string</td> <td align="left"> </td> -<td> A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. +<td>A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. - The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").</td> +The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.wait-activation-delay"></a>wait-activation-delay</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event. +<td>Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event. - The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</td> +The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.wait-device-timeout"></a>wait-device-timeout</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed. +<td>Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed. - The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</td> +The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.zone"></a>zone</td> <td align="left">string</td> <td align="left"> </td> -<td> The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. +<td>The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. - When updating this property on a currently activated connection, the change takes effect immediately.</td> +When updating this property on a currently activated connection, the change takes effect immediately.</td> </tr> </tbody> </table></div> @@ -380,7 +380,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.4"></a><h3>6lowpan setting</h3> -<p> 6LoWPAN Settings.</p> +<p>6LoWPAN Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -399,14 +399,14 @@ <a name="nm-settings-dbus.property.6lowpan.parent"></a>parent</td> <td align="left">string</td> <td align="left"> </td> -<td> If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.</td> +<td>If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.</td> </tr></tbody> </table></div> </div> <hr> <div class="refsect2"> <a name="id-1.2.9.4.5"></a><h3>802-1x setting</h3> -<p> IEEE 802.1x Authentication Settings.</p> +<p>IEEE 802.1x Authentication Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -426,351 +426,355 @@ <a name="nm-settings-dbus.property.802-1x.altsubject-matches"></a>altsubject-matches</td> <td align="left">array of string</td> <td align="left"> </td> -<td> List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.</td> +<td>List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.anonymous-identity"></a>anonymous-identity</td> <td align="left">string</td> <td align="left"> </td> -<td> Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.</td> +<td>Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.auth-timeout"></a>auth-timeout</td> <td align="left">int32</td> <td align="left">0</td> -<td> A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.</td> +<td>A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.ca-cert"></a>ca-cert</td> <td align="left">byte array</td> <td align="left"> </td> -<td> Contains the CA certificate if used by the EAP method specified in the "eap" property. +<td>Contains the CA certificate if used by the EAP method specified in the "eap" property. - Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. +Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. - Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</td> +Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.ca-cert-password"></a>ca-cert-password</td> <td align="left">string</td> <td align="left"> </td> -<td> The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> +<td>The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.ca-cert-password-flags"></a>ca-cert-password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "ca-cert-password" property.</td> +<td>Flags indicating how to handle the "ca-cert-password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.ca-path"></a>ca-path</td> <td align="left">string</td> <td align="left"> </td> -<td> UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property. +<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property. - If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</td> +If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.client-cert"></a>client-cert</td> <td align="left">byte array</td> <td align="left"> </td> -<td> Contains the client certificate if used by the EAP method specified in the "eap" property. +<td>Contains the client certificate if used by the EAP method specified in the "eap" property. - Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.</td> +Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.client-cert-password"></a>client-cert-password</td> <td align="left">string</td> <td align="left"> </td> -<td> The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> +<td>The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.client-cert-password-flags"></a>client-cert-password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "client-cert-password" property.</td> +<td>Flags indicating how to handle the "client-cert-password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.domain-match"></a>domain-match</td> <td align="left">string</td> <td align="left"> </td> -<td> Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</td> +<td>Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.domain-suffix-match"></a>domain-suffix-match</td> <td align="left">string</td> <td align="left"> </td> -<td> Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</td> +<td>Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.eap"></a>eap</td> <td align="left">array of string</td> <td align="left"> </td> -<td> The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.</td> +<td>The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.identity"></a>identity</td> <td align="left">string</td> <td align="left"> </td> -<td> Identity string for EAP authentication methods. Often the user's user or login name.</td> +<td>Identity string for EAP authentication methods. Often the user's user or login name.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.optional"></a>optional</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.</td> +<td>Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.pac-file"></a>pac-file</td> <td align="left">string</td> <td align="left"> </td> -<td> UTF-8 encoded file path containing PAC for EAP-FAST.</td> +<td>UTF-8 encoded file path containing PAC for EAP-FAST.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.password"></a>password</td> <td align="left">string</td> <td align="left"> </td> -<td> UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</td> +<td>UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.password-flags"></a>password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "password" property.</td> +<td>Flags indicating how to handle the "password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.password-raw"></a>password-raw</td> <td align="left">byte array</td> <td align="left"> </td> -<td> Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</td> +<td>Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.password-raw-flags"></a>password-raw-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "password-raw" property.</td> +<td>Flags indicating how to handle the "password-raw" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase1-auth-flags"></a>phase1-auth-flags</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details.</td> +<td>Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. TLS time checks can be also disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x and tls_disable_time_checks settings. See the wpa_supplicant documentation for more details.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase1-fast-provisioning"></a>phase1-fast-provisioning</td> <td align="left">string</td> <td align="left"> </td> -<td> Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details.</td> +<td>Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase1-peaplabel"></a>phase1-peaplabel</td> <td align="left">string</td> <td align="left"> </td> -<td> Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details.</td> +<td>Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase1-peapver"></a>phase1-peapver</td> <td align="left">string</td> <td align="left"> </td> -<td> Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version.</td> +<td>Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-altsubject-matches"></a>phase2-altsubject-matches</td> <td align="left">array of string</td> <td align="left"> </td> -<td> List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.</td> +<td>List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-auth"></a>phase2-auth</td> <td align="left">string</td> <td align="left"> </td> -<td> Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.</td> +<td>Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-autheap"></a>phase2-autheap</td> <td align="left">string</td> <td align="left"> </td> -<td> Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</td> +<td>Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-ca-cert"></a>phase2-ca-cert</td> <td align="left">byte array</td> <td align="left"> </td> -<td> Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. +<td>Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. - Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. +Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. - Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</td> +Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-ca-cert-password"></a>phase2-ca-cert-password</td> <td align="left">string</td> <td align="left"> </td> -<td> The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> +<td>The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-ca-cert-password-flags"></a>phase2-ca-cert-password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "phase2-ca-cert-password" property.</td> +<td>Flags indicating how to handle the "phase2-ca-cert-password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-ca-path"></a>phase2-ca-path</td> <td align="left">string</td> <td align="left"> </td> -<td> UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property. +<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property. - If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</td> +If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-client-cert"></a>phase2-client-cert</td> <td align="left">byte array</td> <td align="left"> </td> -<td> Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. +<td>Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. - Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td> +Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-client-cert-password"></a>phase2-client-cert-password</td> <td align="left">string</td> <td align="left"> </td> -<td> The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> +<td>The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-client-cert-password-flags"></a>phase2-client-cert-password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "phase2-client-cert-password" property.</td> +<td>Flags indicating how to handle the "phase2-client-cert-password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-domain-match"></a>phase2-domain-match</td> <td align="left">string</td> <td align="left"> </td> -<td> Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</td> +<td>Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-domain-suffix-match"></a>phase2-domain-suffix-match</td> <td align="left">string</td> <td align="left"> </td> -<td> Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</td> +<td>Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-private-key"></a>phase2-private-key</td> <td align="left">byte array</td> <td align="left"> </td> -<td> Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". +<td>Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". - Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</td> +Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-private-key-password"></a>phase2-private-key-password</td> <td align="left">string</td> <td align="left"> </td> -<td> The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.</td> +<td>The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-private-key-password-flags"></a>phase2-private-key-password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "phase2-private-key-password" property.</td> +<td>Flags indicating how to handle the "phase2-private-key-password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.phase2-subject-match"></a>phase2-subject-match</td> <td align="left">string</td> <td align="left"> </td> -<td> Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match.</td> +<td>Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used. + +This property is deprecated since version 1.2.Use "phase2-domain-suffix-match" instead.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.pin"></a>pin</td> <td align="left">string</td> <td align="left"> </td> -<td> PIN used for EAP authentication methods.</td> +<td>PIN used for EAP authentication methods.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.pin-flags"></a>pin-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "pin" property.</td> +<td>Flags indicating how to handle the "pin" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.private-key"></a>private-key</td> <td align="left">byte array</td> <td align="left"> </td> -<td> Contains the private key when the "eap" property is set to "tls". +<td>Contains the private key when the "eap" property is set to "tls". - Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. +Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. - WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.</td> +WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.private-key-password"></a>private-key-password</td> <td align="left">string</td> <td align="left"> </td> -<td> The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.</td> +<td>The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.private-key-password-flags"></a>private-key-password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "private-key-password" property.</td> +<td>Flags indicating how to handle the "private-key-password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.subject-match"></a>subject-match</td> <td align="left">string</td> <td align="left"> </td> -<td> Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match.</td> +<td>Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used. + +This property is deprecated since version 1.2.Use "phase2-domain-suffix-match" instead.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-1x.system-ca-certs"></a>system-ca-certs</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).</td> +<td>When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).</td> </tr> </tbody> </table></div> @@ -778,7 +782,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.6"></a><h3>adsl setting</h3> -<p> ADSL Settings.</p> +<p>ADSL Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -798,49 +802,49 @@ <a name="nm-settings-dbus.property.adsl.encapsulation"></a>encapsulation</td> <td align="left">string</td> <td align="left"> </td> -<td> Encapsulation of ADSL connection. Can be "vcmux" or "llc".</td> +<td>Encapsulation of ADSL connection. Can be "vcmux" or "llc".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.adsl.password"></a>password</td> <td align="left">string</td> <td align="left"> </td> -<td> Password used to authenticate with the ADSL service.</td> +<td>Password used to authenticate with the ADSL service.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.adsl.password-flags"></a>password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "password" property.</td> +<td>Flags indicating how to handle the "password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.adsl.protocol"></a>protocol</td> <td align="left">string</td> <td align="left"> </td> -<td> ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm".</td> +<td>ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.adsl.username"></a>username</td> <td align="left">string</td> <td align="left"> </td> -<td> Username used to authenticate with the ADSL service.</td> +<td>Username used to authenticate with the ADSL service.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.adsl.vci"></a>vci</td> <td align="left">uint32</td> <td align="left">0</td> -<td> VCI of ADSL connection</td> +<td>VCI of ADSL connection</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.adsl.vpi"></a>vpi</td> <td align="left">uint32</td> <td align="left">0</td> -<td> VPI of ADSL connection</td> +<td>VPI of ADSL connection</td> </tr> </tbody> </table></div> @@ -848,7 +852,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.7"></a><h3>bluetooth setting</h3> -<p> Bluetooth Settings.</p> +<p>Bluetooth Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -868,14 +872,14 @@ <a name="nm-settings-dbus.property.bluetooth.bdaddr"></a>bdaddr</td> <td align="left">byte array</td> <td align="left"> </td> -<td> The Bluetooth address of the device.</td> +<td>The Bluetooth address of the device.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bluetooth.type"></a>type</td> <td align="left">string</td> <td align="left"> </td> -<td> Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.</td> +<td>Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.</td> </tr> </tbody> </table></div> @@ -883,7 +887,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.8"></a><h3>bond setting</h3> -<p> Bonding Settings.</p> +<p>Bonding Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -910,7 +914,7 @@ <a name="nm-settings-dbus.property.bond.options"></a>options</td> <td align="left">dict of string to string</td> <td align="left">{'mode': 'balance-rr'}</td> -<td> Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).</td> +<td>Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).</td> </tr> </tbody> </table></div> @@ -918,7 +922,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.9"></a><h3>bridge setting</h3> -<p> Bridging Settings.</p> +<p>Bridging Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -938,37 +942,37 @@ <a name="nm-settings-dbus.property.bridge.ageing-time"></a>ageing-time</td> <td align="left">uint32</td> <td align="left">300</td> -<td> The Ethernet MAC address aging time, in seconds.</td> +<td>The Ethernet MAC address aging time, in seconds.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.forward-delay"></a>forward-delay</td> <td align="left">uint32</td> <td align="left">15</td> -<td> The Spanning Tree Protocol (STP) forwarding delay, in seconds.</td> +<td>The Spanning Tree Protocol (STP) forwarding delay, in seconds.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.group-address"></a>group-address</td> <td align="left">byte array</td> <td align="left"> </td> -<td> If specified, The MAC address of the multicast group this bridge uses for STP. +<td>If specified, The MAC address of the multicast group this bridge uses for STP. - The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.</td> +The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.group-forward-mask"></a>group-forward-mask</td> <td align="left">uint32</td> <td align="left">0</td> -<td> A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.</td> +<td>A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.hello-time"></a>hello-time</td> <td align="left">uint32</td> <td align="left">2</td> -<td> The Spanning Tree Protocol (STP) hello time, in seconds.</td> +<td>The Spanning Tree Protocol (STP) hello time, in seconds.</td> </tr> <tr> <td align="left"> @@ -982,166 +986,168 @@ <a name="nm-settings-dbus.property.bridge.mac-address"></a>mac-address</td> <td align="left">byte array</td> <td align="left"> </td> -<td> If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set. +<td>If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set. + +If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. - If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1</td> +This property is deprecated since version 1.12.Use the "cloned-mac-address" property instead.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.max-age"></a>max-age</td> <td align="left">uint32</td> <td align="left">20</td> -<td> The Spanning Tree Protocol (STP) maximum message age, in seconds.</td> +<td>The Spanning Tree Protocol (STP) maximum message age, in seconds.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-hash-max"></a>multicast-hash-max</td> <td align="left">uint32</td> <td align="left">4096</td> -<td> Set maximum size of multicast hash table (value must be a power of 2).</td> +<td>Set maximum size of multicast hash table (value must be a power of 2).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-last-member-count"></a>multicast-last-member-count</td> <td align="left">uint32</td> <td align="left">2</td> -<td> Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.</td> +<td>Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-last-member-interval"></a>multicast-last-member-interval</td> <td align="left">uint64</td> <td align="left">100</td> -<td> Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.</td> +<td>Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-membership-interval"></a>multicast-membership-interval</td> <td align="left">uint64</td> <td align="left">26000</td> -<td> Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.</td> +<td>Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-querier"></a>multicast-querier</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.</td> +<td>Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-querier-interval"></a>multicast-querier-interval</td> <td align="left">uint64</td> <td align="left">25500</td> -<td> If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.</td> +<td>If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-query-interval"></a>multicast-query-interval</td> <td align="left">uint64</td> <td align="left">12500</td> -<td> Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.</td> +<td>Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-query-response-interval"></a>multicast-query-response-interval</td> <td align="left">uint64</td> <td align="left">1000</td> -<td> Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.</td> +<td>Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-query-use-ifaddr"></a>multicast-query-use-ifaddr</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.</td> +<td>If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-router"></a>multicast-router</td> <td align="left">string</td> <td align="left"> </td> -<td> Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work. +<td>Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work. - Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).</td> +Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-snooping"></a>multicast-snooping</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.</td> +<td>Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-startup-query-count"></a>multicast-startup-query-count</td> <td align="left">uint32</td> <td align="left">2</td> -<td> Set the number of IGMP queries to send during startup phase.</td> +<td>Set the number of IGMP queries to send during startup phase.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.multicast-startup-query-interval"></a>multicast-startup-query-interval</td> <td align="left">uint64</td> <td align="left">3125</td> -<td> Sets the time (in deciseconds) between queries sent out at startup to determine membership information.</td> +<td>Sets the time (in deciseconds) between queries sent out at startup to determine membership information.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.priority"></a>priority</td> <td align="left">uint32</td> <td align="left">32768</td> -<td> Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge.</td> +<td>Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.stp"></a>stp</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.</td> +<td>Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.vlan-default-pvid"></a>vlan-default-pvid</td> <td align="left">uint32</td> <td align="left">1</td> -<td> The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.</td> +<td>The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.vlan-filtering"></a>vlan-filtering</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Control whether VLAN filtering is enabled on the bridge.</td> +<td>Control whether VLAN filtering is enabled on the bridge.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.vlan-protocol"></a>vlan-protocol</td> <td align="left">string</td> <td align="left"> </td> -<td> If specified, the protocol used for VLAN filtering. +<td>If specified, the protocol used for VLAN filtering. - Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.</td> +Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.vlan-stats-enabled"></a>vlan-stats-enabled</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Controls whether per-VLAN stats accounting is enabled.</td> +<td>Controls whether per-VLAN stats accounting is enabled.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge.vlans"></a>vlans</td> <td align="left">array of vardict</td> <td align="left"> </td> -<td> Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property. +<td>Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property. - In nmcli the VLAN list can be specified with the following syntax: +In nmcli the VLAN list can be specified with the following syntax: - $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... +$vid [pvid] [untagged] [, $vid [pvid] [untagged]]... - where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</td> +where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</td> </tr> </tbody> </table></div> @@ -1149,7 +1155,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.10"></a><h3>bridge-port setting</h3> -<p> Bridge Port Settings.</p> +<p>Bridge Port Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1169,34 +1175,34 @@ <a name="nm-settings-dbus.property.bridge-port.hairpin-mode"></a>hairpin-mode</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.</td> +<td>Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge-port.path-cost"></a>path-cost</td> <td align="left">uint32</td> <td align="left">100</td> -<td> The Spanning Tree Protocol (STP) port cost for destinations via this port.</td> +<td>The Spanning Tree Protocol (STP) port cost for destinations via this port.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge-port.priority"></a>priority</td> <td align="left">uint32</td> <td align="left">32</td> -<td> The Spanning Tree Protocol (STP) priority of this bridge port.</td> +<td>The Spanning Tree Protocol (STP) priority of this bridge port.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.bridge-port.vlans"></a>vlans</td> <td align="left">array of vardict</td> <td align="left"> </td> -<td> Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property. +<td>Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property. - In nmcli the VLAN list can be specified with the following syntax: +In nmcli the VLAN list can be specified with the following syntax: - $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... +$vid [pvid] [untagged] [, $vid [pvid] [untagged]]... - where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</td> +where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</td> </tr> </tbody> </table></div> @@ -1204,7 +1210,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.11"></a><h3>cdma setting</h3> -<p> CDMA-based Mobile Broadband Settings.</p> +<p>CDMA-based Mobile Broadband Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1224,35 +1230,35 @@ <a name="nm-settings-dbus.property.cdma.mtu"></a>mtu</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td> +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.cdma.number"></a>number</td> <td align="left">string</td> <td align="left"> </td> -<td> The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required.</td> +<td>The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.cdma.password"></a>password</td> <td align="left">string</td> <td align="left"> </td> -<td> The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.</td> +<td>The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.cdma.password-flags"></a>password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "password" property.</td> +<td>Flags indicating how to handle the "password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.cdma.username"></a>username</td> <td align="left">string</td> <td align="left"> </td> -<td> The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.</td> +<td>The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.</td> </tr> </tbody> </table></div> @@ -1260,7 +1266,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.12"></a><h3>dcb setting</h3> -<p> Data Center Bridging Settings.</p> +<p>Data Center Bridging Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1280,107 +1286,107 @@ <a name="nm-settings-dbus.property.dcb.app-fcoe-flags"></a>app-fcoe-flags</td> <td align="left">NMSettingDcbFlags (uint32)</td> <td align="left"> </td> -<td> Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> +<td>Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.app-fcoe-mode"></a>app-fcoe-mode</td> <td align="left">string</td> <td align="left"> </td> -<td> The FCoE controller mode; either "fabric" or "vn2vn". +<td>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".</td> +Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.app-fcoe-priority"></a>app-fcoe-priority</td> <td align="left">int32</td> <td align="left">-1</td> -<td> The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td> +<td>The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.app-fip-flags"></a>app-fip-flags</td> <td align="left">NMSettingDcbFlags (uint32)</td> <td align="left"> </td> -<td> Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> +<td>Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.app-fip-priority"></a>app-fip-priority</td> <td align="left">int32</td> <td align="left">-1</td> -<td> The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td> +<td>The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.app-iscsi-flags"></a>app-iscsi-flags</td> <td align="left">NMSettingDcbFlags (uint32)</td> <td align="left"> </td> -<td> Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> +<td>Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.app-iscsi-priority"></a>app-iscsi-priority</td> <td align="left">int32</td> <td align="left">-1</td> -<td> The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td> +<td>The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.priority-bandwidth"></a>priority-bandwidth</td> <td align="left">array of uint32</td> <td align="left"> </td> -<td> An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents.</td> +<td>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.priority-flow-control"></a>priority-flow-control</td> <td align="left">array of uint32</td> <td align="left"> </td> -<td> An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.</td> +<td>An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.priority-flow-control-flags"></a>priority-flow-control-flags</td> <td align="left">NMSettingDcbFlags (uint32)</td> <td align="left"> </td> -<td> Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> +<td>Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.priority-group-bandwidth"></a>priority-group-bandwidth</td> <td align="left">array of uint32</td> <td align="left"> </td> -<td> An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents.</td> +<td>An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.priority-group-flags"></a>priority-group-flags</td> <td align="left">NMSettingDcbFlags (uint32)</td> <td align="left"> </td> -<td> Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> +<td>Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.priority-group-id"></a>priority-group-id</td> <td align="left">array of uint32</td> <td align="left"> </td> -<td> An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.</td> +<td>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.priority-strict-bandwidth"></a>priority-strict-bandwidth</td> <td align="left">array of uint32</td> <td align="left"> </td> -<td> An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.</td> +<td>An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.dcb.priority-traffic-class"></a>priority-traffic-class</td> <td align="left">array of uint32</td> <td align="left"> </td> -<td> An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.</td> +<td>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.</td> </tr> </tbody> </table></div> @@ -1388,7 +1394,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.13"></a><h3>dummy setting</h3> -<p> Dummy Link Settings.</p> +<p>Dummy Link Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1408,7 +1414,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.14"></a><h3>ethtool setting</h3> -<p> Ethtool Ethernet Settings.</p> +<p>Ethtool Ethernet Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1428,7 +1434,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.15"></a><h3>generic setting</h3> -<p> Generic Link Settings.</p> +<p>Generic Link Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1448,7 +1454,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.16"></a><h3>gsm setting</h3> -<p> GSM-based Mobile Broadband Settings.</p> +<p>GSM-based Mobile Broadband Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1468,98 +1474,100 @@ <a name="nm-settings-dbus.property.gsm.apn"></a>apn</td> <td align="left">string</td> <td align="left"> </td> -<td> The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.</td> +<td>The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.auto-config"></a>auto-config</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.</td> +<td>When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.device-id"></a>device-id</td> <td align="left">string</td> <td align="left"> </td> -<td> The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device.</td> +<td>The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.home-only"></a>home-only</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.</td> +<td>When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.mtu"></a>mtu</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td> +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.network-id"></a>network-id</td> <td align="left">string</td> <td align="left"> </td> -<td> The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.</td> +<td>The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.number"></a>number</td> <td align="left">string</td> <td align="left"> </td> -<td> Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1</td> +<td>Legacy setting that used to help establishing PPP data sessions for GSM-based modems. + +This property is deprecated since version 1.16.User-provided values for this setting are no longer used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.password"></a>password</td> <td align="left">string</td> <td align="left"> </td> -<td> The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.</td> +<td>The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.password-flags"></a>password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "password" property.</td> +<td>Flags indicating how to handle the "password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.pin"></a>pin</td> <td align="left">string</td> <td align="left"> </td> -<td> If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device.</td> +<td>If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.pin-flags"></a>pin-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "pin" property.</td> +<td>Flags indicating how to handle the "pin" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.sim-id"></a>sim-id</td> <td align="left">string</td> <td align="left"> </td> -<td> The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.</td> +<td>The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.sim-operator-id"></a>sim-operator-id</td> <td align="left">string</td> <td align="left"> </td> -<td> A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.</td> +<td>A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.gsm.username"></a>username</td> <td align="left">string</td> <td align="left"> </td> -<td> The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.</td> +<td>The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.</td> </tr> </tbody> </table></div> @@ -1567,7 +1575,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.17"></a><h3>infiniband setting</h3> -<p> Infiniband Settings.</p> +<p>Infiniband Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1587,35 +1595,35 @@ <a name="nm-settings-dbus.property.infiniband.mac-address"></a>mac-address</td> <td align="left">byte array</td> <td align="left"> </td> -<td> If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td> +<td>If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.infiniband.mtu"></a>mtu</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td> +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.infiniband.p-key"></a>p-key</td> <td align="left">int32</td> <td align="left">-1</td> -<td> The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.</td> +<td>The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.infiniband.parent"></a>parent</td> <td align="left">string</td> <td align="left"> </td> -<td> The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".</td> +<td>The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.infiniband.transport-mode"></a>transport-mode</td> <td align="left">string</td> <td align="left"> </td> -<td> The IP-over-InfiniBand transport mode. Either "datagram" or "connected".</td> +<td>The IP-over-InfiniBand transport mode. Either "datagram" or "connected".</td> </tr> </tbody> </table></div> @@ -1623,7 +1631,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.18"></a><h3>ipv4 setting</h3> -<p> IPv4 Settings.</p> +<p>IPv4 Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1650,99 +1658,115 @@ <a name="nm-settings-dbus.property.ipv4.addresses"></a>addresses</td> <td align="left">array of array of uint32</td> <td align="left"> </td> -<td>Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'. Array of IPv4 address structures. Each IPv4 address structure is composed of 3 32-bit values; the first being the IPv4 address (network byte order), the second the prefix (1 - 32), and last the IPv4 gateway (network byte order). The gateway may be left as 0 if no gateway exists for that subnet.</td> +<td>Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'. +Array of IPv4 address structures. Each IPv4 address structure is composed of 3 32-bit values; the first being the IPv4 address (network byte order), the second the prefix (1 - 32), and last the IPv4 gateway (network byte order). The gateway may be left as 0 if no gateway exists for that subnet.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ipv4.auto-route-ext-gw"></a>auto-route-ext-gw</td> +<td align="left">NMTernary (int32)</td> +<td align="left"> </td> +<td>VPN connections will default to add the route automatically unless this setting is set to FALSE. + +For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dad-timeout"></a>dad-timeout</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. +<td>Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. - The property is currently implemented only for IPv4.</td> +The property is currently implemented only for IPv4.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dhcp-client-id"></a>dhcp-client-id</td> <td align="left">string</td> <td align="left"> </td> -<td> A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0. +<td>A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0. - The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links. +The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links. - The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset. +The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset. - The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id. +The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id. - The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key. +The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key. - If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.</td> +If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dhcp-fqdn"></a>dhcp-fqdn</td> <td align="left">string</td> <td align="left"> </td> -<td> If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.</td> +<td>If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dhcp-hostname"></a>dhcp-hostname</td> <td align="left">string</td> <td align="left"> </td> -<td> If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</td> +<td>If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dhcp-hostname-flags"></a>dhcp-hostname-flags</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Flags for the DHCP hostname and FQDN. +<td>Flags for the DHCP hostname and FQDN. - Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. +Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. - When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td> +When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dhcp-iaid"></a>dhcp-iaid</td> <td align="left">string</td> <td align="left"> </td> -<td> A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</td> +<td>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". + +For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id. + +For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address. + +The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dhcp-reject-servers"></a>dhcp-reject-servers</td> <td align="left">array of string</td> <td align="left"> </td> -<td> Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. +<td>Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. - For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). +For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). - This property is currently not implemented for DHCPv6.</td> +This property is currently not implemented for DHCPv6.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dhcp-send-hostname"></a>dhcp-send-hostname</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</td> +<td>If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dhcp-timeout"></a>dhcp-timeout</td> <td align="left">int32</td> <td align="left">0</td> -<td> A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). +<td>A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). - Set to 2147483647 (MAXINT32) for infinity.</td> +Set to 2147483647 (MAXINT32) for infinity.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dhcp-vendor-class-identifier"></a>dhcp-vendor-class-identifier</td> <td align="left">string</td> <td align="left"> </td> -<td> The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.</td> +<td>The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.</td> </tr> <tr> <td align="left"> @@ -1753,126 +1777,140 @@ </tr> <tr> <td align="left"> +<a name="nm-settings-dbus.property.ipv4.dns-data"></a>dns-data</td> +<td align="left">array of strings</td> +<td align="left"> </td> +<td>Array of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings-dbus.property.ipv4.dns-options"></a>dns-options</td> <td align="left">array of string</td> <td align="left"> </td> -<td> Array of DNS options as described in man 5 resolv.conf. +<td>Array of DNS options as described in man 5 resolv.conf. - NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. +NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. - The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". +The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". - The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. +The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. - When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</td> +When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dns-priority"></a>dns-priority</td> <td align="left">int32</td> <td align="left">0</td> -<td> DNS servers priority. +<td>DNS servers priority. - The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). +The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). - Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. +Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. - Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. +Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. - Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. +Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. - When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. +When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. - When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. +When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. - When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</td> +When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.dns-search"></a>dns-search</td> <td align="left">array of string</td> <td align="left"> </td> -<td> List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. +<td>List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. - When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. +When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. - When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).</td> +When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.gateway"></a>gateway</td> <td align="left">string</td> <td align="left"> </td> -<td> The gateway associated with this configuration. This is only meaningful if "addresses" is also set. +<td>The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. +Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".</td> +Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.ignore-auto-dns"></a>ignore-auto-dns</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</td> +<td>When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.ignore-auto-routes"></a>ignore-auto-routes</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</td> +<td>When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.link-local"></a>link-local</td> <td align="left">int32</td> <td align="left">0</td> -<td> Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. +<td>Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. - When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default".</td> +When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.may-fail"></a>may-fail</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</td> +<td>If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.method"></a>method</td> <td align="left">string</td> <td align="left"> </td> -<td> IP configuration method. +<td>IP configuration method. - NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. +NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. - In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. +In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. - For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. +For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. - For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</td> +For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.never-default"></a>never-default</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</td> +<td>If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ipv4.replace-local-rule"></a>replace-local-rule</td> +<td align="left">NMTernary (int32)</td> +<td align="left"> </td> +<td>Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.required-timeout"></a>required-timeout</td> <td align="left">int32</td> <td align="left">-1</td> -<td> The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. +<td>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. +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. +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).</td> +A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).</td> </tr> <tr> <td align="left"> @@ -1886,27 +1924,35 @@ <a name="nm-settings-dbus.property.ipv4.route-metric"></a>route-metric</td> <td align="left">int64</td> <td align="left">-1</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.route-table"></a>route-table</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Enable policy routing (source routing) and set the routing table used when adding routes. +<td>Enable policy routing (source routing) and set the routing table used when adding routes. - This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. +This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. - If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. +If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. - Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</td> +Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv4.routes"></a>routes</td> <td align="left">array of array of uint32</td> <td align="left"> </td> -<td>Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'. Array of IPv4 route structures. Each IPv4 route structure is composed of 4 32-bit values; the first being the destination IPv4 network or address (network byte order), the second the destination network or address prefix (1 - 32), the third being the next-hop (network byte order) if any, and the fourth being the route metric. If the metric is 0, NM will choose an appropriate default metric for the device. (There is no way to explicitly specify an actual metric of 0 with this property.)</td> +<td>Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'. +Array of IPv4 route structures. Each IPv4 route structure is composed of 4 32-bit values; the first being the destination IPv4 network or address (network byte order), the second the destination network or address prefix (1 - 32), the third being the next-hop (network byte order) if any, and the fourth being the route metric. If the metric is 0, NM will choose an appropriate default metric for the device. (There is no way to explicitly specify an actual metric of 0 with this property.)</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ipv4.routing-rules"></a>routing-rules</td> +<td align="left">array of 'a{sv}'</td> +<td align="left"> </td> +<td>Array of dictionaries for routing rules. Each routing rule supports the following options: action (y), dport-end (q), dport-start (q), family (i), from (s), from-len (y), fwmark (u), fwmask (u), iifname (s), invert (b), ipproto (s), oifname (s), priority (u), sport-end (q), sport-start (q), supress-prefixlength (i), table (u), to (s), tos (y), to-len (y), range-end (u), range-start (u).</td> </tr> </tbody> </table></div> @@ -1914,7 +1960,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.19"></a><h3>ipv6 setting</h3> -<p> IPv6 Settings.</p> +<p>IPv6 Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -1934,17 +1980,17 @@ <a name="nm-settings-dbus.property.ipv6.addr-gen-mode"></a>addr-gen-mode</td> <td align="left">int32</td> <td align="left">3</td> -<td> Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3). +<td>Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3). - If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced. +If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced. - The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced. +The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced. - The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively. +The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively. - For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions. +For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions. - Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.</td> +Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.</td> </tr> <tr> <td align="left"> @@ -1958,83 +2004,99 @@ <a name="nm-settings-dbus.property.ipv6.addresses"></a>addresses</td> <td align="left">array of legacy IPv6 address struct (a(ayuay))</td> <td align="left"> </td> -<td>Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'. Array of IPv6 address structures. Each IPv6 address structure is composed of an IPv6 address, a prefix length (0 - 128), and an IPv6 gateway address. The gateway may be zeroed out if no gateway exists for that subnet.</td> +<td>Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'. +Array of IPv6 address structures. Each IPv6 address structure is composed of an IPv6 address, a prefix length (0 - 128), and an IPv6 gateway address. The gateway may be zeroed out if no gateway exists for that subnet.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ipv6.auto-route-ext-gw"></a>auto-route-ext-gw</td> +<td align="left">NMTernary (int32)</td> +<td align="left"> </td> +<td>VPN connections will default to add the route automatically unless this setting is set to FALSE. + +For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dad-timeout"></a>dad-timeout</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. +<td>Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. - The property is currently implemented only for IPv4.</td> +The property is currently implemented only for IPv4.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dhcp-duid"></a>dhcp-duid</td> <td align="left">string</td> <td align="left"> </td> -<td> A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option. +<td>A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option. - The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id. +The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id. - The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk. +The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk. - The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt"). +The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt"). - When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.</td> +When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dhcp-hostname"></a>dhcp-hostname</td> <td align="left">string</td> <td align="left"> </td> -<td> If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</td> +<td>If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dhcp-hostname-flags"></a>dhcp-hostname-flags</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Flags for the DHCP hostname and FQDN. +<td>Flags for the DHCP hostname and FQDN. - Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. +Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. - When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td> +When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dhcp-iaid"></a>dhcp-iaid</td> <td align="left">string</td> <td align="left"> </td> -<td> A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</td> +<td>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". + +For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id. + +For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address. + +The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dhcp-reject-servers"></a>dhcp-reject-servers</td> <td align="left">array of string</td> <td align="left"> </td> -<td> Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. +<td>Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. - For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). +For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). - This property is currently not implemented for DHCPv6.</td> +This property is currently not implemented for DHCPv6.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dhcp-send-hostname"></a>dhcp-send-hostname</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</td> +<td>If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dhcp-timeout"></a>dhcp-timeout</td> <td align="left">int32</td> <td align="left">0</td> -<td> A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). +<td>A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). - Set to 2147483647 (MAXINT32) for infinity.</td> +Set to 2147483647 (MAXINT32) for infinity.</td> </tr> <tr> <td align="left"> @@ -2045,146 +2107,160 @@ </tr> <tr> <td align="left"> +<a name="nm-settings-dbus.property.ipv6.dns-data"></a>dns-data</td> +<td align="left">array of strings</td> +<td align="left"> </td> +<td>Array of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings-dbus.property.ipv6.dns-options"></a>dns-options</td> <td align="left">array of string</td> <td align="left"> </td> -<td> Array of DNS options as described in man 5 resolv.conf. +<td>Array of DNS options as described in man 5 resolv.conf. - NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. +NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. - The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". +The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". - The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. +The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. - When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</td> +When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dns-priority"></a>dns-priority</td> <td align="left">int32</td> <td align="left">0</td> -<td> DNS servers priority. +<td>DNS servers priority. - The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). +The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). - Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. +Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. - Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. +Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. - Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. +Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. - When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. +When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. - When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. +When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. - When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</td> +When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.dns-search"></a>dns-search</td> <td align="left">array of string</td> <td align="left"> </td> -<td> List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. +<td>List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. - When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. +When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. - When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).</td> +When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.gateway"></a>gateway</td> <td align="left">string</td> <td align="left"> </td> -<td> The gateway associated with this configuration. This is only meaningful if "addresses" is also set. +<td>The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. +Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".</td> +Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.ignore-auto-dns"></a>ignore-auto-dns</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</td> +<td>When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.ignore-auto-routes"></a>ignore-auto-routes</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</td> +<td>When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.ip6-privacy"></a>ip6-privacy</td> <td align="left">NMSettingIP6ConfigPrivacy (int32)</td> <td align="left"> </td> -<td> Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). +<td>Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). - Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". +Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". - If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". +If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". - Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.</td> +Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.may-fail"></a>may-fail</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</td> +<td>If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.method"></a>method</td> <td align="left">string</td> <td align="left"> </td> -<td> IP configuration method. +<td>IP configuration method. - NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. +NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. - In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. +In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. - For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. +For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. - For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</td> +For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.mtu"></a>mtu</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect.</td> +<td>Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.never-default"></a>never-default</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</td> +<td>If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.ra-timeout"></a>ra-timeout</td> <td align="left">int32</td> <td align="left">0</td> -<td> A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device. +<td>A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device. - Set to 2147483647 (MAXINT32) for infinity.</td> +Set to 2147483647 (MAXINT32) for infinity.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ipv6.replace-local-rule"></a>replace-local-rule</td> +<td align="left">NMTernary (int32)</td> +<td align="left"> </td> +<td>Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.required-timeout"></a>required-timeout</td> <td align="left">int32</td> <td align="left">-1</td> -<td> The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. +<td>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. +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. +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).</td> +A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).</td> </tr> <tr> <td align="left"> @@ -2198,34 +2274,42 @@ <a name="nm-settings-dbus.property.ipv6.route-metric"></a>route-metric</td> <td align="left">int64</td> <td align="left">-1</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.route-table"></a>route-table</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Enable policy routing (source routing) and set the routing table used when adding routes. +<td>Enable policy routing (source routing) and set the routing table used when adding routes. - This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. +This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. - If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. +If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. - Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</td> +Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.routes"></a>routes</td> <td align="left">array of legacy IPv6 route struct (a(ayuayu))</td> <td align="left"> </td> -<td>Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'. Array of IPv6 route structures. Each IPv6 route structure is composed of an IPv6 address, a prefix length (0 - 128), an IPv6 next hop address (which may be zeroed out if there is no next hop), and a metric. If the metric is 0, NM will choose an appropriate default metric for the device.</td> +<td>Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'. +Array of IPv6 route structures. Each IPv6 route structure is composed of an IPv6 address, a prefix length (0 - 128), an IPv6 next hop address (which may be zeroed out if there is no next hop), and a metric. If the metric is 0, NM will choose an appropriate default metric for the device.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ipv6.routing-rules"></a>routing-rules</td> +<td align="left">array of 'a{sv}'</td> +<td align="left"> </td> +<td>Array of dictionaries for routing rules. Each routing rule supports the following options: action (y), dport-end (q), dport-start (q), family (i), from (s), from-len (y), fwmark (u), fwmask (u), iifname (s), invert (b), ipproto (s), oifname (s), priority (u), sport-end (q), sport-start (q), supress-prefixlength (i), table (u), to (s), tos (y), to-len (y), range-end (u), range-start (u).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ipv6.token"></a>token</td> <td align="left">string</td> <td align="left"> </td> -<td> Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.</td> +<td>Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.</td> </tr> </tbody> </table></div> @@ -2233,7 +2317,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.20"></a><h3>ip-tunnel setting</h3> -<p> IP Tunneling Settings.</p> +<p>IP Tunneling Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2253,91 +2337,98 @@ <a name="nm-settings-dbus.property.ip-tunnel.encapsulation-limit"></a>encapsulation-limit</td> <td align="left">uint32</td> <td align="left">0</td> -<td> How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.</td> +<td>How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.flags"></a>flags</td> <td align="left">uint32</td> <td align="left">0</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.flow-label"></a>flow-label</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.</td> +<td>The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ip-tunnel.fwmark"></a>fwmark</td> +<td align="left">uint32</td> +<td align="left">0</td> +<td>The fwmark value to assign to tunnel packets. This property can be set to a non zero value only on VTI and VTI6 tunnels.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.input-key"></a>input-key</td> <td align="left">string</td> <td align="left"> </td> -<td> The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</td> +<td>The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.local"></a>local</td> <td align="left">string</td> <td align="left"> </td> -<td> The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.</td> +<td>The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.mode"></a>mode</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).</td> +<td>The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.mtu"></a>mtu</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.</td> +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.output-key"></a>output-key</td> <td align="left">string</td> <td align="left"> </td> -<td> The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</td> +<td>The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.parent"></a>parent</td> <td align="left">string</td> <td align="left"> </td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.path-mtu-discovery"></a>path-mtu-discovery</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> Whether to enable Path MTU Discovery on this tunnel.</td> +<td>Whether to enable Path MTU Discovery on this tunnel.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.remote"></a>remote</td> <td align="left">string</td> <td align="left"> </td> -<td> The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.</td> +<td>The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.tos"></a>tos</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.</td> +<td>The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ip-tunnel.ttl"></a>ttl</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.</td> +<td>The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.</td> </tr> </tbody> </table></div> @@ -2345,7 +2436,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.21"></a><h3>macsec setting</h3> -<p> MACSec Settings.</p> +<p>MACSec Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2365,63 +2456,63 @@ <a name="nm-settings-dbus.property.macsec.encrypt"></a>encrypt</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> Whether the transmitted traffic must be encrypted.</td> +<td>Whether the transmitted traffic must be encrypted.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macsec.mka-cak"></a>mka-cak</td> <td align="left">string</td> <td align="left"> </td> -<td> The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.</td> +<td>The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macsec.mka-cak-flags"></a>mka-cak-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "mka-cak" property.</td> +<td>Flags indicating how to handle the "mka-cak" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macsec.mka-ckn"></a>mka-ckn</td> <td align="left">string</td> <td align="left"> </td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macsec.mode"></a>mode</td> <td align="left">int32</td> <td align="left">0</td> -<td> Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.</td> +<td>Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macsec.parent"></a>parent</td> <td align="left">string</td> <td align="left"> </td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macsec.port"></a>port</td> <td align="left">int32</td> <td align="left">1</td> -<td> The port component of the SCI (Secure Channel Identifier), between 1 and 65534.</td> +<td>The port component of the SCI (Secure Channel Identifier), between 1 and 65534.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macsec.send-sci"></a>send-sci</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> Specifies whether the SCI (Secure Channel Identifier) is included in every packet.</td> +<td>Specifies whether the SCI (Secure Channel Identifier) is included in every packet.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macsec.validation"></a>validation</td> <td align="left">int32</td> <td align="left">2</td> -<td> Specifies the validation mode for incoming frames.</td> +<td>Specifies the validation mode for incoming frames.</td> </tr> </tbody> </table></div> @@ -2429,7 +2520,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.22"></a><h3>macvlan setting</h3> -<p> MAC VLAN Settings.</p> +<p>MAC VLAN Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2449,28 +2540,28 @@ <a name="nm-settings-dbus.property.macvlan.mode"></a>mode</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.</td> +<td>The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macvlan.parent"></a>parent</td> <td align="left">string</td> <td align="left"> </td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macvlan.promiscuous"></a>promiscuous</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> Whether the interface should be put in promiscuous mode.</td> +<td>Whether the interface should be put in promiscuous mode.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.macvlan.tap"></a>tap</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Whether the interface should be a MACVTAP.</td> +<td>Whether the interface should be a MACVTAP.</td> </tr> </tbody> </table></div> @@ -2478,7 +2569,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.23"></a><h3>match setting</h3> -<p> Match settings.</p> +<p>Match settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2498,42 +2589,42 @@ <a name="nm-settings-dbus.property.match.driver"></a>driver</td> <td align="left">array of string</td> <td align="left"> </td> -<td> A list of driver names to match. Each element is a shell wildcard pattern. +<td>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.</td> +See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.match.interface-name"></a>interface-name</td> <td align="left">array of string</td> <td align="left"> </td> -<td> A list of interface names to match. Each element is a shell wildcard pattern. +<td>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".</td> +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".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.match.kernel-command-line"></a>kernel-command-line</td> <td align="left">array of string</td> <td align="left"> </td> -<td> 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. +<td>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.</td> +See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the match.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.match.path"></a>path</td> <td align="left">array of string</td> <td align="left"> </td> -<td> 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. +<td>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". +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"). +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. +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.</td> +See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.</td> </tr> </tbody> </table></div> @@ -2541,7 +2632,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.24"></a><h3>802-11-olpc-mesh setting</h3> -<p> OLPC Wireless Mesh Settings.</p> +<p>OLPC Wireless Mesh Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2561,23 +2652,23 @@ <a name="nm-settings-dbus.property.802-11-olpc-mesh.channel"></a>channel</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Channel on which the mesh network to join is located.</td> +<td>Channel on which the mesh network to join is located.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-olpc-mesh.dhcp-anycast-address"></a>dhcp-anycast-address</td> <td align="left">byte array</td> <td align="left"> </td> -<td> 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. +<td>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.</td> +This is currently only implemented by dhclient DHCP plugin.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-olpc-mesh.ssid"></a>ssid</td> <td align="left">byte array</td> <td align="left"> </td> -<td> SSID of the mesh network to join.</td> +<td>SSID of the mesh network to join.</td> </tr> </tbody> </table></div> @@ -2585,7 +2676,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.25"></a><h3>ovs-bridge setting</h3> -<p> OvsBridge Link Settings.</p> +<p>OvsBridge Link Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2605,35 +2696,35 @@ <a name="nm-settings-dbus.property.ovs-bridge.datapath-type"></a>datapath-type</td> <td align="left">string</td> <td align="left"> </td> -<td> The data path type. One of "system", "netdev" or empty.</td> +<td>The data path type. One of "system", "netdev" or empty.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-bridge.fail-mode"></a>fail-mode</td> <td align="left">string</td> <td align="left"> </td> -<td> The bridge failure mode. One of "secure", "standalone" or empty.</td> +<td>The bridge failure mode. One of "secure", "standalone" or empty.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-bridge.mcast-snooping-enable"></a>mcast-snooping-enable</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Enable or disable multicast snooping.</td> +<td>Enable or disable multicast snooping.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-bridge.rstp-enable"></a>rstp-enable</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Enable or disable RSTP.</td> +<td>Enable or disable RSTP.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-bridge.stp-enable"></a>stp-enable</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Enable or disable STP.</td> +<td>Enable or disable STP.</td> </tr> </tbody> </table></div> @@ -2641,7 +2732,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.26"></a><h3>ovs-dpdk setting</h3> -<p> OvsDpdk Link Settings.</p> +<p>OvsDpdk Link Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2661,14 +2752,28 @@ <a name="nm-settings-dbus.property.ovs-dpdk.devargs"></a>devargs</td> <td align="left">string</td> <td align="left"> </td> -<td> Open vSwitch DPDK device arguments.</td> +<td>Open vSwitch DPDK device arguments.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-dpdk.n-rxq"></a>n-rxq</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.</td> +<td>Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ovs-dpdk.n-rxq-desc"></a>n-rxq-desc</td> +<td align="left">uint32</td> +<td align="left">0</td> +<td>The rx queue size (number of rx descriptors) for DPDK ports. Must be zero or a power of 2 between 1 and 4096, and supported by the hardware. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures 2048 descriptors.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ovs-dpdk.n-txq-desc"></a>n-txq-desc</td> +<td align="left">uint32</td> +<td align="left">0</td> +<td>The tx queue size (number of tx descriptors) for DPDK ports. Must be zero or a power of 2 between 1 and 4096, and supported by the hardware. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures 2048 descriptors.</td> </tr> </tbody> </table></div> @@ -2676,7 +2781,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.27"></a><h3>ovs-interface setting</h3> -<p> Open vSwitch Interface Settings.</p> +<p>Open vSwitch Interface Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2690,19 +2795,28 @@ <th>Default Value</th> <th>Value Description</th> </tr></thead> -<tbody><tr> +<tbody> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ovs-interface.ofport-request"></a>ofport-request</td> +<td align="left">uint32</td> +<td align="left">0</td> +<td>Open vSwitch openflow port number. Defaults to zero which means that port number will not be specified and it will be chosen randomly by ovs. OpenFlow ports are the network interfaces for passing packets between OpenFlow processing and the rest of the network. OpenFlow switches connect logically to each other via their OpenFlow ports.</td> +</tr> +<tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-interface.type"></a>type</td> <td align="left">string</td> <td align="left"> </td> -<td> The interface type. Either "internal", "system", "patch", "dpdk", or empty.</td> -</tr></tbody> +<td>The interface type. Either "internal", "system", "patch", "dpdk", or empty.</td> +</tr> +</tbody> </table></div> </div> <hr> <div class="refsect2"> <a name="id-1.2.9.4.28"></a><h3>ovs-patch setting</h3> -<p> OvsPatch Link Settings.</p> +<p>OvsPatch Link Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2721,14 +2835,14 @@ <a name="nm-settings-dbus.property.ovs-patch.peer"></a>peer</td> <td align="left">string</td> <td align="left"> </td> -<td> 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.</td> +<td>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.</td> </tr></tbody> </table></div> </div> <hr> <div class="refsect2"> <a name="id-1.2.9.4.29"></a><h3>ovs-port setting</h3> -<p> OvsPort Link Settings.</p> +<p>OvsPort Link Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2748,42 +2862,51 @@ <a name="nm-settings-dbus.property.ovs-port.bond-downdelay"></a>bond-downdelay</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The time port must be inactive in order to be considered down.</td> +<td>The time port must be inactive in order to be considered down.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-port.bond-mode"></a>bond-mode</td> <td align="left">string</td> <td align="left"> </td> -<td> Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".</td> +<td>Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-port.bond-updelay"></a>bond-updelay</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The time port must be active before it starts forwarding traffic.</td> +<td>The time port must be active before it starts forwarding traffic.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-port.lacp"></a>lacp</td> <td align="left">string</td> <td align="left"> </td> -<td> LACP mode. One of "active", "off", or "passive".</td> +<td>LACP mode. One of "active", "off", or "passive".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-port.tag"></a>tag</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The VLAN tag in the range 0-4095.</td> +<td>The VLAN tag in the range 0-4095.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.ovs-port.trunks"></a>trunks</td> +<td align="left">array of vardict</td> +<td align="left"> </td> +<td>A list of VLAN ranges that this port trunks. + +The property is valid only for ports with mode "trunk", "native-tagged", or "native-untagged port". If it is empty, the port trunks all VLANs.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ovs-port.vlan-mode"></a>vlan-mode</td> <td align="left">string</td> <td align="left"> </td> -<td> The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk" or unset.</td> +<td>The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk", "dot1q-tunnel" or unset.</td> </tr> </tbody> </table></div> @@ -2791,7 +2914,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.30"></a><h3>ppp setting</h3> -<p> Point-to-Point Protocol Settings.</p> +<p>Point-to-Point Protocol Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2811,126 +2934,126 @@ <a name="nm-settings-dbus.property.ppp.baud"></a>baud</td> <td align="left">uint32</td> <td align="left">0</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.crtscts"></a>crtscts</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.lcp-echo-failure"></a>lcp-echo-failure</td> <td align="left">uint32</td> <td align="left">0</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.lcp-echo-interval"></a>lcp-echo-interval</td> <td align="left">uint32</td> <td align="left">0</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.mppe-stateful"></a>mppe-stateful</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, stateful MPPE is used. See pppd documentation for more information on stateful MPPE.</td> +<td>If TRUE, stateful MPPE is used. See pppd documentation for more information on stateful MPPE.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.mru"></a>mru</td> <td align="left">uint32</td> <td align="left">0</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.mtu"></a>mtu</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, instruct pppd to send packets no larger than the specified size.</td> +<td>If non-zero, instruct pppd to send packets no larger than the specified size.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.no-vj-comp"></a>no-vj-comp</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, Van Jacobsen TCP header compression will not be requested.</td> +<td>If TRUE, Van Jacobsen TCP header compression will not be requested.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.noauth"></a>noauth</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.nobsdcomp"></a>nobsdcomp</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, BSD compression will not be requested.</td> +<td>If TRUE, BSD compression will not be requested.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.nodeflate"></a>nodeflate</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, "deflate" compression will not be requested.</td> +<td>If TRUE, "deflate" compression will not be requested.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.refuse-chap"></a>refuse-chap</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, the CHAP authentication method will not be used.</td> +<td>If TRUE, the CHAP authentication method will not be used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.refuse-eap"></a>refuse-eap</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, the EAP authentication method will not be used.</td> +<td>If TRUE, the EAP authentication method will not be used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.refuse-mschap"></a>refuse-mschap</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, the MSCHAP authentication method will not be used.</td> +<td>If TRUE, the MSCHAP authentication method will not be used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.refuse-mschapv2"></a>refuse-mschapv2</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, the MSCHAPv2 authentication method will not be used.</td> +<td>If TRUE, the MSCHAPv2 authentication method will not be used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.refuse-pap"></a>refuse-pap</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, the PAP authentication method will not be used.</td> +<td>If TRUE, the PAP authentication method will not be used.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.require-mppe"></a>require-mppe</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.ppp.require-mppe-128"></a>require-mppe-128</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> 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.</td> +<td>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.</td> </tr> </tbody> </table></div> @@ -2938,7 +3061,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.31"></a><h3>pppoe setting</h3> -<p> PPP-over-Ethernet Settings.</p> +<p>PPP-over-Ethernet Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -2958,35 +3081,35 @@ <a name="nm-settings-dbus.property.pppoe.parent"></a>parent</td> <td align="left">string</td> <td align="left"> </td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.pppoe.password"></a>password</td> <td align="left">string</td> <td align="left"> </td> -<td> Password used to authenticate with the PPPoE service.</td> +<td>Password used to authenticate with the PPPoE service.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.pppoe.password-flags"></a>password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "password" property.</td> +<td>Flags indicating how to handle the "password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.pppoe.service"></a>service</td> <td align="left">string</td> <td align="left"> </td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.pppoe.username"></a>username</td> <td align="left">string</td> <td align="left"> </td> -<td> Username used to authenticate with the PPPoE service.</td> +<td>Username used to authenticate with the PPPoE service.</td> </tr> </tbody> </table></div> @@ -2994,7 +3117,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.32"></a><h3>proxy setting</h3> -<p> WWW Proxy Settings.</p> +<p>WWW Proxy Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3014,28 +3137,28 @@ <a name="nm-settings-dbus.property.proxy.browser-only"></a>browser-only</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Whether the proxy configuration is for browser only.</td> +<td>Whether the proxy configuration is for browser only.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.proxy.method"></a>method</td> <td align="left">int32</td> <td align="left">0</td> -<td> Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)</td> +<td>Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.proxy.pac-script"></a>pac-script</td> <td align="left">string</td> <td align="left"> </td> -<td> PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.</td> +<td>PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.proxy.pac-url"></a>pac-url</td> <td align="left">string</td> <td align="left"> </td> -<td> PAC URL for obtaining PAC file.</td> +<td>PAC URL for obtaining PAC file.</td> </tr> </tbody> </table></div> @@ -3043,7 +3166,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.33"></a><h3>serial setting</h3> -<p> Serial Link Settings.</p> +<p>Serial Link Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3063,14 +3186,14 @@ <a name="nm-settings-dbus.property.serial.baud"></a>baud</td> <td align="left">uint32</td> <td align="left">57600</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.serial.bits"></a>bits</td> <td align="left">uint32</td> <td align="left">8</td> -<td> Byte-width of the serial communication. The 8 in "8n1" for example.</td> +<td>Byte-width of the serial communication. The 8 in "8n1" for example.</td> </tr> <tr> <td align="left"> @@ -3084,14 +3207,14 @@ <a name="nm-settings-dbus.property.serial.send-delay"></a>send-delay</td> <td align="left">uint64</td> <td align="left">0</td> -<td> Time to delay between each byte sent to the modem, in microseconds.</td> +<td>Time to delay between each byte sent to the modem, in microseconds.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.serial.stopbits"></a>stopbits</td> <td align="left">uint32</td> <td align="left">1</td> -<td> Number of stop bits for communication on the serial port. Either 1 or 2. The 1 in "8n1" for example.</td> +<td>Number of stop bits for communication on the serial port. Either 1 or 2. The 1 in "8n1" for example.</td> </tr> </tbody> </table></div> @@ -3099,7 +3222,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.34"></a><h3>sriov setting</h3> -<p> SR-IOV settings.</p> +<p>SR-IOV settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3119,47 +3242,47 @@ <a name="nm-settings-dbus.property.sriov.autoprobe-drivers"></a>autoprobe-drivers</td> <td align="left">NMTernary (int32)</td> <td align="left"> </td> -<td> Whether to autoprobe virtual functions by a compatible driver. +<td>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_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. +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).</td> +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).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.sriov.total-vfs"></a>total-vfs</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The total number of virtual functions to create. +<td>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.</td> +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.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.sriov.vfs"></a>vfs</td> <td align="left">array of vardict</td> <td align="left"> </td> -<td> Array of virtual function descriptors. +<td>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. +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: +When represented as string a VF is in the form: - "INDEX [ATTR=VALUE[ ATTR=VALUE]...]". +"INDEX [ATTR=VALUE[ ATTR=VALUE]...]". - for example: +for example: - "2 mac=00:11:22:33:44:55 spoof-check=true". +"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. +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 +The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form - "ID[.PRIORITY[.PROTO]]". +"ID[.PRIORITY[.PROTO]]". - PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.</td> +PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.</td> </tr> </tbody> </table></div> @@ -3167,7 +3290,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.35"></a><h3>tc setting</h3> -<p> Linux Traffic Control Settings.</p> +<p>Linux Traffic Control Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3187,22 +3310,22 @@ <a name="nm-settings-dbus.property.tc.qdiscs"></a>qdiscs</td> <td align="left">array of vardict</td> <td align="left"> </td> -<td> Array of TC queueing disciplines. +<td>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. +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.</td> +If the "tc" setting is not present, NetworkManager doesn't touch the qdiscs present on the interface.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.tc.tfilters"></a>tfilters</td> <td align="left">array of vardict</td> <td align="left"> </td> -<td> Array of TC traffic filters. +<td>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. +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.</td> +If the "tc" setting is not present, NetworkManager doesn't touch the filters present on the interface.</td> </tr> </tbody> </table></div> @@ -3210,7 +3333,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.36"></a><h3>team setting</h3> -<p> Teaming Settings.</p> +<p>Teaming Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3230,7 +3353,7 @@ <a name="nm-settings-dbus.property.team.config"></a>config</td> <td align="left">string</td> <td align="left"> </td> -<td> The JSON configuration for the team network interface. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</td> +<td>The JSON configuration for the team network interface. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</td> </tr> <tr> <td align="left"> @@ -3244,105 +3367,105 @@ <a name="nm-settings-dbus.property.team.link-watchers"></a>link-watchers</td> <td align="left">array of vardict</td> <td align="left"> </td> -<td> Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</td> +<td>Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.mcast-rejoin-count"></a>mcast-rejoin-count</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd mcast_rejoin.count.</td> +<td>Corresponds to the teamd mcast_rejoin.count.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.mcast-rejoin-interval"></a>mcast-rejoin-interval</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd mcast_rejoin.interval.</td> +<td>Corresponds to the teamd mcast_rejoin.interval.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.notify-peers-count"></a>notify-peers-count</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd notify_peers.count.</td> +<td>Corresponds to the teamd notify_peers.count.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.notify-peers-interval"></a>notify-peers-interval</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd notify_peers.interval.</td> +<td>Corresponds to the teamd notify_peers.interval.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner"></a>runner</td> <td align="left">string</td> <td align="left"> </td> -<td> Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".</td> +<td>Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner-active"></a>runner-active</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> Corresponds to the teamd runner.active.</td> +<td>Corresponds to the teamd runner.active.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner-agg-select-policy"></a>runner-agg-select-policy</td> <td align="left">string</td> <td align="left"> </td> -<td> Corresponds to the teamd runner.agg_select_policy.</td> +<td>Corresponds to the teamd runner.agg_select_policy.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner-fast-rate"></a>runner-fast-rate</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Corresponds to the teamd runner.fast_rate.</td> +<td>Corresponds to the teamd runner.fast_rate.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner-hwaddr-policy"></a>runner-hwaddr-policy</td> <td align="left">string</td> <td align="left"> </td> -<td> Corresponds to the teamd runner.hwaddr_policy.</td> +<td>Corresponds to the teamd runner.hwaddr_policy.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner-min-ports"></a>runner-min-ports</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd runner.min_ports.</td> +<td>Corresponds to the teamd runner.min_ports.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner-sys-prio"></a>runner-sys-prio</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd runner.sys_prio.</td> +<td>Corresponds to the teamd runner.sys_prio.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner-tx-balancer"></a>runner-tx-balancer</td> <td align="left">string</td> <td align="left"> </td> -<td> Corresponds to the teamd runner.tx_balancer.name.</td> +<td>Corresponds to the teamd runner.tx_balancer.name.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner-tx-balancer-interval"></a>runner-tx-balancer-interval</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd runner.tx_balancer.interval.</td> +<td>Corresponds to the teamd runner.tx_balancer.interval.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team.runner-tx-hash"></a>runner-tx-hash</td> <td align="left">array of string</td> <td align="left"> </td> -<td> Corresponds to the teamd runner.tx_hash.</td> +<td>Corresponds to the teamd runner.tx_hash.</td> </tr> </tbody> </table></div> @@ -3350,7 +3473,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.37"></a><h3>team-port setting</h3> -<p> Team Port Settings.</p> +<p>Team Port Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3370,49 +3493,49 @@ <a name="nm-settings-dbus.property.team-port.config"></a>config</td> <td align="left">string</td> <td align="left"> </td> -<td> The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</td> +<td>The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team-port.lacp-key"></a>lacp-key</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd ports.PORTIFNAME.lacp_key.</td> +<td>Corresponds to the teamd ports.PORTIFNAME.lacp_key.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team-port.lacp-prio"></a>lacp-prio</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd ports.PORTIFNAME.lacp_prio.</td> +<td>Corresponds to the teamd ports.PORTIFNAME.lacp_prio.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team-port.link-watchers"></a>link-watchers</td> <td align="left">array of vardict</td> <td align="left"> </td> -<td> Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</td> +<td>Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team-port.prio"></a>prio</td> <td align="left">int32</td> <td align="left">0</td> -<td> Corresponds to the teamd ports.PORTIFNAME.prio.</td> +<td>Corresponds to the teamd ports.PORTIFNAME.prio.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team-port.queue-id"></a>queue-id</td> <td align="left">int32</td> <td align="left">-1</td> -<td> Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.</td> +<td>Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.team-port.sticky"></a>sticky</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Corresponds to the teamd ports.PORTIFNAME.sticky.</td> +<td>Corresponds to the teamd ports.PORTIFNAME.sticky.</td> </tr> </tbody> </table></div> @@ -3420,7 +3543,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.38"></a><h3>tun setting</h3> -<p> Tunnel Settings.</p> +<p>Tunnel Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3440,42 +3563,42 @@ <a name="nm-settings-dbus.property.tun.group"></a>group</td> <td align="left">string</td> <td align="left"> </td> -<td> The group ID which will own the device. If set to NULL everyone will be able to use the device.</td> +<td>The group ID which will own the device. If set to NULL everyone will be able to use the device.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.tun.mode"></a>mode</td> <td align="left">uint32</td> <td align="left">1</td> -<td> The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one.</td> +<td>The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.tun.multi-queue"></a>multi-queue</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If the property is set to TRUE, the interface will support multiple file descriptors (queues) to parallelize packet sending or receiving. Otherwise, the interface will only support a single queue.</td> +<td>If the property is set to TRUE, the interface will support multiple file descriptors (queues) to parallelize packet sending or receiving. Otherwise, the interface will only support a single queue.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.tun.owner"></a>owner</td> <td align="left">string</td> <td align="left"> </td> -<td> The user ID which will own the device. If set to NULL everyone will be able to use the device.</td> +<td>The user ID which will own the device. If set to NULL everyone will be able to use the device.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.tun.pi"></a>pi</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.</td> +<td>If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.tun.vnet-hdr"></a>vnet-hdr</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.</td> +<td>If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.</td> </tr> </tbody> </table></div> @@ -3483,7 +3606,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.39"></a><h3>user setting</h3> -<p> General User Profile Settings.</p> +<p>General User Profile Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3502,14 +3625,14 @@ <a name="nm-settings-dbus.property.user.data"></a>data</td> <td align="left">dict of string to string</td> <td align="left">{}</td> -<td> A dictionary of key/value pairs with user data. This data is ignored by NetworkManager and can be used at the users discretion. The keys only support a strict ascii format, but the values can be arbitrary UTF8 strings up to a certain length.</td> +<td>A dictionary of key/value pairs with user data. This data is ignored by NetworkManager and can be used at the users discretion. The keys only support a strict ascii format, but the values can be arbitrary UTF8 strings up to a certain length.</td> </tr></tbody> </table></div> </div> <hr> <div class="refsect2"> <a name="id-1.2.9.4.40"></a><h3>vlan setting</h3> -<p> VLAN Settings.</p> +<p>VLAN Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3529,30 +3652,30 @@ <a name="nm-settings-dbus.property.vlan.egress-priority-map"></a>egress-priority-map</td> <td align="left">array of string</td> <td align="left"> </td> -<td> For outgoing packets, a list of mappings from Linux SKB priorities to 802.1p priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</td> +<td>For outgoing packets, a list of mappings from Linux SKB priorities to 802.1p priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vlan.flags"></a>flags</td> <td align="left">NMVlanFlags (uint32)</td> <td align="left"> </td> -<td> One or more flags which control the behavior and features of the VLAN interface. Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol). +<td>One or more flags which control the behavior and features of the VLAN interface. Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol). - The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.</td> +The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vlan.id"></a>id</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.</td> +<td>The VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vlan.ingress-priority-map"></a>ingress-priority-map</td> <td align="left">array of string</td> <td align="left"> </td> -<td> For incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</td> +<td>For incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</td> </tr> <tr> <td align="left"> @@ -3566,7 +3689,16 @@ <a name="nm-settings-dbus.property.vlan.parent"></a>parent</td> <td align="left">string</td> <td align="left"> </td> -<td> If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</td> +<td>If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.vlan.protocol"></a>protocol</td> +<td align="left">string</td> +<td align="left"> </td> +<td>Specifies the VLAN protocol to use for encapsulation. + +Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.</td> </tr> </tbody> </table></div> @@ -3574,7 +3706,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.41"></a><h3>vpn setting</h3> -<p> VPN Settings.</p> +<p>VPN Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3594,42 +3726,42 @@ <a name="nm-settings-dbus.property.vpn.data"></a>data</td> <td align="left">dict of string to string</td> <td align="left">{}</td> -<td> Dictionary of key/value pairs of VPN plugin specific data. Both keys and values must be strings.</td> +<td>Dictionary of key/value pairs of VPN plugin specific data. Both keys and values must be strings.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vpn.persistent"></a>persistent</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.</td> +<td>If the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vpn.secrets"></a>secrets</td> <td align="left">dict of string to string</td> <td align="left">{}</td> -<td> Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys. Both keys and values must be strings.</td> +<td>Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys. Both keys and values must be strings.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vpn.service-type"></a>service-type</td> <td align="left">string</td> <td align="left"> </td> -<td> D-Bus service name of the VPN plugin that this setting uses to connect to its network. i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.</td> +<td>D-Bus service name of the VPN plugin that this setting uses to connect to its network. i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vpn.timeout"></a>timeout</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Timeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.</td> +<td>Timeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vpn.user-name"></a>user-name</td> <td align="left">string</td> <td align="left"> </td> -<td> If the VPN connection requires a user name for authentication, that name should be provided here. If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty. If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.</td> +<td>If the VPN connection requires a user name for authentication, that name should be provided here. If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty. If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.</td> </tr> </tbody> </table></div> @@ -3637,7 +3769,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.42"></a><h3>vrf setting</h3> -<p> VRF settings.</p> +<p>VRF settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3656,14 +3788,14 @@ <a name="nm-settings-dbus.property.vrf.table"></a>table</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The routing table for this VRF.</td> +<td>The routing table for this VRF.</td> </tr></tbody> </table></div> </div> <hr> <div class="refsect2"> <a name="id-1.2.9.4.43"></a><h3>vxlan setting</h3> -<p> VXLAN Settings.</p> +<p>VXLAN Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3683,112 +3815,112 @@ <a name="nm-settings-dbus.property.vxlan.ageing"></a>ageing</td> <td align="left">uint32</td> <td align="left">300</td> -<td> Specifies the lifetime in seconds of FDB entries learnt by the kernel.</td> +<td>Specifies the lifetime in seconds of FDB entries learnt by the kernel.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.destination-port"></a>destination-port</td> <td align="left">uint32</td> <td align="left">8472</td> -<td> Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.</td> +<td>Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.id"></a>id</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.</td> +<td>Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.l2-miss"></a>l2-miss</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Specifies whether netlink LL ADDR miss notifications are generated.</td> +<td>Specifies whether netlink LL ADDR miss notifications are generated.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.l3-miss"></a>l3-miss</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Specifies whether netlink IP ADDR miss notifications are generated.</td> +<td>Specifies whether netlink IP ADDR miss notifications are generated.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.learning"></a>learning</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.</td> +<td>Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.limit"></a>limit</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.</td> +<td>Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.local"></a>local</td> <td align="left">string</td> <td align="left"> </td> -<td> If given, specifies the source IP address to use in outgoing packets.</td> +<td>If given, specifies the source IP address to use in outgoing packets.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.parent"></a>parent</td> <td align="left">string</td> <td align="left"> </td> -<td> If given, specifies the parent interface name or parent connection UUID.</td> +<td>If given, specifies the parent interface name or parent connection UUID.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.proxy"></a>proxy</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Specifies whether ARP proxy is turned on.</td> +<td>Specifies whether ARP proxy is turned on.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.remote"></a>remote</td> <td align="left">string</td> <td align="left"> </td> -<td> Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.</td> +<td>Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.rsc"></a>rsc</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> Specifies whether route short circuit is turned on.</td> +<td>Specifies whether route short circuit is turned on.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.source-port-max"></a>source-port-max</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.</td> +<td>Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.source-port-min"></a>source-port-min</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.</td> +<td>Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.tos"></a>tos</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Specifies the TOS value to use in outgoing packets.</td> +<td>Specifies the TOS value to use in outgoing packets.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.vxlan.ttl"></a>ttl</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Specifies the time-to-live value to use in outgoing packets.</td> +<td>Specifies the time-to-live value to use in outgoing packets.</td> </tr> </tbody> </table></div> @@ -3796,7 +3928,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.44"></a><h3>wifi-p2p setting</h3> -<p> Wi-Fi P2P Settings.</p> +<p>Wi-Fi P2P Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3816,25 +3948,25 @@ <a name="nm-settings-dbus.property.wifi-p2p.peer"></a>peer</td> <td align="left">string</td> <td align="left"> </td> -<td> The P2P device that should be connected to. Currently, this is the only way to create or join a group.</td> +<td>The P2P device that should be connected to. Currently, this is the only way to create or join a group.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wifi-p2p.wfd-ies"></a>wfd-ies</td> <td align="left">byte array</td> <td align="left"> </td> -<td> The Wi-Fi Display (WFD) Information Elements (IEs) to set. +<td>The Wi-Fi Display (WFD) Information Elements (IEs) to set. - Wi-Fi Display requires a protocol specific information element to be set in certain Wi-Fi frames. These can be specified here for the purpose of establishing a connection. This setting is only useful when implementing a Wi-Fi Display client.</td> +Wi-Fi Display requires a protocol specific information element to be set in certain Wi-Fi frames. These can be specified here for the purpose of establishing a connection. This setting is only useful when implementing a Wi-Fi Display client.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wifi-p2p.wps-method"></a>wps-method</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Flags indicating which mode of WPS is to be used. +<td>Flags indicating which mode of WPS is to be used. - There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.</td> +There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.</td> </tr> </tbody> </table></div> @@ -3842,7 +3974,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.45"></a><h3>wimax setting</h3> -<p> WiMax Settings.</p> +<p>WiMax Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3862,14 +3994,18 @@ <a name="nm-settings-dbus.property.wimax.mac-address"></a>mac-address</td> <td align="left">byte array</td> <td align="left"> </td> -<td> If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing). Deprecated: 1</td> +<td>If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing). + +This property is deprecated since version 1.2.WiMAX is no longer supported.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wimax.network-name"></a>network-name</td> <td align="left">string</td> <td align="left"> </td> -<td> Network Service Provider (NSP) name of the WiMAX network this connection should use. Deprecated: 1</td> +<td>Network Service Provider (NSP) name of the WiMAX network this connection should use. + +This property is deprecated since version 1.2.WiMAX is no longer supported.</td> </tr> </tbody> </table></div> @@ -3877,7 +4013,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.46"></a><h3>802-3-ethernet setting</h3> -<p> Wired Ethernet Settings.</p> +<p>Wired Ethernet Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -3897,7 +4033,7 @@ <a name="nm-settings-dbus.property.802-3-ethernet.accept-all-mac-addresses"></a>accept-all-mac-addresses</td> <td align="left">NMTernary (int32)</td> <td align="left"> </td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> @@ -3911,7 +4047,7 @@ <a name="nm-settings-dbus.property.802-3-ethernet.auto-negotiate"></a>auto-negotiate</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> 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.</td> +<td>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.</td> </tr> <tr> <td align="left"> @@ -3925,94 +4061,94 @@ <a name="nm-settings-dbus.property.802-3-ethernet.duplex"></a>duplex</td> <td align="left">string</td> <td align="left"> </td> -<td> When a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.</td> +<td>When a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.generate-mac-address-mask"></a>generate-mac-address-mask</td> <td align="left">string</td> <td align="left"> </td> -<td> With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. +<td>With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. - If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. +If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. - If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. +If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. - If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. +If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. - If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</td> +If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.mac-address"></a>mac-address</td> <td align="left">byte array</td> <td align="left"> </td> -<td> If specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td> +<td>If specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.mac-address-blacklist"></a>mac-address-blacklist</td> <td align="left">array of string</td> <td align="left"> </td> -<td> If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).</td> +<td>If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.mtu"></a>mtu</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td> +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.port"></a>port</td> <td align="left">string</td> <td align="left"> </td> -<td> Specific port type to use if the device supports multiple attachment methods. One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.</td> +<td>Specific port type to use if the device supports multiple attachment methods. One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.s390-nettype"></a>s390-nettype</td> <td align="left">string</td> <td align="left"> </td> -<td> s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.</td> +<td>s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.s390-options"></a>s390-options</td> <td align="left">dict of string to string</td> <td align="left">{}</td> -<td> 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]). +<td>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.</td> +Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.s390-subchannels"></a>s390-subchannels</td> <td align="left">array of string</td> <td align="left"> </td> -<td> Identifies specific subchannels that this network device uses for communication with z/VM or s390 host. Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels. The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.</td> +<td>Identifies specific subchannels that this network device uses for communication with z/VM or s390 host. Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels. The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.speed"></a>speed</td> <td align="left">uint32</td> <td align="left">0</td> -<td> When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.</td> +<td>When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.wake-on-lan"></a>wake-on-lan</td> <td align="left">uint32</td> <td align="left">1</td> -<td> The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</td> +<td>The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-3-ethernet.wake-on-lan-password"></a>wake-on-lan-password</td> <td align="left">string</td> <td align="left"> </td> -<td> If specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address. If NULL, no password will be required.</td> +<td>If specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address. If NULL, no password will be required.</td> </tr> </tbody> </table></div> @@ -4020,7 +4156,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.47"></a><h3>wireguard setting</h3> -<p> WireGuard Settings.</p> +<p>WireGuard Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -4040,52 +4176,52 @@ <a name="nm-settings-dbus.property.wireguard.fwmark"></a>fwmark</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise, it is a 32-bit fwmark for outgoing packets. +<td>The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise, it is a 32-bit fwmark for outgoing packets. - Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.</td> +Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wireguard.ip4-auto-default-route"></a>ip4-auto-default-route</td> <td align="left">NMTernary (int32)</td> <td align="left"> </td> -<td> Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing". +<td>Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing". - Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route. +Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route. - Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips. Since this automatism only makes sense if you also have a peer with an /0 allowed-ips, it is usually not necessary to enable this explicitly. However, you can disable it if you want to configure your own routing and rules.</td> +Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips. Since this automatism only makes sense if you also have a peer with an /0 allowed-ips, it is usually not necessary to enable this explicitly. However, you can disable it if you want to configure your own routing and rules.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wireguard.ip6-auto-default-route"></a>ip6-auto-default-route</td> <td align="left">NMTernary (int32)</td> <td align="left"> </td> -<td> Like ip4-auto-default-route, but for the IPv6 default route.</td> +<td>Like ip4-auto-default-route, but for the IPv6 default route.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wireguard.listen-port"></a>listen-port</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.</td> +<td>The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wireguard.mtu"></a>mtu</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments. +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments. - If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, this does not take into account the current routes at the time of activation.</td> +If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, this does not take into account the current routes at the time of activation.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wireguard.peer-routes"></a>peer-routes</td> <td align="left">boolean</td> <td align="left">TRUE</td> -<td> Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively. +<td>Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively. - Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.</td> +Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.</td> </tr> <tr> <td align="left"> @@ -4099,14 +4235,14 @@ <a name="nm-settings-dbus.property.wireguard.private-key"></a>private-key</td> <td align="left">string</td> <td align="left"> </td> -<td> The 256 bit private-key in base64 encoding.</td> +<td>The 256 bit private-key in base64 encoding.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wireguard.private-key-flags"></a>private-key-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "private-key" property.</td> +<td>Flags indicating how to handle the "private-key" property.</td> </tr> </tbody> </table></div> @@ -4114,7 +4250,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.48"></a><h3>802-11-wireless setting</h3> -<p> Wi-Fi Settings.</p> +<p>Wi-Fi Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -4134,13 +4270,13 @@ <a name="nm-settings-dbus.property.802-11-wireless.ap-isolation"></a>ap-isolation</td> <td align="left">NMTernary (int32)</td> <td align="left"> </td> -<td> Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode. +<td>Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode. - If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc. +If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc. - If set to NM_TERNARY_FALSE (0), devices can talk to each other. +If set to NM_TERNARY_FALSE (0), devices can talk to each other. - When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).</td> +When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).</td> </tr> <tr> <td align="left"> @@ -4154,23 +4290,23 @@ <a name="nm-settings-dbus.property.802-11-wireless.band"></a>band</td> <td align="left">string</td> <td align="left"> </td> -<td> 802.11 frequency band of the network. One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11. This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible. This setting depends on specific driver capability and may not work with all drivers.</td> +<td>802.11 frequency band of the network. One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11. This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible. This setting depends on specific driver capability and may not work with all drivers.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.bssid"></a>bssid</td> <td align="left">byte array</td> <td align="left"> </td> -<td> If specified, directs the device to only associate with the given access point. This capability is highly driver dependent and not supported by all devices. Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future. +<td>If specified, directs the device to only associate with the given access point. This capability is highly driver dependent and not supported by all devices. Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future. - Locking a client profile to a certain BSSID will prevent roaming and also disable background scanning. That can be useful, if there is only one access point for the SSID.</td> +Locking a client profile to a certain BSSID will prevent roaming and also disable background scanning. That can be useful, if there is only one access point for the SSID.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.channel"></a>channel</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Wireless channel to use for the Wi-Fi connection. The device will only join (or create for Ad-Hoc networks) a Wi-Fi network on the specified channel. Because channel numbers overlap between bands, this property also requires the "band" property to be set.</td> +<td>Wireless channel to use for the Wi-Fi connection. The device will only join (or create for Ad-Hoc networks) a Wi-Fi network on the specified channel. Because channel numbers overlap between bands, this property also requires the "band" property to be set.</td> </tr> <tr> <td align="left"> @@ -4184,77 +4320,79 @@ <a name="nm-settings-dbus.property.802-11-wireless.generate-mac-address-mask"></a>generate-mac-address-mask</td> <td align="left">string</td> <td align="left"> </td> -<td> With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. +<td>With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. - If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. +If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. - If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. +If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. - If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. +If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. - If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</td> +If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.hidden"></a>hidden</td> <td align="left">boolean</td> <td align="left">FALSE</td> -<td> If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode. +<td>If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode. - In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID. However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution. +In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID. However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution. - In AP mode, the created network does not broadcast its SSID. +In AP mode, the created network does not broadcast its SSID. - Note that marking the network as hidden may be a privacy issue for you (in infrastructure mode) or client stations (in AP mode), as the explicit probe-scans are distinctly recognizable on the air.</td> +Note that marking the network as hidden may be a privacy issue for you (in infrastructure mode) or client stations (in AP mode), as the explicit probe-scans are distinctly recognizable on the air.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.mac-address"></a>mac-address</td> <td align="left">byte array</td> <td align="left"> </td> -<td> If specified, this connection will only apply to the Wi-Fi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td> +<td>If specified, this connection will only apply to the Wi-Fi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.mac-address-blacklist"></a>mac-address-blacklist</td> <td align="left">array of string</td> <td align="left"> </td> -<td> A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").</td> +<td>A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.mac-address-randomization"></a>mac-address-randomization</td> <td align="left">uint32</td> <td align="left">0</td> -<td> One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address). This property is deprecated for 'cloned-mac-address'. Deprecated: 1</td> +<td>One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address). + +This property is deprecated since version 1.4.Use the "cloned-mac-address" property instead.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.mode"></a>mode</td> <td align="left">string</td> <td align="left"> </td> -<td> Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap". If blank, infrastructure is assumed.</td> +<td>Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap". If blank, infrastructure is assumed.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.mtu"></a>mtu</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td> +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.powersave"></a>powersave</td> <td align="left">uint32</td> <td align="left">0</td> -<td> One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.</td> +<td>One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.rate"></a>rate</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, directs the device to only use the specified bitrate for communication with the access point. Units are in Kb/s, ie 5500 = 5.5 Mbit/s. This property is highly driver dependent and not all devices support setting a static bitrate.</td> +<td>If non-zero, directs the device to only use the specified bitrate for communication with the access point. Units are in Kb/s, ie 5500 = 5.5 Mbit/s. This property is highly driver dependent and not all devices support setting a static bitrate.</td> </tr> <tr> <td align="left"> @@ -4268,28 +4406,28 @@ <a name="nm-settings-dbus.property.802-11-wireless.seen-bssids"></a>seen-bssids</td> <td align="left">array of string</td> <td align="left"> </td> -<td> A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network. NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.</td> +<td>A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network. NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.ssid"></a>ssid</td> <td align="left">byte array</td> <td align="left"> </td> -<td> SSID of the Wi-Fi network. Must be specified.</td> +<td>SSID of the Wi-Fi network. Must be specified.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.tx-power"></a>tx-power</td> <td align="left">uint32</td> <td align="left">0</td> -<td> If non-zero, directs the device to use the specified transmit power. Units are dBm. This property is highly driver dependent and not all devices support setting a static transmit power.</td> +<td>If non-zero, directs the device to use the specified transmit power. Units are dBm. This property is highly driver dependent and not all devices support setting a static transmit power.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless.wake-on-wlan"></a>wake-on-wlan</td> <td align="left">uint32</td> <td align="left">1</td> -<td> The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</td> +<td>The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</td> </tr> </tbody> </table></div> @@ -4297,7 +4435,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.49"></a><h3>802-11-wireless-security setting</h3> -<p> Wi-Fi Security Settings.</p> +<p>Wi-Fi Security Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -4317,146 +4455,146 @@ <a name="nm-settings-dbus.property.802-11-wireless-security.auth-alg"></a>auth-alg</td> <td align="left">string</td> <td align="left"> </td> -<td> When WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here. One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP. When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.</td> +<td>When WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here. One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP. When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.fils"></a>fils</td> <td align="left">int32</td> <td align="left">0</td> -<td> Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.</td> +<td>Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.group"></a>group</td> <td align="left">array of string</td> <td align="left"> </td> -<td> A list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".</td> +<td>A list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.key-mgmt"></a>key-mgmt</td> <td align="left">string</td> <td align="left"> </td> -<td> 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). +<td>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.</td> +This property must be set for any Wi-Fi connection that uses security.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.leap-password"></a>leap-password</td> <td align="left">string</td> <td align="left"> </td> -<td> The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</td> +<td>The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.leap-password-flags"></a>leap-password-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "leap-password" property.</td> +<td>Flags indicating how to handle the "leap-password" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.leap-username"></a>leap-username</td> <td align="left">string</td> <td align="left"> </td> -<td> The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</td> +<td>The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.pairwise"></a>pairwise</td> <td align="left">array of string</td> <td align="left"> </td> -<td> A list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "tkip" or "ccmp".</td> +<td>A list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "tkip" or "ccmp".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.pmf"></a>pmf</td> <td align="left">int32</td> <td align="left">0</td> -<td> Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.</td> +<td>Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.proto"></a>proto</td> <td align="left">array of string</td> <td align="left"> </td> -<td> List of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN). If not specified, both WPA and RSN connections are allowed.</td> +<td>List of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN). If not specified, both WPA and RSN connections are allowed.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.psk"></a>psk</td> <td align="left">string</td> <td align="left"> </td> -<td> Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.</td> +<td>Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.psk-flags"></a>psk-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "psk" property.</td> +<td>Flags indicating how to handle the "psk" property.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.wep-key-flags"></a>wep-key-flags</td> <td align="left">NMSettingSecretFlags (uint32)</td> <td align="left"> </td> -<td> Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.</td> +<td>Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.wep-key-type"></a>wep-key-type</td> <td align="left">NMWepKeyType (uint32)</td> <td align="left"> </td> -<td> Controls the interpretation of WEP keys. Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.</td> +<td>Controls the interpretation of WEP keys. Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.wep-key0"></a>wep-key0</td> <td align="left">string</td> <td align="left"> </td> -<td> Index 0 WEP key. This is the WEP key used in most networks. See the "wep-key-type" property for a description of how this key is interpreted.</td> +<td>Index 0 WEP key. This is the WEP key used in most networks. See the "wep-key-type" property for a description of how this key is interpreted.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.wep-key1"></a>wep-key1</td> <td align="left">string</td> <td align="left"> </td> -<td> Index 1 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</td> +<td>Index 1 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.wep-key2"></a>wep-key2</td> <td align="left">string</td> <td align="left"> </td> -<td> Index 2 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</td> +<td>Index 2 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.wep-key3"></a>wep-key3</td> <td align="left">string</td> <td align="left"> </td> -<td> Index 3 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</td> +<td>Index 3 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.wep-tx-keyidx"></a>wep-tx-keyidx</td> <td align="left">uint32</td> <td align="left">0</td> -<td> When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here. Valid values are 0 (default key) through 3. Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.</td> +<td>When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here. Valid values are 0 (default key) through 3. Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.802-11-wireless-security.wps-method"></a>wps-method</td> <td align="left">uint32</td> <td align="left">0</td> -<td> Flags indicating which mode of WPS is to be used if any. +<td>Flags indicating which mode of WPS is to be used if any. - There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities. +There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities. - WPS can be disabled by setting this property to a value of 1.</td> +WPS can be disabled by setting this property to a value of 1.</td> </tr> </tbody> </table></div> @@ -4464,7 +4602,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.50"></a><h3>wpan setting</h3> -<p> IEEE 802.15.4 (WPAN) MAC Settings.</p> +<p>IEEE 802.15.4 (WPAN) MAC Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -4484,35 +4622,35 @@ <a name="nm-settings-dbus.property.wpan.channel"></a>channel</td> <td align="left">int32</td> <td align="left">-1</td> -<td> IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</td> +<td>IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wpan.mac-address"></a>mac-address</td> <td align="left">string</td> <td align="left"> </td> -<td> If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.</td> +<td>If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wpan.page"></a>page</td> <td align="left">int32</td> <td align="left">-1</td> -<td> IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</td> +<td>IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wpan.pan-id"></a>pan-id</td> <td align="left">uint32</td> <td align="left">65535</td> -<td> IEEE 802.15.4 Personal Area Network (PAN) identifier.</td> +<td>IEEE 802.15.4 Personal Area Network (PAN) identifier.</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.wpan.short-address"></a>short-address</td> <td align="left">uint32</td> <td align="left">65535</td> -<td> Short IEEE 802.15.4 address to be used within a restricted environment.</td> +<td>Short IEEE 802.15.4 address to be used within a restricted environment.</td> </tr> </tbody> </table></div> @@ -4520,7 +4658,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.9.4.51"></a><h3>bond-port setting</h3> -<p> Bond Port Settings.</p> +<p>Bond Port Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -4539,14 +4677,14 @@ <a name="nm-settings-dbus.property.bond-port.queue-id"></a>queue-id</td> <td align="left">uint32</td> <td align="left">0</td> -<td> The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.</td> +<td>The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.</td> </tr></tbody> </table></div> </div> <hr> <div class="refsect2"> <a name="id-1.2.9.4.52"></a><h3>hostname setting</h3> -<p> Hostname settings.</p> +<p>Hostname settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -4566,48 +4704,74 @@ <a name="nm-settings-dbus.property.hostname.from-dhcp"></a>from-dhcp</td> <td align="left">NMTernary (int32)</td> <td align="left"> </td> -<td> Whether the system hostname can be determined from DHCP on this connection. +<td>Whether the system hostname can be determined from DHCP on this connection. - When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</td> +When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.hostname.from-dns-lookup"></a>from-dns-lookup</td> <td align="left">NMTernary (int32)</td> <td align="left"> </td> -<td> Whether the system hostname can be determined from reverse DNS lookup of addresses on this device. +<td>Whether the system hostname can be determined from reverse DNS lookup of addresses on this device. - When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</td> +When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.hostname.only-from-default"></a>only-from-default</td> <td align="left">NMTernary (int32)</td> <td align="left"> </td> -<td> If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6). +<td>If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6). - If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route. +If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route. - When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).</td> +When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).</td> </tr> <tr> <td align="left"> <a name="nm-settings-dbus.property.hostname.priority"></a>priority</td> <td align="left">int32</td> <td align="left">0</td> -<td> The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority). A connection with higher priority is considered before connections with lower priority. +<td>The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority). A connection with higher priority is considered before connections with lower priority. - If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100. +If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100. - Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.</td> +Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.</td> </tr> </tbody> </table></div> </div> <hr> <div class="refsect2"> -<a name="id-1.2.9.4.53"></a><h3>ovs-external-ids setting</h3> -<p> OVS External IDs Settings.</p> +<a name="id-1.2.9.4.53"></a><h3>loopback setting</h3> +<p>Loopback Link Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Key Name</th> +<th>Value Type</th> +<th>Default Value</th> +<th>Value Description</th> +</tr></thead> +<tbody><tr> +<td align="left"> +<a name="nm-settings-dbus.property.loopback.mtu"></a>mtu</td> +<td align="left">uint32</td> +<td align="left">0</td> +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td> +</tr></tbody> +</table></div> +</div> +<hr> +<div class="refsect2"> +<a name="id-1.2.9.4.54"></a><h3>ovs-external-ids setting</h3> +<p>OVS External IDs Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -4626,14 +4790,40 @@ <a name="nm-settings-dbus.property.ovs-external-ids.data"></a>data</td> <td align="left">dict of string to string</td> <td align="left">{}</td> -<td> A dictionary of key/value pairs with exernal-ids for OVS.</td> +<td>A dictionary of key/value pairs with external-ids for OVS.</td> +</tr></tbody> +</table></div> +</div> +<hr> +<div class="refsect2"> +<a name="id-1.2.9.4.55"></a><h3>ovs-other-config setting</h3> +<p>OVS Other Config Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Key Name</th> +<th>Value Type</th> +<th>Default Value</th> +<th>Value Description</th> +</tr></thead> +<tbody><tr> +<td align="left"> +<a name="nm-settings-dbus.property.ovs-other-config.data"></a>data</td> +<td align="left">dict of string to string</td> +<td align="left">{}</td> +<td>A dictionary of key/value pairs with other_config settings for OVS. See also "other_config" in the "ovs-vswitchd.conf.db" manual for the keys that OVS supports.</td> </tr></tbody> </table></div> </div> <hr> <div class="refsect2"> -<a name="id-1.2.9.4.54"></a><h3>veth setting</h3> -<p> Veth Settings.</p> +<a name="id-1.2.9.4.56"></a><h3>veth setting</h3> +<p>Veth Settings.</p> <div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> @@ -4652,7 +4842,7 @@ <a name="nm-settings-dbus.property.veth.peer"></a>peer</td> <td align="left">string</td> <td align="left"> </td> -<td> This property specifies the peer interface name of the veth. This property is mandatory.</td> +<td>This property specifies the peer interface name of the veth. This property is mandatory.</td> </tr></tbody> </table></div> </div> diff --git a/docs/api/html/nm-settings-ifcfg-rh.html b/docs/api/html/nm-settings-ifcfg-rh.html index 8189a493..a63ae165 100644 --- a/docs/api/html/nm-settings-ifcfg-rh.html +++ b/docs/api/html/nm-settings-ifcfg-rh.html @@ -274,7 +274,346 @@ DEVICETYPE=TeamPort </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.4"></a><p class="title"><b>Table 12. 802-1x setting</b></p> +<a name="id-1.2.12.7.4"></a><p class="title"><b>Table 12. 802-11-wireless setting</b></p> +<div class="table-contents"><table class="table" summary="802-11-wireless setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">ssid</td> +<td align="left">ESSID</td> +<td align="left"> </td> +<td align="left">SSID of Wi-Fi network.<span class="bold"><strong> + +Example: </strong></span>ESSID="Quick Net"</td> +</tr> +<tr> +<td align="left">mode</td> +<td align="left">MODE</td> +<td align="left"> </td> +<td align="left">Wi-Fi network mode.<span class="bold"><strong> + +Allowed values: </strong></span>Ad-Hoc, Managed (Auto) [case insensitive]</td> +</tr> +<tr> +<td align="left">band</td> +<td align="left">BAND<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">BAND alone is honored, but CHANNEL overrides BAND since it implies a band.<span class="bold"><strong> + +Example: </strong></span>BAND=bg<span class="bold"><strong> + +Allowed values: </strong></span>a, bg</td> +</tr> +<tr> +<td align="left">channel</td> +<td align="left">CHANNEL</td> +<td align="left"> </td> +<td align="left">Channel used for the Wi-Fi communication. Channels greater than 14 mean "a" band, otherwise the band is "bg".<span class="bold"><strong> + +Example: </strong></span>CHANNEL=6</td> +</tr> +<tr> +<td align="left">bssid</td> +<td align="left">BSSID<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Restricts association only to a single AP.<span class="bold"><strong> + +Example: </strong></span>BSSID=00:1E:BD:64:83:21</td> +</tr> +<tr> +<td align="left">rate</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">This property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">tx-power</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">This property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">mac-address</td> +<td align="left">HWADDR</td> +<td align="left"> </td> +<td align="left">Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.</td> +</tr> +<tr> +<td align="left">cloned-mac-address</td> +<td align="left">MACADDR</td> +<td align="left"> </td> +<td align="left">Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).</td> +</tr> +<tr> +<td align="left">generate-mac-address-mask</td> +<td align="left">GENERATE_MAC_ADDRESS_MASK<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">the MAC address mask for generating randomized and stable cloned-mac-address.</td> +</tr> +<tr> +<td align="left">mac-address-blacklist</td> +<td align="left">HWADDR_BLACKLIST<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">It denies usage of the connection for any device whose address is listed.</td> +</tr> +<tr> +<td align="left">seen-bssids</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">This property is not handled by ifcfg-rh plugin.</td> +</tr> +<tr> +<td align="left">mtu</td> +<td align="left">MTU</td> +<td align="left"> </td> +<td align="left">MTU of the wireless interface.</td> +</tr> +<tr> +<td align="left">hidden</td> +<td align="left">SSID_HIDDEN<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Whether the network hides the SSID.</td> +</tr> +<tr> +<td align="left">powersave</td> +<td align="left">POWERSAVE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Enables or disables Wi-Fi power saving.<span class="bold"><strong> + +Example: </strong></span>POWERSAVE=enable<span class="bold"><strong> + +Allowed values: </strong></span>default, ignore, enable, disable</td> +</tr> +<tr> +<td align="left">mac-address-randomization</td> +<td align="left">MAC_ADDRESS_RANDOMIZATION<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Enables or disables Wi-Fi MAC address randomization.<span class="bold"><strong> + +Example: </strong></span>MAC_ADDRESS_RANDOMIZATION=always<span class="bold"><strong> + +Allowed values: </strong></span>default, never, always</td> +</tr> +<tr> +<td align="left">security</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">This property is deprecated and not handled by ifcfg-rh-plugin.</td> +</tr> +<tr> +<td align="left">ap-isolation</td> +<td align="left">AP_ISOLATION<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">missing variable means global default</td> +<td align="left">Whether AP isolation is enabled<span class="bold"><strong> + +Allowed values: </strong></span>"yes", "no"</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.2.12.7.5"></a><p class="title"><b>Table 13. 802-11-wireless-security setting</b></p> +<div class="table-contents"><table class="table" summary="802-11-wireless-security setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">key-mgmt</td> +<td align="left">KEY_MGMT<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Key management method.<span class="bold"><strong> + +Allowed values: </strong></span>none, ieee8021x, owe, wpa-psk, sae, wpa-eap, wpa-eap-suite-b-192</td> +</tr> +<tr> +<td align="left">wep-tx-keyidx</td> +<td align="left">DEFAULTKEY</td> +<td align="left">1</td> +<td align="left">Index of active WEP key. Note that in ifcfg format the index starts counting at 1, while NetworkManager API otherwise is zero based.<span class="bold"><strong> + +Allowed values: </strong></span>1, 2, 3, 4</td> +</tr> +<tr> +<td align="left">auth-alg</td> +<td align="left">SECURITYMODE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Authentication algorithm for WEP.<span class="bold"><strong> + +Allowed values: </strong></span>restricted, open, leap</td> +</tr> +<tr> +<td align="left">proto</td> +<td align="left">WPA_ALLOW_WPA<span class="emphasis"><em>(+)</em></span>, WPA_ALLOW_WPA2<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">no</td> +<td align="left">Allowed WPA protocols, WPA and WPA2 (RSN).<span class="bold"><strong> + +Allowed values: </strong></span>yes, no</td> +</tr> +<tr> +<td align="left">pairwise</td> +<td align="left">CIPHER_PAIRWISE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Restrict pairwise encryption algorithms, specified as a space separated list.<span class="bold"><strong> + +Allowed values: </strong></span>CCMP, TKIP</td> +</tr> +<tr> +<td align="left">group</td> +<td align="left">CIPHER_GROUP<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Restrict group/broadcast encryption algorithms, specified as a space separated list.<span class="bold"><strong> + +Allowed values: </strong></span>CCMP, TKIP, WEP40, WEP104</td> +</tr> +<tr> +<td align="left">pmf</td> +<td align="left">PMF<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Enables or disables PMF (802.11w)<span class="bold"><strong> + +Example: </strong></span>PMF=required<span class="bold"><strong> + +Allowed values: </strong></span>default, disable, optional, required</td> +</tr> +<tr> +<td align="left">leap-username</td> +<td align="left">IEEE_8021X_IDENTITY<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Login name for LEAP.</td> +</tr> +<tr> +<td align="left">wep-key0</td> +<td align="left">KEY1, KEY_PASSPHRASE1<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">The first WEP key (used in most networks). See also DEFAULTKEY for key index.</td> +</tr> +<tr> +<td align="left">wep-key1</td> +<td align="left">KEY2, KEY_PASSPHRASE2<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">WEP key with index 1. See also DEFAULTKEY for key index.</td> +</tr> +<tr> +<td align="left">wep-key2</td> +<td align="left">KEY3, KEY_PASSPHRASE3<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">WEP key with index 2. See also DEFAULTKEY for key index.</td> +</tr> +<tr> +<td align="left">wep-key3</td> +<td align="left">KEY4, KEY_PASSPHRASE4<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">WEP key with index 3. See also DEFAULTKEY for key index.</td> +</tr> +<tr> +<td align="left">wep-key-flags</td> +<td align="left">WEP_KEY_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password flags for KEY<i>, KEY_PASSPHRASE<i> password. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for _FLAGS values)</td> +</tr> +<tr> +<td align="left">psk</td> +<td align="left">WPA_PSK</td> +<td align="left"> </td> +<td align="left">Pre-Shared-Key for WPA networks.</td> +</tr> +<tr> +<td align="left">psk-flags</td> +<td align="left">WPA_PSK_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password flags for WPA_PSK_FLAGS. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for _FLAGS values)<span class="bold"><strong> + +Example: </strong></span>WPA_PSK_FLAGS=user</td> +</tr> +<tr> +<td align="left">leap-password</td> +<td align="left">IEEE_8021X_PASSWORD<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password for LEAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent.</td> +</tr> +<tr> +<td align="left">leap-password-flags</td> +<td align="left">IEEE_8021X_PASSWORD_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Password flags for IEEE_8021X_PASSWORD_FLAGS. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for _FLAGS values)</td> +</tr> +<tr> +<td align="left">wep-key-type</td> +<td align="left">KEY<i> or KEY_PASSPHRASE<i><span class="emphasis"><em>(+)</em></span>; KEY_TYPE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">KEY is used for "key" type (10 or 26 hexadecimal characters, or 5 or 13 character string prefixed with "s:"). KEY_PASSPHRASE is used for WEP passphrases. KEY_TYPE specifies the key type and can be either 'key' or 'passphrase'. KEY_TYPE is redundant and can be omitted.<span class="bold"><strong> + +Example: </strong></span>KEY1=s:ahoj, KEY1=0a1c45bc02, KEY_PASSPHRASE1=mysupersecretkey</td> +</tr> +<tr> +<td align="left">wps-method</td> +<td align="left">WPS_METHOD</td> +<td align="left"> </td> +<td align="left">Used to control the WPS methods to be used Valid values are "default", "auto", "disabled", "pin" and "pbc". If omitted, whatver the AP announces is used.<span class="bold"><strong> + +Example: </strong></span>WPS_METHOD=disabled, WPS_METHOD="pin pbc"</td> +</tr> +<tr> +<td align="left">fils</td> +<td align="left">FILS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Enables or disables FILS (802.11ai)<span class="bold"><strong> + +Example: </strong></span>FILS=required<span class="bold"><strong> + +Allowed values: </strong></span>default, disable, optional, required</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.2.12.7.6"></a><p class="title"><b>Table 14. 802-1x setting</b></p> <div class="table-contents"><table class="table" summary="802-1x setting" border="1"> <colgroup> <col> @@ -602,8 +941,8 @@ Example: </strong></span>IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.5"></a><p class="title"><b>Table 13. bond-port setting</b></p> -<div class="table-contents"><table class="table" summary="bond-port setting" border="1"> +<a name="id-1.2.12.7.7"></a><p class="title"><b>Table 15. 802-3-ethernet setting</b></p> +<div class="table-contents"><table class="table" summary="802-3-ethernet setting" border="1"> <colgroup> <col> <col> @@ -616,18 +955,114 @@ Example: </strong></span>IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12</td> <th>Default</th> <th>Description</th> </tr></thead> -<tbody><tr> -<td align="left">queue-id</td> -<td align="left">BONDING_OPTS: queue-id=</td> -<td align="left">0</td> -<td align="left">Queue ID.<span class="bold"><strong> +<tbody> +<tr> +<td align="left">port</td> +<td align="left">(none)</td> +<td align="left"> </td> +<td align="left">The property is not saved by the plugin.</td> +</tr> +<tr> +<td align="left">speed</td> +<td align="left">ETHTOOL_OPTS</td> +<td align="left"> </td> +<td align="left">Fixed speed for the ethernet link. It is added as "speed" parameter in the ETHTOOL_OPTS variable.</td> +</tr> +<tr> +<td align="left">duplex</td> +<td align="left">ETHTOOL_OPTS</td> +<td align="left"> </td> +<td align="left">Fixed duplex mode for the ethernet link. It is added as "duplex" parameter in the ETHOOL_OPTS variable.</td> +</tr> +<tr> +<td align="left">auto-negotiate</td> +<td align="left">ETHTOOL_OPTS</td> +<td align="left"> </td> +<td align="left">Whether link speed and duplex autonegotiation is enabled. It is not saved only if disabled and no values are provided for the "speed" and "duplex" parameters (skips link configuration).</td> +</tr> +<tr> +<td align="left">mac-address</td> +<td align="left">HWADDR</td> +<td align="left"> </td> +<td align="left">Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.</td> +</tr> +<tr> +<td align="left">cloned-mac-address</td> +<td align="left">MACADDR</td> +<td align="left"> </td> +<td align="left">Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).</td> +</tr> +<tr> +<td align="left">generate-mac-address-mask</td> +<td align="left">GENERATE_MAC_ADDRESS_MASK<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">the MAC address mask for generating randomized and stable cloned-mac-address.</td> +</tr> +<tr> +<td align="left">mac-address-blacklist</td> +<td align="left">HWADDR_BLACKLIST<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">It denies usage of the connection for any device whose address is listed.<span class="bold"><strong> -Allowed values: </strong></span>0 - 65535</td> -</tr></tbody> +Example: </strong></span>HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55"</td> +</tr> +<tr> +<td align="left">mtu</td> +<td align="left">MTU</td> +<td align="left"> </td> +<td align="left">MTU of the interface.</td> +</tr> +<tr> +<td align="left">s390-subchannels</td> +<td align="left">SUBCHANNELS</td> +<td align="left"> </td> +<td align="left">Subchannels for IBM S390 hosts.<span class="bold"><strong> + +Example: </strong></span>SUBCHANNELS=0.0.b00a,0.0.b00b,0.0.b00c</td> +</tr> +<tr> +<td align="left">s390-nettype</td> +<td align="left">NETTYPE</td> +<td align="left"> </td> +<td align="left">Network type of the S390 host.<span class="bold"><strong> + +Example: </strong></span>NETTYPE=qeth<span class="bold"><strong> + +Allowed values: </strong></span>"qeth", "lcs" or "ctc"</td> +</tr> +<tr> +<td align="left">s390-options</td> +<td align="left">OPTIONS and PORTNAME, CTCPROTO,</td> +<td align="left"> </td> +<td align="left">S390 device options. All options go to OPTIONS, except for "portname" and "ctcprot" that have their own variables.</td> +</tr> +<tr> +<td align="left">wake-on-lan</td> +<td align="left">ETHTOOL_OPTS, ETHTOOL_WAKE_ON_LAN</td> +<td align="left"> </td> +<td align="left">Wake on Lan mode for ethernet. The setting "ignore" is expressed with "ETHTOOL_WAKE_ON_LAN=ignore". Otherwise, the "ETHTOOL_OPTS" variable is set with the value "wol" and several of the characters "p|u|m|b|a|g|s|f|d" as explained in the ethtool manual page.</td> +</tr> +<tr> +<td align="left">wake-on-lan-password</td> +<td align="left">ETHTOOL_OPTS</td> +<td align="left"> </td> +<td align="left">Password for secure-on based Wake-on-Lan. It is added as "sopass" parameter in the ETHTOOL_OPTS variable.<span class="bold"><strong> + +Example: </strong></span>ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"</td> +</tr> +<tr> +<td align="left">accept-all-mac-addresses</td> +<td align="left">ACCEPT_ALL_MAC_ADDRESSES</td> +<td align="left"> </td> +<td align="left">Enforce the interface to accept all the packets.</td> +</tr> +</tbody> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.6"></a><p class="title"><b>Table 14. bond setting</b></p> +<a name="id-1.2.12.7.8"></a><p class="title"><b>Table 16. bond setting</b></p> <div class="table-contents"><table class="table" summary="bond setting" border="1"> <colgroup> <col> @@ -652,8 +1087,8 @@ Example: </strong></span>BONDING_OPTS="miimon=100 mode=broadcast"</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.7"></a><p class="title"><b>Table 15. bridge-port setting</b></p> -<div class="table-contents"><table class="table" summary="bridge-port setting" border="1"> +<a name="id-1.2.12.7.9"></a><p class="title"><b>Table 17. bond-port setting</b></p> +<div class="table-contents"><table class="table" summary="bond-port setting" border="1"> <colgroup> <col> <col> @@ -666,42 +1101,18 @@ Example: </strong></span>BONDING_OPTS="miimon=100 mode=broadcast"</td> <th>Default</th> <th>Description</th> </tr></thead> -<tbody> -<tr> -<td align="left">priority</td> -<td align="left">BRIDGING_OPTS: priority=</td> -<td align="left">32</td> -<td align="left">STP priority.<span class="bold"><strong> - -Allowed values: </strong></span>0 - 63</td> -</tr> -<tr> -<td align="left">path-cost</td> -<td align="left">BRIDGING_OPTS: path_cost=</td> -<td align="left">100</td> -<td align="left">STP cost.<span class="bold"><strong> - -Allowed values: </strong></span>1 - 65535</td> -</tr> -<tr> -<td align="left">hairpin-mode</td> -<td align="left">BRIDGING_OPTS: hairpin_mode=</td> -<td align="left">yes</td> -<td align="left">Hairpin mode of the bridge port.</td> -</tr> -<tr> -<td align="left">vlans</td> -<td align="left">BRIDGE_PORT_VLANS</td> -<td align="left"> </td> -<td align="left">List of VLANs on the bridge port<span class="bold"><strong> +<tbody><tr> +<td align="left">queue-id</td> +<td align="left">BONDING_OPTS: queue-id=</td> +<td align="left">0</td> +<td align="left">Queue ID.<span class="bold"><strong> -Example: </strong></span>BRIDGE_PORT_VLANS="1 pvid untagged,20,300-400 untagged"</td> -</tr> -</tbody> +Allowed values: </strong></span>0 - 65535</td> +</tr></tbody> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.8"></a><p class="title"><b>Table 16. bridge setting</b></p> +<a name="id-1.2.12.7.10"></a><p class="title"><b>Table 18. bridge setting</b></p> <div class="table-contents"><table class="table" summary="bridge setting" border="1"> <colgroup> <col> @@ -940,7 +1351,56 @@ Example: </strong></span>BRIDGING_OPTS="multicast_startup_query_interval=4000"</ </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.9"></a><p class="title"><b>Table 17. connection setting</b></p> +<a name="id-1.2.12.7.11"></a><p class="title"><b>Table 19. bridge-port setting</b></p> +<div class="table-contents"><table class="table" summary="bridge-port setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">priority</td> +<td align="left">BRIDGING_OPTS: priority=</td> +<td align="left">32</td> +<td align="left">STP priority.<span class="bold"><strong> + +Allowed values: </strong></span>0 - 63</td> +</tr> +<tr> +<td align="left">path-cost</td> +<td align="left">BRIDGING_OPTS: path_cost=</td> +<td align="left">100</td> +<td align="left">STP cost.<span class="bold"><strong> + +Allowed values: </strong></span>1 - 65535</td> +</tr> +<tr> +<td align="left">hairpin-mode</td> +<td align="left">BRIDGING_OPTS: hairpin_mode=</td> +<td align="left">yes</td> +<td align="left">Hairpin mode of the bridge port.</td> +</tr> +<tr> +<td align="left">vlans</td> +<td align="left">BRIDGE_PORT_VLANS</td> +<td align="left"> </td> +<td align="left">List of VLANs on the bridge port<span class="bold"><strong> + +Example: </strong></span>BRIDGE_PORT_VLANS="1 pvid untagged,20,300-400 untagged"</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.2.12.7.12"></a><p class="title"><b>Table 20. connection setting</b></p> <div class="table-contents"><table class="table" summary="connection setting" border="1"> <colgroup> <col> @@ -1187,7 +1647,7 @@ Allowed values: </strong></span>delay in milliseconds.</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.10"></a><p class="title"><b>Table 18. dcb setting</b></p> +<a name="id-1.2.12.7.13"></a><p class="title"><b>Table 21. dcb setting</b></p> <div class="table-contents"><table class="table" summary="dcb setting" border="1"> <colgroup> <col> @@ -1322,7 +1782,7 @@ Example: </strong></span>DCB_PG_UP2TC=01623701</td> used explicitly to enable DCB so that the rest of the DCB_* variables can apply. </p> <div class="table"> -<a name="id-1.2.12.7.12"></a><p class="title"><b>Table 19. ethtool setting</b></p> +<a name="id-1.2.12.7.15"></a><p class="title"><b>Table 22. ethtool setting</b></p> <div class="table-contents"><table class="table" summary="ethtool setting" border="1"> <colgroup> <col> @@ -1340,7 +1800,7 @@ Example: </strong></span>DCB_PG_UP2TC=01623701</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.13"></a><p class="title"><b>Table 20. hostname setting</b></p> +<a name="id-1.2.12.7.16"></a><p class="title"><b>Table 23. hostname setting</b></p> <div class="table-contents"><table class="table" summary="hostname setting" border="1"> <colgroup> <col> @@ -1374,7 +1834,7 @@ Example: </strong></span>HOSTNAME_PRIORITY=50</td> Example: </strong></span>HOSTNAME_FROM_DHCP=0,1</td> </tr> <tr> -<td align="left">from-dhcp</td> +<td align="left">from-dns-lookup</td> <td align="left">HOSTNAME_FROM_DNS_LOOKUP<span class="emphasis"><em>(+)</em></span> </td> <td align="left">missing variable means global default or 1</td> @@ -1395,7 +1855,7 @@ Example: </strong></span>HOSTNAME_ONLY_FROM_DEFAULT=0,1</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.14"></a><p class="title"><b>Table 21. infiniband setting</b></p> +<a name="id-1.2.12.7.17"></a><p class="title"><b>Table 24. infiniband setting</b></p> <div class="table-contents"><table class="table" summary="infiniband setting" border="1"> <colgroup> <col> @@ -1450,7 +1910,7 @@ Example: </strong></span>PHYSDEV=ib0</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.15"></a><p class="title"><b>Table 22. ipv4 setting</b></p> +<a name="id-1.2.12.7.18"></a><p class="title"><b>Table 25. ipv4 setting</b></p> <div class="table-contents"><table class="table" summary="ipv4 setting" border="1"> <colgroup> <col> @@ -1581,6 +2041,20 @@ Example: </strong></span>RES_OPTIONS=ndots:2 timeout:3</td> Example: </strong></span>IPV4_DNS_PRIORITY=20</td> </tr> <tr> +<td align="left">auto-route-ext-gw</td> +<td align="left">IPV4_AUTO_ROUTE_EXT_GW<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">yes</td> +<td align="left">VPN connections will default to add the route automatically unless this setting is set to %FALSE. For other connection types, adding such an automatic route is currently not supported and setting this to %TRUE has no effect.</td> +</tr> +<tr> +<td align="left">replace-local-rule</td> +<td align="left">IPV4_REPLACE_LOCAL_RULE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">no</td> +<td align="left">Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to %TRUE.</td> +</tr> +<tr> <td align="left">dhcp-client-id</td> <td align="left">DHCP_CLIENT_ID<span class="emphasis"><em>(+)</em></span> </td> @@ -1607,6 +2081,14 @@ Example: </strong></span>ACD_TIMEOUT=2000 or ARPING_WAIT=2</td> Example: </strong></span>IPV4_DHCP_TIMEOUT=10</td> </tr> <tr> +<td align="left">dhcp-hostname-flags</td> +<td align="left">DHCP_HOSTNAME_FLAGS</td> +<td align="left"> </td> +<td align="left">flags for the DHCP hostname and FQDN properties<span class="bold"><strong> + +Example: </strong></span>DHCP_HOSTNAME_FLAGS=5</td> +</tr> +<tr> <td align="left">dhcp-fqdn</td> <td align="left">DHCP_FQDN</td> <td align="left"> </td> @@ -1636,7 +2118,7 @@ Example: </strong></span>IPV4_LINK_LOCAL=auto</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.16"></a><p class="title"><b>Table 23. ipv6 setting</b></p> +<a name="id-1.2.12.7.19"></a><p class="title"><b>Table 26. ipv6 setting</b></p> <div class="table-contents"><table class="table" summary="ipv6 setting" border="1"> <colgroup> <col> @@ -1775,6 +2257,20 @@ Example: </strong></span>IPV6_DNS_PRIORITY=20</td> Example: </strong></span>IPV6_RES_OPTIONS=ndots:2 timeout:3</td> </tr> <tr> +<td align="left">auto-route-ext-gw</td> +<td align="left">IPV6_AUTO_ROUTE_EXT_GW<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">yes</td> +<td align="left">VPN connections will default to add the route automatically unless this setting is set to %FALSE. For other connection types, adding such an automatic route is currently not supported and setting this to %TRUE has no effect.</td> +</tr> +<tr> +<td align="left">replace-local-rule</td> +<td align="left">IPV6_REPLACE_LOCAL_RULE<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">no</td> +<td align="left">Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to %TRUE.</td> +</tr> +<tr> <td align="left">ip6-privacy</td> <td align="left">IPV6_PRIVACY, IPV6_PRIVACY_PREFER_PUBLIC_IP<span class="emphasis"><em>(+)</em></span> </td> @@ -1804,7 +2300,7 @@ Allowed values: </strong></span>IPV6_ADDR_GEN_MODE: default, default-or-eui64, e Example: </strong></span>IPV6_TOKEN=::53</td> </tr> <tr> -<td align="left">dhcp-timeout</td> +<td align="left">ra-timeout</td> <td align="left">IPV6_RA_TIMEOUT<span class="emphasis"><em>(+)</em></span> </td> <td align="left"> </td> @@ -1825,7 +2321,30 @@ Example: </strong></span>DHCPV6_DUID=LL; DHCPV6_DUID=0301deadbeef0001; DHCPV6_DU </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.17"></a><p class="title"><b>Table 24. match setting</b></p> +<a name="id-1.2.12.7.20"></a><p class="title"><b>Table 27. loopback setting</b></p> +<div class="table-contents"><table class="table" summary="loopback setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody><tr> +<td align="left">mtu</td> +<td align="left">MTU</td> +<td align="left"> </td> +<td align="left">MTU of the interface.</td> +</tr></tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.2.12.7.21"></a><p class="title"><b>Table 28. match setting</b></p> <div class="table-contents"><table class="table" summary="match setting" border="1"> <colgroup> <col> @@ -1850,7 +2369,7 @@ Example: </strong></span>MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.18"></a><p class="title"><b>Table 25. ovs-bridge setting</b></p> +<a name="id-1.2.12.7.22"></a><p class="title"><b>Table 29. ovs-bridge setting</b></p> <div class="table-contents"><table class="table" summary="ovs-bridge setting" border="1"> <colgroup> <col> @@ -1868,7 +2387,7 @@ Example: </strong></span>MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.19"></a><p class="title"><b>Table 26. ovs-dpdk setting</b></p> +<a name="id-1.2.12.7.23"></a><p class="title"><b>Table 30. ovs-dpdk setting</b></p> <div class="table-contents"><table class="table" summary="ovs-dpdk setting" border="1"> <colgroup> <col> @@ -1886,7 +2405,7 @@ Example: </strong></span>MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.20"></a><p class="title"><b>Table 27. ovs-external-ids setting</b></p> +<a name="id-1.2.12.7.24"></a><p class="title"><b>Table 31. ovs-external-ids setting</b></p> <div class="table-contents"><table class="table" summary="ovs-external-ids setting" border="1"> <colgroup> <col> @@ -1904,7 +2423,7 @@ Example: </strong></span>MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.21"></a><p class="title"><b>Table 28. ovs-interface setting</b></p> +<a name="id-1.2.12.7.25"></a><p class="title"><b>Table 32. ovs-interface setting</b></p> <div class="table-contents"><table class="table" summary="ovs-interface setting" border="1"> <colgroup> <col> @@ -1922,7 +2441,25 @@ Example: </strong></span>MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.22"></a><p class="title"><b>Table 29. ovs-patch setting</b></p> +<a name="id-1.2.12.7.26"></a><p class="title"><b>Table 33. ovs-other-config setting</b></p> +<div class="table-contents"><table class="table" summary="ovs-other-config setting" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Ifcfg-rh Variable</th> +<th>Default</th> +<th>Description</th> +</tr></thead> +<tbody></tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.2.12.7.27"></a><p class="title"><b>Table 34. ovs-patch setting</b></p> <div class="table-contents"><table class="table" summary="ovs-patch setting" border="1"> <colgroup> <col> @@ -1940,7 +2477,7 @@ Example: </strong></span>MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.23"></a><p class="title"><b>Table 30. ovs-port setting</b></p> +<a name="id-1.2.12.7.28"></a><p class="title"><b>Table 35. ovs-port setting</b></p> <div class="table-contents"><table class="table" summary="ovs-port setting" border="1"> <colgroup> <col> @@ -1958,7 +2495,7 @@ Example: </strong></span>MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.24"></a><p class="title"><b>Table 31. proxy setting</b></p> +<a name="id-1.2.12.7.29"></a><p class="title"><b>Table 36. proxy setting</b></p> <div class="table-contents"><table class="table" summary="proxy setting" border="1"> <colgroup> <col> @@ -2011,7 +2548,7 @@ Example: </strong></span>PAC_SCRIPT="function FindProxyForURL (url, host) { retu </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.25"></a><p class="title"><b>Table 32. sriov setting</b></p> +<a name="id-1.2.12.7.30"></a><p class="title"><b>Table 37. sriov setting</b></p> <div class="table-contents"><table class="table" summary="sriov setting" border="1"> <colgroup> <col> @@ -2056,7 +2593,7 @@ Example: </strong></span>SRIOV_AUTOPROBE_DRIVERS=0,1</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.26"></a><p class="title"><b>Table 33. tc setting</b></p> +<a name="id-1.2.12.7.31"></a><p class="title"><b>Table 38. tc setting</b></p> <div class="table-contents"><table class="table" summary="tc setting" border="1"> <colgroup> <col> @@ -2081,7 +2618,7 @@ Example: </strong></span>SRIOV_AUTOPROBE_DRIVERS=0,1</td> Example: </strong></span>QDISC1=ingress, QDISC2="root handle 1234: fq_codel"</td> </tr> <tr> -<td align="left">qdiscs</td> +<td align="left">tfilters</td> <td align="left">FILTER1<span class="emphasis"><em>(+)</em></span>, FILTER2<span class="emphasis"><em>(+)</em></span>, ..., TC_COMMIT<span class="emphasis"><em>(+)</em></span> </td> <td align="left"> </td> @@ -2093,8 +2630,8 @@ Example: </strong></span>FILTER1="parent ffff: matchall action simple sdata Inpu </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.27"></a><p class="title"><b>Table 34. team-port setting</b></p> -<div class="table-contents"><table class="table" summary="team-port setting" border="1"> +<a name="id-1.2.12.7.32"></a><p class="title"><b>Table 39. team setting</b></p> +<div class="table-contents"><table class="table" summary="team setting" border="1"> <colgroup> <col> <col> @@ -2109,15 +2646,15 @@ Example: </strong></span>FILTER1="parent ffff: matchall action simple sdata Inpu </tr></thead> <tbody><tr> <td align="left">config</td> -<td align="left">TEAM_PORT_CONFIG</td> +<td align="left">TEAM_CONFIG</td> <td align="left"> </td> -<td align="left">Team port configuration in JSON. See man teamd.conf for details.</td> +<td align="left">Team configuration in JSON. See man teamd.conf for details.</td> </tr></tbody> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.28"></a><p class="title"><b>Table 35. team setting</b></p> -<div class="table-contents"><table class="table" summary="team setting" border="1"> +<a name="id-1.2.12.7.33"></a><p class="title"><b>Table 40. team-port setting</b></p> +<div class="table-contents"><table class="table" summary="team-port setting" border="1"> <colgroup> <col> <col> @@ -2132,14 +2669,14 @@ Example: </strong></span>FILTER1="parent ffff: matchall action simple sdata Inpu </tr></thead> <tbody><tr> <td align="left">config</td> -<td align="left">TEAM_CONFIG</td> +<td align="left">TEAM_PORT_CONFIG</td> <td align="left"> </td> -<td align="left">Team configuration in JSON. See man teamd.conf for details.</td> +<td align="left">Team port configuration in JSON. See man teamd.conf for details.</td> </tr></tbody> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.29"></a><p class="title"><b>Table 36. user setting</b></p> +<a name="id-1.2.12.7.34"></a><p class="title"><b>Table 41. user setting</b></p> <div class="table-contents"><table class="table" summary="user setting" border="1"> <colgroup> <col> @@ -2164,7 +2701,7 @@ Example: </strong></span>NM_USER_FOO__BAR=something</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.30"></a><p class="title"><b>Table 37. veth setting</b></p> +<a name="id-1.2.12.7.35"></a><p class="title"><b>Table 42. veth setting</b></p> <div class="table-contents"><table class="table" summary="veth setting" border="1"> <colgroup> <col> @@ -2182,7 +2719,7 @@ Example: </strong></span>NM_USER_FOO__BAR=something</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.31"></a><p class="title"><b>Table 38. vlan setting</b></p> +<a name="id-1.2.12.7.36"></a><p class="title"><b>Table 43. vlan setting</b></p> <div class="table-contents"><table class="table" summary="vlan setting" border="1"> <colgroup> <col> @@ -2218,6 +2755,14 @@ Example: </strong></span>NM_USER_FOO__BAR=something</td> Allowed values: </strong></span>"yes or "no" for GVRP and MVRP; "LOOSE_BINDING" and "NO_REORDER_HDR" for VLAN_FLAGS</td> </tr> <tr> +<td align="left">protocol</td> +<td align="left">VLAN_PROTOCOL</td> +<td align="left"> </td> +<td align="left">VLAN protocol.<span class="bold"><strong> + +Example: </strong></span>VLAN_PROTOCOL="802.1ad"</td> +</tr> +<tr> <td align="left">ingress-priority-map</td> <td align="left">VLAN_INGRESS_PRIORITY_MAP</td> <td align="left"> </td> @@ -2245,7 +2790,7 @@ Example: </strong></span>PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.32"></a><p class="title"><b>Table 39. vrf setting</b></p> +<a name="id-1.2.12.7.37"></a><p class="title"><b>Table 44. vrf setting</b></p> <div class="table-contents"><table class="table" summary="vrf setting" border="1"> <colgroup> <col> @@ -2263,7 +2808,7 @@ Example: </strong></span>PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.33"></a><p class="title"><b>Table 40. wifi-p2p setting</b></p> +<a name="id-1.2.12.7.38"></a><p class="title"><b>Table 45. wifi-p2p setting</b></p> <div class="table-contents"><table class="table" summary="wifi-p2p setting" border="1"> <colgroup> <col> @@ -2281,128 +2826,7 @@ Example: </strong></span>PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.34"></a><p class="title"><b>Table 41. 802-3-ethernet setting</b></p> -<div class="table-contents"><table class="table" summary="802-3-ethernet setting" border="1"> -<colgroup> -<col> -<col> -<col> -<col> -</colgroup> -<thead><tr> -<th>Property</th> -<th>Ifcfg-rh Variable</th> -<th>Default</th> -<th>Description</th> -</tr></thead> -<tbody> -<tr> -<td align="left">port</td> -<td align="left">(none)</td> -<td align="left"> </td> -<td align="left">The property is not saved by the plugin.</td> -</tr> -<tr> -<td align="left">speed</td> -<td align="left">ETHTOOL_OPTS</td> -<td align="left"> </td> -<td align="left">Fixed speed for the ethernet link. It is added as "speed" parameter in the ETHTOOL_OPTS variable.</td> -</tr> -<tr> -<td align="left">duplex</td> -<td align="left">ETHTOOL_OPTS</td> -<td align="left"> </td> -<td align="left">Fixed duplex mode for the ethernet link. It is added as "duplex" parameter in the ETHOOL_OPTS variable.</td> -</tr> -<tr> -<td align="left">auto-negotiate</td> -<td align="left">ETHTOOL_OPTS</td> -<td align="left"> </td> -<td align="left">Whether link speed and duplex autonegotiation is enabled. It is not saved only if disabled and no values are provided for the "speed" and "duplex" parameters (skips link configuration).</td> -</tr> -<tr> -<td align="left">mac-address</td> -<td align="left">HWADDR</td> -<td align="left"> </td> -<td align="left">Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.</td> -</tr> -<tr> -<td align="left">cloned-mac-address</td> -<td align="left">MACADDR</td> -<td align="left"> </td> -<td align="left">Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).</td> -</tr> -<tr> -<td align="left">generate-mac-address-mask</td> -<td align="left">GENERATE_MAC_ADDRESS_MASK<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">the MAC address mask for generating randomized and stable cloned-mac-address.</td> -</tr> -<tr> -<td align="left">mac-address-blacklist</td> -<td align="left">HWADDR_BLACKLIST<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">It denies usage of the connection for any device whose address is listed.<span class="bold"><strong> - -Example: </strong></span>HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55"</td> -</tr> -<tr> -<td align="left">mtu</td> -<td align="left">MTU</td> -<td align="left"> </td> -<td align="left">MTU of the interface.</td> -</tr> -<tr> -<td align="left">s390-subchannels</td> -<td align="left">SUBCHANNELS</td> -<td align="left"> </td> -<td align="left">Subchannels for IBM S390 hosts.<span class="bold"><strong> - -Example: </strong></span>SUBCHANNELS=0.0.b00a,0.0.b00b,0.0.b00c</td> -</tr> -<tr> -<td align="left">s390-nettype</td> -<td align="left">NETTYPE</td> -<td align="left"> </td> -<td align="left">Network type of the S390 host.<span class="bold"><strong> - -Example: </strong></span>NETTYPE=qeth<span class="bold"><strong> - -Allowed values: </strong></span>"qeth", "lcs" or "ctc"</td> -</tr> -<tr> -<td align="left">s390-options</td> -<td align="left">OPTIONS and PORTNAME, CTCPROTO,</td> -<td align="left"> </td> -<td align="left">S390 device options. All options go to OPTIONS, except for "portname" and "ctcprot" that have their own variables.</td> -</tr> -<tr> -<td align="left">wake-on-lan</td> -<td align="left">ETHTOOL_OPTS, ETHTOOL_WAKE_ON_LAN</td> -<td align="left"> </td> -<td align="left">Wake on Lan mode for ethernet. The setting "ignore" is expressed with "ETHTOOL_WAKE_ON_LAN=ignore". Otherwise, the "ETHTOOL_OPTS" variable is set with the value "wol" and several of the characters "p|u|m|b|a|g|s|f|d" as explained in the ethtool manual page.</td> -</tr> -<tr> -<td align="left">wake-on-lan-password</td> -<td align="left">ETHTOOL_OPTS</td> -<td align="left"> </td> -<td align="left">Password for secure-on based Wake-on-Lan. It is added as "sopass" parameter in the ETHTOOL_OPTS variable.<span class="bold"><strong> - -Example: </strong></span>ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"</td> -</tr> -<tr> -<td align="left">accept-all-mac-addresses</td> -<td align="left">ACCEPT_ALL_MAC_ADDRESSES</td> -<td align="left"> </td> -<td align="left">Enforce the interface to accept all the packets.</td> -</tr> -</tbody> -</table></div> -</div> -<br class="table-break"><div class="table"> -<a name="id-1.2.12.7.35"></a><p class="title"><b>Table 42. wireguard setting</b></p> +<a name="id-1.2.12.7.39"></a><p class="title"><b>Table 46. wireguard setting</b></p> <div class="table-contents"><table class="table" summary="wireguard setting" border="1"> <colgroup> <col> @@ -2420,346 +2844,7 @@ Example: </strong></span>ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.12.7.36"></a><p class="title"><b>Table 43. 802-11-wireless-security setting</b></p> -<div class="table-contents"><table class="table" summary="802-11-wireless-security setting" border="1"> -<colgroup> -<col> -<col> -<col> -<col> -</colgroup> -<thead><tr> -<th>Property</th> -<th>Ifcfg-rh Variable</th> -<th>Default</th> -<th>Description</th> -</tr></thead> -<tbody> -<tr> -<td align="left">key-mgmt</td> -<td align="left">KEY_MGMT<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Key management method.<span class="bold"><strong> - -Allowed values: </strong></span>none, ieee8021x, owe, wpa-psk, sae, wpa-eap, wpa-eap-suite-b-192</td> -</tr> -<tr> -<td align="left">wep-tx-keyidx</td> -<td align="left">DEFAULTKEY</td> -<td align="left">1</td> -<td align="left">Index of active WEP key. Note that in ifcfg format the index starts counting at 1, while NetworkManager API otherwise is zero based.<span class="bold"><strong> - -Allowed values: </strong></span>1, 2, 3, 4</td> -</tr> -<tr> -<td align="left">auth-alg</td> -<td align="left">SECURITYMODE<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Authentication algorithm for WEP.<span class="bold"><strong> - -Allowed values: </strong></span>restricted, open, leap</td> -</tr> -<tr> -<td align="left">proto</td> -<td align="left">WPA_ALLOW_WPA<span class="emphasis"><em>(+)</em></span>, WPA_ALLOW_WPA2<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left">no</td> -<td align="left">Allowed WPA protocols, WPA and WPA2 (RSN).<span class="bold"><strong> - -Allowed values: </strong></span>yes, no</td> -</tr> -<tr> -<td align="left">pairwise</td> -<td align="left">CIPHER_PAIRWISE<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Restrict pairwise encryption algorithms, specified as a space separated list.<span class="bold"><strong> - -Allowed values: </strong></span>CCMP, TKIP</td> -</tr> -<tr> -<td align="left">group</td> -<td align="left">CIPHER_GROUP<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Restrict group/broadcast encryption algorithms, specified as a space separated list.<span class="bold"><strong> - -Allowed values: </strong></span>CCMP, TKIP, WEP40, WEP104</td> -</tr> -<tr> -<td align="left">pmf</td> -<td align="left">PMF<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Enables or disables PMF (802.11w)<span class="bold"><strong> - -Example: </strong></span>PMF=required<span class="bold"><strong> - -Allowed values: </strong></span>default, disable, optional, required</td> -</tr> -<tr> -<td align="left">leap-username</td> -<td align="left">IEEE_8021X_IDENTITY<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Login name for LEAP.</td> -</tr> -<tr> -<td align="left">wep-key0</td> -<td align="left">KEY1, KEY_PASSPHRASE1<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">The first WEP key (used in most networks). See also DEFAULTKEY for key index.</td> -</tr> -<tr> -<td align="left">wep-key1</td> -<td align="left">KEY2, KEY_PASSPHRASE2<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">WEP key with index 1. See also DEFAULTKEY for key index.</td> -</tr> -<tr> -<td align="left">wep-key2</td> -<td align="left">KEY3, KEY_PASSPHRASE3<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">WEP key with index 2. See also DEFAULTKEY for key index.</td> -</tr> -<tr> -<td align="left">wep-key3</td> -<td align="left">KEY4, KEY_PASSPHRASE4<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">WEP key with index 3. See also DEFAULTKEY for key index.</td> -</tr> -<tr> -<td align="left">wep-key-flags</td> -<td align="left">WEP_KEY_FLAGS<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Password flags for KEY<i>, KEY_PASSPHRASE<i> password. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for _FLAGS values)</td> -</tr> -<tr> -<td align="left">psk</td> -<td align="left">WPA_PSK</td> -<td align="left"> </td> -<td align="left">Pre-Shared-Key for WPA networks.</td> -</tr> -<tr> -<td align="left">psk-flags</td> -<td align="left">WPA_PSK_FLAGS<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Password flags for WPA_PSK_FLAGS. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for _FLAGS values)<span class="bold"><strong> - -Example: </strong></span>WPA_PSK_FLAGS=user</td> -</tr> -<tr> -<td align="left">leap-password</td> -<td align="left">IEEE_8021X_PASSWORD<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Password for LEAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent.</td> -</tr> -<tr> -<td align="left">leap-password-flags</td> -<td align="left">IEEE_8021X_PASSWORD_FLAGS<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Password flags for IEEE_8021X_PASSWORD_FLAGS. (see <a class="xref" href="nm-settings-dbus.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for _FLAGS values)</td> -</tr> -<tr> -<td align="left">wep-key-type</td> -<td align="left">KEY<i> or KEY_PASSPHRASE<i><span class="emphasis"><em>(+)</em></span>; KEY_TYPE<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">KEY is used for "key" type (10 or 26 hexadecimal characters, or 5 or 13 character string prefixed with "s:"). KEY_PASSPHRASE is used for WEP passphrases. KEY_TYPE specifies the key type and can be either 'key' or 'passphrase'. KEY_TYPE is redundant and can be omitted.<span class="bold"><strong> - -Example: </strong></span>KEY1=s:ahoj, KEY1=0a1c45bc02, KEY_PASSPHRASE1=mysupersecretkey</td> -</tr> -<tr> -<td align="left">wps-method</td> -<td align="left">WPS_METHOD</td> -<td align="left"> </td> -<td align="left">Used to control the WPS methods to be used Valid values are "default", "auto", "disabled", "pin" and "pbc". If omitted, whatver the AP announces is used.<span class="bold"><strong> - -Example: </strong></span>WPS_METHOD=disabled, WPS_METHOD="pin pbc"</td> -</tr> -<tr> -<td align="left">fils</td> -<td align="left">FILS<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Enables or disables FILS (802.11ai)<span class="bold"><strong> - -Example: </strong></span>FILS=required<span class="bold"><strong> - -Allowed values: </strong></span>default, disable, optional, required</td> -</tr> -</tbody> -</table></div> -</div> -<br class="table-break"><div class="table"> -<a name="id-1.2.12.7.37"></a><p class="title"><b>Table 44. 802-11-wireless setting</b></p> -<div class="table-contents"><table class="table" summary="802-11-wireless setting" border="1"> -<colgroup> -<col> -<col> -<col> -<col> -</colgroup> -<thead><tr> -<th>Property</th> -<th>Ifcfg-rh Variable</th> -<th>Default</th> -<th>Description</th> -</tr></thead> -<tbody> -<tr> -<td align="left">ssid</td> -<td align="left">ESSID</td> -<td align="left"> </td> -<td align="left">SSID of Wi-Fi network.<span class="bold"><strong> - -Example: </strong></span>ESSID="Quick Net"</td> -</tr> -<tr> -<td align="left">mode</td> -<td align="left">MODE</td> -<td align="left"> </td> -<td align="left">Wi-Fi network mode.<span class="bold"><strong> - -Allowed values: </strong></span>Ad-Hoc, Managed (Auto) [case insensitive]</td> -</tr> -<tr> -<td align="left">band</td> -<td align="left">BAND<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">BAND alone is honored, but CHANNEL overrides BAND since it implies a band.<span class="bold"><strong> - -Example: </strong></span>BAND=bg<span class="bold"><strong> - -Allowed values: </strong></span>a, bg</td> -</tr> -<tr> -<td align="left">channel</td> -<td align="left">CHANNEL</td> -<td align="left"> </td> -<td align="left">Channel used for the Wi-Fi communication. Channels greater than 14 mean "a" band, otherwise the band is "bg".<span class="bold"><strong> - -Example: </strong></span>CHANNEL=6</td> -</tr> -<tr> -<td align="left">bssid</td> -<td align="left">BSSID<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Restricts association only to a single AP.<span class="bold"><strong> - -Example: </strong></span>BSSID=00:1E:BD:64:83:21</td> -</tr> -<tr> -<td align="left">rate</td> -<td align="left">(none)</td> -<td align="left"> </td> -<td align="left">This property is not handled by ifcfg-rh plugin.</td> -</tr> -<tr> -<td align="left">tx-power</td> -<td align="left">(none)</td> -<td align="left"> </td> -<td align="left">This property is not handled by ifcfg-rh plugin.</td> -</tr> -<tr> -<td align="left">mac-address</td> -<td align="left">HWADDR</td> -<td align="left"> </td> -<td align="left">Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device.</td> -</tr> -<tr> -<td align="left">cloned-mac-address</td> -<td align="left">MACADDR</td> -<td align="left"> </td> -<td align="left">Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99).</td> -</tr> -<tr> -<td align="left">generate-mac-address-mask</td> -<td align="left">GENERATE_MAC_ADDRESS_MASK<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">the MAC address mask for generating randomized and stable cloned-mac-address.</td> -</tr> -<tr> -<td align="left">mac-address-blacklist</td> -<td align="left">HWADDR_BLACKLIST<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">It denies usage of the connection for any device whose address is listed.</td> -</tr> -<tr> -<td align="left">seen-bssids</td> -<td align="left">(none)</td> -<td align="left"> </td> -<td align="left">This property is not handled by ifcfg-rh plugin.</td> -</tr> -<tr> -<td align="left">mtu</td> -<td align="left">MTU</td> -<td align="left"> </td> -<td align="left">MTU of the wireless interface.</td> -</tr> -<tr> -<td align="left">hidden</td> -<td align="left">SSID_HIDDEN<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Whether the network hides the SSID.</td> -</tr> -<tr> -<td align="left">powersave</td> -<td align="left">POWERSAVE<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Enables or disables Wi-Fi power saving.<span class="bold"><strong> - -Example: </strong></span>POWERSAVE=enable<span class="bold"><strong> - -Allowed values: </strong></span>default, ignore, enable, disable</td> -</tr> -<tr> -<td align="left">mac-address-randomization</td> -<td align="left">MAC_ADDRESS_RANDOMIZATION<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left"> </td> -<td align="left">Enables or disables Wi-Fi MAC address randomization.<span class="bold"><strong> - -Example: </strong></span>MAC_ADDRESS_RANDOMIZATION=always<span class="bold"><strong> - -Allowed values: </strong></span>default, never, always</td> -</tr> -<tr> -<td align="left">security</td> -<td align="left">(none)</td> -<td align="left"> </td> -<td align="left">This property is deprecated and not handled by ifcfg-rh-plugin.</td> -</tr> -<tr> -<td align="left">ap-isolation</td> -<td align="left">AP_ISOLATION<span class="emphasis"><em>(+)</em></span> -</td> -<td align="left">missing variable means global default</td> -<td align="left">Whether AP isolation is enabled<span class="bold"><strong> - -Allowed values: </strong></span>"yes", "no"</td> -</tr> -</tbody> -</table></div> -</div> -<br class="table-break"><div class="table"> -<a name="id-1.2.12.7.38"></a><p class="title"><b>Table 45. wpan setting</b></p> +<a name="id-1.2.12.7.40"></a><p class="title"><b>Table 47. wpan setting</b></p> <div class="table-contents"><table class="table" summary="wpan setting" border="1"> <colgroup> <col> diff --git a/docs/api/html/nm-settings-keyfile.html b/docs/api/html/nm-settings-keyfile.html index 69bb333c..12b405b1 100644 --- a/docs/api/html/nm-settings-keyfile.html +++ b/docs/api/html/nm-settings-keyfile.html @@ -189,7 +189,93 @@ id=4 <tr><td>802-11-wireless-security = wifi-security</td></tr> </table> <div class="table"> -<a name="id-1.2.11.6.4"></a><p class="title"><b>Table 1. bridge setting (section)</b></p> +<a name="id-1.2.11.6.4"></a><p class="title"><b>Table 1. 802-11-wireless setting (section)</b></p> +<div class="table-contents"><table class="table" summary="802-11-wireless setting (section)" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Keyfile Variable</th> +<th>Format</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">ssid</td> +<td align="left"> </td> +<td align="left">string (or decimal-byte list - obsolete)</td> +<td align="left">SSID of Wi-Fi network.<span class="bold"><strong> + +Example: </strong></span>ssid=Quick Net</td> +</tr> +<tr> +<td align="left">mac-address</td> +<td align="left"> </td> +<td align="left">usual hex-digits-and-colons notation</td> +<td align="left">MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162).</td> +</tr> +<tr> +<td align="left">cloned-mac-address</td> +<td align="left"> </td> +<td align="left">usual hex-digits-and-colons notation</td> +<td align="left">Cloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178).</td> +</tr> +<tr> +<td align="left">mac-address-blacklist</td> +<td align="left"> </td> +<td align="left">list of MACs (separated with semicolons)</td> +<td align="left">MAC address blacklist.<span class="bold"><strong> + +Example: </strong></span>mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.2.11.6.5"></a><p class="title"><b>Table 2. 802-3-ethernet setting (section)</b></p> +<div class="table-contents"><table class="table" summary="802-3-ethernet setting (section)" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Property</th> +<th>Keyfile Variable</th> +<th>Format</th> +<th>Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left">mac-address</td> +<td align="left"> </td> +<td align="left">usual hex-digits-and-colons notation</td> +<td align="left">MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162)</td> +</tr> +<tr> +<td align="left">cloned-mac-address</td> +<td align="left"> </td> +<td align="left">usual hex-digits-and-colons notation</td> +<td align="left">Cloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178).</td> +</tr> +<tr> +<td align="left">mac-address-blacklist</td> +<td align="left"> </td> +<td align="left">list of MACs (separated with semicolons)</td> +<td align="left">MAC address blacklist.<span class="bold"><strong> + +Example: </strong></span>mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78</td> +</tr> +</tbody> +</table></div> +</div> +<br class="table-break"><div class="table"> +<a name="id-1.2.11.6.6"></a><p class="title"><b>Table 3. bridge setting (section)</b></p> <div class="table-contents"><table class="table" summary="bridge setting (section)" border="1"> <colgroup> <col> @@ -205,7 +291,7 @@ id=4 </tr></thead> <tbody><tr> <td align="left">mac-address</td> -<td align="left">mac-address</td> +<td align="left"> </td> <td align="left">usual hex-digits-and-colons notation</td> <td align="left">MAC address in traditional hex-digits-and-colons notation, or semicolon separated list of 6 decimal bytes (obsolete)<span class="bold"><strong> @@ -214,7 +300,7 @@ Example: </strong></span>mac-address=00:22:68:12:79:A2 mac-address=0;34;104;18;1 </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.11.6.5"></a><p class="title"><b>Table 2. infiniband setting (section)</b></p> +<a name="id-1.2.11.6.7"></a><p class="title"><b>Table 4. infiniband setting (section)</b></p> <div class="table-contents"><table class="table" summary="infiniband setting (section)" border="1"> <colgroup> <col> @@ -230,7 +316,7 @@ Example: </strong></span>mac-address=00:22:68:12:79:A2 mac-address=0;34;104;18;1 </tr></thead> <tbody><tr> <td align="left">mac-address</td> -<td align="left">mac-address</td> +<td align="left"> </td> <td align="left">usual hex-digits-and-colons notation</td> <td align="left">MAC address in traditional hex-digits-and-colons notation, or or semicolon separated list of 20 decimal bytes (obsolete)<span class="bold"><strong> @@ -239,7 +325,7 @@ Example: </strong></span>mac-address= 80:00:00:6d:fe:80:00:00:00:00:00:00:00:02: </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.11.6.6"></a><p class="title"><b>Table 3. ipv4 setting (section)</b></p> +<a name="id-1.2.11.6.8"></a><p class="title"><b>Table 5. ipv4 setting (section)</b></p> <div class="table-contents"><table class="table" summary="ipv4 setting (section)" border="1"> <colgroup> <col> @@ -256,7 +342,7 @@ Example: </strong></span>mac-address= 80:00:00:6d:fe:80:00:00:00:00:00:00:00:02: <tbody> <tr> <td align="left">dns</td> -<td align="left">dns</td> +<td align="left"> </td> <td align="left">list of DNS IP addresses</td> <td align="left">List of DNS servers.<span class="bold"><strong> @@ -290,7 +376,7 @@ Example: </strong></span>route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.11.6.7"></a><p class="title"><b>Table 4. ipv6 setting (section)</b></p> +<a name="id-1.2.11.6.9"></a><p class="title"><b>Table 6. ipv6 setting (section)</b></p> <div class="table-contents"><table class="table" summary="ipv6 setting (section)" border="1"> <colgroup> <col> @@ -307,7 +393,7 @@ Example: </strong></span>route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16</td> <tbody> <tr> <td align="left">dns</td> -<td align="left">dns</td> +<td align="left"> </td> <td align="left">list of DNS IP addresses</td> <td align="left">List of DNS servers.<span class="bold"><strong> @@ -341,7 +427,7 @@ Example: </strong></span>route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11 </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.11.6.8"></a><p class="title"><b>Table 5. serial setting (section)</b></p> +<a name="id-1.2.11.6.10"></a><p class="title"><b>Table 7. serial setting (section)</b></p> <div class="table-contents"><table class="table" summary="serial setting (section)" border="1"> <colgroup> <col> @@ -357,7 +443,7 @@ Example: </strong></span>route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11 </tr></thead> <tbody><tr> <td align="left">parity</td> -<td align="left">parity</td> +<td align="left"> </td> <td align="left">'e', 'o', or 'n'</td> <td align="left">The connection parity; even, odd, or none. Note that older versions of NetworkManager stored this as an integer: 69 ('E') for even, 111 ('o') for odd, or 110 ('n') for none.<span class="bold"><strong> @@ -366,7 +452,7 @@ Example: </strong></span>parity=n</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.11.6.9"></a><p class="title"><b>Table 6. vpn setting (section)</b></p> +<a name="id-1.2.11.6.11"></a><p class="title"><b>Table 8. vpn setting (section)</b></p> <div class="table-contents"><table class="table" summary="vpn setting (section)" border="1"> <colgroup> <col> @@ -401,7 +487,7 @@ Example: </strong></span>password=Popocatepetl</td> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.11.6.10"></a><p class="title"><b>Table 7. wifi-p2p setting (section)</b></p> +<a name="id-1.2.11.6.12"></a><p class="title"><b>Table 9. wifi-p2p setting (section)</b></p> <div class="table-contents"><table class="table" summary="wifi-p2p setting (section)" border="1"> <colgroup> <col> @@ -417,99 +503,13 @@ Example: </strong></span>password=Popocatepetl</td> </tr></thead> <tbody><tr> <td align="left">peer</td> -<td align="left">peer</td> +<td align="left"> </td> <td align="left">usual hex-digits-and-colons notation</td> <td align="left">MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162).</td> </tr></tbody> </table></div> </div> <br class="table-break"><div class="table"> -<a name="id-1.2.11.6.11"></a><p class="title"><b>Table 8. 802-3-ethernet setting (section)</b></p> -<div class="table-contents"><table class="table" summary="802-3-ethernet setting (section)" border="1"> -<colgroup> -<col> -<col> -<col> -<col> -</colgroup> -<thead><tr> -<th>Property</th> -<th>Keyfile Variable</th> -<th>Format</th> -<th>Description</th> -</tr></thead> -<tbody> -<tr> -<td align="left">mac-address</td> -<td align="left">mac-address</td> -<td align="left">usual hex-digits-and-colons notation</td> -<td align="left">MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162)</td> -</tr> -<tr> -<td align="left">cloned-mac-address</td> -<td align="left">cloned-mac-address</td> -<td align="left">usual hex-digits-and-colons notation</td> -<td align="left">Cloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178).</td> -</tr> -<tr> -<td align="left">mac-address-blacklist</td> -<td align="left">mac-address-blacklist</td> -<td align="left">list of MACs (separated with semicolons)</td> -<td align="left">MAC address blacklist.<span class="bold"><strong> - -Example: </strong></span>mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78</td> -</tr> -</tbody> -</table></div> -</div> -<br class="table-break"><div class="table"> -<a name="id-1.2.11.6.12"></a><p class="title"><b>Table 9. 802-11-wireless setting (section)</b></p> -<div class="table-contents"><table class="table" summary="802-11-wireless setting (section)" border="1"> -<colgroup> -<col> -<col> -<col> -<col> -</colgroup> -<thead><tr> -<th>Property</th> -<th>Keyfile Variable</th> -<th>Format</th> -<th>Description</th> -</tr></thead> -<tbody> -<tr> -<td align="left">ssid</td> -<td align="left">ssid</td> -<td align="left">string (or decimal-byte list - obsolete)</td> -<td align="left">SSID of Wi-Fi network.<span class="bold"><strong> - -Example: </strong></span>ssid=Quick Net</td> -</tr> -<tr> -<td align="left">mac-address</td> -<td align="left">mac-address</td> -<td align="left">usual hex-digits-and-colons notation</td> -<td align="left">MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162).</td> -</tr> -<tr> -<td align="left">cloned-mac-address</td> -<td align="left">cloned-mac-address</td> -<td align="left">usual hex-digits-and-colons notation</td> -<td align="left">Cloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178).</td> -</tr> -<tr> -<td align="left">mac-address-blacklist</td> -<td align="left">mac-address-blacklist</td> -<td align="left">list of MACs (separated with semicolons)</td> -<td align="left">MAC address blacklist.<span class="bold"><strong> - -Example: </strong></span>mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78</td> -</tr> -</tbody> -</table></div> -</div> -<br class="table-break"><div class="table"> <a name="id-1.2.11.6.13"></a><p class="title"><b>Table 10. wpan setting (section)</b></p> <div class="table-contents"><table class="table" summary="wpan setting (section)" border="1"> <colgroup> @@ -526,7 +526,7 @@ Example: </strong></span>mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79 </tr></thead> <tbody><tr> <td align="left">mac-address</td> -<td align="left">mac-address</td> +<td align="left"> </td> <td align="left">usual hex-digits-and-colons notation</td> <td align="left">MAC address in hex-digits-and-colons notation (e.g. 76:d8:9b:87:66:60:84:ee).</td> </tr></tbody> diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index e2f76d6a..69b51835 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -68,7 +68,7 @@ </p> <div class="refsect2"> <a name="id-1.2.10.4.7"></a><h3>connection setting</h3> -<p> General Connection Profile Settings.</p> +<p>General Connection Profile Settings.</p> <p> Properties: </p> @@ -81,8 +81,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.auth-retries"></a>auth-retries</code></span></p></td> <td> -<p> The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection.</p> -<p> Currently, this only applies to 802-1x authentication.</p> +<p>The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection.</p> +<p>Currently, this only applies to 802-1x authentication.</p> <p> Format: int32</p> </td> @@ -92,11 +92,11 @@ <td> <p> Alias: autoconnect</p> -<p> 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.</p> -<p> 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.</p> -<p> Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.</p> -<p> If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined.</p> -<p> Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.</p> +<p>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.</p> +<p>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.</p> +<p>Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.</p> +<p>If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined.</p> +<p>Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.</p> <p> Format: boolean</p> </td> @@ -104,7 +104,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.autoconnect-priority"></a>autoconnect-priority</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: int32</p> </td> @@ -112,7 +112,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.autoconnect-retries"></a>autoconnect-retries</code></span></p></td> <td> -<p> The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.</p> +<p>The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.</p> <p> Format: int32</p> </td> @@ -120,7 +120,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.autoconnect-slaves"></a>autoconnect-slaves</code></span></p></td> <td> -<p> Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.</p> +<p>Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.</p> <p> Format: NMSettingConnectionAutoconnectSlaves (int32)</p> </td> @@ -128,9 +128,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.dns-over-tls"></a>dns-over-tls</code></span></p></td> <td> -<p> Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.</p> -<p> 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.</p> -<p> This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</p> +<p>Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.</p> +<p>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.</p> +<p>This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</p> <p> Format: int32</p> </td> @@ -138,7 +138,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.gateway-ping-timeout"></a>gateway-ping-timeout</code></span></p></td> <td> -<p> If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.</p> +<p>If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.</p> <p> Format: uint32</p> </td> @@ -148,7 +148,7 @@ <td> <p> Alias: con-name</p> -<p> A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".</p> +<p>A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".</p> <p> Format: string</p> </td> @@ -158,9 +158,9 @@ <td> <p> Alias: ifname</p> -<p> The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings).</p> -<p> For software devices this specifies the name of the created device.</p> -<p> For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.</p> +<p>The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings).</p> +<p>For software devices this specifies the name of the created device.</p> +<p>For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.</p> <p> Format: string</p> </td> @@ -168,7 +168,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.lldp"></a>lldp</code></span></p></td> <td> -<p> Whether LLDP is enabled for the connection.</p> +<p>Whether LLDP is enabled for the connection.</p> <p> Format: int32</p> </td> @@ -176,9 +176,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.llmnr"></a>llmnr</code></span></p></td> <td> -<p> Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.</p> -<p> The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").</p> -<p> This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</p> +<p>Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.</p> +<p>The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").</p> +<p>This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</p> <p> Format: int32</p> </td> @@ -188,7 +188,7 @@ <td> <p> Alias: master</p> -<p> Interface name of the master device or UUID of the master connection.</p> +<p>Interface name of the master device or UUID of the master connection.</p> <p> Format: string</p> </td> @@ -196,9 +196,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.mdns"></a>mdns</code></span></p></td> <td> -<p> Whether mDNS is enabled for the connection.</p> -<p> The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").</p> -<p> This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</p> +<p>Whether mDNS is enabled for the connection.</p> +<p>The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").</p> +<p>This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.</p> <p> Format: int32</p> </td> @@ -206,8 +206,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.metered"></a>metered</code></span></p></td> <td> -<p> Whether the connection is metered.</p> -<p> When updating this property on a currently activated connection, the change takes effect immediately.</p> +<p>Whether the connection is metered.</p> +<p>When updating this property on a currently activated connection, the change takes effect immediately.</p> <p> Format: NMMetered (int32)</p> </td> @@ -215,15 +215,15 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.mptcp-flags"></a>mptcp-flags</code></span></p></td> <td> -<p> Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints.</p> -<p> If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered.</p> -<p> The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags.</p> -<p> Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless.</p> -<p> Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that.</p> -<p> When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.</p> -<p> If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl.</p> -<p> NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp.</p> -<p> Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).</p> +<p>Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints.</p> +<p>If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered.</p> +<p>The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags.</p> +<p>Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless.</p> +<p>Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that.</p> +<p>When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.</p> +<p>If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl.</p> +<p>NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp.</p> +<p>Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).</p> <p> Format: uint32</p> </td> @@ -231,9 +231,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.mud-url"></a>mud-url</code></span></p></td> <td> -<p> If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://".</p> -<p> The special value "none" is allowed to indicate that no MUD URL is used.</p> -<p> If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".</p> +<p>If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://".</p> +<p>The special value "none" is allowed to indicate that no MUD URL is used.</p> +<p>If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".</p> <p> Format: string</p> </td> @@ -241,7 +241,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.multi-connect"></a>multi-connect</code></span></p></td> <td> -<p> Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.</p> +<p>Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.</p> <p> Format: int32</p> </td> @@ -249,8 +249,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.permissions"></a>permissions</code></span></p></td> <td> -<p> An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah".</p> -<p> At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.</p> +<p>An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah".</p> +<p>At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.</p> <p> Format: array of string</p> </td> @@ -258,7 +258,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.read-only"></a>read-only</code></span></p></td> <td> -<p> FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.</p> +<p>FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.</p> <p> Format: boolean</p> </td> @@ -266,7 +266,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.secondaries"></a>secondaries</code></span></p></td> <td> -<p> List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.</p> +<p>List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.</p> <p> Format: array of string</p> </td> @@ -276,7 +276,7 @@ <td> <p> Alias: slave-type</p> -<p> Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.</p> +<p>Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.</p> <p> Format: string</p> </td> @@ -284,11 +284,11 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.stable-id"></a>stable-id</code></span></p></td> <td> -<p> This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.</p> -<p> The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid].</p> -<p> Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.</p> -<p> The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.</p> -<p> If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.</p> +<p>This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.</p> +<p>The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid].</p> +<p>Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.</p> +<p>The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.</p> +<p>If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.</p> <p> Format: string</p> </td> @@ -296,8 +296,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.timestamp"></a>timestamp</code></span></p></td> <td> -<p> The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.</p> -<p> NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).</p> +<p>The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.</p> +<p>NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).</p> <p> Format: uint64</p> </td> @@ -307,7 +307,7 @@ <td> <p> Alias: type</p> -<p> Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).</p> +<p>Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).</p> <p> Format: string</p> </td> @@ -315,17 +315,17 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.uuid"></a>uuid</code></span></p></td> <td> -<p> A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes.</p> -<p> The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").</p> +<p>A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes.</p> +<p>The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").</p> <p> - Format: string</p> + Format: a valid RFC4122 universally unique identifier (UUID).</p> </td> </tr> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.wait-activation-delay"></a>wait-activation-delay</code></span></p></td> <td> -<p> Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.</p> -<p> The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</p> +<p>Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.</p> +<p>The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</p> <p> Format: int32</p> </td> @@ -333,8 +333,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.wait-device-timeout"></a>wait-device-timeout</code></span></p></td> <td> -<p> Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed.</p> -<p> The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</p> +<p>Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed.</p> +<p>The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</p> <p> Format: int32</p> </td> @@ -342,8 +342,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.connection.zone"></a>zone</code></span></p></td> <td> -<p> The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall.</p> -<p> When updating this property on a currently activated connection, the change takes effect immediately.</p> +<p>The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall.</p> +<p>When updating this property on a currently activated connection, the change takes effect immediately.</p> <p> Format: string</p> </td> @@ -354,7 +354,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.8"></a><h3>6lowpan setting</h3> -<p> 6LoWPAN Settings.</p> +<p>6LoWPAN Settings.</p> <p> Properties: </p> @@ -368,7 +368,7 @@ <td> <p> Alias: dev</p> -<p> If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.</p> +<p>If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.</p> <p> Format: string</p> </td> @@ -378,7 +378,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.9"></a><h3>802-1x setting</h3> -<p> IEEE 802.1x Authentication Settings.</p> +<p>IEEE 802.1x Authentication Settings.</p> <p> Properties: </p> @@ -391,7 +391,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.altsubject-matches"></a>altsubject-matches</code></span></p></td> <td> -<p> List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.</p> +<p>List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.</p> <p> Format: array of string</p> </td> @@ -399,7 +399,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.anonymous-identity"></a>anonymous-identity</code></span></p></td> <td> -<p> Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.</p> +<p>Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.</p> <p> Format: string</p> </td> @@ -407,7 +407,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.auth-timeout"></a>auth-timeout</code></span></p></td> <td> -<p> A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.</p> +<p>A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.</p> <p> Format: int32</p> </td> @@ -415,9 +415,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.ca-cert"></a>ca-cert</code></span></p></td> <td> -<p> Contains the CA certificate if used by the EAP method specified in the "eap" property.</p> -<p> Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</p> -<p> Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</p> +<p>Contains the CA certificate if used by the EAP method specified in the "eap" property.</p> +<p>Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</p> +<p>Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</p> <p> Format: byte array</p> </td> @@ -425,7 +425,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.ca-cert-password"></a>ca-cert-password</code></span></p></td> <td> -<p> The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</p> +<p>The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</p> <p> Format: string</p> </td> @@ -433,7 +433,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.ca-cert-password-flags"></a>ca-cert-password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "ca-cert-password" property.</p> +<p>Flags indicating how to handle the "ca-cert-password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -441,8 +441,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.ca-path"></a>ca-path</code></span></p></td> <td> -<p> UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property.</p> -<p> If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</p> +<p>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property.</p> +<p>If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</p> <p> Format: string</p> </td> @@ -450,8 +450,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.client-cert"></a>client-cert</code></span></p></td> <td> -<p> Contains the client certificate if used by the EAP method specified in the "eap" property.</p> -<p> Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.</p> +<p>Contains the client certificate if used by the EAP method specified in the "eap" property.</p> +<p>Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.</p> <p> Format: byte array</p> </td> @@ -459,7 +459,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.client-cert-password"></a>client-cert-password</code></span></p></td> <td> -<p> The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</p> +<p>The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</p> <p> Format: string</p> </td> @@ -467,7 +467,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.client-cert-password-flags"></a>client-cert-password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "client-cert-password" property.</p> +<p>Flags indicating how to handle the "client-cert-password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -475,7 +475,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.domain-match"></a>domain-match</code></span></p></td> <td> -<p> Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</p> +<p>Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</p> <p> Format: string</p> </td> @@ -483,7 +483,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.domain-suffix-match"></a>domain-suffix-match</code></span></p></td> <td> -<p> Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</p> +<p>Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</p> <p> Format: string</p> </td> @@ -491,7 +491,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.eap"></a>eap</code></span></p></td> <td> -<p> The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.</p> +<p>The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.</p> <p> Format: array of string</p> </td> @@ -499,7 +499,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.identity"></a>identity</code></span></p></td> <td> -<p> Identity string for EAP authentication methods. Often the user's user or login name.</p> +<p>Identity string for EAP authentication methods. Often the user's user or login name.</p> <p> Format: string</p> </td> @@ -507,7 +507,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.optional"></a>optional</code></span></p></td> <td> -<p> Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.</p> +<p>Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.</p> <p> Format: boolean</p> </td> @@ -515,7 +515,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.pac-file"></a>pac-file</code></span></p></td> <td> -<p> UTF-8 encoded file path containing PAC for EAP-FAST.</p> +<p>UTF-8 encoded file path containing PAC for EAP-FAST.</p> <p> Format: string</p> </td> @@ -523,7 +523,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.password"></a>password</code></span></p></td> <td> -<p> UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</p> +<p>UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</p> <p> Format: string</p> </td> @@ -531,7 +531,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.password-flags"></a>password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "password" property.</p> +<p>Flags indicating how to handle the "password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -539,7 +539,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.password-raw"></a>password-raw</code></span></p></td> <td> -<p> Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</p> +<p>Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</p> <p> Format: byte array</p> </td> @@ -547,7 +547,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.password-raw-flags"></a>password-raw-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "password-raw" property.</p> +<p>Flags indicating how to handle the "password-raw" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -555,7 +555,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase1-auth-flags"></a>phase1-auth-flags</code></span></p></td> <td> -<p> Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details.</p> +<p>Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. TLS time checks can be also disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x and tls_disable_time_checks settings. See the wpa_supplicant documentation for more details.</p> <p> Format: uint32</p> </td> @@ -563,7 +563,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase1-fast-provisioning"></a>phase1-fast-provisioning</code></span></p></td> <td> -<p> Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details.</p> +<p>Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details.</p> <p> Format: string</p> </td> @@ -571,7 +571,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase1-peaplabel"></a>phase1-peaplabel</code></span></p></td> <td> -<p> Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details.</p> +<p>Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details.</p> <p> Format: string</p> </td> @@ -579,7 +579,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase1-peapver"></a>phase1-peapver</code></span></p></td> <td> -<p> Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version.</p> +<p>Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version.</p> <p> Format: string</p> </td> @@ -587,7 +587,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-altsubject-matches"></a>phase2-altsubject-matches</code></span></p></td> <td> -<p> List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.</p> +<p>List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.</p> <p> Format: array of string</p> </td> @@ -595,7 +595,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-auth"></a>phase2-auth</code></span></p></td> <td> -<p> Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.</p> +<p>Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.</p> <p> Format: string</p> </td> @@ -603,7 +603,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-autheap"></a>phase2-autheap</code></span></p></td> <td> -<p> Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</p> +<p>Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</p> <p> Format: string</p> </td> @@ -611,9 +611,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-ca-cert"></a>phase2-ca-cert</code></span></p></td> <td> -<p> Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.</p> -<p> Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</p> -<p> Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</p> +<p>Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.</p> +<p>Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</p> +<p>Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</p> <p> Format: byte array</p> </td> @@ -621,7 +621,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-ca-cert-password"></a>phase2-ca-cert-password</code></span></p></td> <td> -<p> The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</p> +<p>The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</p> <p> Format: string</p> </td> @@ -629,7 +629,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-ca-cert-password-flags"></a>phase2-ca-cert-password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "phase2-ca-cert-password" property.</p> +<p>Flags indicating how to handle the "phase2-ca-cert-password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -637,8 +637,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-ca-path"></a>phase2-ca-path</code></span></p></td> <td> -<p> UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property.</p> -<p> If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</p> +<p>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property.</p> +<p>If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</p> <p> Format: string</p> </td> @@ -646,8 +646,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-client-cert"></a>phase2-client-cert</code></span></p></td> <td> -<p> Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.</p> -<p> Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</p> +<p>Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.</p> +<p>Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</p> <p> Format: byte array</p> </td> @@ -655,7 +655,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-client-cert-password"></a>phase2-client-cert-password</code></span></p></td> <td> -<p> The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</p> +<p>The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</p> <p> Format: string</p> </td> @@ -663,7 +663,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-client-cert-password-flags"></a>phase2-client-cert-password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "phase2-client-cert-password" property.</p> +<p>Flags indicating how to handle the "phase2-client-cert-password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -671,7 +671,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-domain-match"></a>phase2-domain-match</code></span></p></td> <td> -<p> Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</p> +<p>Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.</p> <p> Format: string</p> </td> @@ -679,7 +679,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-domain-suffix-match"></a>phase2-domain-suffix-match</code></span></p></td> <td> -<p> Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</p> +<p>Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.</p> <p> Format: string</p> </td> @@ -687,8 +687,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-private-key"></a>phase2-private-key</code></span></p></td> <td> -<p> Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls".</p> -<p> Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</p> +<p>Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls".</p> +<p>Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</p> <p> Format: byte array</p> </td> @@ -696,7 +696,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-private-key-password"></a>phase2-private-key-password</code></span></p></td> <td> -<p> The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.</p> +<p>The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.</p> <p> Format: string</p> </td> @@ -704,7 +704,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-private-key-password-flags"></a>phase2-private-key-password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "phase2-private-key-password" property.</p> +<p>Flags indicating how to handle the "phase2-private-key-password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -712,7 +712,10 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.phase2-subject-match"></a>phase2-subject-match</code></span></p></td> <td> -<p> Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match.</p> +<p>Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.</p> +<p> + This property is deprecated since version 1.2. + Use "phase2-domain-suffix-match" instead.</p> <p> Format: string</p> </td> @@ -720,7 +723,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.pin"></a>pin</code></span></p></td> <td> -<p> PIN used for EAP authentication methods.</p> +<p>PIN used for EAP authentication methods.</p> <p> Format: string</p> </td> @@ -728,7 +731,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.pin-flags"></a>pin-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "pin" property.</p> +<p>Flags indicating how to handle the "pin" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -736,9 +739,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.private-key"></a>private-key</code></span></p></td> <td> -<p> Contains the private key when the "eap" property is set to "tls".</p> -<p> Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</p> -<p> WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.</p> +<p>Contains the private key when the "eap" property is set to "tls".</p> +<p>Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</p> +<p>WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.</p> <p> Format: byte array</p> </td> @@ -746,7 +749,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.private-key-password"></a>private-key-password</code></span></p></td> <td> -<p> The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.</p> +<p>The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.</p> <p> Format: string</p> </td> @@ -754,7 +757,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.private-key-password-flags"></a>private-key-password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "private-key-password" property.</p> +<p>Flags indicating how to handle the "private-key-password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -762,7 +765,10 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.subject-match"></a>subject-match</code></span></p></td> <td> -<p> Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match.</p> +<p>Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.</p> +<p> + This property is deprecated since version 1.2. + Use "phase2-domain-suffix-match" instead.</p> <p> Format: string</p> </td> @@ -770,7 +776,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-1x.system-ca-certs"></a>system-ca-certs</code></span></p></td> <td> -<p> When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).</p> +<p>When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).</p> <p> Format: boolean</p> </td> @@ -781,7 +787,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.10"></a><h3>adsl setting</h3> -<p> ADSL Settings.</p> +<p>ADSL Settings.</p> <p> Properties: </p> @@ -796,7 +802,7 @@ <td> <p> Alias: encapsulation</p> -<p> Encapsulation of ADSL connection. Can be "vcmux" or "llc".</p> +<p>Encapsulation of ADSL connection. Can be "vcmux" or "llc".</p> <p> Format: string</p> </td> @@ -806,7 +812,7 @@ <td> <p> Alias: password</p> -<p> Password used to authenticate with the ADSL service.</p> +<p>Password used to authenticate with the ADSL service.</p> <p> Format: string</p> </td> @@ -814,7 +820,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.adsl.password-flags"></a>password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "password" property.</p> +<p>Flags indicating how to handle the "password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -824,7 +830,7 @@ <td> <p> Alias: protocol</p> -<p> ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm".</p> +<p>ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm".</p> <p> Format: string</p> </td> @@ -834,7 +840,7 @@ <td> <p> Alias: username</p> -<p> Username used to authenticate with the ADSL service.</p> +<p>Username used to authenticate with the ADSL service.</p> <p> Format: string</p> </td> @@ -842,7 +848,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.adsl.vci"></a>vci</code></span></p></td> <td> -<p> VCI of ADSL connection</p> +<p>VCI of ADSL connection</p> <p> Format: uint32</p> </td> @@ -850,7 +856,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.adsl.vpi"></a>vpi</code></span></p></td> <td> -<p> VPI of ADSL connection</p> +<p>VPI of ADSL connection</p> <p> Format: uint32</p> </td> @@ -861,7 +867,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.11"></a><h3>bluetooth setting</h3> -<p> Bluetooth Settings.</p> +<p>Bluetooth Settings.</p> <p> Properties: </p> @@ -876,7 +882,7 @@ <td> <p> Alias: addr</p> -<p> The Bluetooth address of the device.</p> +<p>The Bluetooth address of the device.</p> <p> Format: byte array</p> </td> @@ -886,7 +892,7 @@ <td> <p> Alias: bt-type</p> -<p> Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.</p> +<p>Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.</p> <p> Format: string</p> </td> @@ -897,7 +903,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.12"></a><h3>bond setting</h3> -<p> Bonding Settings.</p> +<p>Bonding Settings.</p> <p> Properties: </p> @@ -909,7 +915,7 @@ <tbody><tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bond.options"></a>options</code></span></p></td> <td> -<p> Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).</p> +<p>Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).</p> <p> Format: dict of string to string</p> </td> @@ -919,7 +925,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.13"></a><h3>bridge setting</h3> -<p> Bridging Settings.</p> +<p>Bridging Settings.</p> <p> Properties: </p> @@ -934,7 +940,7 @@ <td> <p> Alias: ageing-time</p> -<p> The Ethernet MAC address aging time, in seconds.</p> +<p>The Ethernet MAC address aging time, in seconds.</p> <p> Format: uint32</p> </td> @@ -944,7 +950,7 @@ <td> <p> Alias: forward-delay</p> -<p> The Spanning Tree Protocol (STP) forwarding delay, in seconds.</p> +<p>The Spanning Tree Protocol (STP) forwarding delay, in seconds.</p> <p> Format: uint32</p> </td> @@ -952,8 +958,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.group-address"></a>group-address</code></span></p></td> <td> -<p> If specified, The MAC address of the multicast group this bridge uses for STP.</p> -<p> The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.</p> +<p>If specified, The MAC address of the multicast group this bridge uses for STP.</p> +<p>The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.</p> <p> Format: byte array</p> </td> @@ -963,7 +969,7 @@ <td> <p> Alias: group-forward-mask</p> -<p> A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.</p> +<p>A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.</p> <p> Format: uint32</p> </td> @@ -973,7 +979,7 @@ <td> <p> Alias: hello-time</p> -<p> The Spanning Tree Protocol (STP) hello time, in seconds.</p> +<p>The Spanning Tree Protocol (STP) hello time, in seconds.</p> <p> Format: uint32</p> </td> @@ -983,8 +989,11 @@ <td> <p> Alias: mac</p> -<p> If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set.</p> -<p> If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1</p> +<p>If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set.</p> +<p>If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge.</p> +<p> + This property is deprecated since version 1.12. + Use the "cloned-mac-address" property instead.</p> <p> Format: byte array</p> </td> @@ -994,7 +1003,7 @@ <td> <p> Alias: max-age</p> -<p> The Spanning Tree Protocol (STP) maximum message age, in seconds.</p> +<p>The Spanning Tree Protocol (STP) maximum message age, in seconds.</p> <p> Format: uint32</p> </td> @@ -1002,7 +1011,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-hash-max"></a>multicast-hash-max</code></span></p></td> <td> -<p> Set maximum size of multicast hash table (value must be a power of 2).</p> +<p>Set maximum size of multicast hash table (value must be a power of 2).</p> <p> Format: uint32</p> </td> @@ -1010,7 +1019,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-last-member-count"></a>multicast-last-member-count</code></span></p></td> <td> -<p> Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.</p> +<p>Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.</p> <p> Format: uint32</p> </td> @@ -1018,7 +1027,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-last-member-interval"></a>multicast-last-member-interval</code></span></p></td> <td> -<p> Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.</p> +<p>Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.</p> <p> Format: uint64</p> </td> @@ -1026,7 +1035,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-membership-interval"></a>multicast-membership-interval</code></span></p></td> <td> -<p> Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.</p> +<p>Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.</p> <p> Format: uint64</p> </td> @@ -1034,7 +1043,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-querier"></a>multicast-querier</code></span></p></td> <td> -<p> Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.</p> +<p>Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.</p> <p> Format: boolean</p> </td> @@ -1042,7 +1051,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-querier-interval"></a>multicast-querier-interval</code></span></p></td> <td> -<p> If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.</p> +<p>If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.</p> <p> Format: uint64</p> </td> @@ -1050,7 +1059,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-query-interval"></a>multicast-query-interval</code></span></p></td> <td> -<p> Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.</p> +<p>Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.</p> <p> Format: uint64</p> </td> @@ -1058,7 +1067,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-query-response-interval"></a>multicast-query-response-interval</code></span></p></td> <td> -<p> Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.</p> +<p>Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.</p> <p> Format: uint64</p> </td> @@ -1066,7 +1075,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-query-use-ifaddr"></a>multicast-query-use-ifaddr</code></span></p></td> <td> -<p> If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.</p> +<p>If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.</p> <p> Format: boolean</p> </td> @@ -1074,8 +1083,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-router"></a>multicast-router</code></span></p></td> <td> -<p> Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work.</p> -<p> Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).</p> +<p>Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work.</p> +<p>Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).</p> <p> Format: string</p> </td> @@ -1085,7 +1094,7 @@ <td> <p> Alias: multicast-snooping</p> -<p> Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.</p> +<p>Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.</p> <p> Format: boolean</p> </td> @@ -1093,7 +1102,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-startup-query-count"></a>multicast-startup-query-count</code></span></p></td> <td> -<p> Set the number of IGMP queries to send during startup phase.</p> +<p>Set the number of IGMP queries to send during startup phase.</p> <p> Format: uint32</p> </td> @@ -1101,7 +1110,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.multicast-startup-query-interval"></a>multicast-startup-query-interval</code></span></p></td> <td> -<p> Sets the time (in deciseconds) between queries sent out at startup to determine membership information.</p> +<p>Sets the time (in deciseconds) between queries sent out at startup to determine membership information.</p> <p> Format: uint64</p> </td> @@ -1111,7 +1120,7 @@ <td> <p> Alias: priority</p> -<p> Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge.</p> +<p>Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge.</p> <p> Format: uint32</p> </td> @@ -1121,7 +1130,7 @@ <td> <p> Alias: stp</p> -<p> Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.</p> +<p>Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.</p> <p> Format: boolean</p> </td> @@ -1129,7 +1138,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.vlan-default-pvid"></a>vlan-default-pvid</code></span></p></td> <td> -<p> The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.</p> +<p>The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.</p> <p> Format: uint32</p> </td> @@ -1137,7 +1146,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.vlan-filtering"></a>vlan-filtering</code></span></p></td> <td> -<p> Control whether VLAN filtering is enabled on the bridge.</p> +<p>Control whether VLAN filtering is enabled on the bridge.</p> <p> Format: boolean</p> </td> @@ -1145,8 +1154,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.vlan-protocol"></a>vlan-protocol</code></span></p></td> <td> -<p> If specified, the protocol used for VLAN filtering.</p> -<p> Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.</p> +<p>If specified, the protocol used for VLAN filtering.</p> +<p>Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.</p> <p> Format: string</p> </td> @@ -1154,7 +1163,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.vlan-stats-enabled"></a>vlan-stats-enabled</code></span></p></td> <td> -<p> Controls whether per-VLAN stats accounting is enabled.</p> +<p>Controls whether per-VLAN stats accounting is enabled.</p> <p> Format: boolean</p> </td> @@ -1162,10 +1171,10 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge.vlans"></a>vlans</code></span></p></td> <td> -<p> Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property.</p> -<p> In nmcli the VLAN list can be specified with the following syntax:</p> -<p> $vid [pvid] [untagged] [, $vid [pvid] [untagged]]...</p> -<p> where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</p> +<p>Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property.</p> +<p>In nmcli the VLAN list can be specified with the following syntax:</p> +<p>$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...</p> +<p>where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</p> <p> Format: array of vardict</p> </td> @@ -1176,7 +1185,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.14"></a><h3>bridge-port setting</h3> -<p> Bridge Port Settings.</p> +<p>Bridge Port Settings.</p> <p> Properties: </p> @@ -1191,7 +1200,7 @@ <td> <p> Alias: hairpin</p> -<p> Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.</p> +<p>Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.</p> <p> Format: boolean</p> </td> @@ -1201,7 +1210,7 @@ <td> <p> Alias: path-cost</p> -<p> The Spanning Tree Protocol (STP) port cost for destinations via this port.</p> +<p>The Spanning Tree Protocol (STP) port cost for destinations via this port.</p> <p> Format: uint32</p> </td> @@ -1211,7 +1220,7 @@ <td> <p> Alias: priority</p> -<p> The Spanning Tree Protocol (STP) priority of this bridge port.</p> +<p>The Spanning Tree Protocol (STP) priority of this bridge port.</p> <p> Format: uint32</p> </td> @@ -1219,10 +1228,10 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.bridge-port.vlans"></a>vlans</code></span></p></td> <td> -<p> Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property.</p> -<p> In nmcli the VLAN list can be specified with the following syntax:</p> -<p> $vid [pvid] [untagged] [, $vid [pvid] [untagged]]...</p> -<p> where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</p> +<p>Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property.</p> +<p>In nmcli the VLAN list can be specified with the following syntax:</p> +<p>$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...</p> +<p>where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</p> <p> Format: array of vardict</p> </td> @@ -1233,7 +1242,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.15"></a><h3>cdma setting</h3> -<p> CDMA-based Mobile Broadband Settings.</p> +<p>CDMA-based Mobile Broadband Settings.</p> <p> Properties: </p> @@ -1246,7 +1255,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.cdma.mtu"></a>mtu</code></span></p></td> <td> -<p> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</p> +<p>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</p> <p> Format: uint32</p> </td> @@ -1254,7 +1263,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.cdma.number"></a>number</code></span></p></td> <td> -<p> The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required.</p> +<p>The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required.</p> <p> Format: string</p> </td> @@ -1264,7 +1273,7 @@ <td> <p> Alias: password</p> -<p> The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.</p> +<p>The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.</p> <p> Format: string</p> </td> @@ -1272,7 +1281,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.cdma.password-flags"></a>password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "password" property.</p> +<p>Flags indicating how to handle the "password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -1282,7 +1291,7 @@ <td> <p> Alias: user</p> -<p> The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.</p> +<p>The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.</p> <p> Format: string</p> </td> @@ -1293,7 +1302,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.16"></a><h3>dcb setting</h3> -<p> Data Center Bridging Settings.</p> +<p>Data Center Bridging Settings.</p> <p> Properties: </p> @@ -1306,7 +1315,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.app-fcoe-flags"></a>app-fcoe-flags</code></span></p></td> <td> -<p> Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> +<p>Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> <p> Format: NMSettingDcbFlags (uint32)</p> </td> @@ -1314,8 +1323,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.app-fcoe-mode"></a>app-fcoe-mode</code></span></p></td> <td> -<p> The FCoE controller mode; either "fabric" or "vn2vn".</p> -<p> Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".</p> +<p>The FCoE controller mode; either "fabric" or "vn2vn".</p> +<p>Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".</p> <p> Format: string</p> </td> @@ -1323,7 +1332,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.app-fcoe-priority"></a>app-fcoe-priority</code></span></p></td> <td> -<p> The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</p> +<p>The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</p> <p> Format: int32</p> </td> @@ -1331,7 +1340,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.app-fip-flags"></a>app-fip-flags</code></span></p></td> <td> -<p> Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> +<p>Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> <p> Format: NMSettingDcbFlags (uint32)</p> </td> @@ -1339,7 +1348,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.app-fip-priority"></a>app-fip-priority</code></span></p></td> <td> -<p> The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</p> +<p>The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</p> <p> Format: int32</p> </td> @@ -1347,7 +1356,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.app-iscsi-flags"></a>app-iscsi-flags</code></span></p></td> <td> -<p> Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> +<p>Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> <p> Format: NMSettingDcbFlags (uint32)</p> </td> @@ -1355,7 +1364,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.app-iscsi-priority"></a>app-iscsi-priority</code></span></p></td> <td> -<p> The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</p> +<p>The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</p> <p> Format: int32</p> </td> @@ -1363,7 +1372,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.priority-bandwidth"></a>priority-bandwidth</code></span></p></td> <td> -<p> An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents.</p> +<p>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents.</p> <p> Format: array of uint32</p> </td> @@ -1371,7 +1380,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.priority-flow-control"></a>priority-flow-control</code></span></p></td> <td> -<p> An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.</p> +<p>An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.</p> <p> Format: array of uint32</p> </td> @@ -1379,7 +1388,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.priority-flow-control-flags"></a>priority-flow-control-flags</code></span></p></td> <td> -<p> Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> +<p>Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> <p> Format: NMSettingDcbFlags (uint32)</p> </td> @@ -1387,7 +1396,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.priority-group-bandwidth"></a>priority-group-bandwidth</code></span></p></td> <td> -<p> An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents.</p> +<p>An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents.</p> <p> Format: array of uint32</p> </td> @@ -1395,7 +1404,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.priority-group-flags"></a>priority-group-flags</code></span></p></td> <td> -<p> Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> +<p>Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</p> <p> Format: NMSettingDcbFlags (uint32)</p> </td> @@ -1403,7 +1412,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.priority-group-id"></a>priority-group-id</code></span></p></td> <td> -<p> An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.</p> +<p>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.</p> <p> Format: array of uint32</p> </td> @@ -1411,7 +1420,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.priority-strict-bandwidth"></a>priority-strict-bandwidth</code></span></p></td> <td> -<p> An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.</p> +<p>An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.</p> <p> Format: array of uint32</p> </td> @@ -1419,7 +1428,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.dcb.priority-traffic-class"></a>priority-traffic-class</code></span></p></td> <td> -<p> An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.</p> +<p>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.</p> <p> Format: array of uint32</p> </td> @@ -1430,7 +1439,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.17"></a><h3>ethtool setting</h3> -<p> Ethtool Ethernet Settings.</p> +<p>Ethtool Ethernet Settings.</p> <p> Properties: </p> @@ -1794,7 +1803,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.18"></a><h3>gsm setting</h3> -<p> GSM-based Mobile Broadband Settings.</p> +<p>GSM-based Mobile Broadband Settings.</p> <p> Properties: </p> @@ -1809,7 +1818,7 @@ <td> <p> Alias: apn</p> -<p> The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.</p> +<p>The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.</p> <p> Format: string</p> </td> @@ -1817,7 +1826,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.auto-config"></a>auto-config</code></span></p></td> <td> -<p> When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.</p> +<p>When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.</p> <p> Format: boolean</p> </td> @@ -1825,7 +1834,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.device-id"></a>device-id</code></span></p></td> <td> -<p> The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device.</p> +<p>The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device.</p> <p> Format: string</p> </td> @@ -1833,7 +1842,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.home-only"></a>home-only</code></span></p></td> <td> -<p> When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.</p> +<p>When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.</p> <p> Format: boolean</p> </td> @@ -1841,7 +1850,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.mtu"></a>mtu</code></span></p></td> <td> -<p> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</p> +<p>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</p> <p> Format: uint32</p> </td> @@ -1849,7 +1858,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.network-id"></a>network-id</code></span></p></td> <td> -<p> The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.</p> +<p>The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.</p> <p> Format: string</p> </td> @@ -1857,7 +1866,10 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.number"></a>number</code></span></p></td> <td> -<p> Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1</p> +<p>Legacy setting that used to help establishing PPP data sessions for GSM-based modems.</p> +<p> + This property is deprecated since version 1.16. + User-provided values for this setting are no longer used.</p> <p> Format: string</p> </td> @@ -1867,7 +1879,7 @@ <td> <p> Alias: password</p> -<p> The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.</p> +<p>The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.</p> <p> Format: string</p> </td> @@ -1875,7 +1887,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.password-flags"></a>password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "password" property.</p> +<p>Flags indicating how to handle the "password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -1883,7 +1895,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.pin"></a>pin</code></span></p></td> <td> -<p> If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device.</p> +<p>If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device.</p> <p> Format: string</p> </td> @@ -1891,7 +1903,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.pin-flags"></a>pin-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "pin" property.</p> +<p>Flags indicating how to handle the "pin" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -1899,7 +1911,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.sim-id"></a>sim-id</code></span></p></td> <td> -<p> The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.</p> +<p>The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.</p> <p> Format: string</p> </td> @@ -1907,7 +1919,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.gsm.sim-operator-id"></a>sim-operator-id</code></span></p></td> <td> -<p> A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.</p> +<p>A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.</p> <p> Format: string</p> </td> @@ -1917,7 +1929,7 @@ <td> <p> Alias: user</p> -<p> The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.</p> +<p>The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.</p> <p> Format: string</p> </td> @@ -1928,7 +1940,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.19"></a><h3>infiniband setting</h3> -<p> Infiniband Settings.</p> +<p>Infiniband Settings.</p> <p> Properties: </p> @@ -1943,7 +1955,7 @@ <td> <p> Alias: mac</p> -<p> If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</p> +<p>If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</p> <p> Format: byte array</p> </td> @@ -1953,7 +1965,7 @@ <td> <p> Alias: mtu</p> -<p> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</p> +<p>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</p> <p> Format: uint32</p> </td> @@ -1963,7 +1975,7 @@ <td> <p> Alias: p-key</p> -<p> The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.</p> +<p>The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.</p> <p> Format: int32</p> </td> @@ -1973,7 +1985,7 @@ <td> <p> Alias: parent</p> -<p> The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".</p> +<p>The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".</p> <p> Format: string</p> </td> @@ -1983,7 +1995,7 @@ <td> <p> Alias: transport-mode</p> -<p> The IP-over-InfiniBand transport mode. Either "datagram" or "connected".</p> +<p>The IP-over-InfiniBand transport mode. Either "datagram" or "connected".</p> <p> Format: string</p> </td> @@ -1994,7 +2006,7 @@ <hr> <div class="refsect2"> <a name="id-1.2.10.4.20"></a><h3>ipv4 setting</h3> -<p> IPv4 Settings.</p> +<p>IPv4 Settings.</p> <p> Properties: </p> @@ -2009,16 +2021,25 @@ <td> <p> Alias: ip4</p> -<p> Array of IP addresses.</p> +<p>Array of IP addresses.</p> <p> Format: a comma separated list of addresses</p> </td> </tr> <tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.auto-route-ext-gw"></a>auto-route-ext-gw</code></span></p></td> +<td> +<p>VPN connections will default to add the route automatically unless this setting is set to FALSE.</p> +<p>For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.</p> +<p> + Format: NMTernary (int32)</p> +</td> +</tr> +<tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dad-timeout"></a>dad-timeout</code></span></p></td> <td> -<p> Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds.</p> -<p> The property is currently implemented only for IPv4.</p> +<p>Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds.</p> +<p>The property is currently implemented only for IPv4.</p> <p> Format: int32</p> </td> @@ -2026,12 +2047,12 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dhcp-client-id"></a>dhcp-client-id</code></span></p></td> <td> -<p> A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.</p> -<p> The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links.</p> -<p> The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset.</p> -<p> The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id.</p> -<p> The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.</p> -<p> If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.</p> +<p>A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.</p> +<p>The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links.</p> +<p>The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset.</p> +<p>The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id.</p> +<p>The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.</p> +<p>If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.</p> <p> Format: string</p> </td> @@ -2039,7 +2060,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dhcp-fqdn"></a>dhcp-fqdn</code></span></p></td> <td> -<p> If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.</p> +<p>If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.</p> <p> Format: string</p> </td> @@ -2047,7 +2068,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dhcp-hostname"></a>dhcp-hostname</code></span></p></td> <td> -<p> If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</p> +<p>If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</p> <p> Format: string</p> </td> @@ -2055,9 +2076,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dhcp-hostname-flags"></a>dhcp-hostname-flags</code></span></p></td> <td> -<p> Flags for the DHCP hostname and FQDN.</p> -<p> Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.</p> -<p> When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</p> +<p>Flags for the DHCP hostname and FQDN.</p> +<p>Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.</p> +<p>When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</p> <p> Format: uint32</p> </td> @@ -2065,7 +2086,10 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dhcp-iaid"></a>dhcp-iaid</code></span></p></td> <td> -<p> A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</p> +<p>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname".</p> +<p>For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.</p> +<p>For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address.</p> +<p>The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.</p> <p> Format: string</p> </td> @@ -2073,9 +2097,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dhcp-reject-servers"></a>dhcp-reject-servers</code></span></p></td> <td> -<p> Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.</p> -<p> For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24").</p> -<p> This property is currently not implemented for DHCPv6.</p> +<p>Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.</p> +<p>For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24").</p> +<p>This property is currently not implemented for DHCPv6.</p> <p> Format: array of string</p> </td> @@ -2083,7 +2107,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dhcp-send-hostname"></a>dhcp-send-hostname</code></span></p></td> <td> -<p> If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</p> +<p>If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</p> <p> Format: boolean</p> </td> @@ -2091,8 +2115,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dhcp-timeout"></a>dhcp-timeout</code></span></p></td> <td> -<p> A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).</p> -<p> Set to 2147483647 (MAXINT32) for infinity.</p> +<p>A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).</p> +<p>Set to 2147483647 (MAXINT32) for infinity.</p> <p> Format: int32</p> </td> @@ -2100,7 +2124,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dhcp-vendor-class-identifier"></a>dhcp-vendor-class-identifier</code></span></p></td> <td> -<p> The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.</p> +<p>The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.</p> <p> Format: string</p> </td> @@ -2108,7 +2132,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dns"></a>dns</code></span></p></td> <td> -<p> Array of IP addresses of DNS servers.</p> +<p>Array of IP addresses of DNS servers.</p> +<p>For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved.</p> <p> Format: array of uint32</p> </td> @@ -2116,11 +2141,11 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dns-options"></a>dns-options</code></span></p></td> <td> -<p> Array of DNS options as described in man 5 resolv.conf.</p> -<p> NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.</p> -<p> The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".</p> -<p> The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.</p> -<p> When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</p> +<p>Array of DNS options as described in man 5 resolv.conf.</p> +<p>NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.</p> +<p>The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".</p> +<p>The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.</p> +<p>When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</p> <p> Format: array of string</p> </td> @@ -2128,14 +2153,14 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dns-priority"></a>dns-priority</code></span></p></td> <td> -<p> DNS servers priority.</p> -<p> The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority).</p> -<p> Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.</p> -<p> Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.</p> -<p> Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile.</p> -<p> When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.</p> -<p> When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.</p> -<p> When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</p> +<p>DNS servers priority.</p> +<p>The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority).</p> +<p>Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.</p> +<p>Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.</p> +<p>Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile.</p> +<p>When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.</p> +<p>When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.</p> +<p>When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</p> <p> Format: int32</p> </td> @@ -2143,9 +2168,9 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.dns-search"></a>dns-search</code></span></p></td> <td> -<p> List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.</p> -<p> When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.</p> -<p> When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).</p> +<p>List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.</p> +<p>When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.</p> +<p>When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).</p> <p> Format: array of string</p> </td> @@ -2155,9 +2180,9 @@ <td> <p> Alias: gw4</p> -<p> The gateway associated with this configuration. This is only meaningful if "addresses" is also set.</p> -<p> Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.</p> -<p> Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".</p> +<p>The gateway associated with this configuration. This is only meaningful if "addresses" is also set.</p> +<p>Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.</p> +<p>Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".</p> <p> Format: string</p> </td> @@ -2165,7 +2190,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.ignore-auto-dns"></a>ignore-auto-dns</code></span></p></td> <td> -<p> When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</p> +<p>When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</p> <p> Format: boolean</p> </td> @@ -2173,7 +2198,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.ignore-auto-routes"></a>ignore-auto-routes</code></span></p></td> <td> -<p> When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</p> +<p>When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</p> <p> Format: boolean</p> </td> @@ -2181,8 +2206,8 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.link-local"></a>link-local</code></span></p></td> <td> -<p> Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server.</p> -<p> When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default".</p> +<p>Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server.</p> +<p>When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default".</p> <p> Format: int32</p> </td> @@ -2190,7 +2215,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.may-fail"></a>may-fail</code></span></p></td> <td> -<p> If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</p> +<p>If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</p> <p> Format: boolean</p> </td> @@ -2198,11 +2223,11 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.method"></a>method</code></span></p></td> <td> -<p> IP configuration method.</p> -<p> NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.</p> -<p> In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.</p> -<p> For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.</p> -<p> For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</p> +<p>IP configuration method.</p> +<p>NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.</p> +<p>In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.</p> +<p>For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.</p> +<p>For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</p> <p> Format: string</p> </td> @@ -2210,18 +2235,26 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.never-default"></a>never-default</code></span></p></td> <td> -<p> If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</p> +<p>If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</p> <p> Format: boolean</p> </td> </tr> <tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.replace-local-rule"></a>replace-local-rule</code></span></p></td> +<td> +<p>Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.</p> +<p> + Format: NMTernary (int32)</p> +</td> +</tr> +<tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.required-timeout"></a>required-timeout</code></span></p></td> <td> -<p> The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.</p> -<p> 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.</p> -<p> 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.</p> -<p> A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).</p> +<p>The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.</p> +<p>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.</p> +<p>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.</p> +<p>A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).</p> <p> Format: int32</p> </td> @@ -2229,7 +2262,7 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.route-metric"></a>route-metric</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: int64</p> </td> @@ -2237,10 +2270,10 @@ <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.route-table"></a>route-table</code></span></p></td> <td> -<p> Enable policy routing (source routing) and set the routing table used when adding routes.</p> -<p> This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.</p> -<p> If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.</p> -<p> Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</p> +<p>Enable policy routing (source routing) and set the routing table used when adding routes.</p> +<p>This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.</p> +<p>If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.</p> +<p>Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</p> <p> Format: uint32</p> </td> @@ -2249,14 +2282,14 @@ <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv4.routes"></a>routes</code></span></p></td> <td> <p> -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". + 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". </p> <p> -Various attributes are supported: -</p> + Various attributes are supported: + </p> <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="literal">"advmss"</code> - an unsigned 32 bit integer.</p></li> <li class="listitem"><p><code class="literal">"cwnd"</code> - an unsigned 32 bit integer.</p></li> @@ -2269,17 +2302,33 @@ Various attributes are supported: <li class="listitem"><p><code class="literal">"lock-mtu"</code> - a boolean value.</p></li> <li class="listitem"><p><code class="literal">"lock-window"</code> - a boolean value.</p></li> <li class="listitem"><p><code class="literal">"mtu"</code> - an unsigned 32 bit integer.</p></li> -<li class="listitem"><p><code class="literal">"onlink"</code> - a boolean value.</p></li> +<li class="listitem"><p><code class="literal">"onlink"</code> - a boolean value. The onlink flag + is ignored for IPv4 routes without a gateway. That also means, + with a positive "weight" the route cannot merge with ECMP routes + which are onlink and have a gateway. + </p></li> <li class="listitem"><p><code class="literal">"quickack"</code> - a boolean value.</p></li> <li class="listitem"><p><code class="literal">"rto_min"</code> - an unsigned 32 bit integer. -The value is in milliseconds.</p></li> + The value is in milliseconds.</p></li> <li class="listitem"><p><code class="literal">"scope"</code> - an unsigned 8 bit integer. IPv4 only.</p></li> <li class="listitem"><p><code class="literal">"src"</code> - an IPv4 address.</p></li> <li class="listitem"><p><code class="literal">"table"</code> - an unsigned 32 bit integer. The default depends on ipv4.route-table.</p></li> <li class="listitem"><p><code class="literal">"tos"</code> - an unsigned 8 bit integer. IPv4 only.</p></li> <li class="listitem"><p><code class="literal">"type"</code> - one of <code class="literal">unicast</code>, <code class="literal">local</code>, <code class="literal">blackhole</code>, -<code class="literal">unavailable</code>, <code class="literal">prohibit</code>, <code class="literal">throw</code>. -The default is <code class="literal">unicast</code>.</p></li> + <code class="literal">unreachable</code>, <code class="literal">prohibit</code>, <code class="literal">throw</code>. + The default is <code class="literal">unicast</code>.</p></li> +<li class="listitem"> +<p><code class="literal">"weight"</code> - an unsigned 32 bit integer + ranging from 0 to 256. A non-zero weight indicates that the IPv4 + route is an ECMP IPv4 route. NetworkManager will automatically + merge compatible ECMP routes into multi-hop routes. Setting to + zero or omitting the attribute configures single hop routes that + won't get merged. If the route finds no merge partner, it is + configured as single hop route.</p> +<p>Note that in + NetworkManager, currently all nexthops of a ECMP route must share + the same "onlink" flag in order to be mergable.</p> +</li> <li class="listitem"><p><code class="literal">"window"</code> - an unsigned 32 bit integer.</p></li> </ul></div> <p> @@ -2313,7 +2362,7 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.21"></a><h3>ipv6 setting</h3> -<p> IPv6 Settings.</p> +<p>IPv6 Settings.</p> <p> Properties: </p> @@ -2326,12 +2375,12 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.addr-gen-mode"></a>addr-gen-mode</code></span></p></td> <td> -<p> Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3).</p> -<p> If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced.</p> -<p> The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced.</p> -<p> The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively.</p> -<p> For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions.</p> -<p> Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.</p> +<p>Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3).</p> +<p>If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced.</p> +<p>The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced.</p> +<p>The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively.</p> +<p>For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions.</p> +<p>Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.</p> <p> Format: int32</p> </td> @@ -2341,19 +2390,28 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <td> <p> Alias: ip6</p> -<p> Array of IP addresses.</p> +<p>Array of IP addresses.</p> <p> Format: a comma separated list of addresses</p> </td> </tr> <tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.auto-route-ext-gw"></a>auto-route-ext-gw</code></span></p></td> +<td> +<p>VPN connections will default to add the route automatically unless this setting is set to FALSE.</p> +<p>For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.</p> +<p> + Format: NMTernary (int32)</p> +</td> +</tr> +<tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dhcp-duid"></a>dhcp-duid</code></span></p></td> <td> -<p> A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option.</p> -<p> The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id.</p> -<p> The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk.</p> -<p> The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt").</p> -<p> When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.</p> +<p>A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option.</p> +<p>The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id.</p> +<p>The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk.</p> +<p>The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt").</p> +<p>When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.</p> <p> Format: string</p> </td> @@ -2361,7 +2419,7 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dhcp-hostname"></a>dhcp-hostname</code></span></p></td> <td> -<p> If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</p> +<p>If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</p> <p> Format: string</p> </td> @@ -2369,9 +2427,9 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dhcp-hostname-flags"></a>dhcp-hostname-flags</code></span></p></td> <td> -<p> Flags for the DHCP hostname and FQDN.</p> -<p> Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.</p> -<p> When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</p> +<p>Flags for the DHCP hostname and FQDN.</p> +<p>Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.</p> +<p>When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</p> <p> Format: uint32</p> </td> @@ -2379,7 +2437,10 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dhcp-iaid"></a>dhcp-iaid</code></span></p></td> <td> -<p> A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</p> +<p>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname".</p> +<p>For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.</p> +<p>For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address.</p> +<p>The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.</p> <p> Format: string</p> </td> @@ -2387,7 +2448,7 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dhcp-send-hostname"></a>dhcp-send-hostname</code></span></p></td> <td> -<p> If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</p> +<p>If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</p> <p> Format: boolean</p> </td> @@ -2395,8 +2456,8 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dhcp-timeout"></a>dhcp-timeout</code></span></p></td> <td> -<p> A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).</p> -<p> Set to 2147483647 (MAXINT32) for infinity.</p> +<p>A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).</p> +<p>Set to 2147483647 (MAXINT32) for infinity.</p> <p> Format: int32</p> </td> @@ -2404,7 +2465,8 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dns"></a>dns</code></span></p></td> <td> -<p> Array of IP addresses of DNS servers.</p> +<p>Array of IP addresses of DNS servers.</p> +<p>For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved.</p> <p> Format: array of byte array</p> </td> @@ -2412,11 +2474,11 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dns-options"></a>dns-options</code></span></p></td> <td> -<p> Array of DNS options as described in man 5 resolv.conf.</p> -<p> NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.</p> -<p> The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".</p> -<p> The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.</p> -<p> When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</p> +<p>Array of DNS options as described in man 5 resolv.conf.</p> +<p>NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.</p> +<p>The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".</p> +<p>The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.</p> +<p>When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.</p> <p> Format: array of string</p> </td> @@ -2424,14 +2486,14 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dns-priority"></a>dns-priority</code></span></p></td> <td> -<p> DNS servers priority.</p> -<p> The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority).</p> -<p> Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.</p> -<p> Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.</p> -<p> Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile.</p> -<p> When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.</p> -<p> When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.</p> -<p> When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</p> +<p>DNS servers priority.</p> +<p>The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority).</p> +<p>Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.</p> +<p>Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.</p> +<p>Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile.</p> +<p>When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.</p> +<p>When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.</p> +<p>When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.</p> <p> Format: int32</p> </td> @@ -2439,9 +2501,9 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.dns-search"></a>dns-search</code></span></p></td> <td> -<p> List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.</p> -<p> When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.</p> -<p> When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).</p> +<p>List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.</p> +<p>When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.</p> +<p>When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).</p> <p> Format: array of string</p> </td> @@ -2451,9 +2513,9 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <td> <p> Alias: gw6</p> -<p> The gateway associated with this configuration. This is only meaningful if "addresses" is also set.</p> -<p> Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.</p> -<p> Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".</p> +<p>The gateway associated with this configuration. This is only meaningful if "addresses" is also set.</p> +<p>Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.</p> +<p>Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".</p> <p> Format: string</p> </td> @@ -2461,7 +2523,7 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.ignore-auto-dns"></a>ignore-auto-dns</code></span></p></td> <td> -<p> When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</p> +<p>When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</p> <p> Format: boolean</p> </td> @@ -2469,7 +2531,7 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.ignore-auto-routes"></a>ignore-auto-routes</code></span></p></td> <td> -<p> When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</p> +<p>When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</p> <p> Format: boolean</p> </td> @@ -2477,10 +2539,10 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.ip6-privacy"></a>ip6-privacy</code></span></p></td> <td> -<p> Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses).</p> -<p> Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy".</p> -<p> If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr".</p> -<p> Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.</p> +<p>Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses).</p> +<p>Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy".</p> +<p>If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr".</p> +<p>Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.</p> <p> Format: NMSettingIP6ConfigPrivacy (int32)</p> </td> @@ -2488,7 +2550,7 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.may-fail"></a>may-fail</code></span></p></td> <td> -<p> If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</p> +<p>If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</p> <p> Format: boolean</p> </td> @@ -2496,11 +2558,11 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.method"></a>method</code></span></p></td> <td> -<p> IP configuration method.</p> -<p> NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.</p> -<p> In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.</p> -<p> For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.</p> -<p> For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</p> +<p>IP configuration method.</p> +<p>NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.</p> +<p>In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.</p> +<p>For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.</p> +<p>For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</p> <p> Format: string</p> </td> @@ -2508,7 +2570,7 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.mtu"></a>mtu</code></span></p></td> <td> -<p> Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect.</p> +<p>Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect.</p> <p> Format: uint32</p> </td> @@ -2516,7 +2578,7 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.never-default"></a>never-default</code></span></p></td> <td> -<p> If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</p> +<p>If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</p> <p> Format: boolean</p> </td> @@ -2524,19 +2586,27 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.ra-timeout"></a>ra-timeout</code></span></p></td> <td> -<p> A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device.</p> -<p> Set to 2147483647 (MAXINT32) for infinity.</p> +<p>A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device.</p> +<p>Set to 2147483647 (MAXINT32) for infinity.</p> <p> Format: int32</p> </td> </tr> <tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.replace-local-rule"></a>replace-local-rule</code></span></p></td> +<td> +<p>Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.</p> +<p> + Format: NMTernary (int32)</p> +</td> +</tr> +<tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.required-timeout"></a>required-timeout</code></span></p></td> <td> -<p> The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.</p> -<p> 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.</p> -<p> 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.</p> -<p> A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).</p> +<p>The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.</p> +<p>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.</p> +<p>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.</p> +<p>A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).</p> <p> Format: int32</p> </td> @@ -2544,7 +2614,7 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.route-metric"></a>route-metric</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: int64</p> </td> @@ -2552,10 +2622,10 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.route-table"></a>route-table</code></span></p></td> <td> -<p> Enable policy routing (source routing) and set the routing table used when adding routes.</p> -<p> This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.</p> -<p> If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.</p> -<p> Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</p> +<p>Enable policy routing (source routing) and set the routing table used when adding routes.</p> +<p>This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.</p> +<p>If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.</p> +<p>Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</p> <p> Format: uint32</p> </td> @@ -2564,13 +2634,13 @@ Example: <code class="literal">priority 5 from 192.167.4.0/24 table 45</code> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.routes"></a>routes</code></span></p></td> <td> <p> -A list of IPv6 destination addresses, prefix length, optional IPv6 -next hop addresses, optional route metric, optional attribute. The valid syntax is: -"ip[/prefix] [next-hop] [metric] [attribute=val]...[,ip[/prefix]...]". + A list of IPv6 destination addresses, prefix length, optional IPv6 + next hop addresses, optional route metric, optional attribute. The valid syntax is: + "ip[/prefix] [next-hop] [metric] [attribute=val]...[,ip[/prefix]...]". </p> <p> -Various attributes are supported: -</p> + Various attributes are supported: + </p> <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="literal">"advmss"</code> - an unsigned 32 bit integer.</p></li> <li class="listitem"><p><code class="literal">"cwnd"</code> - an unsigned 32 bit integer.</p></li> @@ -2587,12 +2657,12 @@ Various attributes are supported: <li class="listitem"><p><code class="literal">"onlink"</code> - a boolean value.</p></li> <li class="listitem"><p><code class="literal">"quickack"</code> - a boolean value.</p></li> <li class="listitem"><p><code class="literal">"rto_min"</code> - an unsigned 32 bit integer. -The value is in milliseconds.</p></li> + The value is in milliseconds.</p></li> <li class="listitem"><p><code class="literal">"src"</code> - an IPv6 address.</p></li> <li class="listitem"><p><code class="literal">"table"</code> - an unsigned 32 bit integer. The default depends on ipv6.route-table.</p></li> <li class="listitem"><p><code class="literal">"type"</code> - one of <code class="literal">unicast</code>, <code class="literal">local</code>, <code class="literal">blackhole</code>, -<code class="literal">unavailable</code>, <code class="literal">prohibit</code>, <code class="literal">throw</code>. -The default is <code class="literal">unicast</code>.</p></li> + <code class="literal">unreachable</code>, <code class="literal">prohibit</code>, <code class="literal">throw</code>. + The default is <code class="literal">unicast</code>.</p></li> <li class="listitem"><p><code class="literal">"window"</code> - an unsigned 32 bit integer.</p></li> </ul></div> <p> @@ -2623,7 +2693,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ipv6.token"></a>token</code></span></p></td> <td> -<p> Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.</p> +<p>Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.</p> <p> Format: string</p> </td> @@ -2634,7 +2704,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.22"></a><h3>ip-tunnel setting</h3> -<p> IP Tunneling Settings.</p> +<p>IP Tunneling Settings.</p> <p> Properties: </p> @@ -2647,7 +2717,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.encapsulation-limit"></a>encapsulation-limit</code></span></p></td> <td> -<p> How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.</p> +<p>How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.</p> <p> Format: uint32</p> </td> @@ -2655,7 +2725,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.flags"></a>flags</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: uint32</p> </td> @@ -2663,7 +2733,15 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.flow-label"></a>flow-label</code></span></p></td> <td> -<p> The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.</p> +<p>The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.</p> +<p> + Format: uint32</p> +</td> +</tr> +<tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.fwmark"></a>fwmark</code></span></p></td> +<td> +<p>The fwmark value to assign to tunnel packets. This property can be set to a non zero value only on VTI and VTI6 tunnels.</p> <p> Format: uint32</p> </td> @@ -2671,7 +2749,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.input-key"></a>input-key</code></span></p></td> <td> -<p> The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</p> +<p>The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</p> <p> Format: string</p> </td> @@ -2681,7 +2759,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: local</p> -<p> The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.</p> +<p>The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.</p> <p> Format: string</p> </td> @@ -2691,7 +2769,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: mode</p> -<p> The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).</p> +<p>The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).</p> <p> Format: uint32</p> </td> @@ -2699,7 +2777,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.mtu"></a>mtu</code></span></p></td> <td> -<p> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.</p> +<p>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.</p> <p> Format: uint32</p> </td> @@ -2707,7 +2785,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.output-key"></a>output-key</code></span></p></td> <td> -<p> The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</p> +<p>The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</p> <p> Format: string</p> </td> @@ -2717,7 +2795,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: dev</p> -<p> 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.</p> +<p>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.</p> <p> Format: string</p> </td> @@ -2725,7 +2803,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.path-mtu-discovery"></a>path-mtu-discovery</code></span></p></td> <td> -<p> Whether to enable Path MTU Discovery on this tunnel.</p> +<p>Whether to enable Path MTU Discovery on this tunnel.</p> <p> Format: boolean</p> </td> @@ -2735,7 +2813,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: remote</p> -<p> The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.</p> +<p>The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.</p> <p> Format: string</p> </td> @@ -2743,7 +2821,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.tos"></a>tos</code></span></p></td> <td> -<p> The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.</p> +<p>The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.</p> <p> Format: uint32</p> </td> @@ -2751,7 +2829,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ip-tunnel.ttl"></a>ttl</code></span></p></td> <td> -<p> The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.</p> +<p>The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.</p> <p> Format: uint32</p> </td> @@ -2762,7 +2840,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.23"></a><h3>macsec setting</h3> -<p> MACSec Settings.</p> +<p>MACSec Settings.</p> <p> Properties: </p> @@ -2777,7 +2855,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: encrypt</p> -<p> Whether the transmitted traffic must be encrypted.</p> +<p>Whether the transmitted traffic must be encrypted.</p> <p> Format: boolean</p> </td> @@ -2787,7 +2865,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: cak</p> -<p> The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.</p> +<p>The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.</p> <p> Format: string</p> </td> @@ -2795,7 +2873,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.macsec.mka-cak-flags"></a>mka-cak-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "mka-cak" property.</p> +<p>Flags indicating how to handle the "mka-cak" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -2805,7 +2883,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: ckn</p> -<p> 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.</p> +<p>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.</p> <p> Format: string</p> </td> @@ -2815,7 +2893,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: mode</p> -<p> Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.</p> +<p>Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.</p> <p> Format: int32</p> </td> @@ -2825,7 +2903,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: dev</p> -<p> 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.</p> +<p>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.</p> <p> Format: string</p> </td> @@ -2835,7 +2913,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: port</p> -<p> The port component of the SCI (Secure Channel Identifier), between 1 and 65534.</p> +<p>The port component of the SCI (Secure Channel Identifier), between 1 and 65534.</p> <p> Format: int32</p> </td> @@ -2843,7 +2921,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.macsec.send-sci"></a>send-sci</code></span></p></td> <td> -<p> Specifies whether the SCI (Secure Channel Identifier) is included in every packet.</p> +<p>Specifies whether the SCI (Secure Channel Identifier) is included in every packet.</p> <p> Format: boolean</p> </td> @@ -2851,7 +2929,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.macsec.validation"></a>validation</code></span></p></td> <td> -<p> Specifies the validation mode for incoming frames.</p> +<p>Specifies the validation mode for incoming frames.</p> <p> Format: int32</p> </td> @@ -2862,7 +2940,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.24"></a><h3>macvlan setting</h3> -<p> MAC VLAN Settings.</p> +<p>MAC VLAN Settings.</p> <p> Properties: </p> @@ -2877,7 +2955,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: mode</p> -<p> The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.</p> +<p>The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.</p> <p> Format: uint32</p> </td> @@ -2887,7 +2965,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: dev</p> -<p> 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.</p> +<p>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.</p> <p> Format: string</p> </td> @@ -2895,7 +2973,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.macvlan.promiscuous"></a>promiscuous</code></span></p></td> <td> -<p> Whether the interface should be put in promiscuous mode.</p> +<p>Whether the interface should be put in promiscuous mode.</p> <p> Format: boolean</p> </td> @@ -2905,7 +2983,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: tap</p> -<p> Whether the interface should be a MACVTAP.</p> +<p>Whether the interface should be a MACVTAP.</p> <p> Format: boolean</p> </td> @@ -2916,7 +2994,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.25"></a><h3>match setting</h3> -<p> Match settings.</p> +<p>Match settings.</p> <p> Properties: </p> @@ -2929,8 +3007,8 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.match.driver"></a>driver</code></span></p></td> <td> -<p> A list of driver names to match. Each element is a shell wildcard pattern.</p> -<p> See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.</p> +<p>A list of driver names to match. Each element is a shell wildcard pattern.</p> +<p>See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.</p> <p> Format: array of string</p> </td> @@ -2938,8 +3016,8 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.match.interface-name"></a>interface-name</code></span></p></td> <td> -<p> A list of interface names to match. Each element is a shell wildcard pattern.</p> -<p> 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".</p> +<p>A list of interface names to match. Each element is a shell wildcard pattern.</p> +<p>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".</p> <p> Format: array of string</p> </td> @@ -2947,8 +3025,8 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.match.kernel-command-line"></a>kernel-command-line</code></span></p></td> <td> -<p> 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.</p> -<p> See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the match.</p> +<p>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.</p> +<p>See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the match.</p> <p> Format: array of string</p> </td> @@ -2956,11 +3034,11 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.match.path"></a>path</code></span></p></td> <td> -<p> 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.</p> -<p> 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".</p> -<p> 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").</p> -<p> Each element of the list is a shell wildcard pattern.</p> -<p> See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.</p> +<p>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.</p> +<p>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".</p> +<p>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").</p> +<p>Each element of the list is a shell wildcard pattern.</p> +<p>See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.</p> <p> Format: array of string</p> </td> @@ -2973,7 +3051,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <a name="id-1.2.10.4.26"></a><h3>802-11-olpc-mesh setting</h3> <p> Alias: olpc-mesh</p> -<p> OLPC Wireless Mesh Settings.</p> +<p>OLPC Wireless Mesh Settings.</p> <p> Properties: </p> @@ -2988,7 +3066,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: channel</p> -<p> Channel on which the mesh network to join is located.</p> +<p>Channel on which the mesh network to join is located.</p> <p> Format: uint32</p> </td> @@ -2998,8 +3076,8 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: dhcp-anycast</p> -<p> 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.</p> -<p> This is currently only implemented by dhclient DHCP plugin.</p> +<p>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.</p> +<p>This is currently only implemented by dhclient DHCP plugin.</p> <p> Format: byte array</p> </td> @@ -3009,7 +3087,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: ssid</p> -<p> SSID of the mesh network to join.</p> +<p>SSID of the mesh network to join.</p> <p> Format: byte array</p> </td> @@ -3020,7 +3098,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.27"></a><h3>ovs-bridge setting</h3> -<p> OvsBridge Link Settings.</p> +<p>OvsBridge Link Settings.</p> <p> Properties: </p> @@ -3033,7 +3111,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-bridge.datapath-type"></a>datapath-type</code></span></p></td> <td> -<p> The data path type. One of "system", "netdev" or empty.</p> +<p>The data path type. One of "system", "netdev" or empty.</p> <p> Format: string</p> </td> @@ -3041,7 +3119,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-bridge.fail-mode"></a>fail-mode</code></span></p></td> <td> -<p> The bridge failure mode. One of "secure", "standalone" or empty.</p> +<p>The bridge failure mode. One of "secure", "standalone" or empty.</p> <p> Format: string</p> </td> @@ -3049,7 +3127,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-bridge.mcast-snooping-enable"></a>mcast-snooping-enable</code></span></p></td> <td> -<p> Enable or disable multicast snooping.</p> +<p>Enable or disable multicast snooping.</p> <p> Format: boolean</p> </td> @@ -3057,7 +3135,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-bridge.rstp-enable"></a>rstp-enable</code></span></p></td> <td> -<p> Enable or disable RSTP.</p> +<p>Enable or disable RSTP.</p> <p> Format: boolean</p> </td> @@ -3065,7 +3143,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-bridge.stp-enable"></a>stp-enable</code></span></p></td> <td> -<p> Enable or disable STP.</p> +<p>Enable or disable STP.</p> <p> Format: boolean</p> </td> @@ -3076,7 +3154,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.28"></a><h3>ovs-dpdk setting</h3> -<p> OvsDpdk Link Settings.</p> +<p>OvsDpdk Link Settings.</p> <p> Properties: </p> @@ -3089,7 +3167,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-dpdk.devargs"></a>devargs</code></span></p></td> <td> -<p> Open vSwitch DPDK device arguments.</p> +<p>Open vSwitch DPDK device arguments.</p> <p> Format: string</p> </td> @@ -3097,7 +3175,23 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-dpdk.n-rxq"></a>n-rxq</code></span></p></td> <td> -<p> Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.</p> +<p>Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.</p> +<p> + Format: uint32</p> +</td> +</tr> +<tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-dpdk.n-rxq-desc"></a>n-rxq-desc</code></span></p></td> +<td> +<p>The rx queue size (number of rx descriptors) for DPDK ports. Must be zero or a power of 2 between 1 and 4096, and supported by the hardware. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures 2048 descriptors.</p> +<p> + Format: uint32</p> +</td> +</tr> +<tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-dpdk.n-txq-desc"></a>n-txq-desc</code></span></p></td> +<td> +<p>The tx queue size (number of tx descriptors) for DPDK ports. Must be zero or a power of 2 between 1 and 4096, and supported by the hardware. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures 2048 descriptors.</p> <p> Format: uint32</p> </td> @@ -3108,7 +3202,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.29"></a><h3>ovs-interface setting</h3> -<p> Open vSwitch Interface Settings.</p> +<p>Open vSwitch Interface Settings.</p> <p> Properties: </p> @@ -3117,20 +3211,30 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <col align="left" valign="top"> <col> </colgroup> -<tbody><tr> +<tbody> +<tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-interface.ofport-request"></a>ofport-request</code></span></p></td> +<td> +<p>Open vSwitch openflow port number. Defaults to zero which means that port number will not be specified and it will be chosen randomly by ovs. OpenFlow ports are the network interfaces for passing packets between OpenFlow processing and the rest of the network. OpenFlow switches connect logically to each other via their OpenFlow ports.</p> +<p> + Format: uint32</p> +</td> +</tr> +<tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-interface.type"></a>type</code></span></p></td> <td> -<p> The interface type. Either "internal", "system", "patch", "dpdk", or empty.</p> +<p>The interface type. Either "internal", "system", "patch", "dpdk", or empty.</p> <p> Format: string</p> </td> -</tr></tbody> +</tr> +</tbody> </table></div> </div> <hr> <div class="refsect2"> <a name="id-1.2.10.4.30"></a><h3>ovs-patch setting</h3> -<p> OvsPatch Link Settings.</p> +<p>OvsPatch Link Settings.</p> <p> Properties: </p> @@ -3142,7 +3246,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tbody><tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-patch.peer"></a>peer</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: string</p> </td> @@ -3152,7 +3256,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.31"></a><h3>ovs-port setting</h3> -<p> OvsPort Link Settings.</p> +<p>OvsPort Link Settings.</p> <p> Properties: </p> @@ -3165,7 +3269,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-port.bond-downdelay"></a>bond-downdelay</code></span></p></td> <td> -<p> The time port must be inactive in order to be considered down.</p> +<p>The time port must be inactive in order to be considered down.</p> <p> Format: uint32</p> </td> @@ -3173,7 +3277,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-port.bond-mode"></a>bond-mode</code></span></p></td> <td> -<p> Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".</p> +<p>Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".</p> <p> Format: string</p> </td> @@ -3181,7 +3285,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-port.bond-updelay"></a>bond-updelay</code></span></p></td> <td> -<p> The time port must be active before it starts forwarding traffic.</p> +<p>The time port must be active before it starts forwarding traffic.</p> <p> Format: uint32</p> </td> @@ -3189,7 +3293,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-port.lacp"></a>lacp</code></span></p></td> <td> -<p> LACP mode. One of "active", "off", or "passive".</p> +<p>LACP mode. One of "active", "off", or "passive".</p> <p> Format: string</p> </td> @@ -3197,15 +3301,24 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-port.tag"></a>tag</code></span></p></td> <td> -<p> The VLAN tag in the range 0-4095.</p> +<p>The VLAN tag in the range 0-4095.</p> <p> Format: uint32</p> </td> </tr> <tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-port.trunks"></a>trunks</code></span></p></td> +<td> +<p>A list of VLAN ranges that this port trunks.</p> +<p>The property is valid only for ports with mode "trunk", "native-tagged", or "native-untagged port". If it is empty, the port trunks all VLANs.</p> +<p> + Format: array of vardict</p> +</td> +</tr> +<tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ovs-port.vlan-mode"></a>vlan-mode</code></span></p></td> <td> -<p> The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk" or unset.</p> +<p>The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk", "dot1q-tunnel" or unset.</p> <p> Format: string</p> </td> @@ -3216,7 +3329,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.32"></a><h3>ppp setting</h3> -<p> Point-to-Point Protocol Settings.</p> +<p>Point-to-Point Protocol Settings.</p> <p> Properties: </p> @@ -3229,7 +3342,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.baud"></a>baud</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: uint32</p> </td> @@ -3237,7 +3350,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.crtscts"></a>crtscts</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: boolean</p> </td> @@ -3245,7 +3358,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.lcp-echo-failure"></a>lcp-echo-failure</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: uint32</p> </td> @@ -3253,7 +3366,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.lcp-echo-interval"></a>lcp-echo-interval</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: uint32</p> </td> @@ -3261,7 +3374,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.mppe-stateful"></a>mppe-stateful</code></span></p></td> <td> -<p> If TRUE, stateful MPPE is used. See pppd documentation for more information on stateful MPPE.</p> +<p>If TRUE, stateful MPPE is used. See pppd documentation for more information on stateful MPPE.</p> <p> Format: boolean</p> </td> @@ -3269,7 +3382,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.mru"></a>mru</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: uint32</p> </td> @@ -3277,7 +3390,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.mtu"></a>mtu</code></span></p></td> <td> -<p> If non-zero, instruct pppd to send packets no larger than the specified size.</p> +<p>If non-zero, instruct pppd to send packets no larger than the specified size.</p> <p> Format: uint32</p> </td> @@ -3285,7 +3398,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.no-vj-comp"></a>no-vj-comp</code></span></p></td> <td> -<p> If TRUE, Van Jacobsen TCP header compression will not be requested.</p> +<p>If TRUE, Van Jacobsen TCP header compression will not be requested.</p> <p> Format: boolean</p> </td> @@ -3293,7 +3406,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.noauth"></a>noauth</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: boolean</p> </td> @@ -3301,7 +3414,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.nobsdcomp"></a>nobsdcomp</code></span></p></td> <td> -<p> If TRUE, BSD compression will not be requested.</p> +<p>If TRUE, BSD compression will not be requested.</p> <p> Format: boolean</p> </td> @@ -3309,7 +3422,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.nodeflate"></a>nodeflate</code></span></p></td> <td> -<p> If TRUE, "deflate" compression will not be requested.</p> +<p>If TRUE, "deflate" compression will not be requested.</p> <p> Format: boolean</p> </td> @@ -3317,7 +3430,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.refuse-chap"></a>refuse-chap</code></span></p></td> <td> -<p> If TRUE, the CHAP authentication method will not be used.</p> +<p>If TRUE, the CHAP authentication method will not be used.</p> <p> Format: boolean</p> </td> @@ -3325,7 +3438,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.refuse-eap"></a>refuse-eap</code></span></p></td> <td> -<p> If TRUE, the EAP authentication method will not be used.</p> +<p>If TRUE, the EAP authentication method will not be used.</p> <p> Format: boolean</p> </td> @@ -3333,7 +3446,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.refuse-mschap"></a>refuse-mschap</code></span></p></td> <td> -<p> If TRUE, the MSCHAP authentication method will not be used.</p> +<p>If TRUE, the MSCHAP authentication method will not be used.</p> <p> Format: boolean</p> </td> @@ -3341,7 +3454,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.refuse-mschapv2"></a>refuse-mschapv2</code></span></p></td> <td> -<p> If TRUE, the MSCHAPv2 authentication method will not be used.</p> +<p>If TRUE, the MSCHAPv2 authentication method will not be used.</p> <p> Format: boolean</p> </td> @@ -3349,7 +3462,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.refuse-pap"></a>refuse-pap</code></span></p></td> <td> -<p> If TRUE, the PAP authentication method will not be used.</p> +<p>If TRUE, the PAP authentication method will not be used.</p> <p> Format: boolean</p> </td> @@ -3357,7 +3470,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.require-mppe"></a>require-mppe</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: boolean</p> </td> @@ -3365,7 +3478,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.ppp.require-mppe-128"></a>require-mppe-128</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: boolean</p> </td> @@ -3376,7 +3489,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.33"></a><h3>pppoe setting</h3> -<p> PPP-over-Ethernet Settings.</p> +<p>PPP-over-Ethernet Settings.</p> <p> Properties: </p> @@ -3391,7 +3504,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: parent</p> -<p> 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.</p> +<p>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.</p> <p> Format: string</p> </td> @@ -3401,7 +3514,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: password</p> -<p> Password used to authenticate with the PPPoE service.</p> +<p>Password used to authenticate with the PPPoE service.</p> <p> Format: string</p> </td> @@ -3409,7 +3522,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.pppoe.password-flags"></a>password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "password" property.</p> +<p>Flags indicating how to handle the "password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -3419,7 +3532,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: service</p> -<p> 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.</p> +<p>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.</p> <p> Format: string</p> </td> @@ -3429,7 +3542,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: username</p> -<p> Username used to authenticate with the PPPoE service.</p> +<p>Username used to authenticate with the PPPoE service.</p> <p> Format: string</p> </td> @@ -3440,7 +3553,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.34"></a><h3>proxy setting</h3> -<p> WWW Proxy Settings.</p> +<p>WWW Proxy Settings.</p> <p> Properties: </p> @@ -3455,7 +3568,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: browser-only</p> -<p> Whether the proxy configuration is for browser only.</p> +<p>Whether the proxy configuration is for browser only.</p> <p> Format: boolean</p> </td> @@ -3465,7 +3578,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: method</p> -<p> Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)</p> +<p>Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)</p> <p> Format: int32</p> </td> @@ -3475,7 +3588,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: pac-script</p> -<p> PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.</p> +<p>PAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.</p> <p> Format: string</p> </td> @@ -3485,7 +3598,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <td> <p> Alias: pac-url</p> -<p> PAC URL for obtaining PAC file.</p> +<p>PAC URL for obtaining PAC file.</p> <p> Format: string</p> </td> @@ -3496,7 +3609,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.35"></a><h3>serial setting</h3> -<p> Serial Link Settings.</p> +<p>Serial Link Settings.</p> <p> Properties: </p> @@ -3509,7 +3622,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.serial.baud"></a>baud</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: uint32</p> </td> @@ -3517,7 +3630,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.serial.bits"></a>bits</code></span></p></td> <td> -<p> Byte-width of the serial communication. The 8 in "8n1" for example.</p> +<p>Byte-width of the serial communication. The 8 in "8n1" for example.</p> <p> Format: uint32</p> </td> @@ -3525,7 +3638,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.serial.parity"></a>parity</code></span></p></td> <td> -<p> Parity setting of the serial port.</p> +<p>Parity setting of the serial port.</p> <p> Format: NMSettingSerialParity (byte)</p> </td> @@ -3533,7 +3646,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.serial.send-delay"></a>send-delay</code></span></p></td> <td> -<p> Time to delay between each byte sent to the modem, in microseconds.</p> +<p>Time to delay between each byte sent to the modem, in microseconds.</p> <p> Format: uint64</p> </td> @@ -3541,7 +3654,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.serial.stopbits"></a>stopbits</code></span></p></td> <td> -<p> Number of stop bits for communication on the serial port. Either 1 or 2. The 1 in "8n1" for example.</p> +<p>Number of stop bits for communication on the serial port. Either 1 or 2. The 1 in "8n1" for example.</p> <p> Format: uint32</p> </td> @@ -3552,7 +3665,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.36"></a><h3>sriov setting</h3> -<p> SR-IOV settings.</p> +<p>SR-IOV settings.</p> <p> Properties: </p> @@ -3565,10 +3678,10 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.sriov.autoprobe-drivers"></a>autoprobe-drivers</code></span></p></td> <td> -<p> Whether to autoprobe virtual functions by a compatible driver.</p> -<p> 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.</p> -<p> If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them.</p> -<p> 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).</p> +<p>Whether to autoprobe virtual functions by a compatible driver.</p> +<p>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.</p> +<p>If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them.</p> +<p>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).</p> <p> Format: NMTernary (int32)</p> </td> @@ -3576,8 +3689,8 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.sriov.total-vfs"></a>total-vfs</code></span></p></td> <td> -<p> The total number of virtual functions to create.</p> -<p> 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.</p> +<p>The total number of virtual functions to create.</p> +<p>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.</p> <p> Format: uint32</p> </td> @@ -3585,16 +3698,16 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.sriov.vfs"></a>vfs</code></span></p></td> <td> -<p> Array of virtual function descriptors.</p> -<p> Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF.</p> -<p> When represented as string a VF is in the form:</p> -<p> "INDEX [ATTR=VALUE[ ATTR=VALUE]...]".</p> -<p> for example:</p> -<p> "2 mac=00:11:22:33:44:55 spoof-check=true".</p> -<p> 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.</p> -<p> The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form</p> -<p> "ID[.PRIORITY[.PROTO]]".</p> -<p> PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.</p> +<p>Array of virtual function descriptors.</p> +<p>Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF.</p> +<p>When represented as string a VF is in the form:</p> +<p>"INDEX [ATTR=VALUE[ ATTR=VALUE]...]".</p> +<p>for example:</p> +<p>"2 mac=00:11:22:33:44:55 spoof-check=true".</p> +<p>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.</p> +<p>The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form</p> +<p>"ID[.PRIORITY[.PROTO]]".</p> +<p>PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.</p> <p> Format: array of vardict</p> </td> @@ -3605,7 +3718,7 @@ Example: <code class="literal">priority 5 from 1:2:3::5/128 table 45</code> <hr> <div class="refsect2"> <a name="id-1.2.10.4.37"></a><h3>tc setting</h3> -<p> Linux Traffic Control Settings.</p> +<p>Linux Traffic Control Settings.</p> <p> Properties: </p> @@ -3623,7 +3736,7 @@ Array of TC queueing disciplines. qdisc is a basic block in the Linux traffic control subsystem </p> <p> -Each qdisc can be specified by the following attributes: + Each qdisc can be specified by the following attributes: </p> <div class="variablelist"><table border="0" class="variablelist"> <colgroup> @@ -3634,39 +3747,39 @@ Each qdisc can be specified by the following attributes: <tr> <td><p><span class="term"><code class="varname">handle HANDLE</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">parent HANDLE</code></span></p></td> <td><p> -specifies the handle of the parent qdisc the current qdisc must be -attached to. -</p></td> + specifies the handle of the parent qdisc the current qdisc must be + attached to. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">root</code></span></p></td> <td><p> -specifies that the qdisc is attached to the root of device. -</p></td> + specifies that the qdisc is attached to the root of device. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">KIND</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> </tbody> </table></div> <p> -Parameters for 'fq_codel': + Parameters for 'fq_codel': </p> <div class="variablelist"><table border="0" class="variablelist"> <colgroup> @@ -3677,76 +3790,76 @@ Parameters for 'fq_codel': <tr> <td><p><span class="term"><code class="varname">limit U32</code></span></p></td> <td><p> -the hard limit on the real queue size. When this limit is -reached, incoming packets are dropped. Default is 10240 packets. -</p></td> + the hard limit on the real queue size. When this limit is + reached, incoming packets are dropped. Default is 10240 packets. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">memory_limit U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">flows U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">target U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">interval U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">quantum U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">ecn BOOL</code></span></p></td> <td><p> -can be used to mark packets instead of dropping them. ecn is turned -on by default. -</p></td> + can be used to mark packets instead of dropping them. ecn is turned + on by default. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">ce_threshold U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> </tbody> </table></div> <p> -Parameters for 'sfq': + Parameters for 'sfq': </p> <div class="variablelist"><table border="0" class="variablelist"> <colgroup> @@ -3757,57 +3870,57 @@ Parameters for 'sfq': <tr> <td><p><span class="term"><code class="varname">divisor U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">limit U32</code></span></p></td> <td><p> -Upper limit of the SFQ. Can be used to reduce the default -length of 127 packets. -</p></td> + Upper limit of the SFQ. Can be used to reduce the default + length of 127 packets. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">depth U32</code></span></p></td> <td><p> -Limit of packets per flow. Default to -127 and can be lowered. -</p></td> + Limit of packets per flow. Default to + 127 and can be lowered. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">perturb_period U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">quantum U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">flows U32</code></span></p></td> <td><p> -Default value is 127. -</p></td> + Default value is 127. + </p></td> </tr> </tbody> </table></div> <p> -Parameters for 'tbf': + Parameters for 'tbf': </p> <div class="variablelist"><table border="0" class="variablelist"> <colgroup> @@ -3818,55 +3931,55 @@ Parameters for 'tbf': <tr> <td><p><span class="term"><code class="varname">rate U64</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">burst U32</code></span></p></td> <td> <p> -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! -</p> + 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! + </p> <p> -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. -</p> + 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. + </p> <p> -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. -</p> + 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. + </p> </td> </tr> <tr> <td><p><span class="term"><code class="varname">limit U32</code></span></p></td> <td><p> -Limit is the number of bytes that can be queued waiting -for tokens to become available. -</p></td> + Limit is the number of bytes that can be queued waiting + for tokens to become available. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">latency U32</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> </tbody> </table></div> @@ -3878,11 +3991,11 @@ the size of the bucket, the rate and possibly the peakrate <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.tc.tfilters"></a>tfilters</code></span></p></td> <td> <p> -Array of TC traffic filters. Traffic control can manage the packet content during -classification by using filters. + Array of TC traffic filters. Traffic control can manage the packet content during + classification by using filters. </p> <p> -Each tfilters can be specified by the following attributes: + Each tfilters can be specified by the following attributes: </p> <div class="variablelist"><table border="0" class="variablelist"> <colgroup> @@ -3893,37 +4006,37 @@ Each tfilters can be specified by the following attributes: <tr> <td><p><span class="term"><code class="varname">handle HANDLE</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">parent HANDLE</code></span></p></td> <td><p> -specifies the handle of the parent qdisc the current qdisc must be -attached to. -</p></td> + specifies the handle of the parent qdisc the current qdisc must be + attached to. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">root</code></span></p></td> <td><p> -specifies that the qdisc is attached to the root of device. -</p></td> + specifies that the qdisc is attached to the root of device. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">KIND</code></span></p></td> <td><p> -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. -</p></td> + 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. + </p></td> </tr> </tbody> </table></div> <p> -Actions for 'mirred': + Actions for 'mirred': </p> <div class="variablelist"><table border="0" class="variablelist"> <colgroup> @@ -3934,31 +4047,31 @@ Actions for 'mirred': <tr> <td><p><span class="term"><code class="varname">egress bool</code></span></p></td> <td><p> -Define whether the packet should exit from the interface. -</p></td> + Define whether the packet should exit from the interface. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">ingress bool</code></span></p></td> <td><p> -Define whether the packet should come into the interface. -</p></td> + Define whether the packet should come into the interface. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">mirror bool</code></span></p></td> <td><p> -Define whether the packet should be copied to the destination space. -</p></td> + Define whether the packet should be copied to the destination space. + </p></td> </tr> <tr> <td><p><span class="term"><code class="varname">redirect bool</code></span></p></td> <td><p> -Define whether the packet should be moved to the destination space. -</p></td> + Define whether the packet should be moved to the destination space. + </p></td> </tr> </tbody> </table></div> <p> -Action for 'simple': + Action for 'simple': </p> <div class="variablelist"><table border="0" class="variablelist"> <colgroup> @@ -3968,8 +4081,8 @@ Action for 'simple': <tbody><tr> <td><p><span class="term"><code class="varname">sdata char[32]</code></span></p></td> <td><p> -The actual string to print. -</p></td> + The actual string to print. + </p></td> </tr></tbody> </table></div> <p> @@ -3982,7 +4095,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.38"></a><h3>team setting</h3> -<p> Teaming Settings.</p> +<p>Teaming Settings.</p> <p> Properties: </p> @@ -3997,7 +4110,7 @@ The actual string to print. <td> <p> Alias: config</p> -<p> The JSON configuration for the team network interface. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</p> +<p>The JSON configuration for the team network interface. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</p> <p> Format: string</p> </td> @@ -4005,7 +4118,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.link-watchers"></a>link-watchers</code></span></p></td> <td> -<p> Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</p> +<p>Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</p> <p> Format: array of vardict</p> </td> @@ -4013,7 +4126,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.mcast-rejoin-count"></a>mcast-rejoin-count</code></span></p></td> <td> -<p> Corresponds to the teamd mcast_rejoin.count.</p> +<p>Corresponds to the teamd mcast_rejoin.count.</p> <p> Format: int32</p> </td> @@ -4021,7 +4134,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.mcast-rejoin-interval"></a>mcast-rejoin-interval</code></span></p></td> <td> -<p> Corresponds to the teamd mcast_rejoin.interval.</p> +<p>Corresponds to the teamd mcast_rejoin.interval.</p> <p> Format: int32</p> </td> @@ -4029,7 +4142,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.notify-peers-count"></a>notify-peers-count</code></span></p></td> <td> -<p> Corresponds to the teamd notify_peers.count.</p> +<p>Corresponds to the teamd notify_peers.count.</p> <p> Format: int32</p> </td> @@ -4037,7 +4150,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.notify-peers-interval"></a>notify-peers-interval</code></span></p></td> <td> -<p> Corresponds to the teamd notify_peers.interval.</p> +<p>Corresponds to the teamd notify_peers.interval.</p> <p> Format: int32</p> </td> @@ -4045,7 +4158,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner"></a>runner</code></span></p></td> <td> -<p> Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".</p> +<p>Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".</p> <p> Format: string</p> </td> @@ -4053,7 +4166,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner-active"></a>runner-active</code></span></p></td> <td> -<p> Corresponds to the teamd runner.active.</p> +<p>Corresponds to the teamd runner.active.</p> <p> Format: boolean</p> </td> @@ -4061,7 +4174,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner-agg-select-policy"></a>runner-agg-select-policy</code></span></p></td> <td> -<p> Corresponds to the teamd runner.agg_select_policy.</p> +<p>Corresponds to the teamd runner.agg_select_policy.</p> <p> Format: string</p> </td> @@ -4069,7 +4182,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner-fast-rate"></a>runner-fast-rate</code></span></p></td> <td> -<p> Corresponds to the teamd runner.fast_rate.</p> +<p>Corresponds to the teamd runner.fast_rate.</p> <p> Format: boolean</p> </td> @@ -4077,7 +4190,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner-hwaddr-policy"></a>runner-hwaddr-policy</code></span></p></td> <td> -<p> Corresponds to the teamd runner.hwaddr_policy.</p> +<p>Corresponds to the teamd runner.hwaddr_policy.</p> <p> Format: string</p> </td> @@ -4085,7 +4198,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner-min-ports"></a>runner-min-ports</code></span></p></td> <td> -<p> Corresponds to the teamd runner.min_ports.</p> +<p>Corresponds to the teamd runner.min_ports.</p> <p> Format: int32</p> </td> @@ -4093,7 +4206,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner-sys-prio"></a>runner-sys-prio</code></span></p></td> <td> -<p> Corresponds to the teamd runner.sys_prio.</p> +<p>Corresponds to the teamd runner.sys_prio.</p> <p> Format: int32</p> </td> @@ -4101,7 +4214,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner-tx-balancer"></a>runner-tx-balancer</code></span></p></td> <td> -<p> Corresponds to the teamd runner.tx_balancer.name.</p> +<p>Corresponds to the teamd runner.tx_balancer.name.</p> <p> Format: string</p> </td> @@ -4109,7 +4222,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner-tx-balancer-interval"></a>runner-tx-balancer-interval</code></span></p></td> <td> -<p> Corresponds to the teamd runner.tx_balancer.interval.</p> +<p>Corresponds to the teamd runner.tx_balancer.interval.</p> <p> Format: int32</p> </td> @@ -4117,7 +4230,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team.runner-tx-hash"></a>runner-tx-hash</code></span></p></td> <td> -<p> Corresponds to the teamd runner.tx_hash.</p> +<p>Corresponds to the teamd runner.tx_hash.</p> <p> Format: array of string</p> </td> @@ -4128,7 +4241,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.39"></a><h3>team-port setting</h3> -<p> Team Port Settings.</p> +<p>Team Port Settings.</p> <p> Properties: </p> @@ -4143,7 +4256,7 @@ The actual string to print. <td> <p> Alias: config</p> -<p> The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</p> +<p>The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</p> <p> Format: string</p> </td> @@ -4151,7 +4264,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team-port.lacp-key"></a>lacp-key</code></span></p></td> <td> -<p> Corresponds to the teamd ports.PORTIFNAME.lacp_key.</p> +<p>Corresponds to the teamd ports.PORTIFNAME.lacp_key.</p> <p> Format: int32</p> </td> @@ -4159,7 +4272,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team-port.lacp-prio"></a>lacp-prio</code></span></p></td> <td> -<p> Corresponds to the teamd ports.PORTIFNAME.lacp_prio.</p> +<p>Corresponds to the teamd ports.PORTIFNAME.lacp_prio.</p> <p> Format: int32</p> </td> @@ -4167,7 +4280,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team-port.link-watchers"></a>link-watchers</code></span></p></td> <td> -<p> Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</p> +<p>Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are: ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</p> <p> Format: array of vardict</p> </td> @@ -4175,7 +4288,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team-port.prio"></a>prio</code></span></p></td> <td> -<p> Corresponds to the teamd ports.PORTIFNAME.prio.</p> +<p>Corresponds to the teamd ports.PORTIFNAME.prio.</p> <p> Format: int32</p> </td> @@ -4183,7 +4296,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team-port.queue-id"></a>queue-id</code></span></p></td> <td> -<p> Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.</p> +<p>Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.</p> <p> Format: int32</p> </td> @@ -4191,7 +4304,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.team-port.sticky"></a>sticky</code></span></p></td> <td> -<p> Corresponds to the teamd ports.PORTIFNAME.sticky.</p> +<p>Corresponds to the teamd ports.PORTIFNAME.sticky.</p> <p> Format: boolean</p> </td> @@ -4202,7 +4315,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.40"></a><h3>tun setting</h3> -<p> Tunnel Settings.</p> +<p>Tunnel Settings.</p> <p> Properties: </p> @@ -4217,7 +4330,7 @@ The actual string to print. <td> <p> Alias: group</p> -<p> The group ID which will own the device. If set to NULL everyone will be able to use the device.</p> +<p>The group ID which will own the device. If set to NULL everyone will be able to use the device.</p> <p> Format: string</p> </td> @@ -4227,7 +4340,7 @@ The actual string to print. <td> <p> Alias: mode</p> -<p> The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one.</p> +<p>The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one.</p> <p> Format: uint32</p> </td> @@ -4237,7 +4350,7 @@ The actual string to print. <td> <p> Alias: multi-queue</p> -<p> If the property is set to TRUE, the interface will support multiple file descriptors (queues) to parallelize packet sending or receiving. Otherwise, the interface will only support a single queue.</p> +<p>If the property is set to TRUE, the interface will support multiple file descriptors (queues) to parallelize packet sending or receiving. Otherwise, the interface will only support a single queue.</p> <p> Format: boolean</p> </td> @@ -4247,7 +4360,7 @@ The actual string to print. <td> <p> Alias: owner</p> -<p> The user ID which will own the device. If set to NULL everyone will be able to use the device.</p> +<p>The user ID which will own the device. If set to NULL everyone will be able to use the device.</p> <p> Format: string</p> </td> @@ -4257,7 +4370,7 @@ The actual string to print. <td> <p> Alias: pi</p> -<p> If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.</p> +<p>If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.</p> <p> Format: boolean</p> </td> @@ -4267,7 +4380,7 @@ The actual string to print. <td> <p> Alias: vnet-hdr</p> -<p> If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.</p> +<p>If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.</p> <p> Format: boolean</p> </td> @@ -4278,7 +4391,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.41"></a><h3>vlan setting</h3> -<p> VLAN Settings.</p> +<p>VLAN Settings.</p> <p> Properties: </p> @@ -4293,7 +4406,7 @@ The actual string to print. <td> <p> Alias: egress</p> -<p> For outgoing packets, a list of mappings from Linux SKB priorities to 802.1p priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</p> +<p>For outgoing packets, a list of mappings from Linux SKB priorities to 802.1p priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</p> <p> Format: array of string</p> </td> @@ -4303,8 +4416,8 @@ The actual string to print. <td> <p> Alias: flags</p> -<p> One or more flags which control the behavior and features of the VLAN interface. Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol).</p> -<p> The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.</p> +<p>One or more flags which control the behavior and features of the VLAN interface. Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol).</p> +<p>The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.</p> <p> Format: NMVlanFlags (uint32)</p> </td> @@ -4314,7 +4427,7 @@ The actual string to print. <td> <p> Alias: id</p> -<p> The VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.</p> +<p>The VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.</p> <p> Format: uint32</p> </td> @@ -4324,7 +4437,7 @@ The actual string to print. <td> <p> Alias: ingress</p> -<p> For incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</p> +<p>For incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities. The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</p> <p> Format: array of string</p> </td> @@ -4334,7 +4447,16 @@ The actual string to print. <td> <p> Alias: dev</p> -<p> If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</p> +<p>If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created. If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</p> +<p> + Format: string</p> +</td> +</tr> +<tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vlan.protocol"></a>protocol</code></span></p></td> +<td> +<p>Specifies the VLAN protocol to use for encapsulation.</p> +<p>Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.</p> <p> Format: string</p> </td> @@ -4345,7 +4467,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.42"></a><h3>vpn setting</h3> -<p> VPN Settings.</p> +<p>VPN Settings.</p> <p> Properties: </p> @@ -4358,7 +4480,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vpn.data"></a>data</code></span></p></td> <td> -<p> Dictionary of key/value pairs of VPN plugin specific data. Both keys and values must be strings.</p> +<p>Dictionary of key/value pairs of VPN plugin specific data. Both keys and values must be strings.</p> <p> Format: dict of string to string</p> </td> @@ -4366,7 +4488,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vpn.persistent"></a>persistent</code></span></p></td> <td> -<p> If the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.</p> +<p>If the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.</p> <p> Format: boolean</p> </td> @@ -4374,7 +4496,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vpn.secrets"></a>secrets</code></span></p></td> <td> -<p> Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys. Both keys and values must be strings.</p> +<p>Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys. Both keys and values must be strings.</p> <p> Format: dict of string to string</p> </td> @@ -4384,7 +4506,7 @@ The actual string to print. <td> <p> Alias: vpn-type</p> -<p> D-Bus service name of the VPN plugin that this setting uses to connect to its network. i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.</p> +<p>D-Bus service name of the VPN plugin that this setting uses to connect to its network. i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.</p> <p> Format: string</p> </td> @@ -4392,7 +4514,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vpn.timeout"></a>timeout</code></span></p></td> <td> -<p> Timeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.</p> +<p>Timeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.</p> <p> Format: uint32</p> </td> @@ -4402,7 +4524,7 @@ The actual string to print. <td> <p> Alias: user</p> -<p> If the VPN connection requires a user name for authentication, that name should be provided here. If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty. If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.</p> +<p>If the VPN connection requires a user name for authentication, that name should be provided here. If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty. If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.</p> <p> Format: string</p> </td> @@ -4413,7 +4535,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.43"></a><h3>vrf setting</h3> -<p> VRF settings.</p> +<p>VRF settings.</p> <p> Properties: </p> @@ -4427,7 +4549,7 @@ The actual string to print. <td> <p> Alias: table</p> -<p> The routing table for this VRF.</p> +<p>The routing table for this VRF.</p> <p> Format: uint32</p> </td> @@ -4437,7 +4559,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.44"></a><h3>vxlan setting</h3> -<p> VXLAN Settings.</p> +<p>VXLAN Settings.</p> <p> Properties: </p> @@ -4450,7 +4572,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vxlan.ageing"></a>ageing</code></span></p></td> <td> -<p> Specifies the lifetime in seconds of FDB entries learnt by the kernel.</p> +<p>Specifies the lifetime in seconds of FDB entries learnt by the kernel.</p> <p> Format: uint32</p> </td> @@ -4460,7 +4582,7 @@ The actual string to print. <td> <p> Alias: destination-port</p> -<p> Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.</p> +<p>Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.</p> <p> Format: uint32</p> </td> @@ -4470,7 +4592,7 @@ The actual string to print. <td> <p> Alias: id</p> -<p> Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.</p> +<p>Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.</p> <p> Format: uint32</p> </td> @@ -4478,7 +4600,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vxlan.l2-miss"></a>l2-miss</code></span></p></td> <td> -<p> Specifies whether netlink LL ADDR miss notifications are generated.</p> +<p>Specifies whether netlink LL ADDR miss notifications are generated.</p> <p> Format: boolean</p> </td> @@ -4486,7 +4608,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vxlan.l3-miss"></a>l3-miss</code></span></p></td> <td> -<p> Specifies whether netlink IP ADDR miss notifications are generated.</p> +<p>Specifies whether netlink IP ADDR miss notifications are generated.</p> <p> Format: boolean</p> </td> @@ -4494,7 +4616,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vxlan.learning"></a>learning</code></span></p></td> <td> -<p> Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.</p> +<p>Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.</p> <p> Format: boolean</p> </td> @@ -4502,7 +4624,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vxlan.limit"></a>limit</code></span></p></td> <td> -<p> Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.</p> +<p>Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.</p> <p> Format: uint32</p> </td> @@ -4512,7 +4634,7 @@ The actual string to print. <td> <p> Alias: local</p> -<p> If given, specifies the source IP address to use in outgoing packets.</p> +<p>If given, specifies the source IP address to use in outgoing packets.</p> <p> Format: string</p> </td> @@ -4522,7 +4644,7 @@ The actual string to print. <td> <p> Alias: dev</p> -<p> If given, specifies the parent interface name or parent connection UUID.</p> +<p>If given, specifies the parent interface name or parent connection UUID.</p> <p> Format: string</p> </td> @@ -4530,7 +4652,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vxlan.proxy"></a>proxy</code></span></p></td> <td> -<p> Specifies whether ARP proxy is turned on.</p> +<p>Specifies whether ARP proxy is turned on.</p> <p> Format: boolean</p> </td> @@ -4540,7 +4662,7 @@ The actual string to print. <td> <p> Alias: remote</p> -<p> Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.</p> +<p>Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.</p> <p> Format: string</p> </td> @@ -4548,7 +4670,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vxlan.rsc"></a>rsc</code></span></p></td> <td> -<p> Specifies whether route short circuit is turned on.</p> +<p>Specifies whether route short circuit is turned on.</p> <p> Format: boolean</p> </td> @@ -4558,7 +4680,7 @@ The actual string to print. <td> <p> Alias: source-port-max</p> -<p> Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.</p> +<p>Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.</p> <p> Format: uint32</p> </td> @@ -4568,7 +4690,7 @@ The actual string to print. <td> <p> Alias: source-port-min</p> -<p> Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.</p> +<p>Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.</p> <p> Format: uint32</p> </td> @@ -4576,7 +4698,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vxlan.tos"></a>tos</code></span></p></td> <td> -<p> Specifies the TOS value to use in outgoing packets.</p> +<p>Specifies the TOS value to use in outgoing packets.</p> <p> Format: uint32</p> </td> @@ -4584,7 +4706,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.vxlan.ttl"></a>ttl</code></span></p></td> <td> -<p> Specifies the time-to-live value to use in outgoing packets.</p> +<p>Specifies the time-to-live value to use in outgoing packets.</p> <p> Format: uint32</p> </td> @@ -4595,7 +4717,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.45"></a><h3>wifi-p2p setting</h3> -<p> Wi-Fi P2P Settings.</p> +<p>Wi-Fi P2P Settings.</p> <p> Properties: </p> @@ -4610,7 +4732,7 @@ The actual string to print. <td> <p> Alias: peer</p> -<p> The P2P device that should be connected to. Currently, this is the only way to create or join a group.</p> +<p>The P2P device that should be connected to. Currently, this is the only way to create or join a group.</p> <p> Format: string</p> </td> @@ -4618,8 +4740,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wifi-p2p.wfd-ies"></a>wfd-ies</code></span></p></td> <td> -<p> The Wi-Fi Display (WFD) Information Elements (IEs) to set.</p> -<p> Wi-Fi Display requires a protocol specific information element to be set in certain Wi-Fi frames. These can be specified here for the purpose of establishing a connection. This setting is only useful when implementing a Wi-Fi Display client.</p> +<p>The Wi-Fi Display (WFD) Information Elements (IEs) to set.</p> +<p>Wi-Fi Display requires a protocol specific information element to be set in certain Wi-Fi frames. These can be specified here for the purpose of establishing a connection. This setting is only useful when implementing a Wi-Fi Display client.</p> <p> Format: byte array</p> </td> @@ -4627,8 +4749,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wifi-p2p.wps-method"></a>wps-method</code></span></p></td> <td> -<p> Flags indicating which mode of WPS is to be used.</p> -<p> There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.</p> +<p>Flags indicating which mode of WPS is to be used.</p> +<p>There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.</p> <p> Format: uint32</p> </td> @@ -4639,7 +4761,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.46"></a><h3>wimax setting</h3> -<p> WiMax Settings.</p> +<p>WiMax Settings.</p> <p> Properties: </p> @@ -4654,7 +4776,10 @@ The actual string to print. <td> <p> Alias: mac</p> -<p> If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing). Deprecated: 1</p> +<p>If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing).</p> +<p> + This property is deprecated since version 1.2. + WiMAX is no longer supported.</p> <p> Format: byte array</p> </td> @@ -4664,7 +4789,10 @@ The actual string to print. <td> <p> Alias: nsp</p> -<p> Network Service Provider (NSP) name of the WiMAX network this connection should use. Deprecated: 1</p> +<p>Network Service Provider (NSP) name of the WiMAX network this connection should use.</p> +<p> + This property is deprecated since version 1.2. + WiMAX is no longer supported.</p> <p> Format: string</p> </td> @@ -4677,7 +4805,7 @@ The actual string to print. <a name="id-1.2.10.4.47"></a><h3>802-3-ethernet setting</h3> <p> Alias: ethernet</p> -<p> Wired Ethernet Settings.</p> +<p>Wired Ethernet Settings.</p> <p> Properties: </p> @@ -4690,7 +4818,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.accept-all-mac-addresses"></a>accept-all-mac-addresses</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: NMTernary (int32)</p> </td> @@ -4698,7 +4826,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.auto-negotiate"></a>auto-negotiate</code></span></p></td> <td> -<p> 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.</p> +<p>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.</p> <p> Format: boolean</p> </td> @@ -4708,10 +4836,10 @@ The actual string to print. <td> <p> Alias: cloned-mac</p> -<p> If specified, request that the device use this MAC address instead. This is known as MAC cloning or spoofing.</p> -<p> Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random" and "stable" are supported. "preserve" means not to touch the MAC address on activation. "permanent" means to use the permanent hardware address if the device has one (otherwise this is treated as "preserve"). "random" creates a random MAC address on each connect. "stable" creates a hashed MAC address based on connection.stable-id and a machine dependent key.</p> -<p> If unspecified, the value can be overwritten via global defaults, see manual of NetworkManager.conf. If still unspecified, it defaults to "preserve" (older versions of NetworkManager may use a different default value).</p> -<p> On D-Bus, this field is expressed as "assigned-mac-address" or the deprecated "cloned-mac-address".</p> +<p>If specified, request that the device use this MAC address instead. This is known as MAC cloning or spoofing.</p> +<p>Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random" and "stable" are supported. "preserve" means not to touch the MAC address on activation. "permanent" means to use the permanent hardware address if the device has one (otherwise this is treated as "preserve"). "random" creates a random MAC address on each connect. "stable" creates a hashed MAC address based on connection.stable-id and a machine dependent key.</p> +<p>If unspecified, the value can be overwritten via global defaults, see manual of NetworkManager.conf. If still unspecified, it defaults to "preserve" (older versions of NetworkManager may use a different default value).</p> +<p>On D-Bus, this field is expressed as "assigned-mac-address" or the deprecated "cloned-mac-address".</p> <p> Format: byte array</p> </td> @@ -4719,7 +4847,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.duplex"></a>duplex</code></span></p></td> <td> -<p> When a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.</p> +<p>When a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.</p> <p> Format: string</p> </td> @@ -4727,11 +4855,11 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.generate-mac-address-mask"></a>generate-mac-address-mask</code></span></p></td> <td> -<p> With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.</p> -<p> If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.</p> -<p> If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.</p> -<p> If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.</p> -<p> If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</p> +<p>With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.</p> +<p>If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.</p> +<p>If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.</p> +<p>If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.</p> +<p>If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</p> <p> Format: string</p> </td> @@ -4741,7 +4869,7 @@ The actual string to print. <td> <p> Alias: mac</p> -<p> If specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</p> +<p>If specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</p> <p> Format: byte array</p> </td> @@ -4749,7 +4877,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.mac-address-blacklist"></a>mac-address-blacklist</code></span></p></td> <td> -<p> If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).</p> +<p>If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).</p> <p> Format: array of string</p> </td> @@ -4759,7 +4887,7 @@ The actual string to print. <td> <p> Alias: mtu</p> -<p> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</p> +<p>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</p> <p> Format: uint32</p> </td> @@ -4767,7 +4895,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.port"></a>port</code></span></p></td> <td> -<p> Specific port type to use if the device supports multiple attachment methods. One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.</p> +<p>Specific port type to use if the device supports multiple attachment methods. One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.</p> <p> Format: string</p> </td> @@ -4775,7 +4903,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.s390-nettype"></a>s390-nettype</code></span></p></td> <td> -<p> s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.</p> +<p>s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.</p> <p> Format: string</p> </td> @@ -4783,8 +4911,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.s390-options"></a>s390-options</code></span></p></td> <td> -<p> 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]).</p> -<p> Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.</p> +<p>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]).</p> +<p>Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.</p> <p> Format: dict of string to string</p> </td> @@ -4792,7 +4920,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.s390-subchannels"></a>s390-subchannels</code></span></p></td> <td> -<p> Identifies specific subchannels that this network device uses for communication with z/VM or s390 host. Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels. The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.</p> +<p>Identifies specific subchannels that this network device uses for communication with z/VM or s390 host. Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels. The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.</p> <p> Format: array of string</p> </td> @@ -4800,7 +4928,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.speed"></a>speed</code></span></p></td> <td> -<p> When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.</p> +<p>When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.</p> <p> Format: uint32</p> </td> @@ -4808,7 +4936,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.wake-on-lan"></a>wake-on-lan</code></span></p></td> <td> -<p> The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</p> +<p>The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</p> <p> Format: uint32</p> </td> @@ -4816,7 +4944,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-3-ethernet.wake-on-lan-password"></a>wake-on-lan-password</code></span></p></td> <td> -<p> If specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address. If NULL, no password will be required.</p> +<p>If specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address. If NULL, no password will be required.</p> <p> Format: string</p> </td> @@ -4827,7 +4955,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.48"></a><h3>wireguard setting</h3> -<p> WireGuard Settings.</p> +<p>WireGuard Settings.</p> <p> Properties: </p> @@ -4840,8 +4968,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wireguard.fwmark"></a>fwmark</code></span></p></td> <td> -<p> The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise, it is a 32-bit fwmark for outgoing packets.</p> -<p> Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.</p> +<p>The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise, it is a 32-bit fwmark for outgoing packets.</p> +<p>Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.</p> <p> Format: uint32</p> </td> @@ -4849,9 +4977,9 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wireguard.ip4-auto-default-route"></a>ip4-auto-default-route</code></span></p></td> <td> -<p> Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing".</p> -<p> Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route.</p> -<p> Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips. Since this automatism only makes sense if you also have a peer with an /0 allowed-ips, it is usually not necessary to enable this explicitly. However, you can disable it if you want to configure your own routing and rules.</p> +<p>Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing".</p> +<p>Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route.</p> +<p>Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips. Since this automatism only makes sense if you also have a peer with an /0 allowed-ips, it is usually not necessary to enable this explicitly. However, you can disable it if you want to configure your own routing and rules.</p> <p> Format: NMTernary (int32)</p> </td> @@ -4859,7 +4987,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wireguard.ip6-auto-default-route"></a>ip6-auto-default-route</code></span></p></td> <td> -<p> Like ip4-auto-default-route, but for the IPv6 default route.</p> +<p>Like ip4-auto-default-route, but for the IPv6 default route.</p> <p> Format: NMTernary (int32)</p> </td> @@ -4867,7 +4995,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wireguard.listen-port"></a>listen-port</code></span></p></td> <td> -<p> The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.</p> +<p>The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.</p> <p> Format: uint32</p> </td> @@ -4875,8 +5003,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wireguard.mtu"></a>mtu</code></span></p></td> <td> -<p> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.</p> -<p> If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, this does not take into account the current routes at the time of activation.</p> +<p>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.</p> +<p>If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, this does not take into account the current routes at the time of activation.</p> <p> Format: uint32</p> </td> @@ -4884,8 +5012,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wireguard.peer-routes"></a>peer-routes</code></span></p></td> <td> -<p> Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively.</p> -<p> Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.</p> +<p>Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively.</p> +<p>Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.</p> <p> Format: boolean</p> </td> @@ -4893,7 +5021,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wireguard.private-key"></a>private-key</code></span></p></td> <td> -<p> The 256 bit private-key in base64 encoding.</p> +<p>The 256 bit private-key in base64 encoding.</p> <p> Format: string</p> </td> @@ -4901,7 +5029,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.wireguard.private-key-flags"></a>private-key-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "private-key" property.</p> +<p>Flags indicating how to handle the "private-key" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -4914,7 +5042,7 @@ The actual string to print. <a name="id-1.2.10.4.49"></a><h3>802-11-wireless setting</h3> <p> Alias: wifi</p> -<p> Wi-Fi Settings.</p> +<p>Wi-Fi Settings.</p> <p> Properties: </p> @@ -4927,10 +5055,10 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.ap-isolation"></a>ap-isolation</code></span></p></td> <td> -<p> Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode.</p> -<p> If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.</p> -<p> If set to NM_TERNARY_FALSE (0), devices can talk to each other.</p> -<p> When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).</p> +<p>Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from NM_TERNARY_DEFAULT (-1) only when the interface is configured in AP mode.</p> +<p>If set to NM_TERNARY_TRUE (1), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.</p> +<p>If set to NM_TERNARY_FALSE (0), devices can talk to each other.</p> +<p>When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_FALSE (0).</p> <p> Format: NMTernary (int32)</p> </td> @@ -4938,7 +5066,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.band"></a>band</code></span></p></td> <td> -<p> 802.11 frequency band of the network. One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11. This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible. This setting depends on specific driver capability and may not work with all drivers.</p> +<p>802.11 frequency band of the network. One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11. This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible. This setting depends on specific driver capability and may not work with all drivers.</p> <p> Format: string</p> </td> @@ -4946,8 +5074,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.bssid"></a>bssid</code></span></p></td> <td> -<p> If specified, directs the device to only associate with the given access point. This capability is highly driver dependent and not supported by all devices. Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future.</p> -<p> Locking a client profile to a certain BSSID will prevent roaming and also disable background scanning. That can be useful, if there is only one access point for the SSID.</p> +<p>If specified, directs the device to only associate with the given access point. This capability is highly driver dependent and not supported by all devices. Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future.</p> +<p>Locking a client profile to a certain BSSID will prevent roaming and also disable background scanning. That can be useful, if there is only one access point for the SSID.</p> <p> Format: byte array</p> </td> @@ -4955,7 +5083,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.channel"></a>channel</code></span></p></td> <td> -<p> Wireless channel to use for the Wi-Fi connection. The device will only join (or create for Ad-Hoc networks) a Wi-Fi network on the specified channel. Because channel numbers overlap between bands, this property also requires the "band" property to be set.</p> +<p>Wireless channel to use for the Wi-Fi connection. The device will only join (or create for Ad-Hoc networks) a Wi-Fi network on the specified channel. Because channel numbers overlap between bands, this property also requires the "band" property to be set.</p> <p> Format: uint32</p> </td> @@ -4965,10 +5093,10 @@ The actual string to print. <td> <p> Alias: cloned-mac</p> -<p> If specified, request that the device use this MAC address instead. This is known as MAC cloning or spoofing.</p> -<p> Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random" and "stable" are supported. "preserve" means not to touch the MAC address on activation. "permanent" means to use the permanent hardware address of the device. "random" creates a random MAC address on each connect. "stable" creates a hashed MAC address based on connection.stable-id and a machine dependent key.</p> -<p> If unspecified, the value can be overwritten via global defaults, see manual of NetworkManager.conf. If still unspecified, it defaults to "preserve" (older versions of NetworkManager may use a different default value).</p> -<p> On D-Bus, this field is expressed as "assigned-mac-address" or the deprecated "cloned-mac-address".</p> +<p>If specified, request that the device use this MAC address instead. This is known as MAC cloning or spoofing.</p> +<p>Beside explicitly specifying a MAC address, the special values "preserve", "permanent", "random" and "stable" are supported. "preserve" means not to touch the MAC address on activation. "permanent" means to use the permanent hardware address of the device. "random" creates a random MAC address on each connect. "stable" creates a hashed MAC address based on connection.stable-id and a machine dependent key.</p> +<p>If unspecified, the value can be overwritten via global defaults, see manual of NetworkManager.conf. If still unspecified, it defaults to "preserve" (older versions of NetworkManager may use a different default value).</p> +<p>On D-Bus, this field is expressed as "assigned-mac-address" or the deprecated "cloned-mac-address".</p> <p> Format: byte array</p> </td> @@ -4976,11 +5104,11 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.generate-mac-address-mask"></a>generate-mac-address-mask</code></span></p></td> <td> -<p> With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.</p> -<p> If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.</p> -<p> If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.</p> -<p> If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.</p> -<p> If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</p> +<p>With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.</p> +<p>If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.</p> +<p>If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.</p> +<p>If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.</p> +<p>If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</p> <p> Format: string</p> </td> @@ -4988,10 +5116,10 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.hidden"></a>hidden</code></span></p></td> <td> -<p> If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode.</p> -<p> In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID. However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution.</p> -<p> In AP mode, the created network does not broadcast its SSID.</p> -<p> Note that marking the network as hidden may be a privacy issue for you (in infrastructure mode) or client stations (in AP mode), as the explicit probe-scans are distinctly recognizable on the air.</p> +<p>If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode.</p> +<p>In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID. However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution.</p> +<p>In AP mode, the created network does not broadcast its SSID.</p> +<p>Note that marking the network as hidden may be a privacy issue for you (in infrastructure mode) or client stations (in AP mode), as the explicit probe-scans are distinctly recognizable on the air.</p> <p> Format: boolean</p> </td> @@ -5001,7 +5129,7 @@ The actual string to print. <td> <p> Alias: mac</p> -<p> If specified, this connection will only apply to the Wi-Fi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</p> +<p>If specified, this connection will only apply to the Wi-Fi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</p> <p> Format: byte array</p> </td> @@ -5009,7 +5137,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.mac-address-blacklist"></a>mac-address-blacklist</code></span></p></td> <td> -<p> A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").</p> +<p>A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").</p> <p> Format: array of string</p> </td> @@ -5017,7 +5145,10 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.mac-address-randomization"></a>mac-address-randomization</code></span></p></td> <td> -<p> One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address). This property is deprecated for 'cloned-mac-address'. Deprecated: 1</p> +<p>One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address).</p> +<p> + This property is deprecated since version 1.4. + Use the "cloned-mac-address" property instead.</p> <p> Format: uint32</p> </td> @@ -5027,7 +5158,7 @@ The actual string to print. <td> <p> Alias: mode</p> -<p> Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap". If blank, infrastructure is assumed.</p> +<p>Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap". If blank, infrastructure is assumed.</p> <p> Format: string</p> </td> @@ -5037,7 +5168,7 @@ The actual string to print. <td> <p> Alias: mtu</p> -<p> If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</p> +<p>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</p> <p> Format: uint32</p> </td> @@ -5045,7 +5176,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.powersave"></a>powersave</code></span></p></td> <td> -<p> One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.</p> +<p>One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.</p> <p> Format: uint32</p> </td> @@ -5053,7 +5184,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.rate"></a>rate</code></span></p></td> <td> -<p> If non-zero, directs the device to only use the specified bitrate for communication with the access point. Units are in Kb/s, ie 5500 = 5.5 Mbit/s. This property is highly driver dependent and not all devices support setting a static bitrate.</p> +<p>If non-zero, directs the device to only use the specified bitrate for communication with the access point. Units are in Kb/s, ie 5500 = 5.5 Mbit/s. This property is highly driver dependent and not all devices support setting a static bitrate.</p> <p> Format: uint32</p> </td> @@ -5061,7 +5192,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.seen-bssids"></a>seen-bssids</code></span></p></td> <td> -<p> A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network. NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.</p> +<p>A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network. NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.</p> <p> Format: array of string</p> </td> @@ -5071,7 +5202,7 @@ The actual string to print. <td> <p> Alias: ssid</p> -<p> SSID of the Wi-Fi network. Must be specified.</p> +<p>SSID of the Wi-Fi network. Must be specified.</p> <p> Format: byte array</p> </td> @@ -5079,7 +5210,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.tx-power"></a>tx-power</code></span></p></td> <td> -<p> If non-zero, directs the device to use the specified transmit power. Units are dBm. This property is highly driver dependent and not all devices support setting a static transmit power.</p> +<p>If non-zero, directs the device to use the specified transmit power. Units are dBm. This property is highly driver dependent and not all devices support setting a static transmit power.</p> <p> Format: uint32</p> </td> @@ -5087,7 +5218,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless.wake-on-wlan"></a>wake-on-wlan</code></span></p></td> <td> -<p> The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</p> +<p>The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</p> <p> Format: uint32</p> </td> @@ -5100,7 +5231,7 @@ The actual string to print. <a name="id-1.2.10.4.50"></a><h3>802-11-wireless-security setting</h3> <p> Alias: wifi-sec</p> -<p> Wi-Fi Security Settings.</p> +<p>Wi-Fi Security Settings.</p> <p> Properties: </p> @@ -5113,7 +5244,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.auth-alg"></a>auth-alg</code></span></p></td> <td> -<p> When WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here. One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP. When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.</p> +<p>When WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here. One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP. When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.</p> <p> Format: string</p> </td> @@ -5121,7 +5252,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.fils"></a>fils</code></span></p></td> <td> -<p> Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.</p> +<p>Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.</p> <p> Format: int32</p> </td> @@ -5129,7 +5260,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.group"></a>group</code></span></p></td> <td> -<p> A list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".</p> +<p>A list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".</p> <p> Format: array of string</p> </td> @@ -5137,8 +5268,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.key-mgmt"></a>key-mgmt</code></span></p></td> <td> -<p> 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).</p> -<p> This property must be set for any Wi-Fi connection that uses security.</p> +<p>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).</p> +<p>This property must be set for any Wi-Fi connection that uses security.</p> <p> Format: string</p> </td> @@ -5146,7 +5277,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.leap-password"></a>leap-password</code></span></p></td> <td> -<p> The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</p> +<p>The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</p> <p> Format: string</p> </td> @@ -5154,7 +5285,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.leap-password-flags"></a>leap-password-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "leap-password" property.</p> +<p>Flags indicating how to handle the "leap-password" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -5162,7 +5293,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.leap-username"></a>leap-username</code></span></p></td> <td> -<p> The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</p> +<p>The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</p> <p> Format: string</p> </td> @@ -5170,7 +5301,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.pairwise"></a>pairwise</code></span></p></td> <td> -<p> A list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "tkip" or "ccmp".</p> +<p>A list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty. Each list element may be one of "tkip" or "ccmp".</p> <p> Format: array of string</p> </td> @@ -5178,7 +5309,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.pmf"></a>pmf</code></span></p></td> <td> -<p> Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.</p> +<p>Indicates whether Protected Management Frames (802.11w) must be enabled for the connection. One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported). When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.</p> <p> Format: int32</p> </td> @@ -5186,7 +5317,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.proto"></a>proto</code></span></p></td> <td> -<p> List of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN). If not specified, both WPA and RSN connections are allowed.</p> +<p>List of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN). If not specified, both WPA and RSN connections are allowed.</p> <p> Format: array of string</p> </td> @@ -5194,7 +5325,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.psk"></a>psk</code></span></p></td> <td> -<p> Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.</p> +<p>Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.</p> <p> Format: string</p> </td> @@ -5202,7 +5333,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.psk-flags"></a>psk-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "psk" property.</p> +<p>Flags indicating how to handle the "psk" property.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -5210,7 +5341,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.wep-key-flags"></a>wep-key-flags</code></span></p></td> <td> -<p> Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.</p> +<p>Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.</p> <p> Format: NMSettingSecretFlags (uint32)</p> </td> @@ -5218,7 +5349,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.wep-key-type"></a>wep-key-type</code></span></p></td> <td> -<p> Controls the interpretation of WEP keys. Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.</p> +<p>Controls the interpretation of WEP keys. Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.</p> <p> Format: NMWepKeyType (uint32)</p> </td> @@ -5226,7 +5357,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.wep-key0"></a>wep-key0</code></span></p></td> <td> -<p> Index 0 WEP key. This is the WEP key used in most networks. See the "wep-key-type" property for a description of how this key is interpreted.</p> +<p>Index 0 WEP key. This is the WEP key used in most networks. See the "wep-key-type" property for a description of how this key is interpreted.</p> <p> Format: string</p> </td> @@ -5234,7 +5365,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.wep-key1"></a>wep-key1</code></span></p></td> <td> -<p> Index 1 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</p> +<p>Index 1 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</p> <p> Format: string</p> </td> @@ -5242,7 +5373,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.wep-key2"></a>wep-key2</code></span></p></td> <td> -<p> Index 2 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</p> +<p>Index 2 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</p> <p> Format: string</p> </td> @@ -5250,7 +5381,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.wep-key3"></a>wep-key3</code></span></p></td> <td> -<p> Index 3 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</p> +<p>Index 3 WEP key. This WEP index is not used by most networks. See the "wep-key-type" property for a description of how this key is interpreted.</p> <p> Format: string</p> </td> @@ -5258,7 +5389,7 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.wep-tx-keyidx"></a>wep-tx-keyidx</code></span></p></td> <td> -<p> When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here. Valid values are 0 (default key) through 3. Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.</p> +<p>When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here. Valid values are 0 (default key) through 3. Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.</p> <p> Format: uint32</p> </td> @@ -5266,9 +5397,9 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.802-11-wireless-security.wps-method"></a>wps-method</code></span></p></td> <td> -<p> Flags indicating which mode of WPS is to be used if any.</p> -<p> There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities.</p> -<p> WPS can be disabled by setting this property to a value of 1.</p> +<p>Flags indicating which mode of WPS is to be used if any.</p> +<p>There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities.</p> +<p>WPS can be disabled by setting this property to a value of 1.</p> <p> Format: uint32</p> </td> @@ -5279,7 +5410,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.51"></a><h3>wpan setting</h3> -<p> IEEE 802.15.4 (WPAN) MAC Settings.</p> +<p>IEEE 802.15.4 (WPAN) MAC Settings.</p> <p> Properties: </p> @@ -5294,7 +5425,7 @@ The actual string to print. <td> <p> Alias: channel</p> -<p> IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</p> +<p>IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</p> <p> Format: int32</p> </td> @@ -5304,7 +5435,7 @@ The actual string to print. <td> <p> Alias: mac</p> -<p> If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.</p> +<p>If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.</p> <p> Format: string</p> </td> @@ -5314,7 +5445,7 @@ The actual string to print. <td> <p> Alias: page</p> -<p> IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</p> +<p>IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</p> <p> Format: int32</p> </td> @@ -5324,7 +5455,7 @@ The actual string to print. <td> <p> Alias: pan-id</p> -<p> IEEE 802.15.4 Personal Area Network (PAN) identifier.</p> +<p>IEEE 802.15.4 Personal Area Network (PAN) identifier.</p> <p> Format: uint32</p> </td> @@ -5334,7 +5465,7 @@ The actual string to print. <td> <p> Alias: short-addr</p> -<p> Short IEEE 802.15.4 address to be used within a restricted environment.</p> +<p>Short IEEE 802.15.4 address to be used within a restricted environment.</p> <p> Format: uint32</p> </td> @@ -5345,7 +5476,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.52"></a><h3>bond-port setting</h3> -<p> Bond Port Settings.</p> +<p>Bond Port Settings.</p> <p> Properties: </p> @@ -5359,7 +5490,7 @@ The actual string to print. <td> <p> Alias: queue-id</p> -<p> The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.</p> +<p>The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.</p> <p> Format: uint32</p> </td> @@ -5369,7 +5500,7 @@ The actual string to print. <hr> <div class="refsect2"> <a name="id-1.2.10.4.53"></a><h3>hostname setting</h3> -<p> Hostname settings.</p> +<p>Hostname settings.</p> <p> Properties: </p> @@ -5382,8 +5513,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.hostname.from-dhcp"></a>from-dhcp</code></span></p></td> <td> -<p> Whether the system hostname can be determined from DHCP on this connection.</p> -<p> When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</p> +<p>Whether the system hostname can be determined from DHCP on this connection.</p> +<p>When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</p> <p> Format: NMTernary (int32)</p> </td> @@ -5391,8 +5522,8 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.hostname.from-dns-lookup"></a>from-dns-lookup</code></span></p></td> <td> -<p> Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.</p> -<p> When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</p> +<p>Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.</p> +<p>When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</p> <p> Format: NMTernary (int32)</p> </td> @@ -5400,9 +5531,9 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.hostname.only-from-default"></a>only-from-default</code></span></p></td> <td> -<p> If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).</p> -<p> If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route.</p> -<p> When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).</p> +<p>If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).</p> +<p>If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route.</p> +<p>When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).</p> <p> Format: NMTernary (int32)</p> </td> @@ -5410,9 +5541,9 @@ The actual string to print. <tr> <td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.hostname.priority"></a>priority</code></span></p></td> <td> -<p> The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority). A connection with higher priority is considered before connections with lower priority.</p> -<p> If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100.</p> -<p> Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.</p> +<p>The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority). A connection with higher priority is considered before connections with lower priority.</p> +<p>If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100.</p> +<p>Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.</p> <p> Format: int32</p> </td> @@ -5422,8 +5553,32 @@ The actual string to print. </div> <hr> <div class="refsect2"> -<a name="id-1.2.10.4.54"></a><h3>veth setting</h3> -<p> Veth Settings.</p> +<a name="id-1.2.10.4.54"></a><h3>loopback setting</h3> +<p>Loopback Link Settings.</p> +<p> + Properties: + </p> +<div class="variablelist"><table border="0" class="variablelist"> +<colgroup> +<col align="left" valign="top"> +<col> +</colgroup> +<tbody><tr> +<td><p><span class="term"><code class="option"><a name="nm-settings-nmcli.property.loopback.mtu"></a>mtu</code></span></p></td> +<td> +<p> + Alias: mtu</p> +<p>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</p> +<p> + Format: uint32</p> +</td> +</tr></tbody> +</table></div> +</div> +<hr> +<div class="refsect2"> +<a name="id-1.2.10.4.55"></a><h3>veth setting</h3> +<p>Veth Settings.</p> <p> Properties: </p> @@ -5437,7 +5592,7 @@ The actual string to print. <td> <p> Alias: peer</p> -<p> This property specifies the peer interface name of the veth. This property is mandatory.</p> +<p>This property specifies the peer interface name of the veth. This property is mandatory.</p> <p> Format: string</p> </td> diff --git a/docs/api/html/nmcli.html b/docs/api/html/nmcli.html index 526f1ee6..8443d500 100644 --- a/docs/api/html/nmcli.html +++ b/docs/api/html/nmcli.html @@ -1595,6 +1595,39 @@ <td><p>Provides a default value for the internationalization variables that are unset or null.</p></td> </tr> +<tr> +<td><p><span class="term"><code class="envar">NO_COLOR</code></span></p></td> +<td><p>Default to not producing colored and paged output. The + <code class="option">--colors</code> option, if used, takes precedence.</p></td> +</tr> +<tr> +<td><p><span class="term"><code class="envar">PAGER</code></span></p></td> +<td> +<p>Filter to pipe the output through if it doesn't fit on a screen. + Can be a file name of an executable or a shell command. Empty string to + disable the functionality.</p> +<p>Note that the pager command is expected to handle wide characters + and ANSI escape sequences for changing colors (unless they're disabled). + <span class="command"><strong>nmcli</strong></span> sets up the environment variables + <code class="envar">LESS</code> and <code class="envar">LESSCHARSET</code> appropriately for the + <span class="citerefentry"><span class="refentrytitle">less</span>(1)</span> + pager, other pagers may or may not need extra configuration.</p> +<p>If unspecified, + <span class="citerefentry"><span class="refentrytitle">pager</span>(1)</span>, + <span class="citerefentry"><span class="refentrytitle">less</span>(1)</span> + and <span class="citerefentry"><span class="refentrytitle">more</span>(1)</span> + will be tried (in that order).</p> +</td> +</tr> +<tr> +<td><p><span class="term"><code class="envar">TERM</code></span></p></td> +<td> +<p>Terminal type. If <code class="literal">dumb</code>, <span class="command"><strong>nmcli</strong></span> + will not use a pager or produce ANSI escape sequences for coloring.</p> +<p>Terminal types other than <code class="literal">dumb</code> are assumed to + support ASCII escape sequences for setting the output color.</p> +</td> +</tr> </tbody> </table></div> </div> diff --git a/docs/api/html/ref-dbus-devices.html b/docs/api/html/ref-dbus-devices.html index 7d732909..ffff3da4 100644 --- a/docs/api/html/ref-dbus-devices.html +++ b/docs/api/html/ref-dbus-devices.html @@ -54,6 +54,9 @@ <span class="refentrytitle"><a href="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html">org.freedesktop.NetworkManager.Device.Infiniband</a></span><span class="refpurpose"> — Infiniband Device.</span> </dt> <dt> +<span class="refentrytitle"><a href="gdbus-org.freedesktop.NetworkManager.Device.Loopback.html">org.freedesktop.NetworkManager.Device.Loopback</a></span><span class="refpurpose"> — Loopback Device.</span> +</dt> +<dt> <span class="refentrytitle"><a href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html">org.freedesktop.NetworkManager.Device.Lowpan</a></span><span class="refpurpose"> — 6LoWPAN Device.</span> </dt> <dt> diff --git a/docs/api/html/ref-settings.html b/docs/api/html/ref-settings.html index f35354f9..f0cec0d7 100644 --- a/docs/api/html/ref-settings.html +++ b/docs/api/html/ref-settings.html @@ -28,160 +28,166 @@ <dt><span class="chapter"><a href="ch01.html">Configuration Settings</a></span></dt> <dd><dl> <dt> -<span class="refentrytitle"><a href="settings-connection.html">connection</a></span><span class="refpurpose"> — General Connection Profile Settings</span> +<span class="refentrytitle"><a href="settings-connection.html">connection</a></span><span class="refpurpose"> — General Connection Profile Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-6lowpan.html">6lowpan</a></span><span class="refpurpose"> — 6LoWPAN Settings</span> +<span class="refentrytitle"><a href="settings-6lowpan.html">6lowpan</a></span><span class="refpurpose"> — 6LoWPAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-1x.html">802-1x</a></span><span class="refpurpose"> — IEEE 802.1x Authentication Settings</span> +<span class="refentrytitle"><a href="settings-802-1x.html">802-1x</a></span><span class="refpurpose"> — IEEE 802.1x Authentication Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-adsl.html">adsl</a></span><span class="refpurpose"> — ADSL Settings</span> +<span class="refentrytitle"><a href="settings-adsl.html">adsl</a></span><span class="refpurpose"> — ADSL Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bluetooth.html">bluetooth</a></span><span class="refpurpose"> — Bluetooth Settings</span> +<span class="refentrytitle"><a href="settings-bluetooth.html">bluetooth</a></span><span class="refpurpose"> — Bluetooth Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bond.html">bond</a></span><span class="refpurpose"> — Bonding Settings</span> +<span class="refentrytitle"><a href="settings-bond.html">bond</a></span><span class="refpurpose"> — Bonding Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bridge.html">bridge</a></span><span class="refpurpose"> — Bridging Settings</span> +<span class="refentrytitle"><a href="settings-bridge.html">bridge</a></span><span class="refpurpose"> — Bridging Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bridge-port.html">bridge-port</a></span><span class="refpurpose"> — Bridge Port Settings</span> +<span class="refentrytitle"><a href="settings-bridge-port.html">bridge-port</a></span><span class="refpurpose"> — Bridge Port Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-cdma.html">cdma</a></span><span class="refpurpose"> — CDMA-based Mobile Broadband Settings</span> +<span class="refentrytitle"><a href="settings-cdma.html">cdma</a></span><span class="refpurpose"> — CDMA-based Mobile Broadband Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-dcb.html">dcb</a></span><span class="refpurpose"> — Data Center Bridging Settings</span> +<span class="refentrytitle"><a href="settings-dcb.html">dcb</a></span><span class="refpurpose"> — Data Center Bridging Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-dummy.html">dummy</a></span><span class="refpurpose"> — Dummy Link Settings</span> +<span class="refentrytitle"><a href="settings-dummy.html">dummy</a></span><span class="refpurpose"> — Dummy Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ethtool.html">ethtool</a></span><span class="refpurpose"> — Ethtool Ethernet Settings</span> +<span class="refentrytitle"><a href="settings-ethtool.html">ethtool</a></span><span class="refpurpose"> — Ethtool Ethernet Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-generic.html">generic</a></span><span class="refpurpose"> — Generic Link Settings</span> +<span class="refentrytitle"><a href="settings-generic.html">generic</a></span><span class="refpurpose"> — Generic Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-gsm.html">gsm</a></span><span class="refpurpose"> — GSM-based Mobile Broadband Settings</span> +<span class="refentrytitle"><a href="settings-gsm.html">gsm</a></span><span class="refpurpose"> — GSM-based Mobile Broadband Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-infiniband.html">infiniband</a></span><span class="refpurpose"> — Infiniband Settings</span> +<span class="refentrytitle"><a href="settings-infiniband.html">infiniband</a></span><span class="refpurpose"> — Infiniband Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ipv4.html">ipv4</a></span><span class="refpurpose"> — IPv4 Settings</span> +<span class="refentrytitle"><a href="settings-ipv4.html">ipv4</a></span><span class="refpurpose"> — IPv4 Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ipv6.html">ipv6</a></span><span class="refpurpose"> — IPv6 Settings</span> +<span class="refentrytitle"><a href="settings-ipv6.html">ipv6</a></span><span class="refpurpose"> — IPv6 Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ip-tunnel.html">ip-tunnel</a></span><span class="refpurpose"> — IP Tunneling Settings</span> +<span class="refentrytitle"><a href="settings-ip-tunnel.html">ip-tunnel</a></span><span class="refpurpose"> — IP Tunneling Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-macsec.html">macsec</a></span><span class="refpurpose"> — MACSec Settings</span> +<span class="refentrytitle"><a href="settings-macsec.html">macsec</a></span><span class="refpurpose"> — MACSec Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-macvlan.html">macvlan</a></span><span class="refpurpose"> — MAC VLAN Settings</span> +<span class="refentrytitle"><a href="settings-macvlan.html">macvlan</a></span><span class="refpurpose"> — MAC VLAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-match.html">match</a></span><span class="refpurpose"> — Match settings</span> +<span class="refentrytitle"><a href="settings-match.html">match</a></span><span class="refpurpose"> — Match settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-11-olpc-mesh.html">802-11-olpc-mesh</a></span><span class="refpurpose"> — OLPC Wireless Mesh Settings</span> +<span class="refentrytitle"><a href="settings-802-11-olpc-mesh.html">802-11-olpc-mesh</a></span><span class="refpurpose"> — OLPC Wireless Mesh Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-bridge.html">ovs-bridge</a></span><span class="refpurpose"> — OvsBridge Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-bridge.html">ovs-bridge</a></span><span class="refpurpose"> — OvsBridge Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-dpdk.html">ovs-dpdk</a></span><span class="refpurpose"> — OvsDpdk Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-dpdk.html">ovs-dpdk</a></span><span class="refpurpose"> — OvsDpdk Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-interface.html">ovs-interface</a></span><span class="refpurpose"> — Open vSwitch Interface Settings</span> +<span class="refentrytitle"><a href="settings-ovs-interface.html">ovs-interface</a></span><span class="refpurpose"> — Open vSwitch Interface Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-patch.html">ovs-patch</a></span><span class="refpurpose"> — OvsPatch Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-patch.html">ovs-patch</a></span><span class="refpurpose"> — OvsPatch Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-port.html">ovs-port</a></span><span class="refpurpose"> — OvsPort Link Settings</span> +<span class="refentrytitle"><a href="settings-ovs-port.html">ovs-port</a></span><span class="refpurpose"> — OvsPort Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ppp.html">ppp</a></span><span class="refpurpose"> — Point-to-Point Protocol Settings</span> +<span class="refentrytitle"><a href="settings-ppp.html">ppp</a></span><span class="refpurpose"> — Point-to-Point Protocol Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-pppoe.html">pppoe</a></span><span class="refpurpose"> — PPP-over-Ethernet Settings</span> +<span class="refentrytitle"><a href="settings-pppoe.html">pppoe</a></span><span class="refpurpose"> — PPP-over-Ethernet Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-proxy.html">proxy</a></span><span class="refpurpose"> — WWW Proxy Settings</span> +<span class="refentrytitle"><a href="settings-proxy.html">proxy</a></span><span class="refpurpose"> — WWW Proxy Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-serial.html">serial</a></span><span class="refpurpose"> — Serial Link Settings</span> +<span class="refentrytitle"><a href="settings-serial.html">serial</a></span><span class="refpurpose"> — Serial Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-sriov.html">sriov</a></span><span class="refpurpose"> — SR-IOV settings</span> +<span class="refentrytitle"><a href="settings-sriov.html">sriov</a></span><span class="refpurpose"> — SR-IOV settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-tc.html">tc</a></span><span class="refpurpose"> — Linux Traffic Control Settings</span> +<span class="refentrytitle"><a href="settings-tc.html">tc</a></span><span class="refpurpose"> — Linux Traffic Control Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-team.html">team</a></span><span class="refpurpose"> — Teaming Settings</span> +<span class="refentrytitle"><a href="settings-team.html">team</a></span><span class="refpurpose"> — Teaming Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-team-port.html">team-port</a></span><span class="refpurpose"> — Team Port Settings</span> +<span class="refentrytitle"><a href="settings-team-port.html">team-port</a></span><span class="refpurpose"> — Team Port Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-tun.html">tun</a></span><span class="refpurpose"> — Tunnel Settings</span> +<span class="refentrytitle"><a href="settings-tun.html">tun</a></span><span class="refpurpose"> — Tunnel Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-user.html">user</a></span><span class="refpurpose"> — General User Profile Settings</span> +<span class="refentrytitle"><a href="settings-user.html">user</a></span><span class="refpurpose"> — General User Profile Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vlan.html">vlan</a></span><span class="refpurpose"> — VLAN Settings</span> +<span class="refentrytitle"><a href="settings-vlan.html">vlan</a></span><span class="refpurpose"> — VLAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vpn.html">vpn</a></span><span class="refpurpose"> — VPN Settings</span> +<span class="refentrytitle"><a href="settings-vpn.html">vpn</a></span><span class="refpurpose"> — VPN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vrf.html">vrf</a></span><span class="refpurpose"> — VRF settings</span> +<span class="refentrytitle"><a href="settings-vrf.html">vrf</a></span><span class="refpurpose"> — VRF settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-vxlan.html">vxlan</a></span><span class="refpurpose"> — VXLAN Settings</span> +<span class="refentrytitle"><a href="settings-vxlan.html">vxlan</a></span><span class="refpurpose"> — VXLAN Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wifi-p2p.html">wifi-p2p</a></span><span class="refpurpose"> — Wi-Fi P2P Settings</span> +<span class="refentrytitle"><a href="settings-wifi-p2p.html">wifi-p2p</a></span><span class="refpurpose"> — Wi-Fi P2P Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wimax.html">wimax</a></span><span class="refpurpose"> — WiMax Settings</span> +<span class="refentrytitle"><a href="settings-wimax.html">wimax</a></span><span class="refpurpose"> — WiMax Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-3-ethernet.html">802-3-ethernet</a></span><span class="refpurpose"> — Wired Ethernet Settings</span> +<span class="refentrytitle"><a href="settings-802-3-ethernet.html">802-3-ethernet</a></span><span class="refpurpose"> — Wired Ethernet Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wireguard.html">wireguard</a></span><span class="refpurpose"> — WireGuard Settings</span> +<span class="refentrytitle"><a href="settings-wireguard.html">wireguard</a></span><span class="refpurpose"> — WireGuard Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-11-wireless.html">802-11-wireless</a></span><span class="refpurpose"> — Wi-Fi Settings</span> +<span class="refentrytitle"><a href="settings-802-11-wireless.html">802-11-wireless</a></span><span class="refpurpose"> — Wi-Fi Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-802-11-wireless-security.html">802-11-wireless-security</a></span><span class="refpurpose"> — Wi-Fi Security Settings</span> +<span class="refentrytitle"><a href="settings-802-11-wireless-security.html">802-11-wireless-security</a></span><span class="refpurpose"> — Wi-Fi Security Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-wpan.html">wpan</a></span><span class="refpurpose"> — IEEE 802.15.4 (WPAN) MAC Settings</span> +<span class="refentrytitle"><a href="settings-wpan.html">wpan</a></span><span class="refpurpose"> — IEEE 802.15.4 (WPAN) MAC Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-bond-port.html">bond-port</a></span><span class="refpurpose"> — Bond Port Settings</span> +<span class="refentrytitle"><a href="settings-bond-port.html">bond-port</a></span><span class="refpurpose"> — Bond Port Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-hostname.html">hostname</a></span><span class="refpurpose"> — Hostname settings</span> +<span class="refentrytitle"><a href="settings-hostname.html">hostname</a></span><span class="refpurpose"> — Hostname settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-ovs-external-ids.html">ovs-external-ids</a></span><span class="refpurpose"> — OVS External IDs Settings</span> +<span class="refentrytitle"><a href="settings-loopback.html">loopback</a></span><span class="refpurpose"> — Loopback Link Settings</span> </dt> <dt> -<span class="refentrytitle"><a href="settings-veth.html">veth</a></span><span class="refpurpose"> — Veth Settings</span> +<span class="refentrytitle"><a href="settings-ovs-external-ids.html">ovs-external-ids</a></span><span class="refpurpose"> — OVS External IDs Settings</span> +</dt> +<dt> +<span class="refentrytitle"><a href="settings-ovs-other-config.html">ovs-other-config</a></span><span class="refpurpose"> — OVS Other Config Settings</span> +</dt> +<dt> +<span class="refentrytitle"><a href="settings-veth.html">veth</a></span><span class="refpurpose"> — Veth Settings</span> </dt> </dl></dd> <dt><span class="chapter"><a href="secrets-flags.html">Secret flag types</a></span></dt> diff --git a/docs/api/html/settings-6lowpan.html b/docs/api/html/settings-6lowpan.html index a185cc5f..1d692e4d 100644 --- a/docs/api/html/settings-6lowpan.html +++ b/docs/api/html/settings-6lowpan.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>6lowpan</h2> -<p>6lowpan — 6LoWPAN Settings</p> +<p>6lowpan — 6LoWPAN Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.3.2.2.1"></a><p class="title"><b>Table 47. </b></p> +<a name="id-1.3.3.3.2.2.1"></a><p class="title"><b>Table 49. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-802-11-olpc-mesh.html b/docs/api/html/settings-802-11-olpc-mesh.html index 86a6c492..031ccb05 100644 --- a/docs/api/html/settings-802-11-olpc-mesh.html +++ b/docs/api/html/settings-802-11-olpc-mesh.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>802-11-olpc-mesh</h2> -<p>802-11-olpc-mesh — OLPC Wireless Mesh Settings</p> +<p>802-11-olpc-mesh — OLPC Wireless Mesh Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.23.2.2.1"></a><p class="title"><b>Table 67. </b></p> +<a name="id-1.3.3.23.2.2.1"></a><p class="title"><b>Table 69. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-802-11-wireless-security.html b/docs/api/html/settings-802-11-wireless-security.html index 7f6d2474..83f4300e 100644 --- a/docs/api/html/settings-802-11-wireless-security.html +++ b/docs/api/html/settings-802-11-wireless-security.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>802-11-wireless-security</h2> -<p>802-11-wireless-security — Wi-Fi Security Settings</p> +<p>802-11-wireless-security — Wi-Fi Security Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.48.2.2.1"></a><p class="title"><b>Table 92. </b></p> +<a name="id-1.3.3.48.2.2.1"></a><p class="title"><b>Table 94. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-802-11-wireless.html b/docs/api/html/settings-802-11-wireless.html index 00372730..24700c54 100644 --- a/docs/api/html/settings-802-11-wireless.html +++ b/docs/api/html/settings-802-11-wireless.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>802-11-wireless</h2> -<p>802-11-wireless — Wi-Fi Settings</p> +<p>802-11-wireless — Wi-Fi Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.47.2.2.1"></a><p class="title"><b>Table 91. </b></p> +<a name="id-1.3.3.47.2.2.1"></a><p class="title"><b>Table 93. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-802-1x.html b/docs/api/html/settings-802-1x.html index 97827e6a..4ad4158d 100644 --- a/docs/api/html/settings-802-1x.html +++ b/docs/api/html/settings-802-1x.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>802-1x</h2> -<p>802-1x — IEEE 802.1x Authentication Settings</p> +<p>802-1x — IEEE 802.1x Authentication Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.4.2.2.1"></a><p class="title"><b>Table 48. </b></p> +<a name="id-1.3.3.4.2.2.1"></a><p class="title"><b>Table 50. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-802-3-ethernet.html b/docs/api/html/settings-802-3-ethernet.html index b3132cf3..b232048e 100644 --- a/docs/api/html/settings-802-3-ethernet.html +++ b/docs/api/html/settings-802-3-ethernet.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>802-3-ethernet</h2> -<p>802-3-ethernet — Wired Ethernet Settings</p> +<p>802-3-ethernet — Wired Ethernet Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.45.2.2.1"></a><p class="title"><b>Table 89. </b></p> +<a name="id-1.3.3.45.2.2.1"></a><p class="title"><b>Table 91. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-adsl.html b/docs/api/html/settings-adsl.html index 9c9cd333..ab01cb14 100644 --- a/docs/api/html/settings-adsl.html +++ b/docs/api/html/settings-adsl.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>adsl</h2> -<p>adsl — ADSL Settings</p> +<p>adsl — ADSL Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.5.2.2.1"></a><p class="title"><b>Table 49. </b></p> +<a name="id-1.3.3.5.2.2.1"></a><p class="title"><b>Table 51. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-bluetooth.html b/docs/api/html/settings-bluetooth.html index 6af4a0ee..cc035095 100644 --- a/docs/api/html/settings-bluetooth.html +++ b/docs/api/html/settings-bluetooth.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>bluetooth</h2> -<p>bluetooth — Bluetooth Settings</p> +<p>bluetooth — Bluetooth Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.6.2.2.1"></a><p class="title"><b>Table 50. </b></p> +<a name="id-1.3.3.6.2.2.1"></a><p class="title"><b>Table 52. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-bond-port.html b/docs/api/html/settings-bond-port.html index dc63034a..6daf9a3d 100644 --- a/docs/api/html/settings-bond-port.html +++ b/docs/api/html/settings-bond-port.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>bond-port</h2> -<p>bond-port — Bond Port Settings</p> +<p>bond-port — Bond Port Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.50.2.2.1"></a><p class="title"><b>Table 94. </b></p> +<a name="id-1.3.3.50.2.2.1"></a><p class="title"><b>Table 96. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-bond.html b/docs/api/html/settings-bond.html index 81b21536..21d2ff0f 100644 --- a/docs/api/html/settings-bond.html +++ b/docs/api/html/settings-bond.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>bond</h2> -<p>bond — Bonding Settings</p> +<p>bond — Bonding Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.7.2.2.1"></a><p class="title"><b>Table 51. </b></p> +<a name="id-1.3.3.7.2.2.1"></a><p class="title"><b>Table 53. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-bridge-port.html b/docs/api/html/settings-bridge-port.html index 7ab80feb..05b27bc4 100644 --- a/docs/api/html/settings-bridge-port.html +++ b/docs/api/html/settings-bridge-port.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>bridge-port</h2> -<p>bridge-port — Bridge Port Settings</p> +<p>bridge-port — Bridge Port Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.9.2.2.1"></a><p class="title"><b>Table 53. </b></p> +<a name="id-1.3.3.9.2.2.1"></a><p class="title"><b>Table 55. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-bridge.html b/docs/api/html/settings-bridge.html index b47077e9..27f4d555 100644 --- a/docs/api/html/settings-bridge.html +++ b/docs/api/html/settings-bridge.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>bridge</h2> -<p>bridge — Bridging Settings</p> +<p>bridge — Bridging Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.8.2.2.1"></a><p class="title"><b>Table 52. </b></p> +<a name="id-1.3.3.8.2.2.1"></a><p class="title"><b>Table 54. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-cdma.html b/docs/api/html/settings-cdma.html index c718232d..c579ce75 100644 --- a/docs/api/html/settings-cdma.html +++ b/docs/api/html/settings-cdma.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>cdma</h2> -<p>cdma — CDMA-based Mobile Broadband Settings</p> +<p>cdma — CDMA-based Mobile Broadband Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.10.2.2.1"></a><p class="title"><b>Table 54. </b></p> +<a name="id-1.3.3.10.2.2.1"></a><p class="title"><b>Table 56. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-connection.html b/docs/api/html/settings-connection.html index fd66ad01..47eb2f12 100644 --- a/docs/api/html/settings-connection.html +++ b/docs/api/html/settings-connection.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>connection</h2> -<p>connection — General Connection Profile Settings</p> +<p>connection — General Connection Profile Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.2.2.2.1"></a><p class="title"><b>Table 46. </b></p> +<a name="id-1.3.3.2.2.2.1"></a><p class="title"><b>Table 48. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-dcb.html b/docs/api/html/settings-dcb.html index f99db147..acaaf982 100644 --- a/docs/api/html/settings-dcb.html +++ b/docs/api/html/settings-dcb.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>dcb</h2> -<p>dcb — Data Center Bridging Settings</p> +<p>dcb — Data Center Bridging Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.11.2.2.1"></a><p class="title"><b>Table 55. </b></p> +<a name="id-1.3.3.11.2.2.1"></a><p class="title"><b>Table 57. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-dummy.html b/docs/api/html/settings-dummy.html index efdb69b3..f2929aab 100644 --- a/docs/api/html/settings-dummy.html +++ b/docs/api/html/settings-dummy.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>dummy</h2> -<p>dummy — Dummy Link Settings</p> +<p>dummy — Dummy Link Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.12.2.2.1"></a><p class="title"><b>Table 56. </b></p> +<a name="id-1.3.3.12.2.2.1"></a><p class="title"><b>Table 58. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-ethtool.html b/docs/api/html/settings-ethtool.html index 8f7d443b..35273827 100644 --- a/docs/api/html/settings-ethtool.html +++ b/docs/api/html/settings-ethtool.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ethtool</h2> -<p>ethtool — Ethtool Ethernet Settings</p> +<p>ethtool — Ethtool Ethernet Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.13.2.2.1"></a><p class="title"><b>Table 57. </b></p> +<a name="id-1.3.3.13.2.2.1"></a><p class="title"><b>Table 59. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-generic.html b/docs/api/html/settings-generic.html index efe5a89a..23ef5e04 100644 --- a/docs/api/html/settings-generic.html +++ b/docs/api/html/settings-generic.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>generic</h2> -<p>generic — Generic Link Settings</p> +<p>generic — Generic Link Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.14.2.2.1"></a><p class="title"><b>Table 58. </b></p> +<a name="id-1.3.3.14.2.2.1"></a><p class="title"><b>Table 60. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-gsm.html b/docs/api/html/settings-gsm.html index 2834c46d..0f57507e 100644 --- a/docs/api/html/settings-gsm.html +++ b/docs/api/html/settings-gsm.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>gsm</h2> -<p>gsm — GSM-based Mobile Broadband Settings</p> +<p>gsm — GSM-based Mobile Broadband Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.15.2.2.1"></a><p class="title"><b>Table 59. </b></p> +<a name="id-1.3.3.15.2.2.1"></a><p class="title"><b>Table 61. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-hostname.html b/docs/api/html/settings-hostname.html index d6110465..d12fcfba 100644 --- a/docs/api/html/settings-hostname.html +++ b/docs/api/html/settings-hostname.html @@ -7,7 +7,7 @@ <link rel="home" href="index.html" title="NetworkManager Reference Manual"> <link rel="up" href="ch01.html" title="Configuration Settings"> <link rel="prev" href="settings-bond-port.html" title="bond-port"> -<link rel="next" href="settings-ovs-external-ids.html" title="ovs-external-ids"> +<link rel="next" href="settings-loopback.html" title="loopback"> <meta name="generator" content="GTK-Doc V1.33.1 (XML mode)"> <link rel="stylesheet" href="style.css" type="text/css"> </head> @@ -22,14 +22,14 @@ <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> <td><a accesskey="u" href="ch01.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> <td><a accesskey="p" href="settings-bond-port.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> -<td><a accesskey="n" href="settings-ovs-external-ids.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> +<td><a accesskey="n" href="settings-loopback.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> </tr></table> <div class="refentry"> <a name="settings-hostname"></a><div class="titlepage"></div> <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>hostname</h2> -<p>hostname — Hostname settings</p> +<p>hostname — Hostname settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.51.2.2.1"></a><p class="title"><b>Table 95. </b></p> +<a name="id-1.3.3.51.2.2.1"></a><p class="title"><b>Table 97. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-infiniband.html b/docs/api/html/settings-infiniband.html index 317a26a5..6b509038 100644 --- a/docs/api/html/settings-infiniband.html +++ b/docs/api/html/settings-infiniband.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>infiniband</h2> -<p>infiniband — Infiniband Settings</p> +<p>infiniband — Infiniband Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.16.2.2.1"></a><p class="title"><b>Table 60. </b></p> +<a name="id-1.3.3.16.2.2.1"></a><p class="title"><b>Table 62. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-ip-tunnel.html b/docs/api/html/settings-ip-tunnel.html index cd464bac..4f35a153 100644 --- a/docs/api/html/settings-ip-tunnel.html +++ b/docs/api/html/settings-ip-tunnel.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ip-tunnel</h2> -<p>ip-tunnel — IP Tunneling Settings</p> +<p>ip-tunnel — IP Tunneling Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.19.2.2.1"></a><p class="title"><b>Table 63. </b></p> +<a name="id-1.3.3.19.2.2.1"></a><p class="title"><b>Table 65. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> @@ -72,6 +72,12 @@ <td> </td> </tr> <tr> +<td><pre class="screen">fwmark</pre></td> +<td><pre class="screen">uint32</pre></td> +<td><pre class="screen">0</pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">input-key</pre></td> <td><pre class="screen">string</pre></td> <td><pre class="screen"></pre></td> diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html index a933d551..24361ef7 100644 --- a/docs/api/html/settings-ipv4.html +++ b/docs/api/html/settings-ipv4.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ipv4</h2> -<p>ipv4 — IPv4 Settings</p> +<p>ipv4 — IPv4 Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.17.2.2.1"></a><p class="title"><b>Table 61. </b></p> +<a name="id-1.3.3.17.2.2.1"></a><p class="title"><b>Table 63. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> @@ -66,6 +66,12 @@ <td> </td> </tr> <tr> +<td><pre class="screen">auto-route-ext-gw</pre></td> +<td><pre class="screen">NMTernary (int32)</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">dad-timeout</pre></td> <td><pre class="screen">int32</pre></td> <td><pre class="screen">-1</pre></td> @@ -132,6 +138,12 @@ <td> </td> </tr> <tr> +<td><pre class="screen">dns-data</pre></td> +<td><pre class="screen">array of strings</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">dns-options</pre></td> <td><pre class="screen">array of string</pre></td> <td><pre class="screen"></pre></td> @@ -192,6 +204,12 @@ <td> </td> </tr> <tr> +<td><pre class="screen">replace-local-rule</pre></td> +<td><pre class="screen">NMTernary (int32)</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">required-timeout</pre></td> <td><pre class="screen">int32</pre></td> <td><pre class="screen">-1</pre></td> @@ -221,6 +239,12 @@ <td><pre class="screen"></pre></td> <td> </td> </tr> +<tr> +<td><pre class="screen">routing-rules</pre></td> +<td><pre class="screen">array of 'a{sv}'</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> </tbody> </table></div> </div> diff --git a/docs/api/html/settings-ipv6.html b/docs/api/html/settings-ipv6.html index b5ce52e6..776d231e 100644 --- a/docs/api/html/settings-ipv6.html +++ b/docs/api/html/settings-ipv6.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ipv6</h2> -<p>ipv6 — IPv6 Settings</p> +<p>ipv6 — IPv6 Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.18.2.2.1"></a><p class="title"><b>Table 62. </b></p> +<a name="id-1.3.3.18.2.2.1"></a><p class="title"><b>Table 64. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> @@ -72,6 +72,12 @@ <td> </td> </tr> <tr> +<td><pre class="screen">auto-route-ext-gw</pre></td> +<td><pre class="screen">NMTernary (int32)</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">dad-timeout</pre></td> <td><pre class="screen">int32</pre></td> <td><pre class="screen">-1</pre></td> @@ -126,6 +132,12 @@ <td> </td> </tr> <tr> +<td><pre class="screen">dns-data</pre></td> +<td><pre class="screen">array of strings</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">dns-options</pre></td> <td><pre class="screen">array of string</pre></td> <td><pre class="screen"></pre></td> @@ -198,6 +210,12 @@ <td> </td> </tr> <tr> +<td><pre class="screen">replace-local-rule</pre></td> +<td><pre class="screen">NMTernary (int32)</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">required-timeout</pre></td> <td><pre class="screen">int32</pre></td> <td><pre class="screen">-1</pre></td> @@ -228,6 +246,12 @@ <td> </td> </tr> <tr> +<td><pre class="screen">routing-rules</pre></td> +<td><pre class="screen">array of 'a{sv}'</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">token</pre></td> <td><pre class="screen">string</pre></td> <td><pre class="screen"></pre></td> diff --git a/docs/api/html/settings-loopback.html b/docs/api/html/settings-loopback.html new file mode 100644 index 00000000..05caf07c --- /dev/null +++ b/docs/api/html/settings-loopback.html @@ -0,0 +1,69 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> +<title>loopback: NetworkManager Reference Manual</title> +<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"> +<link rel="home" href="index.html" title="NetworkManager Reference Manual"> +<link rel="up" href="ch01.html" title="Configuration Settings"> +<link rel="prev" href="settings-hostname.html" title="hostname"> +<link rel="next" href="settings-ovs-external-ids.html" title="ovs-external-ids"> +<meta name="generator" content="GTK-Doc V1.33.1 (XML mode)"> +<link rel="stylesheet" href="style.css" type="text/css"> +</head> +<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> +<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle"> +<td width="100%" align="left" class="shortcuts"> +<a href="#" class="shortcut">Top</a><span id="nav_properties"> <span class="dim">|</span> + <a href="#settings-loopback.properties" class="shortcut"> + Properties + </a></span> +</td> +<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> +<td><a accesskey="u" href="ch01.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> +<td><a accesskey="p" href="settings-hostname.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> +<td><a accesskey="n" href="settings-ovs-external-ids.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> +</tr></table> +<div class="refentry"> +<a name="settings-loopback"></a><div class="titlepage"></div> +<div class="refnamediv"><table width="100%"><tr> +<td valign="top"> +<h2>loopback</h2> +<p>loopback — Loopback Link Settings</p> +</td> +<td class="gallery_image" valign="top" align="right"></td> +</tr></table></div> +<div class="refsect1"> +<a name="id-1.3.3.52.2"></a><h2> + Properties + </h2> +<div class="table"> +<a name="id-1.3.3.52.2.2.1"></a><p class="title"><b>Table 98. </b></p> +<div class="table-contents"><table class="table" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Key Name</th> +<th>Value Type</th> +<th>Default Value</th> +<th>Value Description</th> +</tr></thead> +<tbody><tr> +<td><pre class="screen">mtu</pre></td> +<td><pre class="screen">uint32</pre></td> +<td><pre class="screen">0</pre></td> +<td> </td> +</tr></tbody> +</table></div> +</div> +<p><br class="table-break"></p> +</div> +</div> +<div class="footer"> +<hr>Generated by GTK-Doc V1.33.1</div> +</body> +</html> \ No newline at end of file diff --git a/docs/api/html/settings-macsec.html b/docs/api/html/settings-macsec.html index 72e103d0..6b19558f 100644 --- a/docs/api/html/settings-macsec.html +++ b/docs/api/html/settings-macsec.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>macsec</h2> -<p>macsec — MACSec Settings</p> +<p>macsec — MACSec Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.20.2.2.1"></a><p class="title"><b>Table 64. </b></p> +<a name="id-1.3.3.20.2.2.1"></a><p class="title"><b>Table 66. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-macvlan.html b/docs/api/html/settings-macvlan.html index aec99676..645bee54 100644 --- a/docs/api/html/settings-macvlan.html +++ b/docs/api/html/settings-macvlan.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>macvlan</h2> -<p>macvlan — MAC VLAN Settings</p> +<p>macvlan — MAC VLAN Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.21.2.2.1"></a><p class="title"><b>Table 65. </b></p> +<a name="id-1.3.3.21.2.2.1"></a><p class="title"><b>Table 67. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-match.html b/docs/api/html/settings-match.html index 2c483f94..916d91ef 100644 --- a/docs/api/html/settings-match.html +++ b/docs/api/html/settings-match.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>match</h2> -<p>match — Match settings</p> +<p>match — Match settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.22.2.2.1"></a><p class="title"><b>Table 66. </b></p> +<a name="id-1.3.3.22.2.2.1"></a><p class="title"><b>Table 68. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-ovs-bridge.html b/docs/api/html/settings-ovs-bridge.html index 6977650b..24b481f6 100644 --- a/docs/api/html/settings-ovs-bridge.html +++ b/docs/api/html/settings-ovs-bridge.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ovs-bridge</h2> -<p>ovs-bridge — OvsBridge Link Settings</p> +<p>ovs-bridge — OvsBridge Link Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.24.2.2.1"></a><p class="title"><b>Table 68. </b></p> +<a name="id-1.3.3.24.2.2.1"></a><p class="title"><b>Table 70. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-ovs-dpdk.html b/docs/api/html/settings-ovs-dpdk.html index 959b44c1..bbd4d878 100644 --- a/docs/api/html/settings-ovs-dpdk.html +++ b/docs/api/html/settings-ovs-dpdk.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ovs-dpdk</h2> -<p>ovs-dpdk — OvsDpdk Link Settings</p> +<p>ovs-dpdk — OvsDpdk Link Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.25.2.2.1"></a><p class="title"><b>Table 69. </b></p> +<a name="id-1.3.3.25.2.2.1"></a><p class="title"><b>Table 71. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> @@ -65,6 +65,18 @@ <td><pre class="screen">0</pre></td> <td> </td> </tr> +<tr> +<td><pre class="screen">n-rxq-desc</pre></td> +<td><pre class="screen">uint32</pre></td> +<td><pre class="screen">0</pre></td> +<td> </td> +</tr> +<tr> +<td><pre class="screen">n-txq-desc</pre></td> +<td><pre class="screen">uint32</pre></td> +<td><pre class="screen">0</pre></td> +<td> </td> +</tr> </tbody> </table></div> </div> diff --git a/docs/api/html/settings-ovs-external-ids.html b/docs/api/html/settings-ovs-external-ids.html index 21de0dc0..c41f7ba5 100644 --- a/docs/api/html/settings-ovs-external-ids.html +++ b/docs/api/html/settings-ovs-external-ids.html @@ -6,8 +6,8 @@ <meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"> <link rel="home" href="index.html" title="NetworkManager Reference Manual"> <link rel="up" href="ch01.html" title="Configuration Settings"> -<link rel="prev" href="settings-hostname.html" title="hostname"> -<link rel="next" href="settings-veth.html" title="veth"> +<link rel="prev" href="settings-loopback.html" title="loopback"> +<link rel="next" href="settings-ovs-other-config.html" title="ovs-other-config"> <meta name="generator" content="GTK-Doc V1.33.1 (XML mode)"> <link rel="stylesheet" href="style.css" type="text/css"> </head> @@ -21,24 +21,24 @@ </td> <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> <td><a accesskey="u" href="ch01.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> -<td><a accesskey="p" href="settings-hostname.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> -<td><a accesskey="n" href="settings-veth.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> +<td><a accesskey="p" href="settings-loopback.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> +<td><a accesskey="n" href="settings-ovs-other-config.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> </tr></table> <div class="refentry"> <a name="settings-ovs-external-ids"></a><div class="titlepage"></div> <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ovs-external-ids</h2> -<p>ovs-external-ids — OVS External IDs Settings</p> +<p>ovs-external-ids — OVS External IDs Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.3.3.52.2"></a><h2> +<a name="id-1.3.3.53.2"></a><h2> Properties </h2> <div class="table"> -<a name="id-1.3.3.52.2.2.1"></a><p class="title"><b>Table 96. </b></p> +<a name="id-1.3.3.53.2.2.1"></a><p class="title"><b>Table 99. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-ovs-interface.html b/docs/api/html/settings-ovs-interface.html index 22dc57f7..c1dabd02 100644 --- a/docs/api/html/settings-ovs-interface.html +++ b/docs/api/html/settings-ovs-interface.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ovs-interface</h2> -<p>ovs-interface — Open vSwitch Interface Settings</p> +<p>ovs-interface — Open vSwitch Interface Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.26.2.2.1"></a><p class="title"><b>Table 70. </b></p> +<a name="id-1.3.3.26.2.2.1"></a><p class="title"><b>Table 72. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> @@ -52,12 +52,20 @@ <th>Default Value</th> <th>Value Description</th> </tr></thead> -<tbody><tr> +<tbody> +<tr> +<td><pre class="screen">ofport-request</pre></td> +<td><pre class="screen">uint32</pre></td> +<td><pre class="screen">0</pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">type</pre></td> <td><pre class="screen">string</pre></td> <td><pre class="screen"></pre></td> <td> </td> -</tr></tbody> +</tr> +</tbody> </table></div> </div> <p><br class="table-break"></p> diff --git a/docs/api/html/settings-ovs-other-config.html b/docs/api/html/settings-ovs-other-config.html new file mode 100644 index 00000000..5b3c728e --- /dev/null +++ b/docs/api/html/settings-ovs-other-config.html @@ -0,0 +1,69 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> +<title>ovs-other-config: NetworkManager Reference Manual</title> +<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"> +<link rel="home" href="index.html" title="NetworkManager Reference Manual"> +<link rel="up" href="ch01.html" title="Configuration Settings"> +<link rel="prev" href="settings-ovs-external-ids.html" title="ovs-external-ids"> +<link rel="next" href="settings-veth.html" title="veth"> +<meta name="generator" content="GTK-Doc V1.33.1 (XML mode)"> +<link rel="stylesheet" href="style.css" type="text/css"> +</head> +<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> +<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle"> +<td width="100%" align="left" class="shortcuts"> +<a href="#" class="shortcut">Top</a><span id="nav_properties"> <span class="dim">|</span> + <a href="#settings-ovs-other-config.properties" class="shortcut"> + Properties + </a></span> +</td> +<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> +<td><a accesskey="u" href="ch01.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> +<td><a accesskey="p" href="settings-ovs-external-ids.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> +<td><a accesskey="n" href="settings-veth.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> +</tr></table> +<div class="refentry"> +<a name="settings-ovs-other-config"></a><div class="titlepage"></div> +<div class="refnamediv"><table width="100%"><tr> +<td valign="top"> +<h2>ovs-other-config</h2> +<p>ovs-other-config — OVS Other Config Settings</p> +</td> +<td class="gallery_image" valign="top" align="right"></td> +</tr></table></div> +<div class="refsect1"> +<a name="id-1.3.3.54.2"></a><h2> + Properties + </h2> +<div class="table"> +<a name="id-1.3.3.54.2.2.1"></a><p class="title"><b>Table 100. </b></p> +<div class="table-contents"><table class="table" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Key Name</th> +<th>Value Type</th> +<th>Default Value</th> +<th>Value Description</th> +</tr></thead> +<tbody><tr> +<td><pre class="screen">data</pre></td> +<td><pre class="screen">dict of string to string</pre></td> +<td><pre class="screen">{}</pre></td> +<td> </td> +</tr></tbody> +</table></div> +</div> +<p><br class="table-break"></p> +</div> +</div> +<div class="footer"> +<hr>Generated by GTK-Doc V1.33.1</div> +</body> +</html> \ No newline at end of file diff --git a/docs/api/html/settings-ovs-patch.html b/docs/api/html/settings-ovs-patch.html index f5e5990f..1abb2211 100644 --- a/docs/api/html/settings-ovs-patch.html +++ b/docs/api/html/settings-ovs-patch.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ovs-patch</h2> -<p>ovs-patch — OvsPatch Link Settings</p> +<p>ovs-patch — OvsPatch Link Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.27.2.2.1"></a><p class="title"><b>Table 71. </b></p> +<a name="id-1.3.3.27.2.2.1"></a><p class="title"><b>Table 73. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-ovs-port.html b/docs/api/html/settings-ovs-port.html index 736c7923..35f828c5 100644 --- a/docs/api/html/settings-ovs-port.html +++ b/docs/api/html/settings-ovs-port.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ovs-port</h2> -<p>ovs-port — OvsPort Link Settings</p> +<p>ovs-port — OvsPort Link Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.28.2.2.1"></a><p class="title"><b>Table 72. </b></p> +<a name="id-1.3.3.28.2.2.1"></a><p class="title"><b>Table 74. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> @@ -84,6 +84,12 @@ <td> </td> </tr> <tr> +<td><pre class="screen">trunks</pre></td> +<td><pre class="screen">array of vardict</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> +<tr> <td><pre class="screen">vlan-mode</pre></td> <td><pre class="screen">string</pre></td> <td><pre class="screen"></pre></td> diff --git a/docs/api/html/settings-ppp.html b/docs/api/html/settings-ppp.html index 62f673d9..baf53247 100644 --- a/docs/api/html/settings-ppp.html +++ b/docs/api/html/settings-ppp.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>ppp</h2> -<p>ppp — Point-to-Point Protocol Settings</p> +<p>ppp — Point-to-Point Protocol Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.29.2.2.1"></a><p class="title"><b>Table 73. </b></p> +<a name="id-1.3.3.29.2.2.1"></a><p class="title"><b>Table 75. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-pppoe.html b/docs/api/html/settings-pppoe.html index 8d36c318..5cfac707 100644 --- a/docs/api/html/settings-pppoe.html +++ b/docs/api/html/settings-pppoe.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>pppoe</h2> -<p>pppoe — PPP-over-Ethernet Settings</p> +<p>pppoe — PPP-over-Ethernet Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.30.2.2.1"></a><p class="title"><b>Table 74. </b></p> +<a name="id-1.3.3.30.2.2.1"></a><p class="title"><b>Table 76. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-proxy.html b/docs/api/html/settings-proxy.html index d49e6fbd..5a28d81a 100644 --- a/docs/api/html/settings-proxy.html +++ b/docs/api/html/settings-proxy.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>proxy</h2> -<p>proxy — WWW Proxy Settings</p> +<p>proxy — WWW Proxy Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.31.2.2.1"></a><p class="title"><b>Table 75. </b></p> +<a name="id-1.3.3.31.2.2.1"></a><p class="title"><b>Table 77. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-serial.html b/docs/api/html/settings-serial.html index 9112980b..70dfcbc3 100644 --- a/docs/api/html/settings-serial.html +++ b/docs/api/html/settings-serial.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>serial</h2> -<p>serial — Serial Link Settings</p> +<p>serial — Serial Link Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.32.2.2.1"></a><p class="title"><b>Table 76. </b></p> +<a name="id-1.3.3.32.2.2.1"></a><p class="title"><b>Table 78. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-sriov.html b/docs/api/html/settings-sriov.html index 9000defc..62f7e68a 100644 --- a/docs/api/html/settings-sriov.html +++ b/docs/api/html/settings-sriov.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>sriov</h2> -<p>sriov — SR-IOV settings</p> +<p>sriov — SR-IOV settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.33.2.2.1"></a><p class="title"><b>Table 77. </b></p> +<a name="id-1.3.3.33.2.2.1"></a><p class="title"><b>Table 79. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-tc.html b/docs/api/html/settings-tc.html index dc1b3765..d83d148a 100644 --- a/docs/api/html/settings-tc.html +++ b/docs/api/html/settings-tc.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>tc</h2> -<p>tc — Linux Traffic Control Settings</p> +<p>tc — Linux Traffic Control Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.34.2.2.1"></a><p class="title"><b>Table 78. </b></p> +<a name="id-1.3.3.34.2.2.1"></a><p class="title"><b>Table 80. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-team-port.html b/docs/api/html/settings-team-port.html index c8d05d09..333d7677 100644 --- a/docs/api/html/settings-team-port.html +++ b/docs/api/html/settings-team-port.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>team-port</h2> -<p>team-port — Team Port Settings</p> +<p>team-port — Team Port Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.36.2.2.1"></a><p class="title"><b>Table 80. </b></p> +<a name="id-1.3.3.36.2.2.1"></a><p class="title"><b>Table 82. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-team.html b/docs/api/html/settings-team.html index 2a572ac5..640185f6 100644 --- a/docs/api/html/settings-team.html +++ b/docs/api/html/settings-team.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>team</h2> -<p>team — Teaming Settings</p> +<p>team — Teaming Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.35.2.2.1"></a><p class="title"><b>Table 79. </b></p> +<a name="id-1.3.3.35.2.2.1"></a><p class="title"><b>Table 81. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-tun.html b/docs/api/html/settings-tun.html index 10fdbfb8..3691e124 100644 --- a/docs/api/html/settings-tun.html +++ b/docs/api/html/settings-tun.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>tun</h2> -<p>tun — Tunnel Settings</p> +<p>tun — Tunnel Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.37.2.2.1"></a><p class="title"><b>Table 81. </b></p> +<a name="id-1.3.3.37.2.2.1"></a><p class="title"><b>Table 83. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-user.html b/docs/api/html/settings-user.html index 66a8248d..8ce10de8 100644 --- a/docs/api/html/settings-user.html +++ b/docs/api/html/settings-user.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>user</h2> -<p>user — General User Profile Settings</p> +<p>user — General User Profile Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.38.2.2.1"></a><p class="title"><b>Table 82. </b></p> +<a name="id-1.3.3.38.2.2.1"></a><p class="title"><b>Table 84. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-veth.html b/docs/api/html/settings-veth.html index 4a8a8213..d045edae 100644 --- a/docs/api/html/settings-veth.html +++ b/docs/api/html/settings-veth.html @@ -6,7 +6,7 @@ <meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"> <link rel="home" href="index.html" title="NetworkManager Reference Manual"> <link rel="up" href="ch01.html" title="Configuration Settings"> -<link rel="prev" href="settings-ovs-external-ids.html" title="ovs-external-ids"> +<link rel="prev" href="settings-ovs-other-config.html" title="ovs-other-config"> <link rel="next" href="secrets-flags.html" title="Secret flag types"> <meta name="generator" content="GTK-Doc V1.33.1 (XML mode)"> <link rel="stylesheet" href="style.css" type="text/css"> @@ -21,7 +21,7 @@ </td> <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> <td><a accesskey="u" href="ch01.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> -<td><a accesskey="p" href="settings-ovs-external-ids.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> +<td><a accesskey="p" href="settings-ovs-other-config.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> <td><a accesskey="n" href="secrets-flags.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> </tr></table> <div class="refentry"> @@ -29,16 +29,16 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>veth</h2> -<p>veth — Veth Settings</p> +<p>veth — Veth Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> <div class="refsect1"> -<a name="id-1.3.3.53.2"></a><h2> +<a name="id-1.3.3.55.2"></a><h2> Properties </h2> <div class="table"> -<a name="id-1.3.3.53.2.2.1"></a><p class="title"><b>Table 97. </b></p> +<a name="id-1.3.3.55.2.2.1"></a><p class="title"><b>Table 101. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-vlan.html b/docs/api/html/settings-vlan.html index 2f10e0c2..5a310346 100644 --- a/docs/api/html/settings-vlan.html +++ b/docs/api/html/settings-vlan.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>vlan</h2> -<p>vlan — VLAN Settings</p> +<p>vlan — VLAN Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.39.2.2.1"></a><p class="title"><b>Table 83. </b></p> +<a name="id-1.3.3.39.2.2.1"></a><p class="title"><b>Table 85. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> @@ -89,6 +89,12 @@ <td><pre class="screen"></pre></td> <td> </td> </tr> +<tr> +<td><pre class="screen">protocol</pre></td> +<td><pre class="screen">string</pre></td> +<td><pre class="screen"></pre></td> +<td> </td> +</tr> </tbody> </table></div> </div> diff --git a/docs/api/html/settings-vpn.html b/docs/api/html/settings-vpn.html index cdd8c3ad..bb452283 100644 --- a/docs/api/html/settings-vpn.html +++ b/docs/api/html/settings-vpn.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>vpn</h2> -<p>vpn — VPN Settings</p> +<p>vpn — VPN Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.40.2.2.1"></a><p class="title"><b>Table 84. </b></p> +<a name="id-1.3.3.40.2.2.1"></a><p class="title"><b>Table 86. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-vrf.html b/docs/api/html/settings-vrf.html index f0472049..e23ce0bc 100644 --- a/docs/api/html/settings-vrf.html +++ b/docs/api/html/settings-vrf.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>vrf</h2> -<p>vrf — VRF settings</p> +<p>vrf — VRF settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.41.2.2.1"></a><p class="title"><b>Table 85. </b></p> +<a name="id-1.3.3.41.2.2.1"></a><p class="title"><b>Table 87. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-vxlan.html b/docs/api/html/settings-vxlan.html index c099f710..c00e3c0d 100644 --- a/docs/api/html/settings-vxlan.html +++ b/docs/api/html/settings-vxlan.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>vxlan</h2> -<p>vxlan — VXLAN Settings</p> +<p>vxlan — VXLAN Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.42.2.2.1"></a><p class="title"><b>Table 86. </b></p> +<a name="id-1.3.3.42.2.2.1"></a><p class="title"><b>Table 88. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-wifi-p2p.html b/docs/api/html/settings-wifi-p2p.html index cae67981..566e1109 100644 --- a/docs/api/html/settings-wifi-p2p.html +++ b/docs/api/html/settings-wifi-p2p.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>wifi-p2p</h2> -<p>wifi-p2p — Wi-Fi P2P Settings</p> +<p>wifi-p2p — Wi-Fi P2P Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.43.2.2.1"></a><p class="title"><b>Table 87. </b></p> +<a name="id-1.3.3.43.2.2.1"></a><p class="title"><b>Table 89. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-wimax.html b/docs/api/html/settings-wimax.html index d4748205..770a44a8 100644 --- a/docs/api/html/settings-wimax.html +++ b/docs/api/html/settings-wimax.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>wimax</h2> -<p>wimax — WiMax Settings</p> +<p>wimax — WiMax Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.44.2.2.1"></a><p class="title"><b>Table 88. </b></p> +<a name="id-1.3.3.44.2.2.1"></a><p class="title"><b>Table 90. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-wireguard.html b/docs/api/html/settings-wireguard.html index 88dc36c2..c5c3fe23 100644 --- a/docs/api/html/settings-wireguard.html +++ b/docs/api/html/settings-wireguard.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>wireguard</h2> -<p>wireguard — WireGuard Settings</p> +<p>wireguard — WireGuard Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.46.2.2.1"></a><p class="title"><b>Table 90. </b></p> +<a name="id-1.3.3.46.2.2.1"></a><p class="title"><b>Table 92. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/settings-wpan.html b/docs/api/html/settings-wpan.html index 83aeb13f..f6560737 100644 --- a/docs/api/html/settings-wpan.html +++ b/docs/api/html/settings-wpan.html @@ -29,7 +29,7 @@ <div class="refnamediv"><table width="100%"><tr> <td valign="top"> <h2>wpan</h2> -<p>wpan — IEEE 802.15.4 (WPAN) MAC Settings</p> +<p>wpan — IEEE 802.15.4 (WPAN) MAC Settings</p> </td> <td class="gallery_image" valign="top" align="right"></td> </tr></table></div> @@ -38,7 +38,7 @@ Properties </h2> <div class="table"> -<a name="id-1.3.3.49.2.2.1"></a><p class="title"><b>Table 93. </b></p> +<a name="id-1.3.3.49.2.2.1"></a><p class="title"><b>Table 95. </b></p> <div class="table-contents"><table class="table" border="1"> <colgroup> <col> diff --git a/docs/api/html/spec.html b/docs/api/html/spec.html index 8de008d9..a4ec537b 100644 --- a/docs/api/html/spec.html +++ b/docs/api/html/spec.html @@ -78,6 +78,9 @@ <span class="refentrytitle"><a href="gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html">org.freedesktop.NetworkManager.Device.Infiniband</a></span><span class="refpurpose"> — Infiniband Device.</span> </dt> <dt> +<span class="refentrytitle"><a href="gdbus-org.freedesktop.NetworkManager.Device.Loopback.html">org.freedesktop.NetworkManager.Device.Loopback</a></span><span class="refpurpose"> — Loopback Device.</span> +</dt> +<dt> <span class="refentrytitle"><a href="gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html">org.freedesktop.NetworkManager.Device.Lowpan</a></span><span class="refpurpose"> — 6LoWPAN Device.</span> </dt> <dt> |