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 [2010/02/19 00:06] – Added source thread for check kill fails darkaudax | airmon-ng [2010/10/31 16:25] – SIOCSIFFLAGS: Unknown error 132 mister_x | ||
---|---|---|---|
Line 286: | Line 286: | ||
| | ||
| | ||
+ | | ||
and then proceed with greping and killing the pids of dhclient and wpa_supplicant. | and then proceed with greping and killing the pids of dhclient and wpa_supplicant. | ||
Line 291: | Line 292: | ||
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 ' | 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:// | + | 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) | ||
+ | |||
+ | It indicates that RF are blocked. It needs to be enabled by using the switch on your laptop and/or using the following command: | ||
+ | |||
+ | rfkill unblock all | ||
+ | |||
+ | See also http:// |
airmon-ng.txt · Last modified: 2022/02/09 00:34 by mister_x