Jump to content
  • EN

Template:Networking rutos manual administration: Difference between revisions

Template:Networking rutos manual administration (view source)

Revision as of 13:43, 5 May 2020

3,033 bytes added ,  5 May 2020
prepare for release
VisualWikitext
(add access control)
(prepare for release)
Line 10: Line 10:


The <b>General</b> section is used to set up some of device managerial parameters, such as changing device name. For more information on the General section, refer to figure and table below.
The <b>General</b> section is used to set up some of device managerial parameters, such as changing device name. For more information on the General section, refer to figure and table below.
{{#switch:{{{series}}}
| RUTX = [[File:Networking_rutx_manual_administration_general_v1.png|border|class=tlt-border]]
| TRB2 = [[File:Networking_trb2_manual_administration_general_v1.png|border|class=tlt-border]]
| TRB1 = [[File:Networking_trb1_manual_administration_general_v1.png|border|class=tlt-border]]
| default =
}}


[[File:Networking_rutx_manual_administration_general_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 144: Line 149:
===General===
===General===


The <b>Access Control</b> page is used to manage remote and local access to the router.
The <b>Access Control</b> page is used to manage remote and local access to device.


<b>Important</b>: turning on remote access leaves the router vulnerable to external attackers. Make sure you use a strong password.
<b>Important</b>: turning on remote access leaves your device vulnerable to external attackers. Make sure you use a strong password.
<br><br>
<br><br>
<b>SSH</b>
<b>SSH</b>
Line 188: Line 193:
         <td>Enable HTTP access</td>
         <td>Enable HTTP access</td>
         <td>off | on; default: <b>on</b></td>
         <td>off | on; default: <b>on</b></td>
         <td>Turns HTTP access from the local network (LAN) to the router's WebUI on or off.</td>
         <td>Turns HTTP access from the local network (LAN) to the device WebUI on or off.</td>
     </tr><tr><td>Enable HTTPS access
     </tr><tr><td>Enable HTTPS access
</td><td>off | on; default: <b>on</b></td><td>Turns HTTPS access from the local network (LAN) to the router's WebUI on or off.</td></tr><tr>
</td><td>off | on; default: <b>on</b></td><td>Turns HTTPS access from the local network (LAN) to the device WebUI on or off.</td></tr><tr>
         <td>Redirect to HTTPS</td>
         <td>Redirect to HTTPS</td>
         <td>off | on; default: <b>off</b></td>
         <td>off | on; default: <b>off</b></td>
Line 198: Line 203:
         <td>Enable remote HTTP access</td>
         <td>Enable remote HTTP access</td>
         <td>off | on; default: <b>off</b></td>
         <td>off | on; default: <b>off</b></td>
         <td>Turns HTTP access from remote networks (WAN) to the router's WebUI on or off.</td>
         <td>Turns HTTP access from remote networks (WAN) to the device WebUI on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 208: Line 213:
         <td>Enable remote HTTPS access</td>
         <td>Enable remote HTTPS access</td>
         <td>off | on; default: <b>off</b></td>
         <td>off | on; default: <b>off</b></td>
         <td>Turns HTTPS access from remote networks (WAN) to the router's WebUI on or off.</td>
         <td>Turns HTTPS access from remote networks (WAN) to the device WebUI on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 273: Line 278:
         <td>integer</td>
         <td>integer</td>
         <td>Amount of times IP address tried to access SSH or WebUI after getting blocked.</td>
         <td>Amount of times IP address tried to access SSH or WebUI after getting blocked.</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:{{{file_diagnostics}}}]]
<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>
</table>
</table>
Line 313: Line 283:
==Troubleshoot==
==Troubleshoot==


The <b>Troubleshoot</b> section is used to download various files that contain information used for troubleshooting the router. Refer to the figure and table below for information on the Troubleshoot page.
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:{{{file_troubleshoot}}}]]
[[File:Networking_rutx_manual_administration_troubleshoot_v1.png]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 326: Line 296:
         <td>System log</td>
         <td>System log</td>
         <td>- (interactive button)</td>
         <td>- (interactive button)</td>
         <td>Displays the contents of the router's system log file. The system log contains records of various system related events, such as starts/stops of various services, errors, reboots, etc.</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>
     <tr>
     <tr>
         <td>Kernel log</td>
         <td>Kernel log</td>
         <td>- (interactive button)</td>
         <td>- (interactive button)</td>
         <td>Displays the contents of the router's kernel log file. The kernel log contains records of various events related to the processes of the operating system (OS).</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>
     <tr>
     <tr>
         <td>Troubleshoot file</td>
         <td>Troubleshoot file</td>
         <td>- (interactive button)</td>
         <td>- (interactive button)</td>
         <td>Downloads the router's Troubleshoot file. It contains the router's configuration information, logs and some other files. When requesting support, it is recommended to always provide the router's Troubleshoot file to Teltonika engineers for analysis.</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>
     <tr>
     <tr>
         <td>TCP dump file</td>
         <td>TCP dump file</td>
         <td>- (interactive button)</td>
         <td>- (interactive button)</td>
         <td>Downloads the router's TCP dump file. TCP dump is a program used to capture packets moving through network interfaces. By default, the router does not store TCP dump information. You must enable TCP dump and save the changes before you can download the file.</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>
     <tr>
     <tr>
Line 354: Line 324:
===TCP dump===
===TCP dump===
----
----
<b>TCP dump</b> is a program used to capture packets moving through network interfaces. By default, the router does not store TCP dump information. You must enable TCP dump and save the changes before you can download the file.  
<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.
If you enable TCP dump, you will notice additional configuration fields appear. Refer to the figure and table below for realted information.


[[File:{{{file_tcpdump}}}]]
[[File:Networking_rutx_manual_administration_troubleshoot_tcp_dump_v3.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 383: Line 353:
     <tr>
     <tr>
         <td>Select packets direction</td>
         <td>Select packets direction</td>
         <td>IN/OUT | Incoming | Outgoing; default: <b>IN/OUT</b></td>
         <td>Incoming/Outgoing | Incoming | Outgoing; default: <b>Incoming/Outgoing</b></td>
         <td>Only captures packets coming from the specified direction.</td>
         <td>Only captures packets coming from the specified direction.</td>
     </tr>
     </tr>
Line 403: Line 373:
</table>
</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_rutx_manual_administration_diagnostics_v3.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>
==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]]
| default [[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]]
| default =
}}


==Root CA==
==Root CA==


The <b>Root CA</b> section is used to add a root CA certificate file to the router. 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.
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_rutx_manual_administration_root_ca_v2.png|border|class=tlt-border]]
 
==Logging==
 
The <b>Logging</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.
 
Refer to the figure and table below for information on the device Logging page.
 
[[File:Networking_rutx_manual_administration_logging_v2.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></table>
 
==Unsaved changes==
 
The <b>Unsaved changes</b> section is used to see and apply or revert all unsaved changes.


[[File:{{{file_root_ca}}}]]
[[File:Networking_rutx_manual_administration_unsaved_changes_v1.png|border|class=tlt-border]]


[[Category:{{{name}}} System section]]
[[Category:{{{name}}} System section]]
Lorurn
0

edits

Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/60740"