Bug ID |
10201
|
Summary |
col.Protocol missing from tshark 1.11.3 and 1.12.0-rc2
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.12.0
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
TShark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
TShark 1.12.0-rc2 (v1.12.0-rc2-0-gfd017ee from master-1.12)
Copyright 1998-2014 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.1.22,
with Gcrypt 1.6.0, without Kerberos, with GeoIP.
Running on 64-bit Windows 7 Service Pack 1, build 7601, without WinPcap.
Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz, with 2047MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
The col.* fields (i.e. col.Protocol, col.Info, etc.) are not functioning in
tshark versions 1.11.3 and 1.12.0-rc2. I've replicated the problem on Ubuntu
14.04 and Windows 7. These fields work properly in tshark 1.10.8. See sample
output below:
The following produces valid data in tshark 1.10.8:
tshark -T fields -e frame.time_epoch -e col.Protocol
Capturing on 'Local Area Connection'
1403125926.751104000 TCP
1403125926.811217000 TCP
1403125926.811312000 TCP
1403125926.847215000 HTTP
Here's the results of tshark 1.11.3 and 1.12.0-rc2 (notice no data for
col.Protocol):
tshark -T fields -e frame.time_epoch -e col.Protocol
Capturing on 'Local Area Connection'
1403125990.020468000
1403125990.069307000
1403125990.080299000
1403125990.140231000
You are receiving this mail because:
- You are watching all bug changes.