Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
howto:mqtt [2023/08/04 20:29] – It's "MQTT" digital manhowto:mqtt [2023/10/01 18:43] (current) – Add firewall note Ree
Line 1: Line 1:
 ====== MQTT ====== ====== MQTT ======
 +
 +===== Setup =====
 +
 This is a bit of a stub for MQTT but it'll help you get going, on Ubuntu at least. This is a bit of a stub for MQTT but it'll help you get going, on Ubuntu at least.
  
Line 121: Line 124:
  
 For collecting data and viewing, I highly recommend Node-Red. You can find installation instructions online and should be able to figure its usage but I highly recommend using the current node.js (Node 18 currently) and install the Dashboard module (which will not run on the Ubuntu provided version of node.js). For collecting data and viewing, I highly recommend Node-Red. You can find installation instructions online and should be able to figure its usage but I highly recommend using the current node.js (Node 18 currently) and install the Dashboard module (which will not run on the Ubuntu provided version of node.js).
 +
 +===== WebSockets =====
 +
 +New browser-based Web Monitor and Node Spy features have been added in 3.20, which are powered by MQTT.  The first time you load either of these features you'll be prompted to provide the Hostname and WebSocket Ports for your MQTT server (these are different than the WebSocket ports used to power fTelnet).
 +
 +Keep in mind that it's your web browser connecting to the MQTT server, so you need to provide a hostname that is reachable by your web browser (ie if your BBS is running on a VPS, then localhost won't be a good choice for the Hostname, unless you plan to remote into that VPS and launch a browser from there).
 +
 +For the WebSocket ports, you'll need to update your Mosquitto server's configuration to listen on additional ports, because it doesn't do this by default.  The config file does a pretty good job of explaining this, but just to give a working example here's what my config file looks like (of course the cert paths will be different for you):
 +
 +    # mqtt protocol standard port
 +    listener 1883
 +    
 +    # mqtt protocol ssl port
 +    listener 8883
 +    certfile C:\Retsyn\Certificates\bbs.ftelnet.ca.pem
 +    keyfile C:\Retsyn\Certificates\bbs.ftelnet.ca.key.pem
 +    
 +    # websocket protocol standard port
 +    listener 1884
 +    protocol websockets
 +    socket_domain ipv4
 +    
 +    # websocket protocol ssl port
 +    listener 8884
 +    protocol websockets
 +    socket_domain ipv4
 +    certfile C:\Retsyn\Certificates\bbs.ftelnet.ca.pem
 +    keyfile C:\Retsyn\Certificates\bbs.ftelnet.ca.key.pem
 +
 +My understanding is that the SSL certs created by the Synchronet Let's Encrypt client can be converted to a format that is usable by Mosquitto, but I haven't investigated that because I run a separate client to handle my SSL certs.  If someone else goes through the conversion process, please add the steps/commands here!
 +
 +===== Security =====
 +
 +It is VERY important that you DO NOT open any of the MQTT ports to the general public.  Sensitive information may be published to some topics, and other topics allow controlling your BBS (eg downing nodes).  So please make sure your MQTT ports are behind a firewall, and if you want to make use of the Web Monitor or Node Spy features, then only IP addresses belonging to you should be allowed through.
  
 ===== See Also ===== ===== See Also =====

Trace: