diff options
Diffstat (limited to 'docs/api/html/settings-ipv6.html')
| -rw-r--r-- | docs/api/html/settings-ipv6.html | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/api/html/settings-ipv6.html b/docs/api/html/settings-ipv6.html index 1680a5a2..62a1be5a 100644 --- a/docs/api/html/settings-ipv6.html +++ b/docs/api/html/settings-ipv6.html @@ -192,6 +192,12 @@ <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> </tr> <tr> +<td><pre class="screen">required-timeout</pre></td> +<td><pre class="screen">int32</pre></td> +<td><pre class="screen">-1</pre></td> +<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. 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> +</tr> +<tr> <td><pre class="screen">route-data</pre></td> <td><pre class="screen">array of vardict</pre></td> <td><pre class="screen"></pre></td> |