-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mosquitto 2.0.11/2.0.18 Bridge => disconnected due to malformed packet on retained packet #3073
Comments
I suppose it has to do with the number of retained messages received upon connection. If I subscribe to a more specific topic, limiting the number of retained messages received upon connection, I don't get disconnects in the very same topic I got disconnected before. |
subscribe using There seems to be a problem with high volume incoming data
|
The 'high volume' on connection is due to the large number of retained topics and expected. |
Installed 2.0.18 from https://repo.mosquitto.org/ issue persists. |
Hi
I'm aware 2.0.11 is not the latest version, but I found no indication that this is a known and fixed issue with newer versions.
I'm bridging my local mosquitto broker with the meshtastic broker. This worked fine for several months but as the user number has grown significantly suddnely it stopped working and I get disconnected because of malformed packets:
But my broker disconnects the bridge while getting the initial retained messages:
Sometimes, when I delete the last topic which was published this seems to solve the issue, only to fail on another one.
When I look at the transactions via wireshark, I don't see any obvious problems. It's hard to tell, as all topics are transmitted in one huge transaction.
I wonder if this could be due to a limitation of the receive buffer or similar.
I attempted to switch to protocol 50 but that did not resolve the issue.
Maybe somebody could get me more insight on how to further pin down the cause of that issue?
-Benoit-
The text was updated successfully, but these errors were encountered: