Wireshark-bugs: [Wireshark-bugs] [Bug 10872] New: ZigBee epoch time is incorrectly displayed in
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 19 Jan 2015 17:06:25 +0000
Bug ID 10872
Summary ZigBee epoch time is incorrectly displayed in OTA cluster
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter alan.michael.bowman@gmail.com 

Build Information:
Version 1.99.2-683-gb2c4586 (v1.99.2rc0-683-gb2c4586 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 GTK+ 2.24.23, with Cairo 1.12.16, with Pango 1.36.8,
with
WinPcap (4_1_3), with libz 1.2.5, 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, with PortAudio V19-devel (built Jan 16 2015), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
English_United Kingdom.1252, 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) Xeon(R) CPU           W3530  @ 2.80GHz (with SSE4.2), with 6141MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 31101
--
In the ZigBee OTA cluster, UpgradeEndResponse message, there is a field that
contains the current time (and also one for the Upgrade time).  This field
should be seconds since the ZigBee epoch (1/1 2000).

The capture reported in bug 10855 displays this (when the patch to fix that bug
is applied).

The same issue was seen (and fixed) in the ZigBee messaging cluster in bug
9128.

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