Wireshark-bugs: [Wireshark-bugs] [Bug 11564] New: Address field in ZigBee Link Status messages n
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 01 Oct 2015 07:58:54 +0000
Bug ID 11564
Summary Address field in ZigBee Link Status messages not displayed correctly
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86-64
OS Windows 10
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter honarbacht@ubisys.de 

Created attachment 13898 [details]
Example trace with link status messages

Build Information:
Version 1.99.9 (v1.99.9-0-g52a4a78 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 5.3.1, with WinPcap (unknown), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, without PortAudio,
with AirPcap.

Running on 64-bit Windows 10, build 10240, with locale C, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz, with 6077MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 31101

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.Paste the
COMPLETE build information from "Help->About Wireshark", "wireshark -v", or
"tshark -v".
--
The address field in link status messages is not displayed correctly. Attached
is a .pcap with a short joining sequence to include the network key and a
couple of link status messages. The address field in the example should show
0x61fd, but appears to be random in the display. In the "Decrypted ZigBee
Payload" view all is fine. Also a screen-shot attached which highlights the
issue.

You are receiving this mail because:
  • You are watching all bug changes.