From cfb80376641fa49137b9996130352697e7f8b436 Mon Sep 17 00:00:00 2001 From: Sebastien Bacher Date: Wed, 25 Aug 2021 15:23:22 +0200 Subject: New upstream version 1.32.10 --- docs/api/html/settings-ipv4.html | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'docs/api/html/settings-ipv4.html') diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html index 63ef91f4..4f91166b 100644 --- a/docs/api/html/settings-ipv4.html +++ b/docs/api/html/settings-ipv4.html @@ -8,7 +8,7 @@ - + @@ -186,6 +186,12 @@ 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. +

required-timeout

int32

-1

+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). + +

route-data

array of vardict

@@ -216,6 +222,6 @@ +

Generated by GTK-Doc V1.33.0 \ No newline at end of file -- cgit 1.3.0-6-gf8a5