| Bug ID |
11424
|
| Summary |
Vssmonitoring Timestamp
|
| Product |
Wireshark
|
| Version |
1.12.6
|
| Hardware |
x86-64
|
| OS |
Windows Server 2008 R2
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13787 [details]
vssmonitoring Failed timestamp decode
Build Information:
Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Jun 17 2015),
with
AirPcap.
Running on 64-bit Windows Server 2008R2 Service Pack 1, build 7601, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, with 16349MB of physical
memory.
--
I am using VSS Monitoring equipment. The equipment add a trailer for timestamp,
and I am not using portstamp. The process is explained in this document
(http://www.vssmonitoring.com/portals/application_note/Port%20and%20Time%20Stamping.pdf).
On most of the packets, it is working fine, but some of the packets, it shows
the bytes as a trailer only, and combines the trailer with the VLAN tag. I
noticed in the packets with the failed decode, the length of the vssmonitoring
tag is 10 bytes instead of 8 in the successful ones. But looking at
epan-dissectors-packet-vssmonitoring.c, 10 bytes should be successful anyway.
Attached is a pcapng file with the failed decodes.
You are receiving this mail because:
- You are watching all bug changes.