8,823
edits
Changes
Template:Networking rutos manual mqtt rut2 rut9 (view source)
Revision as of 08:10, 9 April 2024
, 9 AprilCreated page with "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{se..."
{{Template: Networking_device_manual_fw_disclosure
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} MQTT (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} MQTT (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==Summary==
<b>MQTT (MQ Telemetry Transport or Message Queue Telemetry Transport)</b> is an ISO standard (ISO/IEC PRF 20922) publish-subscribe-based "lightweight" messaging protocol for use on top of the TCP/IP protocol. It is designed to send short messages from one client (<i>publisher</i>) to another (<i>subscriber</i>) through <i>brokers</i>, which are responsible for message delivery to the end point.
{{{name}}} devices support this functionality via an open source Mosquitto broker. The messages are sent this way: a client (subscriber) subscribes to a topic(s); a publisher posts a message to that specific topic(s). The broker then checks who is subscribed to that particular topic(s) and transmits data from the publisher to the subscriber.
This chapter is an overview of the MQTT page for {{{name}}} devices.
{{#switch: {{{series}}}
| #default =
| TRB2|RUT36X|RUT30X|RUT9|TCR1|RUT2|RUT2M|RUT9M|TRB2M|OTD140|RUT301|RUT14X =
<u><b>
Note:</b> MQTT is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
}}
==MQTT Broker==
The <b>MQTT Broker</b> is an entity that listens for connections on the specified port and relays received messages to MQTT client. To begin using this devices as an MQTT Broker, enable it in this page. In order to make the device accept MQTT connections from WAN (remote networks), you also need to turn the 'Enable Remote Access' slider on.
[[File:Networking_rutos_manual_mqtt_broker_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turn MQTT Broker on or off.</td>
</tr>
<tr>
<td>Custom configuration</td>
<td>off | on; default: <b>off</b></td>
<td>Enables reading of custom configuration.</td>
</tr>
<tr>
<td>Local Port</td>
<td>integer [0..65535]; default: <b>1883</b></td>
<td>The TCP port(s) on which the MQTT broker will listen for connections. Click the plus sign to add multiple ports.</td>
</tr>
<tr>
<td>Enable Remote Access</td>
<td>off | on; default: <b>off</b></td>
<td>Turns remote access to this MQTT broker on or off.</td>
</tr>
</table>
==Broker Settings==
===Security===
----
The <b>Security</b> section is used to configure TLS/SSL .
[[File:Networking rutos manual mqtt broker settings security v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Use TLS/SSL</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the use of TLS/SSL for this MQTT connection on or off.</td>
</tr>
<tr>
<td>TLS type</td>
<td>Certificate based {{!}} <span style="color:darkred">Pre-shared key based</span>; default: '''Certificate based'''</td>
<td>Select type of TLS.</td>
</tr>
<tr>
<td>Require certificate</td>
<td>off | on; default: <b>on</b></td>
<td>Demand client certificate and key from the client.</td>
</tr>
<tr>
<td>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>CA File</td>
<td>.ca file; default: <b>none</b></td>
<td>Uploads a Certificate Authority (CA) file. A Certificate Authority (CA) 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>CERT File</td>
<td>.crt file; default: <b>none</b></td>
<td>Uploads a server (broker) certificate file. A certificate file is a type of digital certificate that is used by client systems to make authenticated requests to a remote server.</td>
</tr>
<tr>
<td>Key File</td>
<td>.key file; default: <b>none</b></td>
<td>Uploads a server (broker) key file.</td>
</tr>
<tr>
<td>TLS version</td>
<td>tlsv1 | tlsv1.1 | tlsv1.2 | Support all; default: <b>Support all</b></td>
<td>Specifies which TLS version(s) is will be supported by this broker.</td>
</tr>
<tr>
<td><span style="color:darkred">Pre-shared key based:</span> Pre-Shared-Key</td>
<td>string; default: <b>none</b></td>
<td>The pre-shared-key in hex format with no leading "0x".</td>
</tr>
<tr>
<td><span style="color:darkred">Pre-shared key based:</span> Identity</td>
<td>string; default: <b>none</b></td>
<td>The identity of this client. May be used as the username depending on the server settings.</td>
</tr>
</table>
===Bridge===
----
An <b>MQTT Bridge</b> is used for the communication between MQTT brokers. The window of Bridge parameters is presented below.
<b>Note</b>: this table has a coloring scheme to indicate which fields can be seen with different configuration.
[[File:Networking_rutos_manual_mqtt_broker_settings_bridge_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turns MQTT Bridge on and off.</td>
</tr>
<tr>
<td>Connection Name</td>
<td>string; default: <b>none</b></td>
<td>Name of the Bridge connection. This is used for easier management purposes.</td>
</tr>
<tr>
<td>Protocol version</td>
<td>3.1 | 3.1.1; default: <b>3.1</b></td>
<td>Selects protocol version</td>
</tr>
<tr>
<td>Remote Address</td>
<td>ip; default: <b>none</b></td>
<td>Remote Broker’s address.</td>
</tr>
<tr>
<td>Remote Port</td>
<td>integer [0..65535]; default: '''1883'''</td>
<td>Specifies which port the remote broker uses to listen for connections.</td>
</tr>
<tr>
<td>Use Remote TLS/SSL</td>
<td>off | <span style="color:blue"><b>on</b></span>; default: '''off'''</td>
<td>Enables the use of TSL/SSL certificates of the remote broker. If this is checked, you will be prompted to upload TLS/SSL certificates. More information can be found in the [[#Security|Security]] section of this chapter.</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> Bridge CA File</td>
<td>.ca file; default: <b>none</b></td>
<td>Uploads a Certificate Authority (CA) file. A Certificate Authority (CA) 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:blue">On:</span> Bridge certificate File</td>
<td>.crt file; default: <b>none</b></td>
<td>Uploads a server (broker) certificate file. A certificate file is a type of digital certificate that is used by client systems to make authenticated requests to a remote server.</td>
</tr>
<tr>
<td><span style="color:blue">On:</span> Bridge Key File</td>
<td>.key file; default: <b>none</b></td>
<td>Uploads a server (broker) key file.</td>
</tr>
<tr>
<td><span style="color:blue">On:</span> Bridge TLS version</td>
<td>tlsv1 | tlsv1.1 | tlsv1.2; default: <b>tlsv1</b></td>
<td>TLS version used by the other broker.</td>
</tr>
<tr>
<td><span style="color:blue">On:</span> Bridge ALPN</td>
<td>string; default: <b>none</b></td>
<td>Configure the application layer protocol negotiation option for the TLS session. Useful for brokers that support both websockets and MQTT on the same port. </td>
</tr>
<tr>
<td>Use Remote Bridge Login</td>
<td>off | <span style="color:red"><b>on</b></span>; default: <b>off</b></td>
<td>Indicates whether the remote side of the connection requires login information. If this is turned on, you will be required to enter a remote client ID, username and password.</td>
</tr>
<tr>
<td><span style="color:red">On:</span> Remote ID</td>
<td>string; default: <b>none</b></td>
<td>Identifier of the remote broker</td>
</tr>
<tr>
<td><span style="color:red">On:</span> Remote Username</td>
<td>string; default: <b>none</b></td>
<td>Username for authentication to the remote broker.</td>
</tr>
<tr>
<td><span style="color:red">On:</span> Require password</td>
<td>on | off; default: <b>off</b></td>
<td>Password for authentication to the remote broker.</td>
</tr>
<tr>
<td><span style="color:red">On:</span> Remote Password</td>
<td>string; default: <b>none</b></td>
<td>Password for authentication to the remote broker.</td>
</tr>
<tr>
<td>Try Private</td>
<td>off | on; default: <b>off</b></td>
<td>Check if the remote Broker is another instance of a daemon.</td>
</tr>
<tr>
<td>Clean Session</td>
<td>off | on; default: <b>off</b></td>
<td>When turned on, discards session state after connecting or disconnecting.</td>
</tr>
<tr>
<td>Enable notification</td>
<td>off | on; default: <b>off</b></td>
<td>Publish notification messages to the local and remote brokers giving information about the state of the bridge connection.</td>
</tr>
<tr>
<td>Enable local notifications</td>
<td>off | on; default: <b>off</b></td>
<td>Only publish notification messages to the local broker giving information about the state of the bridge connection.</td>
</tr>
<tr>
<td>Keepalive interval</td>
<td>(5-65535); default: <b>60</b></td>
<td>Set the keepalive interval for this bridge connection, in seconds.</td>
</tr>
</table>
----
You can also create and manage MQTT topics in the <b>Topics</b> list below the Bridge section. To add a new topic, click the 'Add' button.
[[File:Networking_rutos_manual_mqtt_broker_settings_bridge_topics_add_button v2.png|border|class=tlt-border]]
You can then configure the newly added topic from the same page.
[[File:Networking_rutos_manual_mqtt_broker_settings_bridge_topics v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Topic Name</td>
<td>string; default: <b>none</b></td>
<td>The name of the topics that the broker will subscribe to.</td>
</tr>
<tr>
<td>Direction</td>
<td>OUT | IN | BOTH; default: <b>OUT</b></td>
<td>The direction that the messages will be shared.</td>
</tr>
<tr>
<td>QoS Level</td>
<td>At most once (0) | At least once (1) | Exactly once (2); default: <b>At most once (0)</b></td>
<td>Sets the publish/subscribe QoS level used for this topic.</td>
</tr>
</table>
===Miscellaneous===
----
The <b>Miscellaneous</b> section is used to configure MQTT broker parameters that are related to neither Security nor Bridge.
[[File:Networking_rutos_manual_mqtt_broker_settings_miscellaneous v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>ACL File</td>
<td>ACL file; default: <b>none</b></td>
<td>Uploads an ACL file. 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: <b>none</b></td>
<td>Uploads a password. A password file stores usernames and corresponding passwords, used for authentication.</td>
</tr>
<tr>
<td>Persistence</td>
<td>off | on; default: <b>off</b></td>
<td>When turned on, connection, subscription and message data will be written to the disk. Otherwise, the data is stored in the device memory only.</td>
</tr>
<tr>
<td>Allow Anonymous</td>
<td>off | on; default: <b>off</b></td>
<td>Turns anonymous access to this broker on or off.</td>
</tr>
<tr>
<td>Max queued messages</td>
<td>[0..65535]; default: <b>1000</b></td>
<td>The maximum number of QoS 1 and 2 messages to hold in a queue per client above those that are currently in-flight. Set to 0 for no maximum (not recommended).</td>
</tr>
<tr>
<td>Maximum packet size</td>
<td>[1..268435456]; default: <b>1048576</b></td>
<td>Maximum size of packet before it will be dropped.</td>
</tr>
</table>
==MQTT Publisher==
An <b>MQTT Publisher</b> is a client instance that can send messages to the Broker, who can forward these messages to other clients (subscribers).
<b>Note</b>: this table has coloring scheme to indicate which fields can be seen with different configuration.
[[File:Networking_rutos_manual_mqtt_publisher_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Toggles the MQTT Publisher ON or OFF.</td>
</tr>
<tr>
<td>Hostname</td>
<td>host | ip; default: <b>none</b></td>
<td>Broker’s IP address or hostname.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [0..65535]; default: <b>1883</b></td>
<td>Broker's port number.</td>
</tr>
<tr>
<td>Client ID</td>
<td>string; default: <b>empty</b></td>
<td>Client ID to send with the data. If empty, a random client ID will be generated.</td>
</tr>
<tr>
<td>Username</td>
<td>string; default: <b>none</b></td>
<td>Username used for authentication to the Broker.</td>
</tr>
<tr>
<td>Require password</td>
<td>check | uncheck; default: <b>Uncheck</b></td>
<td>Requires password for authentication.</td>
</tr>
<tr>
<td>Password</td>
<td>string; default: <b>none</b></td>
<td>Password used for authentication to the Broker.</td>
</tr>
<tr>
<td>TLS</td>
<td>off | <span style="color:blue"><b>on</b></span>; default: <b>off</b></td>
<td>Turns the use of Transport Layer Security (TLS) on or off.</td>
</tr>
<tr>
<td><span style="color:blue">On:</span> Allow insecure connection</td>
<td>off | on; default: <b>off</b></td>
<td>Allows connections without verifying server authenticity.</td>
</tr>
<tr>
<td>TLS type</td>
<td>Certificate based {{!}} <span style="color:darkred">Pre-shared key based</span>; 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> Certificate file</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> Key file</td>
<td>.key file; default: <b>none</b></td>
<td>Key file used in Transport Layer Security.</td>
</tr>
<tr>
<td><span style="color:darkred">Pre-shared key based:</span> Pre-Shared-Key</td>
<td>string; default: <b>none</b></td>
<td>The pre-shared-key in hex format with no leading "0x".</td>
</tr>
<tr>
<td><span style="color:darkred">Pre-shared key based:</span> Identity</td>
<td>string; default: <b>none</b></td>
<td>The identity of this client. May be used as the username depending on the server settings.</td>
</tr>
<tr>
<td>Publish topic prefix</td>
<td>string; default: <b>empty</b></td>
<td>Prefix of the topic to be used during publish. [[Monitoring_via_MQTT#How_MQTT_works|More information.]]</td>
</tr>
<tr>
<td>Subscribe topic prefix</td>
<td>string; default: <b>empty</b></td>
<td>Prefix of the topic to be used during subscription. [[Monitoring_via_MQTT#How_MQTT_works|More information.]] </td>
</tr>
</table>
[[Category:{{{name}}} Services section]]
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} MQTT (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} MQTT (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==Summary==
<b>MQTT (MQ Telemetry Transport or Message Queue Telemetry Transport)</b> is an ISO standard (ISO/IEC PRF 20922) publish-subscribe-based "lightweight" messaging protocol for use on top of the TCP/IP protocol. It is designed to send short messages from one client (<i>publisher</i>) to another (<i>subscriber</i>) through <i>brokers</i>, which are responsible for message delivery to the end point.
{{{name}}} devices support this functionality via an open source Mosquitto broker. The messages are sent this way: a client (subscriber) subscribes to a topic(s); a publisher posts a message to that specific topic(s). The broker then checks who is subscribed to that particular topic(s) and transmits data from the publisher to the subscriber.
This chapter is an overview of the MQTT page for {{{name}}} devices.
{{#switch: {{{series}}}
| #default =
| TRB2|RUT36X|RUT30X|RUT9|TCR1|RUT2|RUT2M|RUT9M|TRB2M|OTD140|RUT301|RUT14X =
<u><b>
Note:</b> MQTT is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
}}
==MQTT Broker==
The <b>MQTT Broker</b> is an entity that listens for connections on the specified port and relays received messages to MQTT client. To begin using this devices as an MQTT Broker, enable it in this page. In order to make the device accept MQTT connections from WAN (remote networks), you also need to turn the 'Enable Remote Access' slider on.
[[File:Networking_rutos_manual_mqtt_broker_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turn MQTT Broker on or off.</td>
</tr>
<tr>
<td>Custom configuration</td>
<td>off | on; default: <b>off</b></td>
<td>Enables reading of custom configuration.</td>
</tr>
<tr>
<td>Local Port</td>
<td>integer [0..65535]; default: <b>1883</b></td>
<td>The TCP port(s) on which the MQTT broker will listen for connections. Click the plus sign to add multiple ports.</td>
</tr>
<tr>
<td>Enable Remote Access</td>
<td>off | on; default: <b>off</b></td>
<td>Turns remote access to this MQTT broker on or off.</td>
</tr>
</table>
==Broker Settings==
===Security===
----
The <b>Security</b> section is used to configure TLS/SSL .
[[File:Networking rutos manual mqtt broker settings security v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Use TLS/SSL</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the use of TLS/SSL for this MQTT connection on or off.</td>
</tr>
<tr>
<td>TLS type</td>
<td>Certificate based {{!}} <span style="color:darkred">Pre-shared key based</span>; default: '''Certificate based'''</td>
<td>Select type of TLS.</td>
</tr>
<tr>
<td>Require certificate</td>
<td>off | on; default: <b>on</b></td>
<td>Demand client certificate and key from the client.</td>
</tr>
<tr>
<td>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>CA File</td>
<td>.ca file; default: <b>none</b></td>
<td>Uploads a Certificate Authority (CA) file. A Certificate Authority (CA) 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>CERT File</td>
<td>.crt file; default: <b>none</b></td>
<td>Uploads a server (broker) certificate file. A certificate file is a type of digital certificate that is used by client systems to make authenticated requests to a remote server.</td>
</tr>
<tr>
<td>Key File</td>
<td>.key file; default: <b>none</b></td>
<td>Uploads a server (broker) key file.</td>
</tr>
<tr>
<td>TLS version</td>
<td>tlsv1 | tlsv1.1 | tlsv1.2 | Support all; default: <b>Support all</b></td>
<td>Specifies which TLS version(s) is will be supported by this broker.</td>
</tr>
<tr>
<td><span style="color:darkred">Pre-shared key based:</span> Pre-Shared-Key</td>
<td>string; default: <b>none</b></td>
<td>The pre-shared-key in hex format with no leading "0x".</td>
</tr>
<tr>
<td><span style="color:darkred">Pre-shared key based:</span> Identity</td>
<td>string; default: <b>none</b></td>
<td>The identity of this client. May be used as the username depending on the server settings.</td>
</tr>
</table>
===Bridge===
----
An <b>MQTT Bridge</b> is used for the communication between MQTT brokers. The window of Bridge parameters is presented below.
<b>Note</b>: this table has a coloring scheme to indicate which fields can be seen with different configuration.
[[File:Networking_rutos_manual_mqtt_broker_settings_bridge_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turns MQTT Bridge on and off.</td>
</tr>
<tr>
<td>Connection Name</td>
<td>string; default: <b>none</b></td>
<td>Name of the Bridge connection. This is used for easier management purposes.</td>
</tr>
<tr>
<td>Protocol version</td>
<td>3.1 | 3.1.1; default: <b>3.1</b></td>
<td>Selects protocol version</td>
</tr>
<tr>
<td>Remote Address</td>
<td>ip; default: <b>none</b></td>
<td>Remote Broker’s address.</td>
</tr>
<tr>
<td>Remote Port</td>
<td>integer [0..65535]; default: '''1883'''</td>
<td>Specifies which port the remote broker uses to listen for connections.</td>
</tr>
<tr>
<td>Use Remote TLS/SSL</td>
<td>off | <span style="color:blue"><b>on</b></span>; default: '''off'''</td>
<td>Enables the use of TSL/SSL certificates of the remote broker. If this is checked, you will be prompted to upload TLS/SSL certificates. More information can be found in the [[#Security|Security]] section of this chapter.</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> Bridge CA File</td>
<td>.ca file; default: <b>none</b></td>
<td>Uploads a Certificate Authority (CA) file. A Certificate Authority (CA) 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:blue">On:</span> Bridge certificate File</td>
<td>.crt file; default: <b>none</b></td>
<td>Uploads a server (broker) certificate file. A certificate file is a type of digital certificate that is used by client systems to make authenticated requests to a remote server.</td>
</tr>
<tr>
<td><span style="color:blue">On:</span> Bridge Key File</td>
<td>.key file; default: <b>none</b></td>
<td>Uploads a server (broker) key file.</td>
</tr>
<tr>
<td><span style="color:blue">On:</span> Bridge TLS version</td>
<td>tlsv1 | tlsv1.1 | tlsv1.2; default: <b>tlsv1</b></td>
<td>TLS version used by the other broker.</td>
</tr>
<tr>
<td><span style="color:blue">On:</span> Bridge ALPN</td>
<td>string; default: <b>none</b></td>
<td>Configure the application layer protocol negotiation option for the TLS session. Useful for brokers that support both websockets and MQTT on the same port. </td>
</tr>
<tr>
<td>Use Remote Bridge Login</td>
<td>off | <span style="color:red"><b>on</b></span>; default: <b>off</b></td>
<td>Indicates whether the remote side of the connection requires login information. If this is turned on, you will be required to enter a remote client ID, username and password.</td>
</tr>
<tr>
<td><span style="color:red">On:</span> Remote ID</td>
<td>string; default: <b>none</b></td>
<td>Identifier of the remote broker</td>
</tr>
<tr>
<td><span style="color:red">On:</span> Remote Username</td>
<td>string; default: <b>none</b></td>
<td>Username for authentication to the remote broker.</td>
</tr>
<tr>
<td><span style="color:red">On:</span> Require password</td>
<td>on | off; default: <b>off</b></td>
<td>Password for authentication to the remote broker.</td>
</tr>
<tr>
<td><span style="color:red">On:</span> Remote Password</td>
<td>string; default: <b>none</b></td>
<td>Password for authentication to the remote broker.</td>
</tr>
<tr>
<td>Try Private</td>
<td>off | on; default: <b>off</b></td>
<td>Check if the remote Broker is another instance of a daemon.</td>
</tr>
<tr>
<td>Clean Session</td>
<td>off | on; default: <b>off</b></td>
<td>When turned on, discards session state after connecting or disconnecting.</td>
</tr>
<tr>
<td>Enable notification</td>
<td>off | on; default: <b>off</b></td>
<td>Publish notification messages to the local and remote brokers giving information about the state of the bridge connection.</td>
</tr>
<tr>
<td>Enable local notifications</td>
<td>off | on; default: <b>off</b></td>
<td>Only publish notification messages to the local broker giving information about the state of the bridge connection.</td>
</tr>
<tr>
<td>Keepalive interval</td>
<td>(5-65535); default: <b>60</b></td>
<td>Set the keepalive interval for this bridge connection, in seconds.</td>
</tr>
</table>
----
You can also create and manage MQTT topics in the <b>Topics</b> list below the Bridge section. To add a new topic, click the 'Add' button.
[[File:Networking_rutos_manual_mqtt_broker_settings_bridge_topics_add_button v2.png|border|class=tlt-border]]
You can then configure the newly added topic from the same page.
[[File:Networking_rutos_manual_mqtt_broker_settings_bridge_topics v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Topic Name</td>
<td>string; default: <b>none</b></td>
<td>The name of the topics that the broker will subscribe to.</td>
</tr>
<tr>
<td>Direction</td>
<td>OUT | IN | BOTH; default: <b>OUT</b></td>
<td>The direction that the messages will be shared.</td>
</tr>
<tr>
<td>QoS Level</td>
<td>At most once (0) | At least once (1) | Exactly once (2); default: <b>At most once (0)</b></td>
<td>Sets the publish/subscribe QoS level used for this topic.</td>
</tr>
</table>
===Miscellaneous===
----
The <b>Miscellaneous</b> section is used to configure MQTT broker parameters that are related to neither Security nor Bridge.
[[File:Networking_rutos_manual_mqtt_broker_settings_miscellaneous v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>ACL File</td>
<td>ACL file; default: <b>none</b></td>
<td>Uploads an ACL file. 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: <b>none</b></td>
<td>Uploads a password. A password file stores usernames and corresponding passwords, used for authentication.</td>
</tr>
<tr>
<td>Persistence</td>
<td>off | on; default: <b>off</b></td>
<td>When turned on, connection, subscription and message data will be written to the disk. Otherwise, the data is stored in the device memory only.</td>
</tr>
<tr>
<td>Allow Anonymous</td>
<td>off | on; default: <b>off</b></td>
<td>Turns anonymous access to this broker on or off.</td>
</tr>
<tr>
<td>Max queued messages</td>
<td>[0..65535]; default: <b>1000</b></td>
<td>The maximum number of QoS 1 and 2 messages to hold in a queue per client above those that are currently in-flight. Set to 0 for no maximum (not recommended).</td>
</tr>
<tr>
<td>Maximum packet size</td>
<td>[1..268435456]; default: <b>1048576</b></td>
<td>Maximum size of packet before it will be dropped.</td>
</tr>
</table>
==MQTT Publisher==
An <b>MQTT Publisher</b> is a client instance that can send messages to the Broker, who can forward these messages to other clients (subscribers).
<b>Note</b>: this table has coloring scheme to indicate which fields can be seen with different configuration.
[[File:Networking_rutos_manual_mqtt_publisher_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Toggles the MQTT Publisher ON or OFF.</td>
</tr>
<tr>
<td>Hostname</td>
<td>host | ip; default: <b>none</b></td>
<td>Broker’s IP address or hostname.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [0..65535]; default: <b>1883</b></td>
<td>Broker's port number.</td>
</tr>
<tr>
<td>Client ID</td>
<td>string; default: <b>empty</b></td>
<td>Client ID to send with the data. If empty, a random client ID will be generated.</td>
</tr>
<tr>
<td>Username</td>
<td>string; default: <b>none</b></td>
<td>Username used for authentication to the Broker.</td>
</tr>
<tr>
<td>Require password</td>
<td>check | uncheck; default: <b>Uncheck</b></td>
<td>Requires password for authentication.</td>
</tr>
<tr>
<td>Password</td>
<td>string; default: <b>none</b></td>
<td>Password used for authentication to the Broker.</td>
</tr>
<tr>
<td>TLS</td>
<td>off | <span style="color:blue"><b>on</b></span>; default: <b>off</b></td>
<td>Turns the use of Transport Layer Security (TLS) on or off.</td>
</tr>
<tr>
<td><span style="color:blue">On:</span> Allow insecure connection</td>
<td>off | on; default: <b>off</b></td>
<td>Allows connections without verifying server authenticity.</td>
</tr>
<tr>
<td>TLS type</td>
<td>Certificate based {{!}} <span style="color:darkred">Pre-shared key based</span>; 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> Certificate file</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> Key file</td>
<td>.key file; default: <b>none</b></td>
<td>Key file used in Transport Layer Security.</td>
</tr>
<tr>
<td><span style="color:darkred">Pre-shared key based:</span> Pre-Shared-Key</td>
<td>string; default: <b>none</b></td>
<td>The pre-shared-key in hex format with no leading "0x".</td>
</tr>
<tr>
<td><span style="color:darkred">Pre-shared key based:</span> Identity</td>
<td>string; default: <b>none</b></td>
<td>The identity of this client. May be used as the username depending on the server settings.</td>
</tr>
<tr>
<td>Publish topic prefix</td>
<td>string; default: <b>empty</b></td>
<td>Prefix of the topic to be used during publish. [[Monitoring_via_MQTT#How_MQTT_works|More information.]]</td>
</tr>
<tr>
<td>Subscribe topic prefix</td>
<td>string; default: <b>empty</b></td>
<td>Prefix of the topic to be used during subscription. [[Monitoring_via_MQTT#How_MQTT_works|More information.]] </td>
</tr>
</table>
[[Category:{{{name}}} Services section]]
