| Bug ID |
12636
|
| Summary |
Selecting an interface can clear the capture filter
|
| Product |
Wireshark
|
| Version |
2.0.4
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.0.4 (v2.0.4-0-gdd7746e from master-2.0)
Copyright 1998-2016 Gerald Combs <[email protected]> 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.11.0, 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 10, build 10586, 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) i7-6700K CPU @ 4.00GHz (with SSE4.2), with 32686MB of
physical
memory.
--
Wireshark remembers the last capture filter set on each interface during a
session (but not across sessions, it appears). When an interface is selected in
the main window, the remembered capture filter is put into the capture filter
field.
Just after starting Wireshark, no previous capture filters are known, and,
unless the user has found the "default interface" preference, no interface is
selected.
This leads to a usability problem: The capture filter field is located above
the interface list, so the user (at least *this* user) tends to enter the
capture filter before selecting any interfaces. However, as soon as I then
select an interface, the filter string goes away tracelessly and cannot be
recovered because no interface was selected when I entered it.
Suggested fixes (three alternatives):
1. Do not replace the current contents of the capture filter field with the
filter associated with the just-selected interface if the latter is empty.
2. Do not replace the current contents of the capture filter field with the
filter associated with the just-selected interface unless the former is empty.
This would mainly be an improvement for occasional users who don't habitually
have Wireshark running in the background all day.
3. Add UI for the "default interface" selection to the main window, to make it
easier for the user to choose an interface which will be preselected at the
start of the next session. This would ensure that if the user selects another
interface *after* entering a filter, that filter could be recovered by
reselecting the default interface.
You are receiving this mail because:
- You are watching all bug changes.