mosquitto | open source implementation of a server for version

by iosphere C Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | mosquitto Summary

mosquitto is a C library. mosquitto has no bugs and it has low support. However mosquitto has 15 vulnerabilities and it has a Non-SPDX License. You can download it from GitHub.

Mosquitto is an open source implementation of a server for version 3.1 and 3.1.1 of the MQTT protocol.

Support

Quality

Security

License

Reuse

Support

mosquitto has a low active ecosystem.

It has 28 star(s) with 30 fork(s). There are 11 watchers for this library.

It had no major release in the last 6 months.

mosquitto has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of mosquitto is current.

Quality

mosquitto has no bugs reported.

Security

mosquitto has 15 vulnerability issues reported (0 critical, 8 high, 7 medium, 0 low).

License

mosquitto has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

mosquitto releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of mosquitto

Get all kandi verified functions for this library.

mosquitto Key Features

No Key Features are available at this moment for mosquitto.

mosquitto Examples and Code Snippets

No Code Snippets are available at this moment for mosquitto.

Community Discussions

Trending Discussions on mosquitto

Error: Address in use 1883 mosquito Docker

How to update mosquitto to latest version in Ubuntu

How to configure security for Mosquitto with Godaddy certificates

On Windows, PowerShell misinterprets non-ASCII characters in mosquitto_sub output

Lenses MQTT Source Connector doesn't send PINGREQ to MQTT Broker when idle in its keep-alive time

Mosquitto with persitence as MQTT Forwarding Broker

TLS server authentication fails when connecting to mosquitto from a remote client (but it works If I connect locally with the same certificate)

Telegraf connection to Mosquitto using TLS

How to capture MQTT data locally in SSH remote server using Wireshark?

mosquitto : broker stop publish to some clients but subscription ok

QUESTION

Error: Address in use 1883 mosquito Docker

Asked 2021-Jun-11 at 02:49

Getting error on starting mosquito docker in ubuntu 16.04.

...

ANSWER

Answered 2020-Dec-30 at 17:33

You just have another instance of Mosquitto already running.

Use ps ax | grep mosq to see if Mosquitto is still running outside of a container. If you find it, use sudo kill -9 PID where you replace PID with its process ID. Or you can try sudo killall -9 mosquitto.

If that doesn't solve the problem, check Docker.

Use docker ps to list all the Docker containers currently running.

Use docker stop ID where you replace the ID for each container that's running.

If you fail to find an instance of Mosquitto, reboot your computer and try again.

Source https://stackoverflow.com/questions/65510991

QUESTION

How to update mosquitto to latest version in Ubuntu

Asked 2021-May-29 at 14:33

I have installed mosquitto in ubuntu using command:

...

ANSWER

Answered 2021-May-29 at 14:33

If you want a more recent version of mosquitto but you are on an earlier version of Ubuntu then by reading the official download page here you can find that there is more than one approach to install the latest mosquitto version :

Compiling and building directly from source, i wouldn't recommend this.
using the mosquitto-dev PPA.
using snap packages instead of apt and the official repos by simply running sudo snap install mosquitto

However i think the best way to go is by using the mosquitto-dev PPA as building mosquitto from source take more time and effort and using snap involve more tweaks to get up and running.

So.. first uninstall the old mosquitto :

Source https://stackoverflow.com/questions/67613899

QUESTION

How to configure security for Mosquitto with Godaddy certificates

Asked 2021-May-27 at 12:04

I am able to configure security with the openssl certificates. But with the Godaddy certificates, I could not configure the secure mosquitto. I got 3 files from Godaddy SSL,

2324145e73d34dad.crt
2324145e73d34dad.pem
gd_bundle-g2-g1.crt

As per the Godaddy site, the 1st one is Root certificate i.e ca.crt 3rd one is the intermediate / chain certificate.

But I want the server.crt and server.key to configure.

How can we configure the ssl with those files? Can we generate the server.key and server.crt with them?

...

ANSWER

