Options controlling connectivity checking, such as the servers to
attempt to reach to determine if there is a working path to the global
Allowed child options:
Settings for connectivity checking. The connectivity check proceeds in three phases: resolving connectivity check addresses, pinging connectivity check addresses, and simultaneously pinging and attempting HTTP connections to connectivity check addresses. As the UI does not normally allow you to use DNS names as connectivity check addresses, the resolve phase time can be ignored in most cases. The time for the ping phase can be reduced to zero if you would like to immediately check HTTP in addition to ICMP, but be aware of the bandwidth overhead of retrieving HTTP responses on very limited lines. If you have a very slow network and are losing connectivity more often than you think you should, try raising the mixed phase time here. Avoid raising it too high as it can increase the time it takes to bring an interface back up.
Resolve Phase Time unsigned int:
maximum seconds to spend attempting to resolve connectivity check addresses
Ping Phase Time unsigned int:
maximum seconds to spend only attempting ICMP ping to the connectivity check addresses
Mixed Phase Time unsigned int:
maximum seconds to spend attempting ICMP ping and HTTP connections simultaneously to the connectivity check addresses; this occurs only if the ping phase was unsuccessful
List of IP addresses of servers to attempt to reach in order to check for connectivity with the global internet.