Results 1 to 10 of 10

Thread: I need some help with this error from airodump-ng

  1. #1

    I need some help with this error from airodump-ng

    I am using Kali Linux 2.0 in VirtualBox 5.0.2. I'm trying to use aircrack/airodump. However, every time I try run them, it says Connection timed out. It happens with this command: airodump-ng wlan0mon. The wifi adapter I use says Zydas ZD1211B with the command airmon-ng start wlan0. The driver is zd1211rw. Google searches tell me that apparently no one else has to deal with this. any idea how to fix this?

  2. #2
    Join Date
    2013-Apr
    Location
    Kali forums
    Posts
    805
    Can you use the aircrack-ng suite outside of a virtual machine ok?

  3. #3
    Join Date
    2015-Dec
    Posts
    17
    What is the output after entering airmon-ng start wlan0?

  4. #4
    "Can you use the aircrack-ng suite outside of a virtual machine ok?" I don't have the aircrack-ng suite outside of my virtual machine.
    "What is the output after entering airmon-ng start wlan0?"

    Output: 'Found 5 processes that could cause trouble.
    If airodump-ng, aireplay-ng or airtun-ng stop working after some time, you may want to kill (some of ) them!
    570 NetworkManager
    673 wpa_supplicant
    766 avahi daemon
    767 avahi daemon
    971 dhclient'

    Then it gives the wifi card info, which I already stated

    Next it says,
    'failed to set wlan0mon up using ip

    (mac80211 monitor mode vif enabled on [phy0]wlan0 on [phy0]wlan0mon)
    (mac80211 station mode vif disabled on [phy]wlan0)

  5. #5
    Join Date
    2015-Dec
    Posts
    17
    Quote Originally Posted by superchampionoftheworld View Post
    "Can you use the aircrack-ng suite outside of a virtual machine ok?" I don't have the aircrack-ng suite outside of my virtual machine.
    "What is the output after entering airmon-ng start wlan0?"

    Output: 'Found 5 processes that could cause trouble.
    If airodump-ng, aireplay-ng or airtun-ng stop working after some time, you may want to kill (some of ) them!
    570 NetworkManager
    673 wpa_supplicant
    766 avahi daemon
    767 avahi daemon
    971 dhclient'

    Then it gives the wifi card info, which I already stated

    Next it says,
    'failed to set wlan0mon up using ip

    (mac80211 monitor mode vif enabled on [phy0]wlan0 on [phy0]wlan0mon)
    (mac80211 station mode vif disabled on [phy]wlan0)
    Do this

    Disconnect your wireless connection

    airmon-ng check kill

    kill any processes it shows like this (using what you posted above as example)

    airmon-ng kill 570 673 766 767 971

    it may tell you one process doesn't exist, which is ok

    airmon-ng start wlan0

    wait for process to finish up (where it shows wlan0mon)

    if it says failed to setup wlan0mon again then your card may not support monitor mode

    if it does not fail then proceed

    wash -i wlan0mon (this will show all networks in range)

    after that just follow whatever tutorial you're following

    should also note this exact process may not work for you, it did for me...but if it doesnt just post a reply with results

  6. #6
    I know my wifi card can do monitor mode, since if I do airmon-ng start wlan0 twice, the 2nd time it says I can't do it because monitor mode is already enabled. After doing
    wash -i wlan0mon, it says 'failed to open wlan0mon for capturing'

  7. #7
    Join Date
    2013-Jul
    Posts
    844
    To SCOTW

    Make sure there are NO auto connect settings in Network Manager(NM). Use the NM drop down menu and uncheck all autoconnect setting for all ESSIDs listed. This will keep NM inactive. The command airmon-ng check kill should do this thru service commands.


    Next try this simple solution

    1. Place your device in monitor mode with airmon-ng

    airmon-ng start wlan0

    In this example you would get:

    wlan0mon

    Now type the following commands

    ifconfig wlan0mon down
    iwconfig wlan0mon mode monitor
    ifconfig wlan0mon up

    Now type

    wash -i wlan0mon


    If this does not work report back what happened.

    Reference comments about your device supporting monitor mode - what is important is that your device can support packet injection not monitor mode. For example you can put most devices in monitor mode and if the operation does not require packet injection(PI) then the device functions fine. You can use devices that do not support PI with airodump-ng and airbase-ng as PI is not required BUT you cannot use such a device with wash or aireplay-ng.

    Try doing a test on your device with aireplay-ng -9

    MTeams
    Last edited by mmusket33; 2016-05-15 at 01:22.

  8. #8
    It didn't work.
    'ifconfig wlan0mon up' gave an error of 'Connection timed out'

  9. #9
    Join Date
    2013-Jul
    Posts
    844
    MTeams suggests you take Virtual Box out of the equation. Make yourself a persistent usb install of kali-linux and try that Operating System.

    MTeams

  10. #10
    I actually solved this myself. I just used a different WiFi card, and it worked.

Similar Threads

  1. airodump-ng error
    By lolminer123 in forum General Archive
    Replies: 4
    Last Post: 2015-11-19, 17:17

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •