Changes

no edit summary
Line 1: Line 1:  
<!--- {{{series}}}, {{{name}}} --->
 
<!--- {{{series}}}, {{{name}}} --->
{{Template:Networking_rutos_manual_fw_disclosure
+
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.06
+
| fw_version = {{{series}}}{{#ifeq:{{{name}}}|RUT241|M|}}_R_00.07.01
 
| series    = {{{series}}}
 
| series    = {{{series}}}
 
}}
 
}}
 
+
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Administration (legacy WebUI)|click here]]</b> for the old style WebUI (FW version RUT9XX_R_00.06.08.5 and earlier) user manual page.</i>|}}
 +
{{#ifeq: {{{series}}} | RUT2 |
 +
{{#switch: {{{name}}}
 +
  | RUT241 =
 +
  | #default =
 +
<br><i><b>Note</b>: <b>[[{{{name}}} Administration (legacy WebUI)|click here]]</b> for the old style WebUI (FW version RUT2XX_R_00.01.14.4 and earlier) user manual page.</i>}}
 +
|}}
 
==Summary==
 
==Summary==
   Line 46: Line 52:  
         <td>integer [1..60]; default: <b>none</b></td>
 
         <td>integer [1..60]; default: <b>none</b></td>
 
         <td>Maximum time (in seconds) the button can be held to perform an action, after which no action will be performed.</td>
 
         <td>Maximum time (in seconds) the button can be held to perform an action, after which no action will be performed.</td>
    </tr>
  −
    <tr>
  −
  <td>Restore to factory defaults</td>
  −
        <td>-(interactive button)</td>
  −
        <td>Restores device to manufacturer's default settings.</td>
  −
    </tr>
  −
    <tr>
  −
  <td>Restore to user's defaults</td>
  −
        <td>-(interactive button)</td>
  −
        <td>Restores device to custom configuration set by the user.</td>
   
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 166: Line 162:  
     </tr>
 
     </tr>
 
</table>
 
</table>
 
+
<br>
===Security===
+
<b>Telnet</b>
 
----
 
