Broadcom Peek Driver Windows
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, Interl 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. For example, Ralink, Atheros, Qualcomm. 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 supported, software drivers you need and what limitations are associated with them. The next section describes the operating systems supported and limitations by chipset. You first need to determine what wireless chipset your card uses. This can be done by one or more of these techniques:. Searching for “Alfa AWUS036AC wikidevi” returns me on WikiDevi.
The box on the right contain all the information needed to identify the chipset manufacturer and model. In this case, RTL8812AU. It also lists the IDs ( 0bda:8812) which is what would be returned on Linux with the lsusb command, right next to ID. If it were on Windows, even if the drivers were not installed, looking in the device manager, that ID would be found in Details pane of the device itself, in the property “Hardware IDs”. This is also displayed in WikiDevi: USB VID0BDA&PID8812 (this is the same as the IDs on Linux, they're just uppercase and they contain some text around: USB device, VID stands for Vendor ID, PID stands for product ID).
Searching for that ID in WikiDevi or any search engine would also help finding the chipset and driver required. Multiple pages would be returned because multiple adapters share the same USB ID.
The exact same principles apply to internal devices, the only difference is they will be found under lspci. Another way to find the chipset/driver, after exhausting the options above, if you don't have the device itself is to download the driver. It is very useful when searching for laptops that are too new to be in any search engine results.
In this case, the Windows driver of the AWUS036AC. It doesn't really matter which version of Windows, the important information are some filenames (and content). Sometimes the name of the files (.cat,.inf and.sys) can indicate the chipset codename.
Most of the time, they don't and the.inf file needs to be opened in a text editor (supporting UTF-16). Scroll down and there will be lists of IDs that are supported by that driver. In this example, the driver supports both PCI and USB Realtek devices, so, it will help narrow down what compatibility you have to look for on Linux.
If the driver is packed in an executable (.msi or.exe), unpacking will be required. Sometimes multiple times, such as when it is bundled with a WiFi manager. UniExtract (Universal Extractor) is one of the tools to do so.
Broadcom Peek Driver Windows 8
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 supported, software drivers you need and what limitations are associated with them. The section describes the operating systems supported and limitations by chipset.
You first need to determine what wireless chipset your card uses. This can be done by one or more of these techniques:. And details about wireless adapters Chipset Supported by airodump for Windows Supported by airodump for Linux Supported by aireplay for Linux Atheros CardBus: YES PCI: NO (see ) YES YES (driver patching required) Atmel UNTESTED 802.11b YES 802.11g UNTESTED UNTESTED Broadcom bcm43xx Old models only (BRCM driver) YES MOSTLY No fragmentation attack support.
Broadcom b43 NO Yes (1.0-beta2 and up) Yes Centrino b NO PARTIAL (ipw2100 driver doesn't discard corrupted packets) NO Centrino b/g NO YES NO (firmware drops most packets) No fragmentation attack support. Centrino a/b/g NO YES YES (use ipwraw or ) Centrino a/g/n (4965) NO YES MOSTLY, see. Fakeauth is currently broken. Centrino a/g/n (5xxx) NO YES YES Cisco Aironet YES?
Yes, but very problematic NO (firmware issue) Hermes I YES YES NO (firmware corrupts the MAC header) NdisWrapper N/A Never Never Prism2/3 NO YES YES (PCI and CardBus only, driver patching required) NOTE: Prism2/3 does not support shared key authentication and the fragmentation attack. There is a and this chipset is not currently recommended. It may even affect other kernel versions. PrismGT FullMAC YES YES YES (driver patching recommended) PrismGT SoftMAC YES WIP UNTESTED Ralink NO YES YES, see, and. Also see Ralink chipset comments later on this pager for important concerns. RTL8180 YES YES UNSTABLE (driver patching required) RTL8185 NO YES YES (mac80211 driver untested) RTL8187B/RTL8197 NO YES YES (2.6.27+, use the driver with ) RTL8187L UNTESTED YES (driver required to view power levels) YES (driver recommended for injection and required to view power levels) TI (ACX100/ACX111) NO YES YES (driver required) No fragmentation attack support. Please re-test fragmentation with the + mac80211 frag patch!
ZyDAS 1201 NO YES Partially but NOT RECOMMENDED (See for details) ZyDAS 1211(B) softmac NO YES Partially but NOT RECOMMENDED (See for details). Atheros has acquired Zydas and renamed this chipset to AR5007UG.
ZyDAS 1211(B) mac80211 NO YES ( recommended) YES, but no fragmentation attack support yet. Other mac80211 (ADMtek) NO UNTESTED, but likely YES UNTESTED (YES for drivers with AP mode support) Other legacy (Marvel) NO UNKNOWN NO. How much peer support and documentation is available for the card and software drivers. It is not an easy decision to make. By considering these factors, it will help you make a more informed decision on what to purchase. Chipset Windows driver (monitor mode) Linux Drivers Note Atheros or or (see this for more information) or USB is not supported at all (Linux AND windows) Atmel AT76C503/505A based USB WLAN adapters Atmel AT76C503/505A based USB WLAN adapters, mac80211 driver Broadcom Windows: Old models only Linux: always use latest -rc kernel Broadcom with b43 driver, it's slowly becoming the recommended driver Centrino b 802.11b only Centrino b/g See.
See more recent See this for how to do injection. Centrino a/b/g ipw2915 uses ipw2200 driver (See this for alpha injection support.) For ipw3945 you can use the or see for WifiWay which includes patches for injection. Centrino a/g/n. Cisco/Aironet 4500/4800/340/350 series, Firmware 4.25.30 recommended (see for more info) Hermes I 802.11b only Ndiswrapper N/A Using windows drivers in linux. It will never work with aircrack cx3110x (Nokia 770/800) Supports monitor mode (flaky) but not injection prism2/2.5 LinkFerret or aerosol Use STA firmware =1.5.6 (see )802.11b only.
See this regarding windows support. PrismGT only FullMAC cards works with aircrack on Linux prismGT (alternative) p54 untested, should get SoftMAC cards working (mac80211-based) Ralink or or Only rt2500, rt2570, rt61 and rt73 can inject and monitor. Also see Ralink chipset comments later on this pager for important concerns. Realtek 8180 802.11b only Realtek 8187L plus Realtek 8187B (2.6.27+) or TI ZyDAS 1201 802.11b only ZyDAS 1211 plus. The best chipset nowadays is Atheros. It is very well supported under Linux, and also under Windows.
Neither support any USB wireless devices. The latest madwifi-ng patch makes it possible to inject raw 802.11 packets in either in Managed and Monitor mode at arbitrary b/g speeds.
The is an excellent way to determine if a card is compatible with the aircrack-ng suite. Atheros, the chipset manufacturer, also has a web page that enables you to for products incorporating their designs.
The madwifi-ng driver is used for the atheros chipsets. This driver does not support any USB atheros devices. However, Atheros acquired Zydas which makes USB chipsets (zd1211 and zd1211b). Atheros has renamed this chipset to AR5007UG. The AR5007UG chipset is NOT supported by the madwifi-ng driver and is not a recommended chipset.
(Starting with 2.6.23, AR5007UG can be used with.) Another USB chipset, AR9170, also shows some promise, with a test driver (ar9170, mac80211-based) being available. Broadcom's “AirForce One” line of chipsets is recently catching up with Atheros in terms of Linux support. The new b43/b43legacy driver in 2.6.24 and up, when patched, can inject at speeds pretty much on par with Atheros. It also handles all attacks nicely, including fragmentation (although the underlying stack, requires a patch to inject fragments). Current development versions of the driver can actually reach speeds higher than those possible with Atheros, often up to 700 PPS and over. Multi-VAP operation/concurrent monitor and managed interfaces, similar to the one seen in Madwifi, is also implemented through the underlying mac80211 stack. Windows, on the other hand, is not supported, except for some older 802.11b-only chipsets.
Like Madwifi, b43 offers no support for Broadcom-based USB devices. For those, a separate driver called rndiswlan exists, which doesn't support monitor mode (and will never do so, as the chipset has no raw mode). Draft-N devices are also not yet supported.
Ralink makes some nice b/g chipsets, and has been very cooperative with the open-source community to release GPL drivers. Packet injection is now fully supported under Linux on PCI/CardBus RT2500 cards, and also works on USB RT2570 devices. However, these cards are very temperamental, hard to get working, and have a tendency to work for a while then stop working for no reason.
Furthermore, the RT2570 driver (such as that for the chipset inside the Linksys WUSB54Gv4) is currently unusable on big endian systems, such as the PowerPC. Cards with Ralink chipsets should not be your first choice. There is one exception with regards to the Ralink chipsets. This is the RT73 chipset.
There are excellent drivers with high injection rates for the RT73 chipset. Devices with the RT73 chipsets are recommended.
Card name Chipset Antenna Windows support Linux support Notes Asus WL-167g v2 Ralink RT73 Internal No Yes Airlink AWLL3026 Zydas zd1211 Internal No Yes USB info: 0ace:1211 See Notes 1 and 4. Alfa AWUS036E RTL8187L RP-SMA No Yes 80mW Alfa AWUS036H RTL8187L RP-SMA No Yes for a test of this adapter Alfa AWUS036S Ralink rt73 RP-SMA No Yes for a test of this adapter Alfa AWUS050NH Ralink RT2770F RP-SMA No Yes Digitus DN-7003GS RTL8187L Internal No Yes USB info: 0bda:8187 Realtek Semiconductor Corp. D-Link DWL-G122 B1 Ralink RT2570 Internal No Yes D-Link DWL-G122 C1 Ralink RT73 Internal No Yes D-Link WUA-1340 Ralink RT73 Internal No Yes Edimax EW-7318USg Hawking HWUG1 Ralink rt73 RP-SMA No Yes See Note 2 Linksys WUSB54G v4 Ralink rt2570 Internal or No Yes Linksys WUSB54GC v1 Ralink RT73 Internal No Yes See Note 5 Linksys WUSB54GC v2 RTL8187B Internal No Yes See Note 5 Netgear WG111 v1 PrismGT SoftMAC Internal airodump-ng Untested See note 3. Needs a recent GIT kernel from the wireless-testing branch. Netgear WG111 v2 RTL8187L Internal No Yes See note 3 TP-Link TL-WN321G Ralink RT73 Internal No Yes Trendnet TEW-429UB C1 Zydas zd1211b Internal No Yes USB info: 157e:300d ZyXEL AG-225H Zydas zd1211 Internal No Limited See Note 4 ZyXEL G-202 Zydas zd1211b Internal No Limited See Note 4 Notes:.
New laptops now normally come with ExpressCard slots. The current problem is that there are not a lot of ExpressCard wireless cards which are compatible with the aircrack-ng suite. However, ExpressCard to PCMCIA/Cardbus adapters have appeared in the market. The question has always been “Will these adapters work correctly with the aircrack-ng suite”.
There has been at least one success story. Read this for the details. If you try any adapters, please post your findings (good or bad) to the forum.
This is very important so that everyone can benefit from the experiences of others. Here is a list of adapters that people have reported as working successfully:.