https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13020

            Bug ID: 13020
           Summary: Protocol Field Not Displaying Using -T json
           Product: Wireshark
           Version: 2.2.0
          Hardware: x86
                OS: Mac OS X 10.4
            Status: UNCONFIRMED
          Severity: Minor
          Priority: Low
         Component: TShark
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: dan.shana...@gmail.com

Build Information:
TShark (Wireshark) 2.2.0 (v2.2.0-0-g5368c50 from master-2.2)

Copyright 1998-2016 Gerald Combs <ger...@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 libpcap, without POSIX capabilities, with GLib 2.36.0,
with zlib 1.2.5, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2.4, with
GnuTLS
2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP.

Running on Mac OS X 10.10.5, build 14F1912 (Darwin 14.5.0), with locale
en_US.UTF-8, with libpcap version 1.5.3 - Apple version 47, with GnuTLS
2.12.19,
with Gcrypt 1.5.0, with zlib 1.2.5.
Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
Executing command: tshark -r testingtshark.pcap -T json -e _ws.col.Protocol
does not display the protocol field.  The same behavior happens with tshark -r
testingtshark.pcap -T ek -e _ws.col.Protocol.  

The protocol field is displayed fine with this command: tshark -r
testingtshark.pcap -T fields -e _ws.col.Protocol

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to