Answered 2021-May-25 at 10:42

You should already have the private key, you needed to use it to generate the CSR you sent to Godaddy to get the certificate signed.

2324145e73d34dad.pem sounds like it's your server certificate (which is what mosquitto wants)

From the man page:

certfile file path

Path to the PEM encoded server certificate. This option and keyfile must be present to enable certificate based TLS encryption.

Source https://stackoverflow.com/questions/67685587

QUESTION

On Windows, PowerShell misinterprets non-ASCII characters in mosquitto_sub output

Asked 2021-May-26 at 16:04

Note: This self-answered question describes a problem that is specific to using Eclipse Mosquitto on Windows, where it affects both Windows PowerShell and the cross-platform PowerShell (Core) edition, however.

I use something like the following mosquitto_pub command to publish a message:

...

ANSWER

Answered 2021-May-26 at 16:04

Problem:

While the mosquitto_sub man page makes no mention of character encoding as of this writing, it seems that on Windows mosquitto_sub exhibits nonstandard behavior in that it uses the system's active ANSI code page to encode its string output rather than the OEM code page that console applications are expected to use.^[1]

There also appears to be no option that would allow you to specify what encoding to use.

PowerShell decodes output from external applications into .NET strings, based on the encoding stored in [Console]::OutputEncoding, which defaults to the OEM code page. Therefore, when it sees the ANSI byte representation of character é, 0xe9, in the output, it interprets it as the OEM representation, where it represents character Θ (the assumption is that the active ANSI code page is Windows-1252, and the active OEM code page IBM437, as is the case in US-English systems, for instance).

You can verify this as follows:

Source https://stackoverflow.com/questions/66990509

QUESTION

Lenses MQTT Source Connector doesn't send PINGREQ to MQTT Broker when idle in its keep-alive time

Asked 2021-May-25 at 13:59

PROBLEM -

I have created an MQTT Source Connector using Lenses. The connector works fine till the data is being published on my MQTT Mosquitto broker and works seemlessly. Now, when i stop publishing the data and there is no data sent to the mqtt source connector, after about 4-5 mins , if i start publishing the data again , the data doesn't come in my source connector even though the connector is still in running state. For resolving this i need to restart my connector everytime which is bad.

METHODS I HAVE ALREADY TRIED -

Even though the client id is unique, i still changed it everytime to see if that was the issue. But it didn't work.
Tried increasing the keepalive interval to 10 mins but that didn't work too.
There were no error logs in kafka connect logs for this for a long time, but once in 15-20 tries i received this Socket Connection Error

UPDATE

Upon digging more into the issue, I found out that my source connector (behaving as an mqtt client) was not sending any PINGREQ packets to my Mosquitto MQTT broker when it was idle in its keep-alive time interval while other client conencted to my mqtt broker were sending their PINGREQ packets when they were idle and hence the connection between the source connector and the mqtt broker was getting dropped.

Do I need to specify any property explicitly in my MQTT Source Connector properties file to send a PINGREQ packet to the MQTT broker in the keep-alive time or does the connector handles that itself ?

...

ANSWER

Answered 2021-May-25 at 13:59

After a long research , I found out the default keep-alive time which Lenses connector was using (5000) was in seconds. 5000 seconds was way too big, so the mqtt-broker was disconnecting the client even before the first PINGREQ was sent by the client in its keep-alive time. I reduced the keep-alive time to 5 seconds by adding the line connect.mqtt.keep.alive=5 in my connector properties file. This resolved the issue.

Source https://stackoverflow.com/questions/67606647

QUESTION

Mosquitto with persitence as MQTT Forwarding Broker

Asked 2021-May-24 at 08:12

We want to use Mosquitto MQTT as Message Broker on a number of OpenWRT gateways to forward "local" anonymous MQTT publications to a central RabbitMQ/MQTT cluster with authorization.

Our Problem:

Mosquitto does not reliable forward queued messages when restarted (persistance does not work)

Running mosquitto version: 1.4.15

current config

