Changes

Template:Networking rut manual mqtt (view source)

Revision as of 08:21, 22 October 2020

17 bytes added , 08:21, 22 October 2020

no edit summary

Line 29: Line 29:

<tr>

−

<th>~~field~~ name</th>

+

<th>Field name</th>

−

<th>~~value~~</th>

+

<th>Value</th>

−

<th>~~description~~</th>

+

<th>Description</th>

</tr>

<tr>

<td>Enable</td>

<td>yes | no; default: '''no'''</td>

−

<td>Toggles MQTT Broker ON or OFF</td>

+

<td>Toggles MQTT Broker ON or OFF.</td>

</tr>

<tr>

<td>Local Port</td>

<td>integer [0..65535]; default: <b>1883</b></td>

−

<td>Specifies the local port that the MQTT broker will listen to</td>

+

<td>Specifies the local port that the MQTT broker will listen to.</td>

</tr>

<tr>

<td>Enable Remote Access</td>

<td>yes | no; default: '''no'''</td>

−

<td>If enabled, MQTT Broker will be reachable by remote user (from WAN)</td>

+

<td>If enabled, MQTT Broker will be reachable by remote user (from WAN).</td>

</tr>

</table>

Line 58: Line 58:

<tr>

−

<th>~~field~~ name</th>

+

<th>Field name</th>

−

<th>~~value~~</th>

+

<th>Value</th>

−

<th>~~description~~</th>

+

<th>Description</th>

</tr>

<tr>

<td>yes | no; default: '''no'''</td>

−

<td>Toggles the use of TLS/SSL certificates ON or OFF</td>

+

<td>Toggles the use of TLS/SSL certificates ON or OFF.</td>

</tr>

<tr>

<td>.ca file; default: '''none'''</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>

</tr>

<tr>

<td>.crt file; default: '''none'''</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>

+

<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; default: '''none'''</td>

−

<td>Private key for client to establish connection</td>

+

<td>Private key for client to establish connection.</td>

</tr>

<tr>

<td>TLS version</td>

<td>tlsv1.1 | tlsv1.2 | Support all; default: '''Support all'''</td>

−

<td>Authenticates a client to a server and establishes precisely who they are</td>

+

<td>Authenticates a client to a server and establishes precisely who they are.</td>

</tr>

</table>

Line 97: Line 97:

<tr>

−

<th>~~field~~ name</th>

+

<th>Field name</th>

−

<th>~~value~~</th>

+

<th>Value</th>

−

<th>~~description~~</th>

+

<th>Description</th>

</tr>

<tr>

Line 163: Line 163:

<td>.ACL file; default: '''none'''</td>

−

<td>The contents of this file are used to control client access to topics of the broker</td>

+

<td>The contents of this file are used to control client access to topics of the broker.</td>

</tr>

<tr>

<td>Password File</td>

<td>password file; default: '''none'''</td>

−

<td>The Password file stores user names and corresponding passwords, used for authentication. The file can be produced by mosquitto_passwd on the ssh command line, see https://mosquitto.org/man/mosquitto_passwd-1.html</td>

+

<td>The Password file stores user names and corresponding passwords, used for authentication. The file can be produced by mosquitto_passwd on the ssh command line, see https://mosquitto.org/man/mosquitto_passwd-1.html </td>

</tr>

<tr>

<td>Persistence</td>

<td>yes | no; default: '''no'''</td>

−

<td>If enabled, connection, subscription and message data will be written to the disk. Otherwise, the data is stored in the router’s memory only</td>

+

<td>If enabled, connection, subscription and message data will be written to the disk. Otherwise, the data is stored in the router’s memory only.</td>

</tr>

<tr>

<td>Allow Anonymous</td>

<td>yes | no; default: '''yes'''</td>

−

<td>If enabled, the Broker allows anonymous access</td>

+

<td>If enabled, the Broker allows anonymous access.</td>

</tr>

</table>

Line 197: Line 197:

<td>Enable</td>

<td>yes | no; default: '''no'''</td>

−

<td>Toggles the MQTT Publisher ON or OFF</td>

+

<td>Toggles the MQTT Publisher ON or OFF.</td>

</tr>

<tr>

<td>Hostname</td>

<td>host | ip; default: '''none'''</td>

−

<td>Broker’s IP address or hostname</td>

+

<td>Broker’s IP address or hostname.</td>

</tr>

<tr>

<td>integer [0..65535]; default: '''1883'''</td>

−

<td>Specifies the port used for connecting to the Broker</td>

+

<td>Specifies the port used for connecting to the Broker.</td>

</tr>

<tr>

<td>Username</td>

<td>string; default: '''none'''</td>

−

<td>User name used for authentication when connecting to the Broker</td>

+

<td>User name used for authentication when connecting to the Broker.</td>

</tr>

<tr>

<td>Password</td>

<td>string; default: '''none'''</td>

−

<td>Password used for authentication when connecting to the Broker</td>

+

<td>Password used for authentication when connecting to the Broker.</td>

</tr>

<tr>

LorurnA

Administrators

1,244

edits