mqtt: Fix subscribe/suback QoS values

Change-Id: I15424b768e6e0fe2e8268db69b82d81351146155
Reviewed-on: https://code.wireshark.org/review/17643
Reviewed-by: Stig Bjørlykke <stig@bjorlykke.org>
This commit is contained in:
Stig Bjørlykke 2016-09-11 20:21:10 +02:00
parent bb46efdca9
commit c2b858e26d
1 changed files with 6 additions and 8 deletions

View File

@ -97,17 +97,15 @@ static const value_string mqtt_qos_vals[] = {
{ 0, NULL }
};
#define MQTT_QOS_0 0
#define MQTT_QOS_1 1
#define MQTT_QOS_2 2
#define MQTT_SUBACK_FAILURE 128
static const value_string mqtt_subqos_vals[] = {
{ MQTT_QOS_0, "0" },
{ MQTT_QOS_1, "1" },
{ MQTT_QOS_2, "2" },
{ MQTT_SUBACK_FAILURE, "Failure" },
{ 0, NULL }
{ MQTT_QOS_ATMOST_ONCE, "At most once delivery (Fire and Forget)" },
{ MQTT_QOS_ATLEAST_ONCE, "At least once delivery (Acknowledged deliver)" },
{ MQTT_QOS_EXACTLY_ONCE, "Exactly once delivery (Assured Delivery)" },
{ MQTT_QOS_RESERVED, "Reserved" },
{ MQTT_SUBACK_FAILURE, "Failure" },
{ 0, NULL }
};
#define MQTT_CON_ACCEPTED 0