Version: 1.08 September 25, 2009
A common question that people ask is “I have model ABC wireless card, is it compatible with Aircrack-ng?” or “What card should I buy?” or “Can my card do injection?” and so on. This tutorial address these questions.
First off, answering these questions involves some work on your part. It is not as easy as posting the question on the Forum and waiting for an answer. If you do not do your homework first, no help will be provided. On the other hand, if you in fact do your homework properly, people will make every effort to help you.
If you are planning to purchase a card then the easiest method is to pick a card from the list of supported cards. If you are considering purchasing a particular then you can use this tutorial to determine if it will work with aircrack-ng.
Another point I want to make is that there are many, many compatible cards out there that are not listed in the supported cards section. Please, please take the time to post to the Forum when you are successful with a particular card. This is the only way we can expand the list of supported cards. When you post, please provide the manufacturer, model, card revision if applicable, chipset and what drivers you used.
Now, on to the matter at hand. Here are the steps we will be following:
First decide if you simply want to listen to wireless network traffic or to both listen to and inject packets. It is important to realize that at this point in time, Windows can only be used for listening to network traffic. Windows cannot inject data packets. This is a fundamental limitation. As well, there are far fewer cards compatible with Windows.
Depending on the card/chipset, Linux gives you the ability to both listen to and inject packets.
So at this point you need to have decided:
These will be constraints later on in this tutorial.
There are two manufacturers involved with wireless cards. The first is the brand of the card itself. Examples of card manufacturers are Netgear, Ubiquiti , Linksys and D-Link. There are many, many manufacturers beyond the examples give here.
The second manufacturer is who makes the wireless chipset within the card. This is the most important company to know. Unfortunately, it is sometimes the hardest to determine. This is because card manufacturers generally don’t want to reveal what they use inside their card. However, for our purposes, it is critical to know the wireless chipset manufacturer. Knowing the wireless chipset manufacturer allows you to determine which operating systems are support, software drivers you need and what limitations are associated with them.
It is very important to realize that the difference between the two manufacturers. Just knowing the card manufacturer and model does not allow you to proceed. What you really need to know is the chipset. The next step provides information about how to determine the chipset in your card or the card you are planning to purchase.
Ok, this is the really hard part. I will tell you up front that you need to do your research well in this step to be successful. On the other hand, if you are lucky, your card is already listed in the supported card section and this gives you all the information required.
If this is not the case, then you first need to determine what wireless chipset your card uses. This can be done by one or more of these techniques:
Here are some other resources to assist you in determine what chipset you have:
Card manufacturers add to the confusion by keeping the same card model number yet changing the chipset inside them. This is where you will hear the term “card revision” or “card version”. D-Link seems to do this a lot. So first determine if this applies to your card. The version is typically found stamped on the card and located near the serial number or MAC address. See this D-Link page for an example of the same card with different revisions.
So when you are determining the chipset for your card, make sure to include the revision/version when doing a search. For example, search for “DWL-G650 C1 chipset” and not just “DWL-G650”. The revision/version is extremely important.
If you are running linux, there are a variety of methods to obtain card information and possibly determine the chipset. Here are some methods:
Even if you are running Windows, you can boot from a live distro and use the linux techniques above.
In a Windows environment, try hardware analysis tools such HWiNFO to obtain the chipset information.
If you are unable to determine which chipset your card has, then you are out of luck. Your options are to purchase a card from the compatible list or to research and identify a card which matches your criteria then purchase it.
Once you know the chipset, then proceed to the next step.
Using the Compatibly Section determine what features the chipset provides for the particular operating system that you will be using.
If this matches your requirements, great. If not, the consider using another operating system or using a different card.
If your prime operating system is Windows, and you like the linux features, consider using a live linux distro. This way you have the best of both worlds.
Proceed to the next step of determining the drivers and patches required.
Using the Drivers Section you can now determine the drivers required for your chipset and your operating system. The web site has links to the software required.
For linux, generally, you need to patch the drivers in order to get the advanced features such as monitor mode and injection capability. Most patches can be found here. Remember you will need to have the kernel headers and, in some cases, the kernel sources on your system prior to compiling the drivers.
This tutorial will not be providing detailed instructions on how to patch your system.
Conversely, if you know what chipset provides the features you want, you can use the Compatible card list to find a card that uses that particular chipset.
As well, this tutorial will have given you the knowledge to determine if a particular card you are considering purchasing will provide you the features you want.