Wireshark-bugs: [Wireshark-bugs] [Bug 6649] New: ZigBee ZCL Dissector reports invalid status
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 6 Dec 2011 09:03:33 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6649

           Summary: ZigBee ZCL Dissector reports invalid status
           Product: Wireshark
           Version: 1.6.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: honarbacht@xxxxxxxxx


Created an attachment (id=7528)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=7528)
A configure reporting response frame with status code 0x8d

Build Information:
Version 1.6.2 (SVN Rev 38931 from /trunk-1.6)

Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3,
with
Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Sep
 7 2011), with AirPcap.

Running on 32-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022
--
The status code 0x8d contained in an attriute status record in a configure
reporting response frame is incorrectly displayed as "Write only" (where
WRITE_ONLY = 0x8f). According to the ZigBee Cluster Library Specification,
Document 075123r03ZB, April 26, 2010 a status of 0x8d should display as
"INVALID_DATA_TYPE". This is likely to affect other attribute status records as
well (i.e. read attribute, write attribute commands).

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.