First time here? Check out the FAQ!
THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
0

MQTT5 publish packets not dissected correctly unless Connect command packet is captured [closed]

  • retag add tags

MQTT5 packets include properties right before the message. MQTT3 packets do not include properties. See: https://docs.oasis-open.org/mqtt/mqtt...

When capturing MQTT5 traffic, the properties are not dissected properly. E.g., a "property length" byte of zero is displayed as a zero byte at the start of the message, resulting in a "Trailing stray characters" warning:

image description

Only when the Connect command packet is also captured, which includes the version number 5, are the properties displayed correctly:

image description

image description

Is there any way to get Wireshark to display MQTT5 packets correctly even when the Connect command packet is not part of the capture? Is there a setting for "MQTT version"? I did not find anything like that.

veracl's avatar
3
veracl
asked 2020-07-26 15:55:55 +0000, updated 2020-07-26 16:07:04 +0000
edit flag offensive 0 remove flag reopen merge delete

Closed for the following reason "the question is answered, right answer was accepted" by veracl 2020-07-27 12:19:02 +0000

Comments

add a comment see more comments

1 Answer

0

Yes, download the development version of Wireshark, which has a fix for bug 16722 addressing just this.

Jaap's avatar
13.7k
Jaap
answered 2020-07-26 17:00:46 +0000
edit flag offensive 0 remove flag delete link

Comments

Great, thanks. That works.

veracl's avatar veracl (2020-07-27 12:18:09 +0000) edit
add a comment see more comments