Difference between revisions of "Template:Networking rut manual auto reboot"
Gytispieze (talk | contribs) m (Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}") |
(Created page with "==Summary== Various automatic router reboot scenarios can be configured in the <b>Auto Reboot</b> section. Automatic reboots can be used as a prophylactic or precautionary me...") |
||
(55 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Summary== | ==Summary== | ||
− | Various automatic router reboot scenarios can be configured in the <b>Auto Reboot</b> | + | Various automatic router reboot scenarios can be configured in the <b>Auto Reboot</b> section. Automatic reboots can be used as a prophylactic or precautionary measure that ensures the device will self-correct some unexpected issues, especially related to connection downtime. |
− | |||
− | |||
==Ping Reboot== | ==Ping Reboot== | ||
Line 17: | Line 7: | ||
The <b>Ping Reboot</b> function periodically sends Ping commands to a specified IP address and wait for received responses. If no response is received, the device will send Ping commands a defined number of times at a defined frequency. If no response is received after the defined number of unsuccessful retries, the device will commit the specified action (reboot, by default). | The <b>Ping Reboot</b> function periodically sends Ping commands to a specified IP address and wait for received responses. If no response is received, the device will send Ping commands a defined number of times at a defined frequency. If no response is received after the defined number of unsuccessful retries, the device will commit the specified action (reboot, by default). | ||
− | The Ping Reboot section contains one | + | The Ping Reboot section contains one preconfigured rule by default. The figure below is an example of that rule and the table below provides information on the fields that make up that rule: |
− | [[File: | + | [[File:{{{file_ping_reboot}}}]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
− | <th> | + | <th>field name</th> |
− | <th> | + | <th>value</th> |
− | <th> | + | <th>description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 62: | Line 52: | ||
<td>host | ip; Default: <b>8.8.8.8</b></td> | <td>host | ip; Default: <b>8.8.8.8</b></td> | ||
<td>Indicates the host to which ping requests will be sent</td> | <td>Indicates the host to which ping requests will be sent</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 77: | Line 57: | ||
===Ping Reboot Settings=== | ===Ping Reboot Settings=== | ||
---- | ---- | ||
− | |||
− | [[File: | + | [[File:{{{file_ping_reboot_settings}}}]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
− | <th> | + | <th>field name</th> |
− | <th> | + | <th>value</th> |
− | <th> | + | <th>description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 125: | Line 104: | ||
<td>Interface</td> | <td>Interface</td> | ||
<td>Automatically selected | Ping from mobile; Default: <b>Automatically selected</b></td> | <td>Automatically selected | Ping from mobile; Default: <b>Automatically selected</b></td> | ||
− | <td>Specifies through which interface the pings will be sent. If <b>Automatically selected< | + | <td>Specifies through which interface the pings will be sent. If <b>Automatically selected<b> is set, the pings will go through the main WAN interface</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 136: | Line 115: | ||
==Periodic Reboot== | ==Periodic Reboot== | ||
− | + | [[File:{{{file_periodic_reboot_setup}}}]] | |
− | |||
− | |||
− | + | ==Wget Reboot== | |
− | + | [[File:{{{file_wget_reboot_setup}}}]] | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | [[File | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 16:56, 9 January 2019
Summary
Various automatic router reboot scenarios can be configured in the Auto Reboot section. Automatic reboots can be used as a prophylactic or precautionary measure that ensures the device will self-correct some unexpected issues, especially related to connection downtime.
Ping Reboot
The Ping Reboot function periodically sends Ping commands to a specified IP address and wait for received responses. If no response is received, the device will send Ping commands a defined number of times at a defined frequency. If no response is received after the defined number of unsuccessful retries, the device will commit the specified action (reboot, by default).
The Ping Reboot section contains one preconfigured rule by default. The figure below is an example of that rule and the table below provides information on the fields that make up that rule:
[[File:{{{file_ping_reboot}}}]]
field name | value | description |
---|---|---|
Enable | yes | no; Default: no | Turns the rule ON or OFF |
Action | Reboot | Modem restart | Restart mobile connection | (Re)register | none; Default: Reboot | The action that will be taken if no ICMP echo is received |
Interval (min) | 5 mins | 15 mins | 30 mins | 1 hour | 2 hours; Default: 5 mins | Interval at which ping requests are sent to the specified host |
Ping timeout (sec) | integer [1..9999]; Default: 5 | Maximum response time (in seconds). If no echo is received after the amount of time specified in this field, the ping request is considered to have failed |
Packet size | integer [0..1000]; Default: 56 | Ping packet size in bytes |
Retry count | integer [1..9999]; Default: 2 | Indicates how many additional times the device will try sending ping requests if the initial one fails |
Host to ping | host | ip; Default: 8.8.8.8 | Indicates the host to which ping requests will be sent |
Ping Reboot Settings
[[File:{{{file_ping_reboot_settings}}}]]
field name | value | description |
---|---|---|
Enable | yes | no; Default: no | Turns the rule ON or OFF |
No action on data limit | yes | no; Default: no | If enabled, stops taking actions after data limit is reached |
Action if no echo is received | Reboot | Modem restart | Restart mobile connection | (Re)register | none; Default: Reboot | The action that will be taken if no ICMP echo is received |
Interval between pings | 5 mins | 15 mins | 30 mins | 1 hour | 2 hours; Default: 5 mins | Interval at which ping requests are sent to the specified host |
Ping timeout (sec) | integer [1..9999]; Default: 5 | Maximum response time (in seconds). If no echo is received after the amount of time specified in this field, the ping request is considered to have failed |
Packet size | integer [0..1000]; Default: 56 | Ping packet size in bytes |
Retry count | integer [1..9999]; Default: 2 | Indicates how many additional times the device will try sending ping requests if the initial one fails |
Interface | Automatically selected | Ping from mobile; Default: Automatically selected | Specifies through which interface the pings will be sent. If Automatically selected is set, the pings will go through the main WAN interface |
Host to ping | host | ip; Default: 8.8.8.8 | Indicates the host to which ping requests will be sent |
Periodic Reboot
[[File:{{{file_periodic_reboot_setup}}}]]
Wget Reboot
[[File:{{{file_wget_reboot_setup}}}]]