| Bug ID |
10564
|
| Summary |
Not all monitor interfaces show up in WIreless Toolbar menu
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.99.1 (v1.99.1rc0-73-geb72d2a from unknown)
Copyright 1998-2014 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 GTK+ 3.4.2, with Cairo 1.10.2, with Pango 1.30.0, with
libpcap, without POSIX capabilities, with libnl 2, with libz 1.2.3.4, with GLib
2.32.4, without SMI, without c-ares, without ADNS, with Lua 5.1, without
GnuTLS,
without Gcrypt, without Kerberos, without GeoIP, without PortAudio, without
AirPcap.
Running on Linux 3.13.0-36-generic, with locale en_US.UTF-8, with libpcap
version 1.1.1, with libz 1.2.3.4.
Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz (with SSE4.2)
Built using gcc 4.6.3.
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
With some network adapters the Wireless Toolbar fails to identify the network
interface even though it supports monitor mode and can be found with iw tool.
For example the D-Link DWA-160 wireless USB adapter is not identified
correctly. Inserting one of these to the USB port gives "0 monitor interfaces
found". Inserting another one gives "1 monitor interface found" and so on.
After digging into this a bit it seems some network interface drivers have
problems with the NL80211_GET_WIPHY command when split wiphy dump feature is
not used. To solve this problem the wireless toolbar menu should support using
split wiphy dump feature when kernel supports it.
You are receiving this mail because:
- You are watching all bug changes.