| Bug ID |
11103
|
| Summary |
"Filter out this stream" renders illogical display filter
|
| Product |
Wireshark
|
| Version |
1.12.4
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Trivial
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.12.4 (v1.12.4-0-gb4861da from master-1.12)
Copyright 1998-2015 Gerald Combs <[email protected]> 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.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 4 2015),
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 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, with 3893MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Imagine you have sniff with few TCP streams, then you hit "Statistics /
Conversation List / TCP .. ", you get screen with identified items, you select
e.g. first one, hit "Follow Stream", then "Filter Out This Stream" till you get
crazy display filter like :
tcp.stream eq 0 and !(tcp.stream eq 0)
How can this filter, when nothing complies?? Is like "1 AND 0", fail.
I like to improve this great product!
Regards
Peter
You are receiving this mail because:
- You are watching all bug changes.