Changes

Line 22: Line 22:  
  | TCR1=[[File:Networking_rutos_manual_administration_general_tcr_v2.png|border|class=tlt-border]]
 
  | TCR1=[[File:Networking_rutos_manual_administration_general_tcr_v2.png|border|class=tlt-border]]
 
  | TRB1|TRB2|TRB5=[[File:Networking_rutos_manual_administration_general_trb_v2.png|border|class=tlt-border]]
 
  | TRB1|TRB2|TRB5=[[File:Networking_rutos_manual_administration_general_trb_v2.png|border|class=tlt-border]]
  | #default=[[File:Networking_rutos_manual_administration_general_rut_V3.png|border|class=tlt-border]]
+
  | #default=[[File:Networking_rutos_manual_administration_general_rut_v2.png|border|class=tlt-border]]
 
}}
 
}}
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 44: Line 44:  
       <td>Basic {{!}} Advanced; default: <b>Basic</b></td>
 
       <td>Basic {{!}} Advanced; default: <b>Basic</b></td>
 
       <td>Mode determines what options and configurations are shown. In Basic mode only the essential configurations are shown. In Advanced mode there is greater freedom to configure and access more options.</td>
 
       <td>Mode determines what options and configurations are shown. In Basic mode only the essential configurations are shown. In Advanced mode there is greater freedom to configure and access more options.</td>
     </tr>
+
     </tr>}}
    <tr>
  −
      <td>Data Analytics</td>
  −
      <td>Off {{!}} On; default: <b>Off</b></td>
  −
      <td>Enables collecting usage data</td>
  −
    </tr>
  −
    }}
   
     <tr>
 
     <tr>
 
       <th>Device name and hostname</th>
 
       <th>Device name and hostname</th>
Line 304: Line 298:  
----{{#switch:{{{series}}}
 
----{{#switch:{{{series}}}
 
|TAP100|TAP200 = [[File:Networking_rutos_manual_administration_access_control_general_webui_tap100_v1.png|border|class=tlt-border]]
 
|TAP100|TAP200 = [[File:Networking_rutos_manual_administration_access_control_general_webui_tap100_v1.png|border|class=tlt-border]]
|#default = [[File:Networking_rutos_manual_administration_access_control_general_webui_v2.png|border|class=tlt-border]]}}
+
|#default = [[File:Networking_rutos_manual_administration_access_control_general_webui_v1.png|border|class=tlt-border]]}}
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 366: Line 360:  
         <td>.key; default: <b>uhttpd.key</b></td>
 
         <td>.key; default: <b>uhttpd.key</b></td>
 
         <td>Server key file.</td>
 
         <td>Server key file.</td>
    </tr>
  −
    <tr>
  −
        <td>Certificate file</td>
  −
        <td><b>Download</b></td>
  −
        <td>Certificate file.</td>
   
     </tr>}}
 
     </tr>}}
 
</table>
 
</table>
Line 464: Line 453:  
         <td>Required {{!}} Requisite {{!}} Sufficient {{!}} Optional; default: <b>Optional </b></td>
 
         <td>Required {{!}} Requisite {{!}} Sufficient {{!}} Optional; default: <b>Optional </b></td>
 
         <td>Determines the continuation or failure behavior for the module</td>
 
         <td>Determines the continuation or failure behavior for the module</td>
    </tr>
  −
    <tr>
  −
        <td><span style="color:red">Radius</span>: Enable for all users</td>
  −
        <td>off {{!}} on; default: <b>off</b></td>
  −
        <td>Turn on PAM authentication for all users. It will allow login with users that are not created on the device.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 615: Line 599:  
After clicking 'Edit' you should be redirected to that phone group's configuration page where you can start adding phone numbers to it.
 
After clicking 'Edit' you should be redirected to that phone group's configuration page where you can start adding phone numbers to it.
   −
[[File:Networking_rutos_manual_administration_recipients_phone_groups_modify_phone_group_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_administration_recipients_phone_groups_modify_phone_group.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 719: Line 703:  
The <b>Certificate Generation</b> tab provides the possibility to generate TLS certificates required for secure authentication and communication encryption used by some of the devices services.
 
The <b>Certificate Generation</b> tab provides the possibility to generate TLS certificates required for secure authentication and communication encryption used by some of the devices services.
   −
There are six distinct generation methods (denoted by the selected 'File Type').  
+
There are five distinct generation methods (denoted by the selected 'File Type').  
    
<ol>
 
<ol>
Line 734: Line 718:  
     <li><b>Client</b> - generates a client certificate and key. A client certificate validates a client's identity to the server that it's connecting to, while a key is responsible for encryption.</li>
 
     <li><b>Client</b> - generates a client certificate and key. A client certificate validates a client's identity to the server that it's connecting to, while a key is responsible for encryption.</li>
 
     <li><b>DH Parameters</b> - generates a Diffie-Hellman (DH) parameters file. DH parameters are used in symmetric encryption to protect and define how OpenSSL key exchange is performed.</li>
 
     <li><b>DH Parameters</b> - generates a Diffie-Hellman (DH) parameters file. DH parameters are used in symmetric encryption to protect and define how OpenSSL key exchange is performed.</li>
    <li><b>Let's encrypt</b> - generates SSL certificate.</li>
   
</ol>
 
</ol>