Wireshark-bugs: [Wireshark-bugs] [Bug 6304] Incorrect dissection of ZigBee "Write Attributes Res
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6304
Bill Meier <wmeier@xxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Major |Minor
--- Comment #1 from Bill Meier <wmeier@xxxxxxxxxxx> 2011-09-02 12:34:13 EDT ---
I note from the spec (page 24):
"2.4.5.1.2 Status Field
The status field is 8-bits in length and specifies the status of the write
operation attempted on this attribute, as detailed in 2.4.3.3.
Note that write attribute status records are not included for successfully
written attributes, in order to save bandwidth. In the case of successful
writing of all attributes, only a single write attribute status record shall be
included in the command, with the status field set to SUCCESS and the attribute
identifier field omitted."
The way I read the above, it would seem that in the SUCCESS case there should
be no attribute ID (and thus the packet is arguably actually malformed).
I've no knowledge of the ZigBee protocol so I'll defer to someone familiar with
the protocol...
P.S. Normally (when appropriate) a small capture file should be attached to a
bug report which can be used to demonstrate the problem and test a fix.
In this case I generated a pcap capture file from the hex bytes in the images
using text2pcap; I'll attach the generated pcap file to this bug report
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
