Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 7528] New: Protocol Hierarchy Statistics show "Short Frame" when TCP ports are

[bugzilla-daemon@xxxxxxxxxxxxx]

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

           Summary: Protocol Hierarchy Statistics show "Short Frame" when
                    TCP ports are available
           Product: Wireshark
           Version: 1.8.1
          Platform: x86
        OS/Version: Windows 7
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: kporter@xxxxxxxxx


Created attachment 8841
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=8841
Protocol Hierarchy Statistics Screen and Detailed Packet Capture Screen shot of
Filter

Build Information:
Version 1.8.1 (SVN Rev 43946 from /trunk-1.8)

Copyright 1998-2012 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 (64-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with PortAudio
V19-devel (built Jul 23 2012), with AirPcap.

Running on 64-bit Windows 7, build 7600, with WinPcap version 4.1.2 (packet.dll
version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.


--
Protocol Hierarchy Statistics show "Short Frame" when TCP ports are available.  

I have a capture  -   and the originator had sliced the frames after a certain
size.   

However, I believe that many of these sliced Frames are getting classified as
"Short Frame" when viewing the "Protocol Hierarchy Statistics" even though the
source and destination TCP ports are shown and available for analysis.   

See the attached JPG showing the results.   

If I create a filter out of this info..    I can still view the TCP Port Info..
 --   Thus, why isn't these ports properly displayed?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.