diff options
Diffstat (limited to 'docs/api/html/nm-settings-ifcfg-rh.html')
| -rw-r--r-- | docs/api/html/nm-settings-ifcfg-rh.html | 35 |
1 files changed, 32 insertions, 3 deletions
diff --git a/docs/api/html/nm-settings-ifcfg-rh.html b/docs/api/html/nm-settings-ifcfg-rh.html index 390509ad..8189a493 100644 --- a/docs/api/html/nm-settings-ifcfg-rh.html +++ b/docs/api/html/nm-settings-ifcfg-rh.html @@ -1143,6 +1143,15 @@ Allowed values: </strong></span>yes,no,resolve</td> Allowed values: </strong></span>yes,no,opportunistic</td> </tr> <tr> +<td align="left">mptcp-flags</td> +<td align="left">MPTCP_FLAGS<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left">missing variable means global default</td> +<td align="left">The MPTCP flags that indicate whether MPTCP is enabled and which flags to use for the address endpoints.<span class="bold"><strong> + +Example: </strong></span>MPTCP_FLAGS="signal,subflow"</td> +</tr> +<tr> <td align="left">wait-device-timeout</td> <td align="left">DEVTIMEOUT<span class="emphasis"><em>(+)</em></span> </td> @@ -1163,6 +1172,17 @@ Example: </strong></span>https://yourdevice.example.com/model.json<span class="b Allowed values: </strong></span>a valid URL that points to recommended policy for this device</td> </tr> +<tr> +<td align="left">wait-activation-delay</td> +<td align="left">WAIT_ACTIVATION_DELAY<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.<span class="bold"><strong> + +Example: </strong></span>WAIT_ACTIVATION_DELAY=5000<span class="bold"><strong> + +Allowed values: </strong></span>delay in milliseconds.</td> +</tr> </tbody> </table></div> </div> @@ -1603,6 +1623,15 @@ Example: </strong></span>DHCP_FQDN=foo.bar.com</td> Example: </strong></span>DHCP_VENDOR_CLASS_IDENTIFIER=foo</td> </tr> +<tr> +<td align="left">link-local</td> +<td align="left">IPV4_LINK_LOCAL<span class="emphasis"><em>(+)</em></span> +</td> +<td align="left"> </td> +<td align="left">Configure link-local IP address in interaction with method<span class="bold"><strong> + +Example: </strong></span>IPV4_LINK_LOCAL=auto</td> +</tr> </tbody> </table></div> </div> @@ -1759,12 +1788,12 @@ Allowed values: </strong></span>IPV6_PRIVACY: no, yes (rfc3041 or rfc4941); IPV6 <tr> <td align="left">addr-gen-mode</td> <td align="left">IPV6_ADDR_GEN_MODE</td> -<td align="left">eui64</td> +<td align="left">"default-or-eui64"</td> <td align="left">Configure IPv6 Stable Privacy addressing for SLAAC (RFC7217).<span class="bold"><strong> Example: </strong></span>IPV6_ADDR_GEN_MODE=stable-privacy<span class="bold"><strong> -Allowed values: </strong></span>IPV6_ADDR_GEN_MODE: eui64, stable-privacy</td> +Allowed values: </strong></span>IPV6_ADDR_GEN_MODE: default, default-or-eui64, eui64, stable-privacy</td> </tr> <tr> <td align="left">token</td> @@ -2754,7 +2783,7 @@ Allowed values: </strong></span>"yes", "no"</td> <p> Each secret property in a NetworkManager setting has an associated <span class="emphasis"><em>flags</em></span> property that describes how to handle that secret. - In the <span class="emphasis"><em>fcfg-rh</em></span> plugin variables for secret flags have a + In the <span class="emphasis"><em>ifcfg-rh</em></span> plugin variables for secret flags have a <span class="emphasis"><em>_FLAGS</em></span> suffix. The variables contain one or more of the following values (space separated). Missing (or empty) *_FLAGS variable means that the password is owned by NetworkManager. |