User Tools

Site Tools


airmon-ng

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
airmon-ng [2019/05/01 22:19]
mister_x Removed useless entry
airmon-ng [2019/08/18 01:15]
mister_x brcmf_cfg80211_add_iface: iface validation failed: err=-95
Line 204: Line 204:
  
 X is the monitor interface number - 0 unless you run multiple monitoring interfaces simultaneously. X is the monitor interface number - 0 unless you run multiple monitoring interfaces simultaneously.
 +
 +==== Debugging issues ====
 +
 +airmon-ng has two options to show more information,​ which can be useful when reporting or debugging issues.
 +
 +=== --verbose flag ===
 +
 +It gives information about the system as well as details about the wireless card.
 +
 +  root@kali:​~#​ airmon-ng --verbose
 +  ​
 +  No LSB modules are available.
 +  Distributor ID: Kali
 +  Description:​ Kali GNU/Linux Rolling
 +  Release:​ 2019.1
 +  Codename:​ n/​a
 +  ​
 +  Linux kali 4.19.0-kali4-amd64 #1 SMP Debian 4.19.28-2kali1 (2019-03-18) x86_64 GNU/Linux
 +  Detected VM using lspci
 +  This appears to be a VMware Virtual Machine
 +  If your system supports VT-d, it may be possible to use PCI devices
 +  If your system does not support VT-d, you can only use USB wifi cards
 +  ​
 +  K indicates driver is from 4.19.0-kali4-amd64
 +  V indicates driver comes directly from the vendor, almost certainly a bad thing
 +  S indicates driver comes from the staging tree, these drivers are meant for reference not actual use, BEWARE
 +  ? indicates we do not know where the driver comes from... report this
 +  ​
 +  ​
 +  X[PHY]Interface Driver[Stack]-FirmwareRev Chipset Extended Info
 +  ​
 +  K[phy1]wlan0 ath9k_htc[mac80211]-1.4 Qualcomm Atheros Communications AR9271 802.11n mode managed
 +
 +In this case, the following additional information can be seen:
 +  - Detailed information about the Linux distribution as well as kernel version
 +  - System is a virtual machine (and detailed information about supported features)
 +  - Detailed driver information (kernel, vendor driver, staging or unknown source), wireless stack, current operating mode and firmware version
 +
 +=== --debug flag ===
 +
 +It  will give the same information as verbose and add more details: ​
 +
 +  root@kali:​~#​ airmon-ng --debug
 +  ​
 +  /bin/sh -> /​usr/​bin/​dash
 +  ​
 +  SHELL is GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu)
 +  Copyright (C) 2019 Free Software Foundation, Inc.
 +  License GPLv3+: GNU GPL version 3 or later <​http://​gnu.org/​licenses/​gpl.html>​
 +  ​
 +  This is free software; you are free to change and redistribute it.
 +  There is NO WARRANTY, to the extent permitted by law.
 +  ​
 +  No LSB modules are available.
 +  Distributor ID: Kali
 +  Description:​ Kali GNU/Linux Rolling
 +  Release:​ 2019.1
 +  Codename:​ n/​a
 +  ​
 +  Linux kali 4.19.0-kali4-amd64 #1 SMP Debian 4.19.28-2kali1 (2019-03-18) x86_64 GNU/Linux
 +  Detected VM using lspci
 +  This appears to be a VMware Virtual Machine
 +  If your system supports VT-d, it may be possible to use PCI devices
 +  If your system does not support VT-d, you can only use USB wifi cards
 +  ​
 +  K indicates driver is from 4.19.0-kali4-amd64
 +  V indicates driver comes directly from the vendor, almost certainly a bad thing
 +  S indicates driver comes from the staging tree, these drivers are meant for reference not actual use, BEWARE
 +  ? indicates we do not know where the driver comes from... report this
 +  ​
 +  ​
 +  X[PHY]Interface Driver[Stack]-FirmwareRev Chipset Extended Info
 +  ​
 +  getStack mac80211
 +  getBus usb
 +  getdriver() ath9k_htc
 +  getchipset() Qualcomm Atheros Communications AR9271 802.11n
 +  BUS = usb
 +  BUSINFO = 0CF3:9271
 +  DEVICEID = 
 +  getFrom() K
 +  getFirmware 1.4
 +  K[phy1]wlan0 ath9k_htc[mac80211]-1.4 Qualcomm Atheros Communications AR9271 802.11n mode managed
 +
 +Additional information:​
 +  - Shell name and version
 +  - Debug information regarding the wireless adapter and loaded driver
  
 ===== Usage Troubleshooting ===== ===== Usage Troubleshooting =====
Line 337: Line 424:
    mon0: ERROR while getting interface flags: No such device    mon0: ERROR while getting interface flags: No such device
  
-This means you have an old version of airmon-ng installed. Upgrade to at least v1.0-rc1. ​ Preferably you should upgrade to the latest SVN version. ​ See the [[install_aircrack|installation page]] for more details. ​ Also, don't forget you need to be root to use airmon-ng (or use sudo).+This means you have an old version of airmon-ng installed. Upgrade to at least v1.0-rc1. ​ Preferably you should upgrade to the current ​version. ​ See the [[install_aircrack|installation page]] for more details. ​ Also, don't forget you need to be root to use airmon-ng (or use sudo).
  
 ==== check kill fails ==== ==== check kill fails ====
Line 369: Line 456:
   ​   ​
 See also http://​ubuntuforums.org/​showthread.php?​t=1311886 See also http://​ubuntuforums.org/​showthread.php?​t=1311886
 +
 +==== ERROR adding monitor mode interface: command failed: Operation not supported (-95) ====
 +
 +It is known to happen on the Raspberry Pi, when using [[airmon-ng]]. When that happens, the following can be seen in dmesg:
 +
 +  brcmfmac: brcmf_vif_add_validate:​ Attempt to add a MONITOR interface...
 +  brcmfmac: brcmf_vif_add_validate:​ ... there is already a monitor interface, returning EOPNOTSUPP
 +  brcmfmac: brcmf_cfg80211_add_iface:​ iface validation failed: err=-95
 + 
 +There may be instances of the following in dmesg as well prior to the above output:
 +
 +  brcmfmac: brcmf_vif_add_validate:​ Attempt to add a MONITOR interface...
 +  brcmfmac: brcmf_mon_add_vif:​ brcmf_mon_add_vif called
 +  brcmfmac: brcmf_mon_add_vif:​ Adding vif "​wlan0mon"​
 +  brcmfmac: brcmf_cfg80211_get_channel:​ chanspec failed (-52)
 +
 +Even though dmesg says the interface is already in monitor mode and "iw dev wlan0 info" confirms it is, [[airodump-ng]] will fail and report the interface data linktype is Ethernet. This is a bug in the driver and/or firmware, and the workaround is to reboot the system or to reload the driver:
 +
 +  rmmod brcmfmac
 +  modprobe brcmfmac
airmon-ng.txt ยท Last modified: 2019/08/18 01:15 by mister_x