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 [2015/08/23 23:40] – [Typical Uses] Updated mister_x | airmon-ng [2015/08/24 00:08] – monX interfaces are deprecated mister_x | ||
---|---|---|---|
Line 51: | Line 51: | ||
1115 wpa_supplicant | 1115 wpa_supplicant | ||
- | ===Turn monitor mode on=== | + | ===Enable |
**Note**: It is very important to kill the network managers before putting a card in monitor mode! | **Note**: It is very important to kill the network managers before putting a card in monitor mode! | ||
Line 75: | Line 75: | ||
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. | 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. | ||
- | ===Turn monitor mode off=== | + | ===Disable |
~# airmon-ng stop wlan0mon | ~# airmon-ng stop wlan0mon | ||
Line 84: | Line 84: | ||
(mac80211 monitor mode vif disabled for [phy0]wlan0mon) | (mac80211 monitor mode vif disabled for [phy0]wlan0mon) | ||
- | And you might as well want to restart the network manager | + | Don't forget |
service network-manager start | service network-manager start | ||
Line 165: | Line 165: | ||
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 [[install_drivers# | ||
- | |||
- | 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 235: | Line 211: | ||
==== General ==== | ==== General ==== | ||
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..) ==== |
airmon-ng.txt · Last modified: 2022/02/09 00:34 by mister_x