Changes

1,245 bytes added ,  11:51, 16 March 2020
no edit summary
Line 8: Line 8:  
The '''Broker''' will “listen” for connections on the specified Local port. In order to accept connections from WAN, you also need to check Enable Remote Access.
 
The '''Broker''' will “listen” for connections on the specified Local port. In order to accept connections from WAN, you also need to check Enable Remote Access.
   −
[[Image:Networking rut manual mqtt broker.png|border]]
+
[[Image:Networking rut manual mqtt broker.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 37: Line 37:  
The MQTT '''Security''' tab is used to establish MQTT connection security via TLS/SSL.
 
The MQTT '''Security''' tab is used to establish MQTT connection security via TLS/SSL.
   −
[[Image:Networking rut manual mqtt security.png|border]]
+
[[Image:Networking rut manual mqtt security.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 63: Line 63:  
     <td>Key File</td>
 
     <td>Key File</td>
 
         <td>.key file; Default: " "</td>
 
         <td>.key file; Default: " "</td>
         <td>Specifies the local port that the MQTT broker will listen to</td>
+
         <td>Authenticates the client to the server and establishes precisely who they are.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 76: Line 76:  
The MQTT Broker also supports a functionality called '''Bridge'''. An MQTT Bridge is used for the communication between two MQTT Brokers. The window of Bridge parameters is presented below. Some of these are mandatory as they are needed to create a connection: '''Connection Name, Remote Address and Remote Port'''. For more information on '''MQTT Bridge''' parameters you can read the official mosquitto.org manual page.
 
The MQTT Broker also supports a functionality called '''Bridge'''. An MQTT Bridge is used for the communication between two MQTT Brokers. The window of Bridge parameters is presented below. Some of these are mandatory as they are needed to create a connection: '''Connection Name, Remote Address and Remote Port'''. For more information on '''MQTT Bridge''' parameters you can read the official mosquitto.org manual page.
   −
[[Image:Networking rut manual mqtt bridge.png|border]]
+
[[Image:Networking rut manual mqtt bridge.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 127: Line 127:  
The last section of MQTT Broker parameters is called '''Miscellaneous'''. It contains parameters that are related to neither Security nor Bridge.
 
The last section of MQTT Broker parameters is called '''Miscellaneous'''. It contains parameters that are related to neither Security nor Bridge.
   −
[[Image:Services mqtt broker settings misc.PNG|border]]
+
[[Image:Services mqtt broker settings misc.PNG|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 161: Line 161:  
An '''MQTT Publisher''' is a client that sends messages to the Broker, who then forwards these messages to the Subscriber.
 
An '''MQTT Publisher''' is a client that sends messages to the Broker, who then forwards these messages to the Subscriber.
   −
[[Image:Services mqtt publisher.PNG|border]]
+
[[Image:Services mqtt publisher.PNG|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 194: Line 194:  
         <td>Password used for authentication when connecting to the Broker</td>
 
         <td>Password used for authentication when connecting to the Broker</td>
 
     </tr>
 
     </tr>
 +
    <tr>
 +
      <td>TLS</td>
 +
      <td>yes | no; Default: '''no'''</td>
 +
      <td>Toggles TLS encryption ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Allow insecure connection </td>
 +
      <td>yes | no; Default: '''no'''</td>
 +
      <td>Allow connection without server authenticity verification</td>
 +
    </tr>
 +
    <tr>
 +
      <td>CA file</td>
 +
      <td>.ca file; Default: " "</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>Certificate file</td>
 +
        <td>.crt file; Default: " "</td>
 +
        <td>Certificate file is a type of digital certificate that is used by client systems to make authenticated requests to a remote server. Client certificates play a key role in many mutual authentication designs, providing strong assurances of a requester's identity</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Key file</td>
 +
        <td>.key file; Default: " "</td>
 +
        <td>Authenticates the client to the server and establishes precisely who they are.</td>
 +
    </tr>
 +
 
</table>
 
</table>
    
[[Category:RUT240 WebUI]]
 
[[Category:RUT240 WebUI]]