Airodump-ng is used for packet capturing of raw 802.11 frames and is particularly suitable for collecting WEP [[http://​en.wikipedia.org/​wiki/​Initialization_vector|IVs]] (Initialization Vector) for the intent of using them with [[aircrack-ng]]. If you have a GPS receiver connected to the computer, airodump-ng is capable of logging the coordinates of the found access points. ​Additionally,​ airodump-ng writes out a text file containing the details of all access points and clients seen.

+

Airodump-ng is used for packet capturing of raw 802.11 frames and is particularly suitable for collecting WEP [[http://​en.wikipedia.org/​wiki/​Initialization_vector|IVs]] (Initialization Vector) for the intent of using them with [[aircrack-ng]]. If you have a GPS receiver connected to the computer, airodump-ng is capable of logging the coordinates of the found access points.

+

+

Additionally,​ airodump-ng writes out several files containing the details of all access points and clients seen.

===== Usage =====

===== Usage =====

Line 10:

Line 12:

​

​

Options:

Options:

-

--ivs ​: Save only captured IVs

+

--ivs ​: Save only captured IVs

-

--gpsd ​: Use GPSd

+

--gpsd ​: Use GPSd

-

--write ​<​prefix>​ : Dump file prefix

+

--write ​<​prefix>​ : Dump file prefix

-

-w : same as --write

+

-w : same as --write

-

--beacons ​ ​: Record all beacons in dump file

+

--beacons ​ ​: Record all beacons in dump file

-

--update ​ ​<​secs>​ : Display update delay in seconds

+

--update ​ ​<​secs>​ : Display update delay in seconds

-

--showack ​ ​: Prints ack/cts/rts statistics

+

--showack ​ ​: Prints ack/cts/rts statistics

-

-h : Hides known stations for --showack

+

-h : Hides known stations for --showack

-

-f <​msecs>​ : Time in ms between hopping channels

+

-f <​msecs>​ : Time in ms between hopping channels

-

--berlin ​ ​<​secs>​ : Time before removing the AP/client

+

--berlin ​ ​<​secs>​ : Time before removing the AP/client

-

from the screen when no more packets

+

from the screen when no more packets

-

are received (Default: 120 seconds)

+

are received (Default: 120 seconds)

-

-r ​<​file>​ : Read packets from that file

+

-r ​<​file>​ : Read packets from that file

-

-x <​msecs>​ : Active Scanning Simulation

+

-x <​msecs>​ : Active Scanning Simulation

-

--nocap : Don't write pcap/ivs file (require ​-w)

+

--manufacturer ​ ​: Display manufacturer from IEEE OUI list

-

+

--uptime ​ : Display AP Uptime from Beacon Timestamp

+

--wps : Display WPS information (if any)

+

--output-format

+

<​formats>​ : Output format. Possible values:

+

​pcap, ivs, csv, gps, kismet, netxml, logcsv

+

Short format "​-o"​

+

The option can be specified multiple times. ​ In this case, each file format

The first line shows the current channel, elapsed running time, current date and optionally if a WPA/WPA2 handshake was detected. ​ In the example above, "WPA handshake: 00:​14:​6C:​7E:​40:​80"​ indicates that a WPA/WPA2 handshake was successfully captured for the BSSID.

The first line shows the current channel, elapsed running time, current date and optionally if a WPA/WPA2 handshake was detected. ​ In the example above, "WPA handshake: 00:​14:​6C:​7E:​40:​80"​ indicates that a WPA/WPA2 handshake was successfully captured for the BSSID.

+

+

In the example above the client rate of "​36-24"​ means:

+

* The first number is the last data rate from the AP (BSSID) to the Client (STATION). ​ In this case 36 megabits per second.

+

* The second number is the last data rate from Client (STATION) to the AP (BSSID). ​ In this case 24 megabits per second.

+

* These rates may potentially change on each packet transmission. ​ It is simply the last speed seen.

+

* These rates are only displayed when locked to a single channel, the AP/client transmission speeds are displayed as part of the clients listed at the bottom. ​

+

* NOTE: APs need more then one packet to appear on the screen. ​ APs with a single packet are not displayed.

|MB|Maximum speed supported by the AP. If MB = 11, it's 802.11b, if MB = 22 it's 802.11b+ and up to 54 are 802.11g. Anything higher is 802.11n or 802.11ac. The dot (after 54 above) indicates short preamble is supported. Displays "​e"​ following the MB speed value if the network has QoS enabled.|

-

|ENC|Encryption algorithm in use. OPN = no encryption,"​WEP?"​ = WEP or higher (not enough data to choose between WEP and WPA/WPA2), WEP (without the question mark) indicates static or dynamic WEP, and WPA or WPA2 if TKIP or CCMP is present.|

|CIPHER|The cipher detected. One of CCMP, WRAP, TKIP, WEP, WEP40, or WEP104. ​ Not mandatory, but TKIP is typically used with WPA and CCMP is typically used with WPA2. WEP40 is displayed when the key index is greater then 0. The standard states that the index can be 0-3 for 40bit and should be 0 for 104 bit.|

|CIPHER|The cipher detected. One of CCMP, WRAP, TKIP, WEP, WEP40, or WEP104. ​ Not mandatory, but TKIP is typically used with WPA and CCMP is typically used with WPA2. WEP40 is displayed when the key index is greater then 0. The standard states that the index can be 0-3 for 40bit and should be 0 for 104 bit.|

|ESSID|The so-called "​SSID",​ which can be empty if SSID hiding is activated. In this case, airodump-ng will try to recover the SSID from probe responses and association requests.|

+

|ESSID|Shows the wireless network name. ​The so-called "​SSID",​ which can be empty if SSID hiding is activated. In this case, airodump-ng will try to recover the SSID from probe responses and association requests. See [[airodump-ng#​hidden_ssids_length|this section]] for more information concerning hidden ESSIDs.|

|STATION|MAC address of each associated station or stations searching for an AP to connect with. Clients not currently associated with an AP have a BSSID of "(not associated)"​.|

|STATION|MAC address of each associated station or stations searching for an AP to connect with. Clients not currently associated with an AP have a BSSID of "(not associated)"​.|

+

|Rate| Station'​s receive rate, followed by transmit rate. Displays "​e"​ following each rate if the network has QoS enabled.|

|Lost|The number of data packets lost over the last 10 seconds based on the sequence number. ​ See note below for a more detailed explanation.|

|Lost|The number of data packets lost over the last 10 seconds based on the sequence number. ​ See note below for a more detailed explanation.|

|Packets|The number of data packets sent by the client.|

|Packets|The number of data packets sent by the client.|

Line 93:

Line 121:

RXQ expanded:​\\ ​

RXQ expanded:​\\ ​

-

Its measured over all management and data frames. ​ That's the clue, this allows you to read more things out of this value. ​ Lets say you got 100 percent RXQ and all 10 (or whatever the rate) beacons per second coming in. Now all of a sudden the RXQ drops below 90, but you still capture all sent beacons. ​ Thus you know that the AP is sending frames to a client but you can't hear the client nor the AP sending to the client (need to get closer). ​ Another thing would be, that you got a 11MB card to monitor and capture frames (say a prism2.5) and you have a very good position to the AP. The AP is set to 54MBit and then again the RXQ drops, so you know that there is at least one 54MBit client connected to the AP.

+

Its measured over all management and data frames. The received frames contain a sequence number which is added by the sending access point. ​ RXQ = 100 means that all packets were received from the access point in numerical sequence and none were missing. That's the clue, this allows you to read more things out of this value. ​ Lets say you got 100 percent RXQ and all 10 (or whatever the rate) beacons per second coming in. Now all of a sudden the RXQ drops below 90, but you still capture all sent beacons. ​ Thus you know that the AP is sending frames to a client but you can't hear the client nor the AP sending to the client (need to get closer). ​ Another thing would be, that you got a 11MB card to monitor and capture frames (say a prism2.5) and you have a very good position to the AP. The AP is set to 54MBit and then again the RXQ drops, so you know that there is at least one 54MBit client connected to the AP.

+

+

N.B.: RXQ column will only be shown if you are locked on a single channel, not channel hopping.

Lost expanded:​\\ ​

Lost expanded:​\\ ​

Line 112:

Line 142:

==== Limiting Data Capture to a Single AP ====

==== Limiting Data Capture to a Single AP ====

-

To limit the data capture to a single AP you are interested in, include the "- -bssid"​ option and specificy ​the AP MAC address. ​ For example: "​airodump-ng -c 8 - -bssid 00:​14:​6C:​7A:​41:​20 -w capture ath0".

+

To limit the data capture to a single AP you are interested in, include the "- -bssid"​ option and specify ​the AP MAC address. ​ For example: "​airodump-ng -c 8 - -bssid 00:​14:​6C:​7A:​41:​20 -w capture ath0".

==== How to Minimize Disk Space for Captures ====

==== How to Minimize Disk Space for Captures ====

Line 203:

Line 233:

==== Airodump-ng stops capturing data after a short period of time ====

==== Airodump-ng stops capturing data after a short period of time ====

-

The most common cause is that a connection manager is running on your system and takes the card out of monitor mode. This is a very common problem especially with the Ubuntu distribution. ​Be sure to stop all connection managers prior to using the aircrack-ng suite.

+

The most common cause is that a connection manager is running on your system and takes the card out of monitor mode. Be sure to stop all connection managers prior to using the aircrack-ng suite. ​In general, disabling "​Wireless"​ in your network manager should be enough but sometimes you have to stop them completely. It can be done with [[airmon-ng]]:​

Recent linux distributions use //​upstart//;​ it automatically restarts the network manager. In order to stop it, see the following [[airmon-ng#​check_kill_fails|entry]].

As well, make sure that [[http://​hostap.epitest.fi/​wpa_supplicant/​|wpa_supplicant]] is not running. ​ Another potential cause is the PC going to sleep due to power saving options. ​ Check your power saving options.

As well, make sure that [[http://​hostap.epitest.fi/​wpa_supplicant/​|wpa_supplicant]] is not running. ​ Another potential cause is the PC going to sleep due to power saving options. ​ Check your power saving options.

Line 211:

Line 243:

The madwifi-ng driver for the atheros chipset contains a bug in releases up to r2830 which causes airodump-ng in channel hopping mode to stop capturing data after a few minutes. ​ The fix is to use r2834 or above of the madwifi-ng drivers.

The madwifi-ng driver for the atheros chipset contains a bug in releases up to r2830 which causes airodump-ng in channel hopping mode to stop capturing data after a few minutes. ​ The fix is to use r2834 or above of the madwifi-ng drivers.

+

See also [[airmon-ng#​check_kill_fails|this entry]] for recent ​

==== Hidden SSIDs "<​length: ​ ?>" ====

==== Hidden SSIDs "<​length: ​ ?>" ====

Line 245:

Line 278:

It is critical that the root cause of the problem be eliminated and then airodump-ng restarted again. ​ Here are some possible reasons and how to correct them:

It is critical that the root cause of the problem be eliminated and then airodump-ng restarted again. ​ Here are some possible reasons and how to correct them:

-

* There is one or more intefaces ​in "​managed mode" and these are are scanning for an AP to connect to. Do not use any command, process or program to connect to APs at the same time as you use the aircrack-ng suite. ​

+

* There is one or more interfaces ​in "​managed mode" and these are are scanning for an AP to connect to. Do not use any command, process or program to connect to APs at the same time as you use the aircrack-ng suite. ​

* Other processes are changing the channel. A common problem are network managers. ​ You can also use "​airmon-ng check" on current versions of the aircrack-ng suite to identify problem processes. ​ Then use "​kill"​ or "​killall"​ to destroy the problem processes. ​ For example, use “killall NetworkManager && killall NetworkManagerDispatcher” to eliminate network managers.

* Other processes are changing the channel. A common problem are network managers. ​ You can also use "​airmon-ng check" on current versions of the aircrack-ng suite to identify problem processes. ​ Then use "​kill"​ or "​killall"​ to destroy the problem processes. ​ For example, use “killall NetworkManager && killall NetworkManagerDispatcher” to eliminate network managers.

* If you are using the madwifi-ng driver and have more then the ath0 interface created, the driver may be automatically scanning on the other interfaces. ​ To resolve this, stop all interfaces except ath0.

* If you are using the madwifi-ng driver and have more then the ath0 interface created, the driver may be automatically scanning on the other interfaces. ​ To resolve this, stop all interfaces except ath0.

Line 254:

Line 287:

\\

\\

It can also means that you cannot use this channel (and airodump-ng failed to set the channel). Eg: using channel 13 with a card that only supports channels from 1 to 11.

It can also means that you cannot use this channel (and airodump-ng failed to set the channel). Eg: using channel 13 with a card that only supports channels from 1 to 11.

+

+

==== Where did my output files go? ====

+

+

You ran airodump-ng and now cannot find the output files.

+

+

First, make sure you ran airodump-ng with the option to create output files. ​ You must include -w or --write plus the file name prefix. ​ If you fail to do this then no output files are created.

+

+

By default, the output files are placed in the directory where you start airodump-ng. ​ Before starting airodump-ng,​ use "​pwd"​ to display the current directory. ​ Make a note of this directory so your return to it a later time. To return to this directory, simply type "cd <full directory name including the full path>"​.

+

+

To output the files to a specific directly, add the full path to the file prefix name. For example, lets say you want to output all your files to "/​aircrack-ng/​captures"​. ​ First, create /​aircrack-ng/​captures if it does not already exist. ​ Then include "-w /​aircrack-ng/​captures/<​file prefix>"​ on your airodump-ng command line.

+

+

To access your files later when running aircrack-ng,​ either change to the directory where the files are located or prefix the file name with the full path.

+

==== Windows specific ====

==== Windows specific ====

Line 306:

Line 352:

* Check the "​Driver Provider"​ name for the driver being used for your wireless device via properties to ensure it says Wildpackets. ​ Also confirm the driver version is what you expect.

* Check the "​Driver Provider"​ name for the driver being used for your wireless device via properties to ensure it says Wildpackets. ​ Also confirm the driver version is what you expect.

* Using a command prompt, change to the directory where airodump-ng.exe is located. ​ Confirm that peek.dll and peek.sys exist in this directory.

* Using a command prompt, change to the directory where airodump-ng.exe is located. ​ Confirm that peek.dll and peek.sys exist in this directory.

-

* Using the command prompt and while still in the directory containing airodump-ng,​ try starting airodump-ng. ​ It should not ask you about downloading ​wildpackets ​or peek files. ​ If it does, you do not have everything installed correctly. Redo the installation instructions.

+

* Using the command prompt and while still in the directory containing airodump-ng,​ try starting airodump-ng. ​ It should not ask you about downloading ​Wildpackets ​or peek files. ​ If it does, you do not have everything installed correctly. Redo the installation instructions.

=== Review all your steps ===

=== Review all your steps ===

Line 316:

Line 362:

Airodump-ng or any "user space" program cannot produce a bluescreen, it is the driver which is the root cause. In most cases, these bluescreen failures cannot be resolved since these drivers are closed source.

Airodump-ng or any "user space" program cannot produce a bluescreen, it is the driver which is the root cause. In most cases, these bluescreen failures cannot be resolved since these drivers are closed source.

+

===== Interaction =====

+

Since revision r1648, airodump-ng can receive and interpret key strokes while running. The following list describes the currently assigned keys and supposed actions.

* The first number is the last data rate from the AP (BSSID) to the Client (STATION). ​ In this case 36 megabits per second.

+

-

* The second number ​is the last data rate from Client (STATION) to the AP (BSSID). ​ In this case 24 megabits per second.

+

-

* These rates may potentially change on each packet transmission. ​ It is simply the last speed seen.

+

-

* NOTE: APs need more then one packet to appear on the screen. ​ APs with a single packet are not displayed.

+

-

+

-

Other changes:

+

-

+

-

* The default cracking method is PTW. This is done in two phases. ​ In the first phase, aircrack-ng only uses ARP packets. ​ If the key is not found, then it uses all the packets in the capture. ​ Please remember that not all packets can be used for the PTW method. ​ This [[supported_packets|Tutorial:​ Packets Supported for the PTW Attack]] provides details.

+

-

* "​-f"​ option is the time to dwell on each channel before hopping.

+

-

* "​--berlin <​seconds>" ​ is the time before removing the AP/client from the screen when no more packets are received (Default: 120 seconds).