Wireshark-bugs: [Wireshark-bugs] [Bug 6633] New: The active display filter should be taken into

Date: Wed, 30 Nov 2011 08:38:11 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6633

           Summary: The active display filter should be taken into account
                    when changing "Configuration profile"
           Product: Wireshark
           Version: 1.7.x (Experimental)
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: wireshark.jmdlpro@xxxxxxxx


Build Information:
Version 1.7.0 (SVN Rev 39768 from /trunk)

Copyright 1998-2011 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 (64-bit) with GTK+ 2.22.1, with Cairo 1.10.2, with Pango 1.28.3, with
GLib 2.26.1, with WinPcap (version unknown), with libz 1.2.5, without POSIX
capabilities, with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python,
with GnuTLS 2.10.3, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Nov  8 2011), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022

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

Check the man page and http://www.wireshark.org for more information.
--
Note that this bug was already present in 1.6 and previous.
1. define at least 2 configuration profiles
2. make a capture with a given display filter
3. change the current configuration profile : the captured packets are
reprocessed, but ignoring the current display filter
4. so one has to re-apply the display filter, leading to a 2nd reprocess of all
the packets, what could be annoying with a big capture

Expected behavior :
in step 3, changing the configuration profile should lead to the reprocess of
all the packets, but while taking into account the display filter if one is
active, thus eliminating the need of step 4.

TIA

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