https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4720
Summary: Ethernet Global Data (EGD) timestamp field has wrong
byte order
Product: Wireshark
Version: 1.2.7
Platform: x86
OS/Version: Windows XP
Status: NEW
Severity: Minor
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: oliver@xxxxxxxxxxxxxxxxx
Build Information:
Version 1.2.7 (SVN Rev 32341)
Copyright 1998-2010 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 with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, without libpcre, with SMI 0.4.8,
with c-ares 1.7.0, with Lua 5.1, with GnuTLS 2.8.5, with Gcrypt 1.4.5, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 31 2010), with
AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.1
(packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 30729
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Recently Wireshark has added GE's EGD packets to its vast array of supported
protocols. EGD packets have a simple 32 byte header, two fields of which are a
timestamp (1st seconds since 1970, 2nd nano seconds).
When interpreted by wireshark, these two fields are displayed as having the
opposite byte-order to everything else. From what I understand in the EGD spec,
there is no mention that these two fields should use a different endian to the
rest of the header (and this is indeed supported by the compiled examples from
http://application.gefanuc.com/support/plc/fax06810.htm)
Could you confirm this?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.