diff options
Diffstat (limited to 'docs/api/html/nm-settings-dbus.html')
| -rw-r--r-- | docs/api/html/nm-settings-dbus.html | 60 |
1 files changed, 57 insertions, 3 deletions
diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index 9f5c9842..52539c2e 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -137,8 +137,8 @@ Depending on "connection.multi-connect", a profile can (auto)connect only once a <tr> <td align="left"> <a name="nm-settings-dbus.property.connection.autoconnect-ports"></a>autoconnect-ports</td> -<td align="left">NMTernary (int32)</td> -<td align="left"> </td> +<td align="left">int32</td> +<td align="left">-1</td> <td>Whether or not ports of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for controller connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave port connections untouched, 1: activate all the port connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-ports is read to determine the real value. If it is default as well, this fallbacks to 0.</td> </tr> <tr> @@ -1475,7 +1475,17 @@ Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was reject <th>Default Value</th> <th>Value Description</th> </tr></thead> -<tbody></tbody> +<tbody><tr> +<td align="left"> +<a name="nm-settings-dbus.property.generic.device-handler"></a>device-handler</td> +<td align="left">string</td> +<td align="left"> </td> +<td>Name of the device handler that will be invoked to add and delete the device for this connection. The name can only contain ASCII alphanumeric characters and '-', '_', '.'. It cannot start with '.'. + +See the NetworkManager-dispatcher(8) man page for more details about how to write the device handler. + +By setting this property the generic connection becomes "virtual", meaning that it can be activated without an existing device; the device will be created at the time the connection is started by invoking the device-handler.</td> +</tr></tbody> </table></div> </div> <hr> @@ -2570,6 +2580,19 @@ When set, the token is used as IPv6 interface identifier instead of the hardware </tr> <tr> <td align="left"> +<a name="nm-settings-dbus.property.macsec.offload"></a>offload</td> +<td align="left">int32</td> +<td align="left">-1</td> +<td>Specifies the MACsec offload mode. + +0 (off) disables MACsec offload. + +1 (phy) and 2 (mac) request offload respectively to the PHY or to the MAC; if the selected mode is not available, the connection will fail. + +-1 (default) uses the global default value specified in NetworkManager configuration; if no global default is defined, the built-in default is 0 (off).</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> @@ -3334,6 +3357,37 @@ When set to -1 (default), the global default is used; in case the global default </tr> <tr> <td align="left"> +<a name="nm-settings-dbus.property.sriov.eswitch-encap-mode"></a>eswitch-encap-mode</td> +<td align="left">int32</td> +<td align="left">-1</td> +<td>Select the eswitch encapsulation support. + +Currently it's only supported for PCI PF devices, and only if the eswitch device is managed from the same PCI address than the PF. + +If set to -1 (preserve) (default) the eswitch encap-mode won't be modified by NetworkManager.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.sriov.eswitch-inline-mode"></a>eswitch-inline-mode</td> +<td align="left">int32</td> +<td align="left">-1</td> +<td>Select the eswitch inline-mode of the device. Some HWs need the VF driver to put part of the packet headers on the TX descriptor so the e-switch can do proper matching and steering. + +Currently it's only supported for PCI PF devices, and only if the eswitch device is managed from the same PCI address than the PF. + +If set to -1 (preserve) (default) the eswitch inline-mode won't be modified by NetworkManager.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings-dbus.property.sriov.eswitch-mode"></a>eswitch-mode</td> +<td align="left">int32</td> +<td align="left">-1</td> +<td>Select the eswitch mode of the device. Currently it's only supported for PCI PF devices, and only if the eswitch device is managed from the same PCI address than the PF. + +If set to -1 (preserve) (default) the eswitch mode won't be modified by NetworkManager.</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> |