Wireshark-bugs: [Wireshark-bugs] [Bug 9817] New: Provide a way to clear the capture window witho
Date: Fri, 28 Feb 2014 15:09:10 +0000
Bug ID 9817
Summary Provide a way to clear the capture window without restarting the capture or reapplying the filter
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Enhancement
Priority Low
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter ryan.shripat@gmail.com

Build Information:
Version 1.10.2 (SVNRev 51934 from /trunk-1.10)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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 (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Sep 10 2013), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
AMD Athlon(tm) II X2 245 Processor, with 8191MB of physical memory.


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.
--
Is there a way to clear the capture window in Wireshark without restarting the
capture or re-applying the filter? It's difficult to tell one set of traffic
from another without looking very closely at the timestamp.

My only solution is to restart the running live capture.

http://stackoverflow.com/questions/19366795/how-do-i-clear-the-capture-window-in-wireshark


You are receiving this mail because:
  • You are watching all bug changes.