https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16781
Bug ID: 16781
Summary: Display protocol abbrev on Statistics->Protocol
Hierarchy (Request for feedback)
Product: Wireshark
Version: 3.2.6
Hardware: x86
OS: Windows 10
Status: UNCONFIRMED
Severity: Enhancement
Priority: Low
Component: Qt UI
Assignee: bugzilla-ad...@wireshark.org
Reporter: bubbas...@gmail.com
Target Milestone: ---
Created attachment 17942
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17942&action=edit
Selected protocol abbrev displayed in footer
Build Information:
3.2.6 (Git commit 4f9257fb8ccc)
Compiled (64-bit) with Qt 5.9.5, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with GLib 2.56.4, with zlib 1.2.11, with SMI 0.4.8, with c-ares
1.14.0, with Lua 5.2.4, with GnuTLS 3.5.18 and PKCS #11 support, with Gcrypt
1.8.1, with MIT Kerberos, with MaxMind DB resolver, with nghttp2 1.30.0, with
brotli, with LZ4, with Zstandard, with Snappy, with libxml2 2.9.10, with
QtMultimedia, without automatic updates, with SpeexDSP (using system library),
with SBC, with SpanDSP, without bcg729.
Running on Linux 4.15.0-112-generic, with Intel(R) Xeon(R) CPU E5645
@ 2.40GHz (with SSE4.2), with 3944 MB of physical memory, with locale
en_US.UTF-8, with light display mode, without HiDPI, with libpcap version
1.8.1,
with GnuTLS 3.5.18, with Gcrypt 1.8.1, with brotli 1.0.7, with zlib 1.2.11,
binary plugins supported (0 loaded).
Built using gcc 7.5.0.
--
When coming up to speed on a capture that someone else created, I typically
work down through the Statistics menu items.
The long protocol descriptions are nice but sometimes it would be nice to know
the abbrev that will be used in a filter before using them in "Apply as Filter"
or "Prepare a Filter".
The attached screenshots show examples of the protocol abbrev displayed in the
footer for the current selected protocol or as a new column showing them all.
Thoughts?
--
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
