Line 361: |
Line 361: |
| <tr> | | <tr> |
| <td>Health monitor interval</td> | | <td>Health monitor interval</td> |
− | <td>Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec.; default: '''10 sec.'''</td> | + | <td>Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec.; default: <b>5 sec.</b></td> |
− | <td>The interval at which health checks are performed</td> | + | <td>The interval at which health checks are performed.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Health monitor ICMP host(s)</td> | | <td>Health monitor ICMP host(s)</td> |
− | <td>ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; default: '''8.8.4.4'''</td> | + | <td>ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; default: <b>8.8.8.8</b></td> |
− | <td>Indicate where to send ping requests for a health check. As there is no definitive way to determine when the connection to internet is down for good, it is best to define a host whose availability is that of the internet as a whole (e.g., 8.8.8.8, 8.8.4.4)</td> | + | <td>Indicate where to send ping requests for a health check. As there is no definitive way to determine when the connection to internet is down for good, it is best to define a host whose availability is that of the internet as a whole (e.g., 8.8.8.8, 8.8.4.4).</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Health monitor ICMP timeout</td> | | <td>Health monitor ICMP timeout</td> |
− | <td>1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec.; default: '''3 sec.'''</td> | + | <td>1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec.; default: <b>1 sec.</b></td> |
− | <td>The frequency at which ICMP requests are to be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes)</td> | + | <td>The frequency at which ICMP requests will be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes).</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Attempts before failover</td> | | <td>Attempts before failover</td> |
− | <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: '''3'''</td> | + | <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: <b>3</b></td> |
− | <td>The number of failed ping attempts after which the connection is to be declared as “'''down'''” </td> | + | <td>The number of failed ping attempts before the connection is to be declared as "down". </td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Attempts before recovery</td> | | <td>Attempts before recovery</td> |
− | <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: '''3'''</td> | + | <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: <b>3</b></td> |
− | <td>The number of successful ping attempts after which the connection is to be declared as “'''up'''”</td> | + | <td>The number of successful ping attempts before the connection is to be declared as "up".</td> |
| + | </tr> |
| + | <tr> |
| + | <td>Execute command</td> |
| + | <td>yes {{!}} no; default: <b>no</b></td> |
| + | <td>Executes a user specified command when the WAN fails over to this interface.</td> |
| + | </tr> |
| + | <tr> |
| + | <td>Command</td> |
| + | <td>string; default: <b>none</b></td> |
| + | <td>A command that will executed when the WAN fails over to this interface.</td> |
| </tr> | | </tr> |
| </table> | | </table> |