User Tools

Site Tools


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 [2009/05/04 00:04] – cleanup (newlines) mister_xcompatible_cards [2014/01/08 03:44] – [Determine the chipset] Updated link for atheros chipset search mister_x
Line 1: Line 1:
 ====== Tutorial: Is My Wireless Card Compatible? ====== ====== Tutorial: Is My Wireless Card Compatible? ======
-Version: 1.06 December 312008 \\+Version: 1.08 September 252009 \\
 By: darkAudax By: darkAudax
  
Line 31: Line 31:
  
   * Which operating system you plan to use   * Which operating system you plan to use
-  * Your prefered hardware format (PCI, PCMCIA, USB, etc.)+  * Your preferred hardware format (PCI, PCMCIA, USB, etc.)
   * Which features you require (listening, injection)   * Which features you require (listening, injection)
  
Line 42: Line 42:
 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. 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.+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.
  
 ===== Determine the chipset ===== ===== Determine the chipset =====
Line 50: Line 50:
 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: 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:
  
-  *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 determining the chipset.  Be sure to check a number of search entries to ensure they are consistent.
   *Search the [[http://forum.aircrack-ng.org/|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.
Line 63: Line 63:
   * [[http://atheros.rapla.net/|Atheros chipsets based wireless 802.11a/b/g devices]] only Atheros-based cards   * [[http://atheros.rapla.net/|Atheros chipsets based wireless 802.11a/b/g devices]] only Atheros-based cards
   * [[http://www.linux-wlan.org/docs/wlan_adapters.html.gz|WLAN Adapter Chipset Directory]] not up-to-date but still very useful   * [[http://www.linux-wlan.org/docs/wlan_adapters.html.gz|WLAN Adapter Chipset Directory]] not up-to-date but still very useful
-  * [[http://customerproducts.atheros.com/customerproducts/default.asp|Atheros Communications Total 802.11 Product Search]]+  * [[https://qca.qualcomm.com/|Atheros Product Search]] - See Search QCA Products combobox.
   * [[http://www.seattlewireless.net/index.cgi/HardwareComparison|Hardware Comparison]] with a lot of details.   * [[http://www.seattlewireless.net/index.cgi/HardwareComparison|Hardware Comparison]] with a lot of details.
   * [[http://wiki.uni-konstanz.de/wiki/bin/view/Wireless/ListeChipsatz|Overview]] and details about wireless adapters   * [[http://wiki.uni-konstanz.de/wiki/bin/view/Wireless/ListeChipsatz|Overview]] and details about wireless adapters
   * [[http://www.qbik.ch/usb/devices/search.php|USB Product ID lookup]] For USB devices, obtain the device id via the linux lsusb command and then look it up via the product id.  This is the first half of the device id before the colon.  E.g. 0bda:8187.  Use "0bda" then match the "8187" to entries found.   * [[http://www.qbik.ch/usb/devices/search.php|USB Product ID lookup]] For USB devices, obtain the device id via the linux lsusb command and then look it up via the product id.  This is the first half of the device id before the colon.  E.g. 0bda:8187.  Use "0bda" then match the "8187" to entries found.
  
-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 addess.  See this [[http://www.dlink.com/products/support.asp?pid=11&sec=0#drivers|D-Link page]] for an example of the same card with different revisions. +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 [[http://www.dlink.com/products/support.asp?pid=11&sec=0#drivers|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. 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.
Line 76: 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 92: Line 92:
 ===== Verify the chipset capabilities ===== ===== Verify the chipset capabilities =====
  
-Using the [[http://aircrack-ng.org/doku.php?id=compatibility_drivers#compatibility|Compatibily Section]] determine what features the chipset provides for the particular operating system that you will be using.+Using the [[compatibility_drivers#compatibility|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 this matches your requirements, great.  If not, the consider using another operating system or using a different card.
Line 102: Line 102:
 ===== Determine the drivers and patches required ===== ===== Determine the drivers and patches required =====
  
-Using the [[http://aircrack-ng.org/doku.php?id=compatibility_drivers#drivers|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.+Using the [[compatibility_drivers#drivers|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 [[http://patches.aircrack-ng.org/|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. 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 [[http://patches.aircrack-ng.org/|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.
Line 108: Line 108:
 This tutorial will not be providing detailed instructions on how to patch your system. This tutorial will not be providing detailed instructions on how to patch your system.
  
-If you don't have the skills or experience to patch your system, consider using a live linux distro such as [[http://www.remote-exploit.org/backtrack.html|BackTrack]] which already has all the patched drivers.+If you don't have the skills or experience to patch your system, consider using a live linux distro such as [[http://www.remote-exploit.org/backtrack.html|BackTrack]] or the new [[http://www.kali.org/|Kali Linux]] that have already all the patched drivers.
  
 ===== Select a card ===== ===== Select a card =====
  
-Conversely, if you know what chipset provides the features you want, you can use the [[http://aircrack-ng.org/doku.php?id=compatibility_drivers#which_is_the_best_card_to_buy|Compatible card list]] to find a card that uses that particular chipset.+Conversely, if you know what chipset provides the features you want, you can use the [[compatibility_drivers#which_is_the_best_card_to_buy|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. 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.
  
compatible_cards.txt · Last modified: 2018/10/08 01:37 by mister_x