Giantfire Posted June 28, 2017 Share Posted June 28, 2017 hi i'm recently trying to make the deauth tool using pi 3. but with no luck. I installed/compiled everything like lorcon, libnl-dev, libnl1 and pylorcon. but with no luck. I always get this error. Unable to get driver Interface wlan0 does not exist Airdrop-ng will now exit Sent 0 Packets Exiting Program, Please take your card wlan0 out of monitor mode I wonder, if anyone could help me out in this case. Quote Link to comment Share on other sites More sharing options...
0phoi5 Posted June 28, 2017 Share Posted June 28, 2017 What output do you get if you run 'iwconfig'? Have you used airmon to place your card in monitor mode? Are you using an external WiFi card (I don't believe the internal WiFi on the RPi3 supports monitor mode)? Have you extensively read through the instructions on the aircrack website? Quote Link to comment Share on other sites More sharing options...
Giantfire Posted June 28, 2017 Author Share Posted June 28, 2017 I am using nexmon firmware to latch the internal wifi chipset of Rpi3, and now my rpi3 inbuild wifi chipset supports the monitor mode. Yes i have tested out with iwconfig, it says mode is monitor and interface is wlan0. Quote Link to comment Share on other sites More sharing options...
0phoi5 Posted June 28, 2017 Share Posted June 28, 2017 (edited) 1 hour ago, Giantfire said: It says mode is monitor and interface is wlan0. Doesn't sound like airmon has set monitor mode successfully. If this was the case, the interface would usually show as mon0 or wlan0mon. Could you post your full command list and output? Edited June 28, 2017 by haze1434 Quote Link to comment Share on other sites More sharing options...
digip Posted June 28, 2017 Share Posted June 28, 2017 start with "airmon-ng check" by itself. If anything found, run "airmon-ng check kill" then "airmon-ng check" again. If nothing found, then type "airmon-ng start wlan0" and you will see it start and the new name with something like haze pointed out above, like wlan0mon or such. Will show you what it created. Can then run iwconfig to see what it shows for the new device, will say monitor mode. To stop or end monitor mode, "airmon-ng stop wlan0mon" or the name of the new nic ID, then iwconfig again, you will see the original ID back again with mode now set to managed. Any errors you get from this, post here, as well as dmesg output, might help show issues. Quote Link to comment Share on other sites More sharing options...
Daemon0x90 Posted July 25, 2017 Share Posted July 25, 2017 1.) If you're using the on-board wifi card, that doe snot support monitor mode, get an different NIC (Alfa, TP-Link) 2.) Check your interface configs before and after airmon-ng: ifconfig airmon-ng start wlan0 ifconfig Your interface name may have changed from wlan0 to wlan0mon after taking on the monitor mode you just initialized. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.