| Bug ID |
8524
|
| Summary |
Capture Filter column pop-up help tip incorrect
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.8.6
|
| Hardware |
x86
|
| OS |
Windows XP
|
| Status |
UNCONFIRMED
|
| Severity |
Trivial
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.8.6 (SVN Rev 48142 from /trunk-1.8)
Copyright 1998-2013 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 (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_2), 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.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Mar 6 2013), with AirPcap.
Running on Windows XP Service Pack 3, build 2600, 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.12.18, Gcrypt 1.4.6, without AirPcap, from the
PortableApps U3 device in drive E:.
Built using Microsoft Visual C++ 10.0 build 40219
--
Each column of the "Capture" area of the Capture Options page has an associated
pop-up help tip. If you hover the mouse in the "Capture Filter" column, the
following help is displayed, which has nothing to do with capture filters:
"Usually a Wi-Fi adapter will, even in promiscuous mode, only capture the
traffic on the BSS to which it's associated. If you want to capture all traffic
that the Wi-Fi adapter can 'receive', mark this option.In order to see IEEE
802.11 headers or to see radio information for captured packets,it might be
necessary to turn this option on."
"Note that, in monitor mode, the adapter might disassociate from the network to
which it's associated. mode"
The build information is from the PortableApps version 1.8.6, but this same
behavior occurs in the non-PortableApps version and in the current development
version as of March 25, 2013.
You are receiving this mail because:
- You are watching all bug changes.