Aircrack-ng

User Tools

Site Tools

Trace:
compatible_cards

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
compatible_cards [2008/12/31 20:11] – Add more detail about using PCI IDs to identify cards. darkaudaxcompatible_cards [2009/05/17 20:27] – Added additional lspci information. darkaudax
Line 1: Line 1:
 ====== Tutorial: Is My Wireless Card Compatible? ====== ====== Tutorial: Is My Wireless Card Compatible? ======
-Version: 1.06 December 31, 2008 \\+Version: 1.07 May 17, 2009 \\
 By: darkAudax By: darkAudax
  
Line 7: Line 7:
 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. 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 [[http://forum.tinyshell.be/|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.+First off, answering these questions involves some work on your part.  It is not as easy as posting the question on the [[http://forum.aircrack-ng.org/|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 [[compatibility_drivers#which_is_the_best_card_to_buy|supported cards]].  If you are considering purchasing a particular then you can use this tutorial to determine if it will work with aircrack-ng.   If you are planning to purchase a card then the easiest method is to pick a card from the list of [[compatibility_drivers#which_is_the_best_card_to_buy|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 [[compatibility_drivers#which_is_the_best_card_to_buy|supported cards section]].  Please, please take the time to post to the [[http://forum.tinyshell.be/|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.+Another point I want to make is that there are many, many compatible cards out there that are not listed in the [[compatibility_drivers#which_is_the_best_card_to_buy|supported cards section]].  Please, please take the time to post to the [[http://forum.aircrack-ng.org/|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: Now, on to the matter at hand.  Here are the steps we will be following:
Line 21: Line 21:
   - Determine the drivers and patches required   - Determine the drivers and patches required
   - Select a card   - Select a card
- 
  
 ===== Determine your requirements and constraints ===== ===== Determine your requirements and constraints =====
Line 44: Line 43:
  
 It is a 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. It is a 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.
- 
- 
- 
- 
  
 ===== Determine the chipset ===== ===== Determine the chipset =====
Line 56: Line 51:
  
   *Search the internet for "<your card model> chipset" or "<your card model> linux". Quite often you can find references to what chipset your card uses and/or other people's experiences.  This is by far the easiest and most successful way of determing the chipset.  Be sure to check a number of search entries to ensure they are consistent.   *Search the internet for "<your card model> chipset" or "<your card model> linux". Quite often you can find references to what chipset your card uses and/or other people's experiences.  This is by far the easiest and most successful way of determing the chipset.  Be sure to check a number of search entries to ensure they are consistent.
-  *Search the [[http://forum.tinyshell.be/|Forum]]+  *Search the [[http://forum.aircrack-ng.org/|Forum]]
   *You may also have a look at windows driver file names, it's often the name of the chipset or the driver to use.   *You may also have a look at windows driver file names, it's often the name of the chipset or the driver to use.
   *Check the card manufacturers page. Sometimes they say what chipset they use.   *Check the card manufacturers page. Sometimes they say what chipset they use.
Line 81: Line 76:
   * The "dmesg" command can quite often contain detailed messages indicating what card was detected and the chipset.   * The "dmesg" command can quite often contain detailed messages indicating what card was detected and the chipset.
   * If the card is an ISA card, you are usually out of luck.    * If the card is an ISA card, you are usually out of luck. 
-  * If the card is a PCI card, you need to use the command "lspci -nn" to display the card identification strings. In some cases, such as on cards with Broadcom chipsets, this alone can reveal the chipset.  The "-nn" should cause the PCI ID to be displayed.  An example of what a PCI ID looks like is "168c:0013" for an Atheros chipset card.  Once you have the PCI ID, there are many Internet sites to do lookups.  Some sites are [[http://pciids.sourceforge.net/]] or [[http://www.pcidatabase.com/]].  You can find other lookup sites by search for "PCI ID".+  * If the card is a PCI card, you need to use the command "lspci -nn" to display the card identification strings. In some cases, such as on cards with Broadcom chipsets, this alone can reveal the chipset.  The "-nn" should cause the PCI ID to be displayed.  An example of what a PCI ID looks like is "168c:0013" for an Atheros chipset card.  Once you have the PCI ID, there are many Internet sites to do lookups.  Some sites are [[http://pciids.sourceforge.net/]] or [[http://www.pcidatabase.com/]].  You can find other lookup sites by search for "PCI ID".  As well, the kernel modules required and in use are displayed.  This can be very helpful in identifying the chipset.
   * If the hardware is a USB dongle, you need to use the command "lsusb" to display the dongle identification strings. In some case, "lsusb" doesn't work (for example if usbfs is not mounted), and you can get the identification strings from the kernel log using "dmesg" (or in /var/log/messages).    * If the hardware is a USB dongle, you need to use the command "lsusb" to display the dongle identification strings. In some case, "lsusb" doesn't work (for example if usbfs is not mounted), and you can get the identification strings from the kernel log using "dmesg" (or in /var/log/messages). 
   * If the card is a Cardbus card (32 bits Pcmcia), and if you are using a relatively new kernel (2.4.X or above) with the kernel Pcmcia subsystem, you need to use the command "lspci -nn" to display the card identification strings. If the card is a Cardbus card (32 bits Pcmcia), and if you are using an older kernel with the standalone Pcmcia subsystem, you need to use the command "cardctl ident" display the card identification strings. Try both and see what comes out.    * If the card is a Cardbus card (32 bits Pcmcia), and if you are using a relatively new kernel (2.4.X or above) with the kernel Pcmcia subsystem, you need to use the command "lspci -nn" to display the card identification strings. If the card is a Cardbus card (32 bits Pcmcia), and if you are using an older kernel with the standalone Pcmcia subsystem, you need to use the command "cardctl ident" display the card identification strings. Try both and see what comes out. 
Line 104: Line 99:
  
 Proceed to the next step of determining the drivers and patches required. Proceed to the next step of determining the drivers and patches required.
- 
  
 ===== Determine the drivers and patches required ===== ===== Determine the drivers and patches required =====
compatible_cards.txt · Last modified: 2018/10/08 01:37 by mister_x