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:57]
mister_x Added section about --verbose and --debug
airmon-ng [2019/08/18 01:15]
mister_x brcmf_cfg80211_add_iface: iface validation failed: err=-95
Line 237: Line 237:
   K[phy1]wlan0 ath9k_htc[mac80211]-1.4 Qualcomm Atheros Communications AR9271 802.11n mode managed   K[phy1]wlan0 ath9k_htc[mac80211]-1.4 Qualcomm Atheros Communications AR9271 802.11n mode managed
  
-In this case, the following additional informatio can be seen:+In this case, the following additional information can be seen:
   - Detailed information about the Linux distribution as well as kernel version   - Detailed information about the Linux distribution as well as kernel version
   - System is a virtual machine (and detailed information about supported features)   - System is a virtual machine (and detailed information about supported features)
Line 424: 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 456: 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