| Bug ID |
12162
|
| Summary |
packet timestamp zeroes after two pass tshark run
|
| Product |
Wireshark
|
| Version |
1.12.8
|
| Hardware |
x86
|
| OS |
Windows 10
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
TShark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
TShark 1.12.8 (v1.12.8-0-g5b6e543 from master-1.12)
Copyright 1998-2015 Gerald Combs <[email protected]> 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 (64-bit) 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.
Running on 64-bit Windows 10, build 10586, without WinPcap.
Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz, with 16266MB of physical memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
After running this commandline:
tshark -r a.pcap -w b.pcap -2 -R openflow
The 'timestamp' field of all packets in b.pcap (output file) is now 0. In
a.pcap, it wasn't 0.
Without '-2', the timestamps are remained OK.
Checked also on Linux Ubuntu with TShark 1.10.6 from master-1.10, same results.
You are receiving this mail because:
- You are watching all bug changes.