Wireshark-bugs: [Wireshark-bugs] [Bug 12021] New: PDU header timestamp truncated in DIS dissecto
| Bug ID |
12021
|
| Summary |
PDU header timestamp truncated in DIS dissector
|
| Product |
Wireshark
|
| Version |
2.1.x (Experimental)
|
| Hardware |
All
|
| OS |
All
|
| Status |
CONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
alpartis@thundernet.com
|
Build Information:
$ ./wireshark -v
Wireshark 2.1.0 (v2.1.0rc0-1428-gf6791c1 from master)
Copyright 1998-2016 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, with POSIX capabilities
(Linux), without libnl, with libz 1.2.8, with GLib 2.38.2, without SMI,
without c-ares, without ADNS, without Lua, with GnuTLS 3.1.28, with Gcrypt
1.5.3, with MIT Kerberos, without GeoIP, with QtMultimedia, without
AirPcap.
Running on Linux 3.19.8-100.fc20.x86_64, with locale C, with libpcap
version 1.5.3, with libz 1.2.8, with GnuTLS 3.1.28, with Gcrypt 1.5.3.
Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz (with SSE4.2)
Built using gcc 4.8.3 20140911 (Red Hat 4.8.3-7).
--
Problem observed using SimPhonics V+ to generate DIS packet capture then
dissecting with wireshark running on various platforms: Windows 7, 8.1, 10, and
64-bit linux (Fedora).
----- description of problem:
IEEE 1278.1-2012 DIS spec details the PDU header timestamp in section 6.2.88 as
a 31-bit unsigned integer count of microseconds since the start of the current
interval (start of the hour UTC in the case of absolute timestamps for
example). The wireshark DIS dissector instead calculates and presents only to
millisecond resolution and truncates the existing microsecond data in the
captured packets.
This bug report is primarily for documentation purposes and reference for
anyone else observing this. A fix for this is already commited in change
#13210 https://code.wireshark.org/review/13210 .
You are receiving this mail because:
- You are watching all bug changes.
