Wireshark-bugs: [Wireshark-bugs] [Bug 10860] New: ZigBee ZCL cluster dissector incorrectly tied
| Bug ID |
10860
|
| Summary |
ZigBee ZCL cluster dissector incorrectly tied to ProfileId
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
chris.brandson@gmail.com
|
Build Information:
Version 1.99.2 (v1.99.2rc0-681-gd009b55 from master)
Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (64-bit) with Qt 4.8.6, with libpcap, without POSIX capabilities,
without libnl, with libz 1.2.8, with GLib 2.40.2, without SMI, without c-ares,
without ADNS, without Lua, with GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT
Kerberos, without GeoIP, without PortAudio, with AirPcap.
Running on Linux 3.13.0-43-generic, with locale en_CA.UTF-8, with libpcap
version 1.5.3, with libz 1.2.8, with GnuTLS 2.12.23, with Gcrypt 1.5.3, without
AirPcap.
Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz
Built using gcc 4.8.2.
--
Originally ZigBee Clusters were tied to ProfileIds. Over time clusters were
reused between profiles and the recent Profile Interop effort further reduces
this dependence. In proto_reg_handoff_zbee_zcl() the ZCL handler is added on a
profile by profile in a hardcoded list. This led to problems recently when the
Retail Services profile was added and packets were not being dissected. Over
time more profiles and clusters will be added creating a maintenance problem
with the current design.
ZDO and Test Profile #2 are the only non-ZCL clusters. The ZCL dissector could
use the defined cluster range and/or the ZCL dissector could be converted to a
heuristic dissector to alleviate this problem. This problem has independently
been raised on the ZigBee Alliance mailing list.
You are receiving this mail because:
- You are watching all bug changes.
