Wireshark-bugs: [Wireshark-bugs] [Bug 2988] New: Goto undisplayed packet should do something sen
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 21 Oct 2008 17:55:54 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2988

           Summary: Goto undisplayed packet should do something sensible
           Product: Wireshark
           Version: 1.0.2
          Platform: PC
        OS/Version: Windows Vista
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: martinvisser99@xxxxxxxxx


Build Information:
Version 1.0.2 (SVN Rev 25698)

Copyright 1998-2008 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 with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.

Running on Windows Vista, build 6000, with WinPcap version 4.0.2 (packet.dll
version 4.0.0.1040), based on libpcap version 0.9.5, without AirPcap.

Built using Microsoft Visual C++ 6.0 build 8804

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

Check the man page and http://www.wireshark.org for more information.
--
If you use menu Go:Go to packet or click on a graph point in the IO Graph,
Wireshark should scroll the packet view to the appropriate packet

If you have a filtered display (not displaying all packets) the selected target
packet may not be in view. In this case, Wireshark pops a dialog "The packet
number nnnn isn't currently being displayed." However this is not so friendly.
Wireshark should probably scroll to the nearest packet (and inform you it has
done so possibly). This is particular useful if you are using the IO Graph to
identify points of interest and by clicking on the graph you want to see the
nearest relevant packet. For instance I might have a filter "http.request ||
http.response" and by clicking anywhere on the IO graph I would want to see the
relevant HTTP traffic


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