This is the last tested config:

...

ANSWER

Answered 2021-May-24 at 08:12

After running an update to mosquitto version 1.6.10 still no success.

I could isolate the main problem - the database did not save when seetings:

Source https://stackoverflow.com/questions/67634784

QUESTION

TLS server authentication fails when connecting to mosquitto from a remote client (but it works If I connect locally with the same certificate)

Asked 2021-May-21 at 14:46

I have a mosquitto broker running on a raspbian instance. I then have an ubuntu instance which I'm trying to use to publish a message using mosquitto_pub with TLS server authentication, by Running this command:

...

ANSWER

Answered 2021-May-20 at 14:22

A guess from an issue I have sometimes regarding TLS, you might need to disable the hostname verification. mosquitto_sub has the --insecure flag for that:

--insecure

When using certificate based encryption, this option disables verification of the server hostname in the server certificate. This can be useful when testing initial server configurations but makes it possible for a malicious third party to impersonate your server through DNS spoofing, for example. Use this option in testing only. If you need to resort to using this option in a production environment, your setup is at fault and there is no point using encryption.

Source: https://mosquitto.org/man/mosquitto_sub-1.html

As having the hostname verification disabled isn't a good idea here a good article how to solve this issue: Certificate for doesn't match any of the subject alternative names

Source https://stackoverflow.com/questions/67618833

QUESTION

Telegraf connection to Mosquitto using TLS

Asked 2021-May-16 at 13:25

In my system (with raspberry) I have some sensors that publish data to Mosquitto, I'm using Telegraf to transfer the data do an influxDB database and I'm using Grafana to show the data.

During the test without TLS connection (in mosquittos) everything works correctly but when I activated the TLS I start to have a problem with Telegraf.

The sensor are sending the data to the broker using the client.key, client.crt and ca.crt. In the broker I can see the data from the sensor. So I think the problem in not in this.

In telegraf (I suppose it works as client) I tried to configure the TLS connection. Looking at the telegraf.service status , it is active and running. Looking at the journal I don't see errors in the connection but I can't see any data from the broker.

In Telegraf.conf I set the certificate as you can see here below. Instead using pem file I used the file that I use for the sensor or other client connected to the system: the extension is different and I don't know if the problem is here.

Here the configuration of Telegraf (mqtt_consumer)

...

ANSWER

Answered 2021-Jan-13 at 14:48

Your MQTT URL starts with tcp:// but it should start with ssl:// for a MQTT over SSL connection.

Source https://stackoverflow.com/questions/65702577

QUESTION

How to capture MQTT data locally in SSH remote server using Wireshark?

Asked 2021-May-15 at 15:45

I want to capture MQTT packets on the SSH Linux-based remote server using Wireshark from my home. I can capture data go out through the Internet, such as when I use this command line mosquitto_pub -h test.mosquitto.org -t topic -m "Hello", I can see the packets in Wireshark. But, When I publish data in localhost, such as using this command mosquitto_pub -d -h localhost -t hello/world -m "75" I can't see any packets in Wireshark. I want to make a client/server in the same remote server.

I use this command to open Wireshark:

...

ANSWER

Answered 2021-May-15 at 15:45

You didn't specify the interface that tcpdump should capture on. Try adding the -i lo option, as in:

Source https://stackoverflow.com/questions/67547125

QUESTION

mosquitto : broker stop publish to some clients but subscription ok

Asked 2021-May-03 at 13:07

The context:

mosquitto broker 1.5.7 running on a private cloud:

Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux

Extract of mosquitto.conf:

...

ANSWER

Answered 2021-May-03 at 13:07

I finally find a solution to make my architecture work: I switch the Qos SUB of all my devices to Qos1 (instead of Qos2).

My conclusion is the Qos2 on SUB is not well managed by the broker if multiple subscribers on the same topic (7 in my case).

In this case: turn Qos SUB to Qos 1 and it works fine!

Source https://stackoverflow.com/questions/67299775

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install mosquitto

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: