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 revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
airmon-ng [2010/02/19 00:06] – Added source thread for check kill fails darkaudaxairmon-ng [2010/10/31 16:25] – SIOCSIFFLAGS: Unknown error 132 mister_x
Line 286: Line 286:
    service network-manager stop    service network-manager stop
    service avahi-daemon stop    service avahi-daemon stop
 +   service upstart-udev-bridge stop
  
 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 'tasks'. 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 'tasks'.
  
-Source thread: http://forum.aircrack-ng.org/index.php?topic=6398.0+Source thread: http://forum.aircrack-ng.org/index.php?topic=6398.0 and http://forum.aircrack-ng.org/index.php?topic=8573 
 + 
 +==== SIOCSIFFLAGS: Unknown error 132 ==== 
 + 
 +If you have an output similar to: 
 + 
 +  # airmon-ng start wlan0 
 +  Interface Chipset Driver 
 +  wlan0 Broadcom b43 - [phy0]SIOCSIFFLAGS: Unknown error 132 
 +  (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://ubuntuforums.org/showthread.php?t=1311886
airmon-ng.txt · Last modified: 2022/02/09 00:34 by mister_x