Bug ID |
11138
|
Summary |
Feature request: search and mark/unmark
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
All
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Enhancement
|
Priority |
Low
|
Component |
Qt UI
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
wireshark 1.12.4 (Git Rev Unknown from unknown)
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 GTK+ 3.14.6, with Cairo 1.14.0, with Pango 1.36.8, with
GLib 2.42.1, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
with libnl 3, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without Python,
with GnuTLS 3.2.18, with Gcrypt 1.6.1, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built May 28 2014 05:39:06), without AirPcap.
Running on Linux 3.16.7-7-desktop, with locale en_GB.UTF-8, with libpcap
version
1.6.2, with libz 1.2.8, GnuTLS 3.2.18, Gcrypt 1.6.1.
Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
Built using gcc 4.8.3 20140627 [gcc-4_8-branchrevision 212064].
--
This feature request might seem redundant at first, but it's not. There is a
case where the traditional "filter+mark all" does not work. I want to mark
packets in which latency (measured by frame.time_displayed_delta) is below a
threshold.
The "filter+mark all" approach fails because the filter changes
time_displayed_delta and nothing is matched. The only workaround is to search
and mark packet by packet, manually.
You are receiving this mail because:
- You are watching all bug changes.