Wireshark-bugs: [Wireshark-bugs] [Bug 9115] New: When using WS in RDP session, last used Capture
| Bug ID |
9115
|
| Summary |
When using WS in RDP session, last used Capture Filter is replaced
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.1
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Trivial
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
mwood@frontporch.com
|
Build Information:
Version 1.10.1 (SVN Rev 50926 from /trunk-1.10)
Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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 (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Jul 26 2013), with AirPcap.
Running on 32-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 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz, with 2047MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
When running WS in an RDP session, the Capture Filter auto-populates with "not
tcp port 3389". If I manually enter another capture filter, such as "tcp port
80", run a sniff and then go back to Capture Options, the recent capture filter
of "tcp port 80" is replaced with "not tcp port 3389". This may be related to
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7278 since my capture
filter isn't saved to the drop-down list, but frustrating in it's own right
since I would still have to select the recent filter from the drop-down.
You are receiving this mail because:
- You are watching all bug changes.
