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/07/14 16:47] – Document return-to-managed for mac80211 drivers. netrolller3d | airmon-ng [2019/05/01 22:19] – Removed useless entry mister_x | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Usage ===== | ===== Usage ===== | ||
- | usage: airmon-ng < | + | usage: airmon-ng < |
Where:\\ | Where:\\ | ||
Line 11: | 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 16: | Line 17: | ||
==== Typical Uses ==== | ==== Typical Uses ==== | ||
- | To start wlan0 in monitor mode: airmon-ng start wlan0 | + | ===Check status and/or listing wireless interfaces === |
- | To start wlan0 in monitor mode on channel 8: airmon-ng | + | ~# airmon-ng |
+ | PHY Interface Driver Chipset | ||
+ | |||
+ | phy0 wlan0 ath9k_htc Atheros Communications, | ||
- | To stop wlan0: airmon-ng stop wlan0 | + | ===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) | ||
+ | |||
+ | Don't forget to restart the network manager. It is usually done with the following command: | ||
+ | |||
+ | service network-manager start | ||
- | To check the status: airmon-ng | ||
==== Madwifi-ng driver monitor mode ==== | ==== Madwifi-ng driver monitor mode ==== | ||
Line 46: | 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 66: | 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 100: | Line 167: | ||
You can set the channel number by adding it to the end: airmon-ng start wifi0 9 | You can set the channel number by adding it to the end: airmon-ng start wifi0 9 | ||
- | |||
- | |||
- | ==== mac80211 drivers monitor mode ==== | ||
- | |||
- | See [[http:// | ||
- | |||
- | When using the mac80211 version of a driver, the use of airmon-ng and the aircrack-ng tools are slightly different. | ||
- | |||
- | Running: | ||
- | |||
- | | ||
- | |||
- | Gives something like: | ||
- | |||
- | | ||
- | |||
- | | ||
- | (monitor mode enabled on mon0) | ||
- | |||
- | Notice that it created " | ||
- | |||
- | To remove monitor mode enter: | ||
- | |||
- | | ||
Line 137: | Line 180: | ||
To determine the current channel, enter " | To determine the current channel, enter " | ||
- | |||
- | ==== BSSIDs with Spaces, Special Characters ==== | ||
- | |||
- | See this [[faq# | ||
==== How Do I Put My Card Back into Managed Mode? ==== | ==== How Do I Put My Card Back into Managed Mode? ==== | ||
Line 146: | Line 185: | ||
It depends on which driver you are using. | It depends on which driver you are using. | ||
- | airmon-ng stop < | + | |
For madwifi-ng, first stop ALL interfaces: | For madwifi-ng, first stop ALL interfaces: | ||
- | airmon-ng stop athX | + | |
Where X is 0, 1, 2 etc. Do a stop for each interface that iwconfig lists. | Where X is 0, 1, 2 etc. Do a stop for each interface that iwconfig lists. | ||
Line 162: | Line 201: | ||
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: | 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: | ||
- | airmon-ng stop monX | + | |
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. | ||
Line 168: | Line 207: | ||
===== Usage Troubleshooting ===== | ===== Usage Troubleshooting ===== | ||
- | ==== General | + | ==== Madwifi-ng |
Quite often, the standard scripts on a linux distribution will setup ath0 and or additional athX interfaces. | Quite often, the standard scripts on a linux distribution will setup ath0 and or additional athX interfaces. | ||
+ | |||
+ | |||
+ | ==== 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. | ||
+ | |||
+ | 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 ==== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | Refer to the documentation above to kill network managers and put it back into monitor mode. | ||
==== Interface athX number rising (ath0, ath1, ath2.... ath45..) ==== | ==== Interface athX number rising (ath0, ath1, ath2.... ath45..) ==== | ||
Line 244: | Line 306: | ||
* Error message: " | * Error message: " | ||
- | Then [[http:// | + | Then [[faq# |
==== Error message: " | ==== Error message: " | ||
Line 277: | Line 339: | ||
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. | ||
- | ===== Release Candidate or SVN Version Notes ===== | + | ==== 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: | ||
+ | |||
+ | # 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