Wireshark-bugs: [Wireshark-bugs] [Bug 11860] New: Display filter operator != not working as exep
Date: Mon, 07 Dec 2015 06:24:26 +0000
Bug ID 11860
Summary Display filter operator != not working as exepected
Product Wireshark
Version 2.0.0
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Normal
Priority Low
Component GTK+ UI
Assignee bugzilla-admin@wireshark.org
Reporter hvgeekwtrvl@gmail.com

Created attachment 14123 [details]
screenshot showing display filter not working

Build Information:
Version 2.0.0 (v2.0.0-0-g9a73b82 from master-2.0)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
       Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz (with SSE4.2), with 12167MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 31101

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

Check the man page and http://www.wireshark.org for more information.
--
Problem: Incorrectly applied filter _expression_ when viewing captured packets
the operators '==' and '!=' both acting as '=='.

When filtering captured packets created the following _expression_: ip.addr !=
192.168.1.52

Expected results: All packets with a source or destination IPv4 address of
192.168.1.52 will NOT be displayed.

Actual Results: All packets that contained the IPv4 address WERE displayed as
if the _expression_ were ip.addr == 192.168.1.52

Workaround: using the following display filter works as expected: !(ip.addr ==
192.168.1.52)


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