31,703
edits
Changes
Template:Networking rut manual auto reboot legacy (view source)
Revision as of 08:44, 4 June 2021
, 08:44, 4 June 2021Created page with "{{Template: Networking_rutos_manual_fw_disclosure | fw_version = {{#switch: {{{series}}} | RUT2XX = {{{series}}}_R_00.01.14 | RUT850 = {{{series}}}_R_00.01.04 | RUT9XX =..."
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{#switch: {{{series}}}
| RUT2XX = {{{series}}}_R_00.01.14
| RUT850 = {{{series}}}_R_00.01.04
| RUT9XX = {{{series}}}_R_00.06.08.1}}
| series = {{{series}}}
}}
<i><b>Note</b>: this user manual page is for {{{name}}}'s old WebUI style available in earlier FW versions. <b>[[{{{name}}} Auto Reboot|Click here]]</b> for information based on the latest FW version.</i>
==Summary==
Various automatic router reboot scenarios can be configured in the <b>Auto Reboot</b> page. 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.
This chapter of the user manual provides an overview of the Auto Reboot page for {{{name}}} devices.
==Ping Reboot==
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 pre-configured 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:Rutxxx_webui_services_auto_reboot_ping_reboot_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns the rule ON or OFF</td>
</tr>
<tr>
<td>Action</td>
<td>Reboot | Modem restart | Restart mobile connection | (Re)register | none; Default: <b>Reboot</b></td>
<td>The action that will be taken if no ICMP echo is received</td>
</tr>
<tr>
<td>Interval (min)</td>
<td>5 mins | 15 mins | 30 mins | 1 hour | 2 hours; Default: <b>5 mins</b></td>
<td>Interval at which ping requests are sent to the specified host</td>
</tr>
<tr>
<td>Ping timeout (sec)</td>
<td>integer [1..9999]; Default: <b>5</b></td>
<td>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</td>
</tr>
<tr>
<td>Packet size</td>
<td>integer [0..1000]; Default: <b>56</b></td>
<td>Ping packet size in bytes</td>
</tr>
<tr>
<td>Retry count</td>
<td>integer [1..9999]; Default: <b>2</b></td>
<td>Indicates how many additional times the device will try sending ping requests if the initial one fails</td>
</tr>
<tr>
<td>Host to ping</td>
<td>host | ip; Default: <b>8.8.8.8</b></td>
<td>Indicates the host to which ping requests will be sent</td>
</tr>
<tr>
<td>Edit</td>
<td>- (interactive button)</td>
<td>Redirects the user to the rule's configuration window</td>
</tr>
<tr>
<td>Delete</td>
<td>- (interactive button)</td>
<td>Removes the rule from the configuration</td>
</tr>
</table>
===Ping Reboot Settings===
----
If you click the "Edit" button located to a ping reboot rule, you will be redirected to that rule's configuration window. The figure below is an example of that window and the table below provides information on the fields contained in that window:
[[File:Rutxxx_webui_services_auto_reboot_ping_reboot_settings_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns the rule ON or OFF</td>
</tr>
<tr>
<td>No action on data limit</td>
<td>yes | no; Default: <b>no</b></td>
<td>If enabled, stops taking actions after data limit is reached</td>
</tr>
<tr>
<td>Action if no echo is received</td>
<td>Reboot | Modem restart | Restart mobile connection | (Re)register | none; Default: <b>Reboot</b></td>
<td>The action that will be taken if no ICMP echo is received</td>
</tr>
<tr>
<td>Interval between pings</td>
<td>5 mins | 15 mins | 30 mins | 1 hour | 2 hours; Default: <b>5 mins</b></td>
<td>Interval at which ping requests are sent to the specified host</td>
</tr>
<tr>
<td>Ping timeout (sec)</td>
<td>integer [1..9999]; Default: <b>5</b></td>
<td>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</td>
</tr>
<tr>
<td>Packet size</td>
<td>integer [0..1000]; Default: <b>56</b></td>
<td>Ping packet size in bytes</td>
</tr>
<tr>
<td>Retry count</td>
<td>integer [1..9999]; Default: <b>2</b></td>
<td>Indicates how many additional times the device will try sending ping requests if the initial one fails</td>
</tr>
<tr>
<td>Interface</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</b> is set, the pings will go through the main WAN interface</td>
</tr>
<tr>
<td>Host to ping</td>
<td>host | ip; Default: <b>8.8.8.8</b></td>
<td>Indicates the host to which ping requests will be sent</td>
</tr>
</table>
==Periodic Reboot==
<b>Periodic Reboot</b> is a function that reboots the router at a specified time interval regardless of other circumstances. It can be used as prophylactic measure, for example, to reboot the router once at the end of every week.
The figure below is an example of the Periodic Reboot configuration page and the table below provides information on the fields contained in that page:
[[File:Rutxxx_webui_services_auto_reboot_periodic_reboot_setup_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns Periodic Reboot ON or OFF</td>
</tr>
<tr>
<td>Days</td>
<td>Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday; Default: <b>none</b></td>
<td>The day or multiple days on which the router will reboot</td>
</tr>
<tr>
<td>Hour</td>
<td>integer [0..23]; Default: <b>23</b></td>
<td>The hour of the day on which the router will reboot</td>
</tr>
<tr>
<td>Minute</td>
<td>integer [0..59]; Default: <b>0</b></td>
<td>The minute of the hour on which the router will reboot</td>
</tr>
</table>
{{#ifeq: {{{wget}}} | 1 | <h2>Wget Reboot</h2>
<b>Wget</b> is a computer program that retrieves content from web servers. The <b>Wget Reboot</b> function works in a very similar manner to Ping Reboot. While Ping Reboot sends ping requests to determine whether the conditions for the specified action have been met, Wget Reboot attempts to retrieve the contents of a web server.
The figure below is an example of the Wget Reboot configuration page and the table below provides information on the fields contained in that page:
[[File:Rutxxx_webui_services_auto_reboot_wget_reboot_setup_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes {{!}} no; Default: <b>no</b></td>
<td>Turns Wget Reboot ON or OFF</td>
</tr>
<tr>
<td>Action if no response is received</td>
<td>Reboot {{!}} Modem restart {{!}} Restart mobile connection {{!}} (Re)register {{!}} Send SMS {{!}} None; Default: <b>Reboot</b></td>
<td>The action that will be performed after the specified number of failed Wget requests</td>
</tr>
<tr>
<td>Interval between requests</td>
<td>5 mins {{!}} 15 mins {{!}} 30 mins {{!}} 1 hour {{!}} 2 hours; Default: <b>5 mins</b></td>
<td>Interval at which Wget requests will be sent to the specified host or IP address</td>
</tr>
<tr>
<td>Wget timeout (sec)</td>
<td>integer [1..9999]; Default: <b>2</b></td>
<td>Maximum response time (in seconds). If no response is received after the amount of time specified in this field, the Wget request is considered to have failed</td>
</tr>
<tr>
<td>Retry count</td>
<td>integer [1..9999]; Default: <b>5</b></td>
<td>Indicates how many additional times the device will try retrieving the web server's content with Wget if the initial attempt fails</td>
</tr>
<tr>
<td>Host to ping</td>
<td>host {{!}} ip; Default: <b><nowiki>www.google.com</nowiki></b></td>
<td>Host or IP address to send Wget requests to</td>
</tr>
</table>
|}}
[[Category:{{{name}}} Services section (legacy)]]
| fw_version = {{#switch: {{{series}}}
| RUT2XX = {{{series}}}_R_00.01.14
| RUT850 = {{{series}}}_R_00.01.04
| RUT9XX = {{{series}}}_R_00.06.08.1}}
| series = {{{series}}}
}}
<i><b>Note</b>: this user manual page is for {{{name}}}'s old WebUI style available in earlier FW versions. <b>[[{{{name}}} Auto Reboot|Click here]]</b> for information based on the latest FW version.</i>
==Summary==
Various automatic router reboot scenarios can be configured in the <b>Auto Reboot</b> page. 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.
This chapter of the user manual provides an overview of the Auto Reboot page for {{{name}}} devices.
==Ping Reboot==
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 pre-configured 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:Rutxxx_webui_services_auto_reboot_ping_reboot_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns the rule ON or OFF</td>
</tr>
<tr>
<td>Action</td>
<td>Reboot | Modem restart | Restart mobile connection | (Re)register | none; Default: <b>Reboot</b></td>
<td>The action that will be taken if no ICMP echo is received</td>
</tr>
<tr>
<td>Interval (min)</td>
<td>5 mins | 15 mins | 30 mins | 1 hour | 2 hours; Default: <b>5 mins</b></td>
<td>Interval at which ping requests are sent to the specified host</td>
</tr>
<tr>
<td>Ping timeout (sec)</td>
<td>integer [1..9999]; Default: <b>5</b></td>
<td>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</td>
</tr>
<tr>
<td>Packet size</td>
<td>integer [0..1000]; Default: <b>56</b></td>
<td>Ping packet size in bytes</td>
</tr>
<tr>
<td>Retry count</td>
<td>integer [1..9999]; Default: <b>2</b></td>
<td>Indicates how many additional times the device will try sending ping requests if the initial one fails</td>
</tr>
<tr>
<td>Host to ping</td>
<td>host | ip; Default: <b>8.8.8.8</b></td>
<td>Indicates the host to which ping requests will be sent</td>
</tr>
<tr>
<td>Edit</td>
<td>- (interactive button)</td>
<td>Redirects the user to the rule's configuration window</td>
</tr>
<tr>
<td>Delete</td>
<td>- (interactive button)</td>
<td>Removes the rule from the configuration</td>
</tr>
</table>
===Ping Reboot Settings===
----
If you click the "Edit" button located to a ping reboot rule, you will be redirected to that rule's configuration window. The figure below is an example of that window and the table below provides information on the fields contained in that window:
[[File:Rutxxx_webui_services_auto_reboot_ping_reboot_settings_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns the rule ON or OFF</td>
</tr>
<tr>
<td>No action on data limit</td>
<td>yes | no; Default: <b>no</b></td>
<td>If enabled, stops taking actions after data limit is reached</td>
</tr>
<tr>
<td>Action if no echo is received</td>
<td>Reboot | Modem restart | Restart mobile connection | (Re)register | none; Default: <b>Reboot</b></td>
<td>The action that will be taken if no ICMP echo is received</td>
</tr>
<tr>
<td>Interval between pings</td>
<td>5 mins | 15 mins | 30 mins | 1 hour | 2 hours; Default: <b>5 mins</b></td>
<td>Interval at which ping requests are sent to the specified host</td>
</tr>
<tr>
<td>Ping timeout (sec)</td>
<td>integer [1..9999]; Default: <b>5</b></td>
<td>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</td>
</tr>
<tr>
<td>Packet size</td>
<td>integer [0..1000]; Default: <b>56</b></td>
<td>Ping packet size in bytes</td>
</tr>
<tr>
<td>Retry count</td>
<td>integer [1..9999]; Default: <b>2</b></td>
<td>Indicates how many additional times the device will try sending ping requests if the initial one fails</td>
</tr>
<tr>
<td>Interface</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</b> is set, the pings will go through the main WAN interface</td>
</tr>
<tr>
<td>Host to ping</td>
<td>host | ip; Default: <b>8.8.8.8</b></td>
<td>Indicates the host to which ping requests will be sent</td>
</tr>
</table>
==Periodic Reboot==
<b>Periodic Reboot</b> is a function that reboots the router at a specified time interval regardless of other circumstances. It can be used as prophylactic measure, for example, to reboot the router once at the end of every week.
The figure below is an example of the Periodic Reboot configuration page and the table below provides information on the fields contained in that page:
[[File:Rutxxx_webui_services_auto_reboot_periodic_reboot_setup_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns Periodic Reboot ON or OFF</td>
</tr>
<tr>
<td>Days</td>
<td>Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday; Default: <b>none</b></td>
<td>The day or multiple days on which the router will reboot</td>
</tr>
<tr>
<td>Hour</td>
<td>integer [0..23]; Default: <b>23</b></td>
<td>The hour of the day on which the router will reboot</td>
</tr>
<tr>
<td>Minute</td>
<td>integer [0..59]; Default: <b>0</b></td>
<td>The minute of the hour on which the router will reboot</td>
</tr>
</table>
{{#ifeq: {{{wget}}} | 1 | <h2>Wget Reboot</h2>
<b>Wget</b> is a computer program that retrieves content from web servers. The <b>Wget Reboot</b> function works in a very similar manner to Ping Reboot. While Ping Reboot sends ping requests to determine whether the conditions for the specified action have been met, Wget Reboot attempts to retrieve the contents of a web server.
The figure below is an example of the Wget Reboot configuration page and the table below provides information on the fields contained in that page:
[[File:Rutxxx_webui_services_auto_reboot_wget_reboot_setup_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes {{!}} no; Default: <b>no</b></td>
<td>Turns Wget Reboot ON or OFF</td>
</tr>
<tr>
<td>Action if no response is received</td>
<td>Reboot {{!}} Modem restart {{!}} Restart mobile connection {{!}} (Re)register {{!}} Send SMS {{!}} None; Default: <b>Reboot</b></td>
<td>The action that will be performed after the specified number of failed Wget requests</td>
</tr>
<tr>
<td>Interval between requests</td>
<td>5 mins {{!}} 15 mins {{!}} 30 mins {{!}} 1 hour {{!}} 2 hours; Default: <b>5 mins</b></td>
<td>Interval at which Wget requests will be sent to the specified host or IP address</td>
</tr>
<tr>
<td>Wget timeout (sec)</td>
<td>integer [1..9999]; Default: <b>2</b></td>
<td>Maximum response time (in seconds). If no response is received after the amount of time specified in this field, the Wget request is considered to have failed</td>
</tr>
<tr>
<td>Retry count</td>
<td>integer [1..9999]; Default: <b>5</b></td>
<td>Indicates how many additional times the device will try retrieving the web server's content with Wget if the initial attempt fails</td>
</tr>
<tr>
<td>Host to ping</td>
<td>host {{!}} ip; Default: <b><nowiki>www.google.com</nowiki></b></td>
<td>Host or IP address to send Wget requests to</td>
</tr>
</table>
|}}
[[Category:{{{name}}} Services section (legacy)]]
