Injection test

Important note: This option is only available on aircrack-ng 0.9 and up.

Description

The injection test determines if your card can successfully inject and determine the ping response times to the Access Point (AP). If you have two wireless cards, it can also determine which specific injection tests can be successfully performed.

The basic injection test provides additional valuable information as well. First, it lists access points in the area which respond to broadcast probes. Second, for each, it does a 30 packet test that indicates the connection quality. This connection quality quantifies the ability of your card to successfully send and then receive a response to the test packet. The percentage of responses received gives an excellent indication of the link quality.

You may optionally specify the AP name and MAC address. This can be used to test a specific AP or test a hidden SSID.

So how does it work? The following will briefly describe how the testing is performed.

The program initially sends out broadcast probe requests. These are probe requests which ask any AP listening to respond with a description of itself. Not every AP will respond to this type of request. A list of responding APs is assembled to be used in subsequent steps. If any AP responds, a messages is printed on the screen indicating that the card can successfully inject.

At the same time, any AP identified via a beacon packet is also added to the list of APs to be processed in subsequent steps.

If a specific AP was optionally listed on the command line (BSSID and SSID), this is also added to the list of APs to be processed.

Then for each AP in the list, 30 directed probe requests are sent out. A directed probe request is addressed to a specific AP. The count of probe responses received plus the percentage is then printed on the screen. This indicates if you can communicate with the AP and how well.

If two wireless cards were specified then each attack mode is tried and the results printed on the screen.

An additional feature is the ability to test connectivity to airserv-ng. Once the basic connectivity test is completed then it proceeds with the standard injection tests via the wireless card linked to airserv-ng.

Usage

aireplay-ng -9 -e teddy -a 00:de:ad:ca:fe:00 -i wlan1 wlan0

Where:

-9 means injection test. Long form is --test.

-e teddy is the network name (SSID). This is optional.

-a 00:de:ad:ca:fe:00 ath0 is MAC address of the access point (BSSID). This is optional.

-i wlan1 is interface name of the second card if you want to determine which attacks your card supports. This interfaces acts as an AP and receives packets. This is optional.

wlan0 is the interface name or airserv-ng IP Address plus port number. This interface is used to send packets. For example - 127.0.0.1:666. (Mandatory)

IMPORTANT: You must set your card to monitor mode and to the desired channel with airmon-ng prior to running any of the tests.

Usage Examples

Basic Test

This is a basic test to determine if you card successfully supports injection.

16:29:41 wlan0 channel: 9: This tells you which interface was used and the channel it was running on.

16:29:41 Injection is working!: This confirms your card can inject.

16:29:42 Found 5 APs: These access points (APs) were found either through the broadcast probes or received beacons.

16:29:42 00:09:5B:5C:CD:2A - channel: 11 - 'NETGEAR': Notice that this AP is on channel 11 and not on our card channel of 9. It is common for adjacent channels to spill over.

16:29:55 Ping (min/avg/max): 2.763ms/4.190ms/8.159ms: It an AP responds with one or more packets then the ping times are calculated.

16:29:55 27/30: 90% for teddy: This is the only AP that the card can successfully communicate with. This is another verification that your card can inject. You will also notice that all the other APs have 0%.

Hidden or Specific SSID

You can check a hidden SSID or check a specific SSID with the following command:

Connection successful: This indicates that there is connectivity It is import to make sure both your cards are on the same channel otherwise the tests will not work correctly.

The second part of the output is identical to what has been presented earlier.

Usage Tips

Nothing at this point in time.

Usage Troubleshooting

General

Make sure you use the correct interface name. For mac80211 drivers, it is typically “mon0”. For madwifi-ng, it is typically “ath0”. As well, ensure you don't have multiple monitor interfaces created meaning “mon0”, “mon1”, etc. is bad and the extra interfaces need to be destroyed.

Make sure the card(s) are on the same channel as your AP and locked on this channel. When putting your card into monitor mode, be sure to specify the channel via airmon-ng. You can use iwconfig to confirm which channel your card is currently on. The injection test will fail if your card and access point are on different channels.

Make sure your card is not channel hopping. A very common mistake is to have airodump-ng running in channel hopping mode. If you use airodump-ng, be sure to use the “-c <channel>” option. Additionally, ensure all network managers and similar are killed off.

"Network is down" error message

If you get error messages similar to the following for Atheros-based cards and the madwifi-ng driver:

Remove the “-B” bitrate option from the request. There is an underlying problem with the madwifi-ng driver concerning changing bitrates on the fly. Simply put, you cannot currently change bitrates on the fly. A request has been made to the madwifi-ng developers to fix this. Until this is done, you cannot use the “-B” option with madwifi-ng drivers.

Airodump-ng shows APs but they don't respond

The injection test uses broadcast probe requests. Not all APs respond to broadcast probe requests. So the injection test may fail because the APs are ignoring the broadcast packets. As well, you quite often can receive packets from APs further away then your card can transmit to. So the injection test may fail because your card cannot transmit far enough for the AP to receive them.

In both cases, try another channel with multiple APs. Or try the specific SSID test described above.