0

I think I have a problem with airodump in Kali in Vmware - when I come to the stage that I should enter airodump - ng wlan0mon, it does not show me any MAC address it - is just empty between BSSID and channel, but in my computer it shows a lot more wireless networks available. I have searched about it, but I couldn't find any help, hope you help me with this stuff. Thanks in advance.enter image description here

  • Additionally, I have done airmon-ng start wlan0 and airmon-ng check kill. – M. Kennedy Dec 23 '16 at 9:08
  • does your wireless hardware supports monitor mode ? – storm Dec 23 '16 at 9:26
  • I am not sure how to know that? – M. Kennedy Dec 23 '16 at 9:30
  • When running airmon-ng start you should get a new wireless interface mon0 or something similar , also try to change/specify the channel , for example airmon-ng start wlan0 11 will put your wireless card in monitor mode on channel 11 ( try with channels 1 , 6 and 11 ) – storm Dec 23 '16 at 9:40
  • Do I supposed to plug my lan cable to modem? – M. Kennedy Dec 23 '16 at 9:43
2

Are you using an internal or external wireless USB to monitor network traffic? Either way you'll want to check to make sure the chip set your card uses is supported by airmon-ng (you'll have to do some googling to find out which chip set you're using and if it's supported) and you'll need to change the card from promiscuous to monitor mode. Assuming that airmon-ng does support your network card you'll need to put it in monitor mode. You can do this by entering the following commands in terminal

ifconfig *network interface, e.g. wlan0* down
ifconfig *network interface* mode monitor
ifconfig *network interface* up

Once you've done that check to make sure there are no processes running on your computer that will interfere with airmon-ng running the following command

airmon-ng check *network interface*

That should list items like Network Manager, Daemons, Supplicants, etc. You'll need to kill off all of these processes and make sure they don't re-spawn by entering the following commands

kill *whatever number is listed before the process, e.g. 1657*

Once you've killed all the items that may possibly interfere with airmon-ng, check the status again, if nothing comes up, then start airmon-ng using the following command

airmon-ng start *network interface*

That should change your network interface from something like wlan0 to wlan0mon. Make sure you're using the new interface when using airmon-ng.

  • Thanks for your time to answer my problem. However, I think the problem is vmware. I mean I should use bootable usb or Dual boot for computer. Other than that I should buy some kind of wireless stuff to work in vmware. – M. Kennedy Dec 29 '16 at 18:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.