----
[[File:Networking_rutos_manual_administration_access_control_security.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_administration_access_control_general_telnet.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 178: Line 174:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Fail count</td>
+
         <td>Enable Telnet access</td>
         <td>integer; default: <b>10</b></td>
+
         <td>off | on; default: <b>on</b></td>
         <td>An amount of times IP address can try to access SSH or WebUI before being blocked.</td>
+
         <td>Turns Telnet access from the local network (LAN) on or off.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Blocked address</td>
+
         <td>Enable remote Telnet access</td>
         <td>ip</td>
+
         <td>off | on; default: <b>off</b></td>
         <td>IP address which was blocked due to reaching fail count limit.</td>
+
         <td>Turns Telnet access from remote networks (WAN) on or off.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Failed attempts</td>
+
         <td>Port range</td>
         <td>integer</td>
+
         <td>integer [0..65535]; default: <b>23</b></td>
         <td>Amount of times IP address tried to access SSH or WebUI after getting blocked.</td>
+
         <td>Selects which port to use for Telnet access.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
   −
===Root CA===
+
===Security===
 
----
 
----
The <b>Root CA</b> section is used to add a root CA certificate file to the device. There is a default file already preloaded on the device which will be overwritten by any uploaded file. The certificates must be in .pem format, maximum file size is 300 KB. These certificates are only needed if you want to use HTTPS for your services and the default file should be sufficient in most cases.
+
[[File:Networking_rutos_manual_administration_access_control_security.png|border|class=tlt-border]]
 
  −
[[File:Networking_rutos_manual_administration_access_control_root_ca.png|border|class=tlt-border]]
  −
 
  −
==Troubleshoot==
  −
 
  −
===Logging Settings===
  −
----
  −
The <b>Logging Settings</b> section is used to configure how and where the device stores system log data. The system log is a file that contains information on various system related events and is useful to engineers for troubleshooting the device.
  −
 
  −
[[File:Networking_rutos_manual_administration_troubleshoot_logging_settings.png|border|class=tlt-border]]
      
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 215: Line 201:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
      <td>System log buffer size</td>
+
        <td>Fail count</td>
      <td>integer; default: <b>128</b></td>
+
        <td>integer; default: <b>10</b></td>
      <td>System log buffer size in kibibytes (KiB).</td>
+
        <td>An amount of times IP address can try to access SSH or WebUI before being blocked.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
      <td>External system log server</td>
+
        <td>Blocked address</td>
      <td>ip; default: <b>none</b></td>
+
        <td>ip</td>
      <td>IP address of an external server that will be used to store device logs.</td>
+
        <td>IP address which was blocked due to reaching fail count limit.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
      <td>External system log server port</td>
+
        <td>Failed attempts</td>
      <td>integer [0..65535]; default: <b>none</b></td>
+
        <td>integer</td>
      <td>TCP/UDP port number of the external log server.</td>
+
        <td>Amount of times IP address tried to access SSH or WebUI after getting blocked.</td>
    </tr>
  −
    <tr>
  −
      <td>External system log server protocol</td>
  −
      <td>UDP | TCP; default: <b>UDP</b></td>
  −
      <td>Communication protocol used by the external log server.</td>
  −
    </tr>
  −
    <tr>
  −
      <td>Save log in</td>
  −
      <td>RAM memory | Flash memory; default: <b>RAM memory</b></td>
  −
      <td>Specifies which type of memory to use for storing system logs.</td>
   
     </tr>
 
     </tr>
 
</table>
 
</table>
   −
===Troubleshoot===
+
===Root CA===
 
----
 
----
The <b>Troubleshoot</b> section is used to download various files that contain information used for troubleshooting the device. Refer to the figure and table below for information on the Troubleshoot page.
+
The <b>Root CA</b> section is used to add a root CA certificate file to the device. There is a default file already preloaded on the device which will be overwritten by any uploaded file. The certificates must be in .pem format, maximum file size is 300 KB. These certificates are only needed if you want to use HTTPS for your services and the default file should be sufficient in most cases.
   −
[[File:Networking_rutos_manual_administration_troubleshoot_troubleshoot.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_administration_access_control_root_ca.png|border|class=tlt-border]]
   −
<table class="nd-mantable">
+
==Recipients==
    <tr>
  −
        <th>Field</th>
  −
      <th>Value</th>
  −
      <th>Description</th>
  −
    </tr>
  −
    <tr>
  −
        <td>System log</td>
  −
        <td>- (interactive button)</td>
  −
        <td>Displays the contents of the device system log file. The system log contains records of various system related events, such as starts/stops of various services, errors, reboots, etc.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Kernel log</td>
  −
        <td>- (interactive button)</td>
  −
        <td>Displays the contents of the device kernel log file. The kernel log contains records of various events related to the processes of the operating system (OS).</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Troubleshoot file</td>
  −
        <td>- (interactive button)</td>
  −
        <td>Downloads the device Troubleshoot file. It contains the device configuration information, logs and some other files. When requesting support, it is recommended to always provide the device Troubleshoot file to Teltonika engineers for analysis.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>TCP dump file</td>
  −
        <td>- (interactive button)</td>
  −
        <td>Downloads the device TCP dump file. TCP dump is a program used to capture packets moving through network interfaces. By default, the device does not store TCP dump information. You must enable TCP dump and save the changes before you can download the file.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Enable TCP dump<span class="asterisk">*</span></td>
  −
        <td>off | on; default: <b>off</b></td>
  −
        <td>Turns TCP dump packets capture on or off.</td>
  −
    </tr>
  −
</table>
  −
 
  −
<font size="-1"><span class="asterisk">*</span> More on TCP dump in the [[#TCP_dump|next section]].</font>
  −
 
  −
====TCP dump====
  −
----
  −
<b>TCP dump</b> is a program used to capture packets moving through network interfaces. By default, the device does not store TCP dump information. You must enable TCP dump and save the changes before you can download the file.
  −
 
  −
If you enable TCP dump, you will notice additional configuration fields appear. Refer to the figure and table below for realted information.
  −
 
  −
[[File:Networking_rutos_manual_administration_troubleshoot_tcp_dump.png|border|class=tlt-border]]
  −
 
  −
<table class="nd-mantable">
  −
    <tr>
  −
        <th>Field</th>
  −
      <th>Value</th>
  −
      <th>Description</th>
  −
    </tr>
  −
    <tr>
  −
        <td>Enable TCP dump</td>
  −
        <td>off | on; default: <b>off</b></td>
  −
        <td>Turns TCP dump packet capture on or off.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Select interface</td>
  −
        <td>network interface; default: '''br-lan'''</td>
  −
        <td>Only captures packets that move through the specified network interface.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Select protocol filter</td>
  −
        <td>all | icmp | tcp | udp | arp; default: <b>All</b></td>
  −
        <td>Only captures packets that match the specified protocol.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Select packets direction</td>
  −
        <td>Incoming/Outgoing | Incoming | Outgoing; default: <b>Incoming/Outgoing</b></td>
  −
        <td>Only captures packets coming from the specified direction.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Host</td>
  −
        <td>ip | host; default: <b>none</b></td>
  −
        <td>Only captures packets related to the specified host.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Port</td>
  −
        <td>integer [0..65335]; default: <b>none</b></td>
  −
        <td>Only captures packets related to the specified communication port.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Select storage</td>
  −
        <td>Internal storage | / ; default: <b>Internal storage</b></td>
  −
        <td>Specifies where the TCP dump file will be stored.</td>
  −
    </tr>
  −
</table>
  −
 
  −
===Diagnostics===
  −
----
  −
The <b>Diagnostics</b> section is used to execute simple network diagnostic tests, including <i>ping</i>, <i>traceroute</i> and <i>nslookup</i>.
  −
 
  −
[[File:Networking_rutos_manual_administration_troubleshoot_diagnostics.png|border|class=tlt-border]]
  −
 
  −
<table class="nd-mantable">
  −
    <tr>
  −
        <th>Field</th>
  −
      <th>Value</th>
  −
      <th>Description</th>
  −
    </tr>
  −
    <tr>
  −
      <td>Method</td>
  −
      <td>Ping | Traceroute | Nslookup; default: <b>Ping</b></td>
  −
      <td>Selects diagnostic method.
  −
            <ul>
  −
                <li><b>Ping</b> - sends ICMP requests to the specified address.</li>
  −
                <li><b>Traceroute</b> - displays the path that packets have to take in order to reach the specified address.</li>
  −
                <li><b>Nslookup</b> - obtains domain name address and IP address mapping information.</li>
  −
            </ul>
  −
        </td>
  −
    </tr>
  −
    <tr>
  −
      <td>Protocol</td>
  −
      <td>IPv4 | IPv6; default: <b>IPv4</b></td>
  −
      <td>Selects IP address family for diagnostic test.</td>
  −
    </tr>
  −
    <tr>
  −
      <td>Address</td>
  −
      <td>ip | host; default: <b>none</b></td>
  −
      <td>IP address or hostname on which the diagnostic test will be performed.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>Perform</td>
  −
      <td>-(interactive button)</td>
  −
      <td>Performs diagnostic test when clicked.</td>
  −
    </tr>
  −
</table>
     −
==Recipients==
+
The <b>Recipients</b> section is used to configure{{#ifeq:{{{mobile}}}|0|&nbsp;|&nbsp;phone groups and&nbsp;}}email
 +
users, which can later be used along with{{#ifeq:{{{mobile}}}|0|&nbsp;|&nbsp;SMS or&nbsp;}}email related
 +
services{{#ifeq:{{{events_reporting}}}|0|.|, such as [[{{{name}}} Events Reporting|Events Reporting]].}}
   −
The <b>Recipients</b> section is used to configure phone groups and email users, which can later be used along with SMS or email related services, such as [[{{{name}}} Events Reporting|Events Reporting]].
+
{{#ifeq:{{{mobile}}}|0||
    
===Phone Groups===
 
===Phone Groups===
Line 410: Line 264:  
     </tr>
 
     </tr>
 
</table>
 
</table>
 +
}}
    
===Email Accounts===
 
===Email Accounts===
 
----
 
----
When email related services (such as [[{{{name}}} Events Reporting|Events Reporting]]) are used, the device logs in to the specified email account and reads the inbox (e.g., Email to SMS) or sends out a message (e.g., SMS to Email) depending on the configured service. In this context, an <b>Email Account</b> is an configuration instance that contains the necessary data required in order to log into an email account.
+
When email related services{{#ifeq:{{{events_reporting}}}|0|&nbsp;|&nbsp;(such as [[{{{name}}} Events Reporting|Events Reporting]])&nbsp;}}are used, the device logs in to the specified email account and reads the inbox (e.g., Email to SMS) or sends out a message (e.g., SMS to Email) depending on the configured service. In this context, an <b>Email Account</b> is an configuration instance that contains the necessary data required in order to log into an email account.
    
The email accounts list is empty by default thus, you must first add at least one new account before you can configure it. To create and begin editing an email account, follow these steps:
 
The email accounts list is empty by default thus, you must first add at least one new account before you can configure it. To create and begin editing an email account, follow these steps:
Line 466: Line 321:  
     </tr>
 
     </tr>
 
</table>
 
</table>
  −
==Overview setup==
  −
  −
The <b>Overview setup</b> section is used to select which widgets will be shown in the [[{{{name}}}_Overview]] window.
  −
{{#switch:{{{series}}}
  −
| RUTX = {{#switch:{{{name}}}
  −
        | RUTX10 = [[File:Networking_rutx10_manual_administration_overview_setup_v1.png|border|class=tlt-border]]
  −
        | RUTX08 = [[File:Networking_rutx10_manual_administration_overview_setup_v1.png|border|class=tlt-border]]
  −
        | [[File:Networking_rutx11_manual_administration_overview_setup_v1.png|border|class=tlt-border]]
  −
        }}
  −
| TRB2 = [[File:Networking_trb2_manual_administration_overview_setup_v1.png|border|class=tlt-border]]
  −
| TRB1 = [[File:Networking_trb1_manual_administration_overview_setup_v1.png|border|class=tlt-border]]
  −
| RUT36X = [[File:Networking_trb1_manual_administration_overview_setup_v1.png|border|class=tlt-border]]
  −
| RUT30X = [[File:Networking_rut30x_manual_administration_overview_setup_v1.png|border|class=tlt-border]]
  −
}}
      
==Certificates==
 
==Certificates==
   −
The <b>Certificates</b> page is used for convenient TLS certificate and key generation and management. Generated files can be exported and used on other machines or locally on this device with functions that use TLS/SSL, such as [[{{{name}}} MQTT|MQTT]], [[{{{name}}} VPN#OpenVPN|OpenVPN]], [[{{{name}}} VPN#IPsec|IPsec]] and others.
+
The <b>Certificates</b> page is used for convenient TLS certificate and key generation and management. Generated files can be exported and used on other machines or locally on this device with functions that use TLS/SSL, such as {{#ifeq:{{{mqtt}}}|0||[[{{{name}}} MQTT|MQTT]],&nbsp;}}[[{{{name}}} VPN#OpenVPN|OpenVPN]], [[{{{name}}} VPN#IPsec|IPsec]] and others.
    
===Certificate Generation===
 
===Certificate Generation===
Line 633: Line 473:  
====Certificate Import====
 
====Certificate Import====
 
----
 
----
The <b>Certificate Import</b> section provides the possibility to import certificates and files generated on another machine. To upload such a file simply click 'Browse', locate the file on your computer and click 'Import'
+
The <b>Certificate Import</b> section provides the possibility to import certificates and files generated on another machine. To upload such a file simply click 'Browse' and locate the file on your computer, it should then start uploading automatically.
    
[[File:Networking_rutos_manual_administartion_certificates_certificates_manager_certificate_import_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_administartion_certificates_certificates_manager_certificate_import_v1.png|border|class=tlt-border]]
Line 647: Line 487:  
The 'Export' buttons are used to download the files from the device onto your local machine. The 'X' buttons located to the right of each entry are used to delete related files.
 
The 'Export' buttons are used to download the files from the device onto your local machine. The 'X' buttons located to the right of each entry are used to delete related files.
   −
==Unsaved changes==
+
==Troubleshoot==
 +
 
 +
===Logging Settings===
 +
----
 +
The <b>Logging Settings</b> section is used to configure how and where the device stores system log data. The system log is a file that contains information on various system related events and is useful to engineers for troubleshooting the device.
 +
 
 +
[[File:Networking_rutos_manual_administration_troubleshoot_logging_settings.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>System log buffer size</td>
 +
      <td>integer; default: <b>128</b></td>
 +
      <td>System log buffer size in kibibytes (KiB).</td>
 +
    </tr>
 +
    <tr>
 +
      <td>External system log server</td>
 +
      <td>ip; default: <b>none</b></td>
 +
      <td>IP address of an external server that will be used to store device logs.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>External system log server port</td>
 +
      <td>integer [0..65535]; default: <b>none</b></td>
 +
      <td>TCP/UDP port number of the external log server.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>External system log server protocol</td>
 +
      <td>UDP | TCP; default: <b>UDP</b></td>
 +
      <td>Communication protocol used by the external log server.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Save log in</td>
 +
      <td>RAM memory | Flash memory; default: <b>RAM memory</b></td>
 +
      <td>Specifies which type of memory to use for storing system logs.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Show hostname</td>
 +
      <td>off | on; default: <b>off</b></td>
 +
      <td>Show hostname instead of IP address in syslog.</td>
 +
    </tr>
 +
</table>
 +
 
 +
===Troubleshoot===
 +
----
 +
The <b>Troubleshoot</b> section is used to download various files that contain information used for troubleshooting the device. Refer to the figure and table below for information on the Troubleshoot page.
 +
 
 +
[[File:Networking_rutos_manual_administration_troubleshoot_troubleshoot.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>System log</td>
 +
        <td>- (interactive button)</td>
 +
        <td>Displays the contents of the device system log file. The system log contains records of various system related events, such as starts/stops of various services, errors, reboots, etc.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Kernel log</td>
 +
        <td>- (interactive button)</td>
 +
        <td>Displays the contents of the device kernel log file. The kernel log contains records of various events related to the processes of the operating system (OS).</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Troubleshoot file</td>
 +
        <td>- (interactive button)</td>
 +
        <td>Downloads the device Troubleshoot file. It contains the device configuration information, logs and some other files. When requesting support, it is recommended to always provide the device Troubleshoot file to Teltonika engineers for analysis.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>TCP dump file<span class="asterisk">*</span></td>
 +
        <td>- (interactive button)</td>
 +
        <td>Downloads the device TCP dump file. TCP dump is a program used to capture packets moving through network interfaces. By default, the device does not store TCP dump information. You must enable TCP dump and save the changes before you can download the file.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Enable TCP dump<span class="asterisk">*</span></td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>Turns TCP dump packets capture on or off.</td>
 +
    </tr>
 +
</table>
 +
 
 +
<font size="-1"><span class="asterisk">*</span> As of {{{series}}}_R_00.07.00, TCPdump is not part of core functionality anymore. To see these options, the TCPdump package must be downloaded from [[{{{name}}}_Package_Manager|Package Manager]].</font>
 +
 
 +
====TCP dump====
 +
----
 +
<b>TCP dump</b> is an <i>optional</i> downloadable functionality<span class="asterisk">*</span> used to capture packets moving through network interfaces. By default, the device does not store TCP dump information. You must enable TCP dump and save the changes before you can download the file.
 +
 
 +
If you enable TCP dump, you will notice additional configuration fields appear. Refer to the figure and table below for realted information.
 +
 
 +
<font size="-1"><span class="asterisk">*</span> You can download the TCPdump package from [[{{{name}}}_Package_Manager|Package Manager]].</font>
   −
The <b>Unsaved changes</b> section is used to see and apply or revert all unsaved changes.
+
[[File:Networking_rutos_manual_administration_troubleshoot_tcp_dump.png|border|class=tlt-border]]
   −
[[File:Networking_rutos_manual_administration_unsaved_changes.png|border|class=tlt-border]]
+
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Enable TCP dump</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>Turns TCP dump packet capture on or off.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Select interface</td>
 +
        <td>network interface; default: '''br-lan'''</td>
 +
        <td>Only captures packets that move through the specified network interface.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Select protocol filter</td>
 +
        <td>All | ICMP | TCP | UDP | ARP; default: <b>All</b></td>
 +
        <td>Only captures packets that match the specified protocol.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Select packets direction</td>
 +
        <td>Incoming/Outgoing | Incoming | Outgoing; default: <b>Incoming/Outgoing</b></td>
 +
        <td>Only captures packets coming from the specified direction.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Host</td>
 +
        <td>ip | host; default: <b>none</b></td>
 +
        <td>Only captures packets related to the specified host.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Port</td>
 +
        <td>integer [0..65335]; default: <b>none</b></td>
 +
        <td>Only captures packets related to the specified communication port.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Select storage</td>
 +
        <td>RAM memory; default: <b>RAM memory</b></td>
 +
        <td>Specifies where the TCP dump file will be stored.</td>
 +
    </tr>
 +
</table>
 +
 
 +
===Diagnostics===
 +
----
 +
The <b>Diagnostics</b> section is used to execute simple network diagnostic tests, including <i>ping</i>, <i>traceroute</i> and <i>nslookup</i>.
 +
 
 +
[[File:Networking_rutos_manual_administration_troubleshoot_diagnostics.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Method</td>
 +
      <td>Ping | Traceroute | Nslookup; default: <b>Ping</b></td>
 +
      <td>Selects diagnostic method.
 +
            <ul>
 +
                <li><b>Ping</b> - sends ICMP requests to the specified address.</li>
 +
                <li><b>Traceroute</b> - displays the path that packets have to take in order to reach the specified address.</li>
 +
                <li><b>Nslookup</b> - obtains domain name address and IP address mapping information.</li>
 +
            </ul>
 +
        </td>
 +
    </tr>
 +
    <tr>
 +
      <td>Protocol</td>
 +
      <td>IPv4 | IPv6; default: <b>IPv4</b></td>
 +
      <td>Selects IP address family for diagnostic test.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Address</td>
 +
      <td>ip | host; default: <b>none</b></td>
 +
      <td>IP address or hostname on which the diagnostic test will be performed.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Perform</td>
 +
      <td>-(interactive button)</td>
 +
      <td>Performs diagnostic test when clicked.</td>
 +
    </tr>
 +
</table>
    
[[Category:{{{name}}} System section]]
 
[[Category:{{{name}}} System section]]

Navigation menu