We're now a non-profit! Support open source packet analysis by making a donation.

Wireshark-bugs: [Wireshark-bugs] [Bug 10063] New: "Next Matching", "Previous Matching " packet n

Date: Wed, 30 Apr 2014 05:46:14 +0000
Bug ID 10063
Summary "Next Matching", "Previous Matching " packet navigation for Packet Detail field values
Classification Unclassified
Product Wireshark
Version 1.10.7
Hardware x86
OS Windows 7
Severity Major
Priority Low
Component Wireshark
Assignee [email protected]
Reporter [email protected]

Build Information:
Version 1.10.7 (v1.10.7-0-g6b931a1 from master-1.10)

Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO

Compiled (64-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, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Apr 22 2014), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version, based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
       Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz, with 6038MB of physical

Built using Microsoft Visual C++ 10.0 build 40219

I'm currently using Wireshark to browse through two types of packets, where a
much small number of one of the types of packet (packet A) is interleaved
throughout the many other types of packets (packet B). For example, there might
be a few 100 packet Bs between packet As. 

I'm interested in where the smaller number of packet As are in relation
(timestamp, packet number) to the larger number of packet Bs, yet am not
interested in the details of the packet Bs.

Currently, to move to the next or previous packet A, I have to scroll
individually through the packet Bs using the up/down arrow keys or the mouse
scroll wheel, manually looking for the next or previous packet A. With 100s or
1000s of packet Bs betwen packet As, this can be quite time consuming, or,
alternatively, if I scroll quickly over the packet Bs, it is possible to miss
packet As.

I think it would be very useful in this scenario to have a "Next Matching" or
"Previous Matching" navigation option, which uses the currently highlighted
field or field value in the packet details window as the navigation selector. I
think these navigation options would be best available in both the 'Go' menu
and when right clicking on the field/field value in the Packet Detail window.

Perhaps a further enhancement to this would be to also be able to use specified
or saved filters to help navigate packet captures with large numbers of packets
e.g. "Next Filter Matching", "Previous Filter Matching" options.

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