airmon-ng
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
airmon-ng [2009/03/22 14:44] – Added you need to be root. darkaudax | airmon-ng [2019/08/17 04:01] – [Error "add_iface: Permission denied"] SVN doesn't exist anymore mister_x | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Airmon-ng ====== | ====== Airmon-ng ====== | ||
- | |||
- | |||
===== Description ===== | ===== Description ===== | ||
This script can be used to enable monitor mode on wireless interfaces. It may also be used to go back from monitor mode to managed mode. Entering the airmon-ng command without parameters will show the interfaces status. | This script can be used to enable monitor mode on wireless interfaces. It may also be used to go back from monitor mode to managed mode. Entering the airmon-ng command without parameters will show the interfaces status. | ||
Line 7: | Line 5: | ||
===== Usage ===== | ===== Usage ===== | ||
- | usage: airmon-ng < | + | usage: airmon-ng < |
Where:\\ | Where:\\ | ||
Line 13: | Line 11: | ||
*< | *< | ||
*[channel] optionally set the card to a specific channel.\\ | *[channel] optionally set the card to a specific channel.\\ | ||
+ | *< | ||
===== Usage Examples ===== | ===== Usage Examples ===== | ||
Line 18: | Line 17: | ||
==== Typical Uses ==== | ==== Typical Uses ==== | ||
- | To start wlan0 in monitor mode: airmon-ng start wlan0 | + | ===Check status and/or listing wireless interfaces === |
+ | |||
+ | ~# airmon-ng | ||
+ | PHY Interface Driver Chipset | ||
+ | |||
+ | phy0 wlan0 ath9k_htc Atheros Communications, | ||
+ | |||
+ | ===Checking for interfering processes=== | ||
+ | |||
+ | When putting a card into monitor mode, it will automatically check for interfering processes. It can also be done manually by running the following command: | ||
+ | |||
+ | ~# airmon-ng check | ||
+ | Found 5 processes that could cause trouble. | ||
+ | If airodump-ng, | ||
+ | a short period of time, you may want to kill (some of) them! | ||
+ | |||
+ | PID Name | ||
+ | 718 NetworkManager | ||
+ | 870 dhclient | ||
+ | 1104 avahi-daemon | ||
+ | 1105 avahi-daemon | ||
+ | 1115 wpa_supplicant | ||
+ | |||
+ | == Killing interfering processes== | ||
+ | |||
+ | This command stops network managers then kill interfering processes left: | ||
+ | |||
+ | ~# airmon-ng check kill | ||
+ | Killing these processes: | ||
+ | |||
+ | PID Name | ||
+ | 870 dhclient | ||
+ | 1115 wpa_supplicant | ||
+ | |||
+ | ===Enable monitor mode=== | ||
+ | |||
+ | **Note**: It is very important to kill the network managers before putting a card in monitor mode! | ||
+ | |||
+ | ~# airmon-ng start wlan0 | ||
+ | Found 5 processes that could cause trouble. | ||
+ | If airodump-ng, | ||
+ | a short period of time, you may want to kill (some of) them! | ||
+ | |||
+ | PID Name | ||
+ | 718 NetworkManager | ||
+ | 870 dhclient | ||
+ | 1104 avahi-daemon | ||
+ | 1105 avahi-daemon | ||
+ | 1115 wpa_supplicant | ||
+ | |||
+ | PHY Interface Driver Chipset | ||
+ | |||
+ | phy0 wlan0 ath9k_htc Atheros Communications, | ||
+ | (mac80211 monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon) | ||
+ | (mac80211 station mode vif disabled for [phy0]wlan0) | ||
+ | |||
+ | As you can see, it created a monitor mode interface called wlan0mon and it notified there are a few process that will interfere with the tools. | ||
+ | |||
+ | ===Disable monitor mode=== | ||
+ | |||
+ | ~# airmon-ng stop wlan0mon | ||
+ | PHY Interface Driver Chipset | ||
+ | |||
+ | phy0 wlan0mon ath9k_htc Atheros Communications, | ||
+ | (mac80211 station mode vif enabled on [phy0]wlan0) | ||
+ | (mac80211 monitor mode vif disabled for [phy0]wlan0mon) | ||
- | To start wlan0 in monitor mode on channel 8: airmon-ng start wlan0 8 | + | Don't forget to restart the network manager. It is usually done with the following command: |
- | To stop wlan0: airmon-ng stop wlan0 | + | service network-manager start |
- | To check the status: airmon-ng | ||
==== Madwifi-ng driver monitor mode ==== | ==== Madwifi-ng driver monitor mode ==== | ||
Line 48: | Line 111: | ||
If you want to use ath0 (which is already used): | If you want to use ath0 (which is already used): | ||
- | airmon-ng stop ath0 | + | |
And the system will respond: | And the system will respond: | ||
Line 68: | Line 131: | ||
You can see ath0 is gone. | You can see ath0 is gone. | ||
- | To start ath0 in monitor mode: airmon-ng start wifi0 | + | To put wifi0 in monitor mode: |
+ | |||
+ | | ||
System responds: | System responds: | ||
Line 104: | Line 169: | ||
- | ==== mac80211 drivers monitor mode ==== | + | ===== Usage Tips ===== |
- | See [[http:// | + | ==== Confirming the Card is in Monitor Mode ==== |
- | When using the mac80211 version of a driver, the use of airmon-ng | + | To confirm that the card is in monitor mode, run the command " |
- | Running: | + | For the madwifi-ng driver, the access point field from iwconfig shows your the MAC address of the wireless card. |
- | | + | ==== Determining the Current Channel ==== |
- | Gives something like: | + | To determine the current channel, enter " |
- | | + | ==== How Do I Put My Card Back into Managed Mode? ==== |
- | + | ||
- | | + | |
- | (monitor mode enabled on mon0) | + | |
- | Notice that it created " | + | It depends on which driver you are using. |
- | To remove monitor mode enter: | + | airmon-ng stop < |
- | | + | For madwifi-ng, first stop ALL interfaces: |
+ | airmon-ng stop athX | ||
- | ===== Usage Tips ===== | + | Where X is 0, 1, 2 etc. Do a stop for each interface that iwconfig lists. |
- | ==== Confirming the Card is in Monitor Mode ==== | + | Then: |
- | To confirm that the card is in monitor mode, run the command " | + | wlanconfig ath create wlandev wifi0 wlanmode sta |
- | For the madwifi-ng | + | See [[http:// |
+ | For mac80211 drivers, nothing has to be done, as airmon-ng keeps the managed interface alongside the monitor mode one (mac80211 uses interface types rather than modes of operation). If you no longer need the monitor interface and want to remove it, use the following: | ||
- | ==== Determining the Current Channel ==== | + | airmon-ng stop monX |
- | To determine | + | X is the monitor |
+ | ==== Debugging issues ==== | ||
- | ==== BSSIDs with Spaces, Special Characters ==== | + | airmon-ng has two options to show more information, which can be useful when reporting or debugging issues. |
- | See this [[faq# | + | === --verbose flag === |
+ | It gives information about the system as well as details about the wireless card. | ||
+ | root@kali: | ||
+ | | ||
+ | No LSB modules are available. | ||
+ | Distributor ID: Kali | ||
+ | Description: | ||
+ | Release: | ||
+ | Codename: | ||
+ | | ||
+ | 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 | ||
- | ==== How Do I Put My Card Back into Managed Mode? ==== | + | 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 | ||
- | It depends on which driver you are using. | + | === --debug flag === |
- | | + | It will give the same information as verbose and add more details: |
- | For madwifi-ng, first stop ALL interfaces: | + | root@kali: |
+ | |||
+ | /bin/sh -> / | ||
+ | |||
+ | 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 < | ||
+ | |||
+ | 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: | ||
+ | Release: | ||
+ | Codename: | ||
+ | |||
+ | 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: |
+ | | ||
+ | - Debug information regarding the wireless adapter and loaded driver | ||
- | Where X is 0, 1, 2 etc. Do a stop for each interface that iwconfig lists. | + | ===== Usage Troubleshooting ===== |
- | Then: | + | ==== Madwifi-ng ==== |
+ | Quite often, the standard scripts on a linux distribution will setup ath0 and or additional athX interfaces. | ||
- | wlanconfig ath create wlandev wifi0 wlanmode sta | ||
- | See [[http:// | + | ==== Airmon-ng says the interface is not in monitor mode ==== |
+ | ~# airmon-ng stop wlan0mon | ||
+ | PHY Interface Driver Chipset | ||
+ | | ||
+ | phy0 wlan0mon ath9k_htc Atheros Communications, | ||
+ | | ||
+ | You are trying to stop a device that isn't in monitor mode. | ||
+ | Doing so is a terrible idea, if you really want to do it then you | ||
+ | need to type 'iw wlan2mon del' yourself since it is a terrible idea. | ||
+ | Most likely you want to remove an interface called wlan[0-9]mon | ||
+ | If you feel you have reached this warning in error, | ||
+ | please report it. | ||
- | ===== Usage Troubleshooting ===== | + | It most likely mean the interface mode was changed from monitor to managed mode by a network manager. In this case, when stopping monitor mode, this is not a problem. |
+ | |||
+ | ==== My interface was put in monitor mode but tools says it is not ==== | ||
- | ==== General ==== | + | It usually means the interface was put in monitor mode prior to killing network managers. And the network manager put the card back in managed mode. |
- | Quite often, | + | |
+ | Refer to the documentation above to kill network managers | ||
==== Interface athX number rising (ath0, ath1, ath2.... ath45..) ==== | ==== Interface athX number rising (ath0, ath1, ath2.... ath45..) ==== | ||
- | The original problem description and solution can be found in this [[http:// | + | The original problem description and solution can be found in this [[http:// |
Problem: | Problem: | ||
Line 181: | Line 329: | ||
The second problem is that if you run airmon-ng on wifi0 the athXX created does not show as being shown as in Monitor mode, even though it is. This can be confirmed via iwconfig. | The second problem is that if you run airmon-ng on wifi0 the athXX created does not show as being shown as in Monitor mode, even though it is. This can be confirmed via iwconfig. | ||
- | All these problem related to how udev assigns interface names. | + | All these problem related to how udev assigns interface names. |
Each distro is different... So here is a solution specifically for Gentoo. | Each distro is different... So here is a solution specifically for Gentoo. | ||
Line 209: | Line 357: | ||
This is also on Gentoo, both 2.6.19-gentoo-r5 and 2.6.20-gentoo-r6 | This is also on Gentoo, both 2.6.19-gentoo-r5 and 2.6.20-gentoo-r6 | ||
- | For Ubuntu, see this [[http:// | + | For Ubuntu, see this [[http:// |
# these rules generate rules for persistent network device naming | # these rules generate rules for persistent network device naming | ||
Line 227: | Line 375: | ||
| | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
| | ||
Line 241: | Line 384: | ||
This troubleshooting tip applies to madwifi-ng drivers. First try stopping each VAP interface that is running (" | This troubleshooting tip applies to madwifi-ng drivers. First try stopping each VAP interface that is running (" | ||
- | If this does not resolve the problem then follow the advice in this [[http://tinyshell.be/ | + | If this does not resolve the problem then follow the advice in this [[http://forum.aircrack-ng.org/ |
==== Why do I get ioctl(SIOCGIFINDEX) failed? ==== | ==== Why do I get ioctl(SIOCGIFINDEX) failed? ==== | ||
Line 251: | Line 393: | ||
* Error message: " | * Error message: " | ||
- | Then [[http:// | + | Then [[faq# |
==== Error message: " | ==== Error message: " | ||
Line 264: | Line 406: | ||
See this entry under [[rt73# | See this entry under [[rt73# | ||
- | |||
- | |||
- | |||
- | |||
==== Error " | ==== Error " | ||
Line 286: | 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. | + | This means you have an old version of airmon-ng installed. Upgrade to at least v1.0-rc1. |
+ | |||
+ | ==== check kill fails ==== | ||
+ | |||
+ | Distros from now on are going to adopt ' | ||
+ | |||
+ | Basically do: | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | and then proceed with greping and killing the pids of dhclient and wpa_supplicant. | ||
+ | |||
+ | This is the only way to kill ALL of the potentially problematic pids for aireplay-ng permanently. The trick is the kill the daemons first and then terminate the ' | ||
+ | |||
+ | Source thread: http:// | ||
+ | |||
+ | ==== SIOCSIFFLAGS: | ||
+ | |||
+ | If you have an output similar to: | ||
- | ===== Release Candidate or SVN Version Notes ===== | + | # airmon-ng start wlan0 |
+ | Interface Chipset Driver | ||
+ | wlan0 Broadcom b43 - [phy0]SIOCSIFFLAGS: | ||
+ | (monitor mode enabled on mon0) | ||
- | This section ONLY applies | + | It indicates that RF are blocked. It needs to be enabled by using the switch on your laptop |
- | | + | |
- | * " | + | |
+ | See also http:// |
airmon-ng.txt · Last modified: 2022/02/09 00:34 by mister_x