Changes

no edit summary
Line 1: Line 1:  
<!-- Template uses {{{name}}}, {{{series}}}, {{{bluetooth}}}, {{{wifi}}}-->
 
<!-- Template uses {{{name}}}, {{{series}}}, {{{bluetooth}}}, {{{wifi}}}-->
 
{{Template: Networking_rutos_manual_fw_disclosure
 
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.06.1
+
| 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}}} Modbus (legacy WebUI)#Modbus Data to Server|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}}} Modbus (legacy WebUI)#Modbus Data to Server|click here]]</b> for the old style WebUI (FW version RUT2XX_R_00.01.14.4 and earlier) user manual page.</i>}}
    
==Summary==
 
==Summary==
    
The <b>Data to Server</b> feature provides you with the possibility to set up data senders that collect data from various sources and periodically send it to remote servers.
 
The <b>Data to Server</b> feature provides you with the possibility to set up data senders that collect data from various sources and periodically send it to remote servers.
{{#ifeq: {{{series}}} | RUT36X |<u><b>
+
{{#switch: {{{series}}}
 +
| RUTX =
 +
| TRB1 =
 +
| TRB2 =
 +
| RUT9 =
 +
| #default =
 +
<u><b>
   −
Note:</b>On {{{name}}}, Data to Server is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>|}}
+
Note:</b> On {{{name}}}, Data to Server is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.
{{#ifeq: {{{series}}} | RUT30X |<u><b>
  −
 
  −
Note:</b> On {{{name}}}, Data to Server is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>|}}
      +
</u>}}
 
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 
| series = {{{series}}}
 
| series = {{{series}}}
Line 55: Line 65:  
     <tr>
 
     <tr>
 
       <td>Data source</td>
 
       <td>Data source</td>
       <td><span style="color:red">Modbus data</span>{{#ifeq:{{{series}}}|RUT36X|<span class="asterisk">*</span>|}}{{#ifeq:{{{series}}}|RUT30X|<span class="asterisk">*</span>|}} {{#ifeq:{{{bluetooth}}}|1|<nowiki>|</nowiki> <span style="color:green">Bluetooth data</span> |}} {{#ifeq:{{{wiki}}}|1|<nowiki>|</nowiki> WiFi scanner data{{#ifeq: {{{series}}} | RUTX | | <span class="asterisk">*</span>}}|}} | <span style="color:magenta">DNP3</span><span class="asterisk">*</span>; default: <b>Modbus data</b></td>
+
       <td><span style="color:red">Modbus data</span>{{#ifeq:{{{series}}}|RUT36X|<span class="asterisk">*</span>|}}{{#ifeq:{{{series}}}|RUT30X|<span class="asterisk">*</span>|}} {{#ifeq:{{{bluetooth}}}|1|<nowiki>|</nowiki> <span style="color:green">Bluetooth data</span> |}} {{#ifeq:{{{wifi}}}|1|<nowiki>|</nowiki> WiFi scanner data{{#ifeq: {{{series}}} | RUTX | | <span class="asterisk">*</span>}}|}} | <span style="color:magenta">DNP3</span><span class="asterisk">*</span>; default: <b>Modbus data</b></td>
 
       <td>Source of the data to be sent to server.</td>
 
       <td>Source of the data to be sent to server.</td>
 
     </tr>
 
     </tr>
Line 137: Line 147:  
       <td>off | on; default: <b>off</b></td>
 
       <td>off | on; default: <b>off</b></td>
 
       <td>When turned on, the data sender retries failed sending attempts until the are successfully delivered.</td>
 
       <td>When turned on, the data sender retries failed sending attempts until the are successfully delivered.</td>
    </tr>
  −
    <tr>
  −
      <td>Custom Header</td>
  −
      <td>string; default: <b>none</b></td>
  −
      <td>Allows to add custom headers to the HTTP requests.</td>
  −
    </tr>
  −
    <tr>
  −
    <td>Use TLS</td>
  −
      <td>off | <span style="color:blue"><b>on</b></span>; default: <b>off</b></td>
  −
      <td>Use TLS to encrypt the data sent.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>TLS type</td>
  −
      <td>Certificate based; default: '''Certificate based'''</td>
  −
      <td>Select type of TLS.</td>
  −
    </tr>
  −
    <tr>
  −
      <td><span style="color:blue">On:</span> Certificate files from device</td>
  −
      <td>off | on; default: <b>off</b></td>
  −
      <td>When turned on, provides the possibility to use certificate files generated on this device instead of uploading certificate files. You can generate TLS certificates on your device in the System → Administration → [[{{{name}}} Administration#Certificates|Certificates]] page.</td>
  −
    </tr>
  −
    <tr>
  −
    <td><span style="color:blue">On:</span> CA file</td>
  −
        <td>.ca file; default: <b>none</b></td>
  −
        <td>Certificate authority file used in Transport Layer Security.</td>
  −
    </tr>
  −
    <tr>
  −
    <td><span style="color:blue">On:</span> Client certificate</td>
  −
        <td>.crt file; default: <b>none</b></td>
  −
        <td>Certificate file used in Transport Layer Security.</td>
  −
    </tr>
  −
    <tr>
  −
    <td><span style="color:blue">On:</span> Private key</td>
  −
        <td>.key file; default: <b>none</b></td>
  −
        <td>Key file used in Transport Layer Security.</td>
   
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 201: Line 176:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
       <td><span style="color:red">On:</span> A File</td>
+
       <td><span style="color:red">On:</span> CA File</td>
 
       <td>.ca file; default: <b>none</b></td>
 
       <td>.ca file; default: <b>none</b></td>
 
       <td>'''Certificate authority''' is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate.</td>
 
       <td>'''Certificate authority''' is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate.</td>
Line 347: Line 322:  
         <td>string; default: <b>none</b></td>
 
         <td>string; default: <b>none</b></td>
 
         <td>Secret access key is a part of Access keys used for authentication.</td>
 
         <td>Secret access key is a part of Access keys used for authentication.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Use TLS</td>
 +
      <td>off | <span style="color:red">on</span>; default: '''off'''</td>
 +
      <td>Enables the use of TSL certificates.</td>
 +
    </tr>
 +
    <tr>
 +
      <td><span style="color:red">On:</span> TLS type</td>
 +
      <td>Certificate based; default: '''Certificate based'''</td>
 +
      <td>Select type of TLS.</td>
 +
    </tr>
 +
    <tr>
 +
      <td><span style="color:red">On:</span> CA File</td>
 +
      <td>.ca file; default: <b>none</b></td>
 +
      <td>'''Certificate authority''' is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate.</td>
 +
    </tr>
 +
    <tr>
 +
    <td><span style="color:red">On:</span> Client Certificate</td>
 +
        <td>.crt file; default: <b>none</b></td>
 +
        <td>Certificate file is a type of digital certificate that is used by client systems to make authenticated requests to a remote server. If client certificate is not needed, leave both client certificate and client key fields empty.</td>
 +
    </tr>
 +
    <tr>
 +
    <td><span style="color:red">On:</span> Private Key</td>
 +
        <td>.key file; default: <b>none</b></td>
 +
        <td>File containing private key for this client. This file needs to be not encrypted.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
    
[[Category:{{{name}}} Services section]]
 
[[Category:{{{name}}} Services section]]

Navigation menu