Supported
The following wireless drivers have been tested or reported to work successfully with Reaver:
- ath9k
- rtl8187
- carl19170
- ipw2000
- rt2800pci
- rt73usb
Partially Supported
The following wireless drivers have had mixed success, and may or may not work depending on your wireless card (i.e., if you are having problems with these drivers/cards, consider trying a new card before submitting a trouble ticket):
- ath5k
- iwlagn
- rtl2800usb (using the latest compat-wireless drivers has fixed many user's problems, hint hint...)
- b43
Not Supported
The following wireless drivers/cards have been tested or reported to not work properly with Reaver:
- iwl4965
- RT3070L
- Netgear WG111v3
rtl8187L or rtl8187B
ipw2200 works (after switching in mon-mode with airmon-ng, iwconfig is not enough)
couldnt get rt73 to work. rt2501usb
With iwlagn I keep getting a lot of these:
A typical session:
Atheros AR2425 (driver ath5k) works for me.
I can confirm that with the ath5k driver works pretty well! i tryied also an usb wifi key (rt73usb) and it works, but it's a little slower then the atheros.
Someone tested the Alfa USB AWUS036NH with rt2x00usb drivers?
b43 works (Broadcom BCM4312 card)
Alfa AWUS050NH with rt2800usb driver seems to not work so far (Ubuntu 10.04 64-bit).
RaLink? RTL8187B works
for the tl-wn951n, i don't have it, but you MUST use monitor mode. if you have trouble to find the network, do, what i have done for my rt73usb: open two terminals and on one call ./reaver -i mon0 -b 74:EA:3A:E5:44:A4 -vv , on the other one airodump-ng mon0 --channel N. (change N with the channel number of the router.) it will help a lot!!
for the rt2x00usb i can say that probably works!
I am also expieriencing this issue with the ath9k driver....both with monitor mode and without. Ive also tried using the mon0 interface created without success.
reaver -i wlan0 -b 00:23:cd:de:32:4a
Reaver v1.2 WiFi? Protected Setup Attack Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
[-] Failed to initialize interface 'wlan0' [-] Failed to recover WPA key
DRIVER ath9k
I tried with mon0 created with airmon-ng
Was able to crack a DIR-655 using iwlagn driver on an Intel 5100 chip (OS: BT4). Originally wouldn't associate to AP when AP was restricted to 'n' (no abg) only.
@malering: your monitor mode interface is probably mon0, not wlan0.
@felipe: make sure you are running Reaver as root.
iwl3954 works. It's old, but still works.
ALFA AWUS036NEH usb longe range adapter works fine aka Ralink RT2870/3070 ~ rt2800usb
iwlagn driver works (Intel Wireless WiFi? Link 5300)
@Those who tested ath9k:
What did you do to get it working because for me it's still trying only one pin and gives me a timeout warning after every try. What I did:
Result: {{{[+] Waiting for beacon from 00:23:08:9E:E4:03 [+] Switching mon0 to channel 1 [+] Associated with 00:23:08:9E:E4:03 (ESSID: EasyBox?-9EE451) [+] Trying pin 08334572 [!] WARNING: Receive timeout occurred [+] Trying pin 08334572 [!] WARNING: Receive timeout occurred [+] Trying pin 08334572 [!] WARNING: Receive timeout occurred [+] Trying pin 08334572 [!] WARNING: Receive timeout occurred [+] Trying pin 08334572 [!] WARNING: Receive timeout occurred [+] Trying pin 08334572 [!] WARNING: Receive timeout occurred [+] 0.00% complete @ 0 seconds/attempt [+] Trying pin 08334572 [!] WARNING: Receive timeout occurred [+] Trying pin 08334572}}}
My WLAN Adaptor is: root@bt:~/Desktop/WPS_Hack# lspci | grep Network
05:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
zd1211rw and rt2800usb driver works
BT5 R1 x86 Alfa AWUS036NH w/compat-wireless-2011-12-30 drivers. I'm at 95% of my first test. Looks good so far!! Will update when finished.
All I have to say is: This tool is amazing!! Thanks yo everyone that worked on it.
[+] Key cracked in 21100 seconds [+] WPS PIN: '1234xxxx' [+] WPA PSK: 'zoomxxxx' [+] AP SSID: 'ZOOM'
According to my testing, Cohiba 3887 is unsupported.
TP-LINK WN-722N with ATHEROS AR9271 CHIP tested & working fine
RA-LINK (RT2870/3070) / RT2800 Chip Tested but NOT WORKING Correctly.
This chip in some ALFA & TENDA & Other
RT2870/RT3070L (Rokland N3 adapter) works great with the rt2x00 driver
hello all i'm getting the same thing as above... WARNING: Failed to associate with
why can someone tell me what i'm doing wrong?
RT2870/3070 USB stick not working. Goes in monitor mode but never selects the right channel. Same settings work with built-in Atheros AR9280.
Ralink 2570 USB stick using rt2500 USB driver is confirmed not to work.
I get a bunch of failed to associate with AP as several people posted in this thread and the one dedicated to that issue.
Intel Wireless Link 5100, driver iwlagn on Backtrack 5 R1
am i, the only one that think that "WARNING: Failed to associate with" means "maybe i'm to far from the router?!" ??
(i got my wpa password after 15000 secs..)
"Comment by mheijnem...@ictmbo.nl, Today (2 hours ago)
RT2870/3070 USB stick not working. Goes in monitor mode but never selects the right channel. Same settings work with built-in Atheros AR9280. "
I can confirm that it does infact work, as I have cracked several WPS pins with RT2870 / RT3070 chipset usb adapters. I did set the channel manually with airmon-zc tho. rt2800usb /rt2x00 driver
"Comment by der...@libero.it, Today (37 minutes ago) am i, the only one that think that "WARNING: Failed to associate with" means "maybe i'm to far from the router?!" ?? "
I'm too far from my own router now?? Nah your dismissal is too easy, remember life's a bitch :D I have 100 RXQ and about -50 PWR.
I had the failed to associate problem yesterday, i rebooted and never connected to a wireless network and immediately did the airodump command and and in another window started reaver using the -vv cmd.
I have been running mine for 24 hours now and it states it has worked for 47seconds 13.75% complete i get a lot of time outs
I am using a dell 820 with a dell wireless card BT5.1 and my wireless driver is not listed as "approved"
linksys wusb100v2 is RT2870 chipset with rt2800usb driver. It seems to be running fine with ubuntu 11.04 on vmware... although Im only 5% done and frequently getting "warning: receive timeout occurred"
Ath9K on netgear WNA1100 aka N150 seems working. Lots of timeouts and detecting AP rate limiting on a netgear router. Ubuntu 11.10 64bit
Update to above. Using an AP with better signal the Timeouts were eliminated.
However the Dlink-655 stops accepting WPS requests about 0.54% into the search with default settings. Reaver reports AP rate limiting from here on. Router log: primary: STA with MAC (00200074XXXX) WPS process closed
Rebooting router allows the process to restart until the same point. Hope i put this in the right place.
Regarding the failed to associate issue with iwlagn (the issue has been deleted but the following might be useful).
I was having these problems I described with my AP (Livebox 2) but when I tried on another (Bbox), it worked fine. Reaver did associate properly and started testing pins as expected. The AP rate limiting kicked in and lasted longer than 315 seconds (might be due to a Bbox specificity and not iwlagn), so I couldn't finish the attack.
It worked same way on another Bbox.
Reminder: Intel Wireless Link 5100, iwlagn driver, Backtrack 5 R1.
So I'm not so sure anymore that it's a driver incompatibility and not a problem Reaver against some AP.
If you add this feature http://code.google.com/p/reaver-wps/issues/detail?id=62 , you have not to care about HW support anymore.
I was troubled with debian 2.6.32 stock kernel; lots of timeouts or unable to associate. Upgraded to a newer kernel and my problems went away. I suggest you to use a recent kernel before saying 'reaver doesn't work with foo card'
OOooookay.
I'm using Reaver 1.3 r48, and now it does work on Livebox 2 with iwlagn driver. At least association works.
But then trying the right PIN gives no success, Reaver tries and tries again. IMO it's not the program's fault though, I suspect the Livebox to only have WPS enabled through Push Button. Looking into one of the beacons from that AP, the WPS registrar config has Push Button set to 1 and external and internal interfaces set to 0. That would mean Reaver 1.3 works properly though I'd need to test it on another AP, which I'm not able to considering the time necessary to complete an attack.
Previous version not working was Reaver 1.2 r35.
Not sure what could have changed related to the association issue and/or iwlagn?
tested with Sagem Fast sagem fast 3304, and it doesn't work
@Above: The Livebox 2 I'm talking above probably uses a Sagem F@st 3xxx router too. In which way does your test fail?
(Also, I've been told that what I found in the beacons about WPS registrar config is also found in beacons from routers against which Reaver succeeded. So Livebox might still be vulnerable; actually I've also been told that the new Walsh tool says Livebox IS vulnerable)
Tested with AR542x on ath5k: works ok Though only successfull when monitor mode was enabled with iwconfig instead of airmon.
I have one ath9k on Cardbus internal in the Notebook and one external ath9k on USB. The internal Cardbus works fine, the USB one not.
a follow up to my last post i have succeeded in my home hack project ringing in at 51 hours now im on to my neighbors with permission of course. i am then going to go back to mine and try to do it a little faster by ignoring the errors.
My final output was the SSID the WPA pass code and the correct WPS pin
Hi Craig,
Works well with the rt2500usb driver, here under ubuntu 10.10.
Thanks for this great security tool
With my testing i think the biggest problem to get reaver working right is the integration of the wireless adapter, i have 2 ath9k one mini pci working, one external not working, 2 Ralink RT2870/3070 USB not working, but with Aircack-ng every attack and ijection works with all of them.....
Hello, just tested Reaver on a Ralink 2570 USB (rt2500usb) and it worked great! I fed it an already known PIN and cracked it no problems. I do not know if the card would be stable in a full length session though...
RA-LINK RT2870 works fine now with reaver 1.3 using this order:
reaver -i mon0 -n -w -L -vv -b 00:11:22:33:44:55 -c 5
yo jellest, i was getting problems with using airmon-ng and not being able to associate, it seemed to change the wlan0 mac address (as seen through ifconfig) to a seemingly corrupt value.
I will try the iwconfig method you mentioned...did you use
sudo iwconfig wlan0 mode monitor?
Cheers
- dan
Hmm interesting...o.k so putting the card into monitor mode either with airmon-ng or iwconfig seems to create this discrepency in the wlan0 mac-field....
wlan0 Link encap:UNSPEC HWaddr 10-00-00-00-00-00-30-30-00-00-00-00-00-00-00-00
As opposed to a normally operating wlan0 config
wlan0 Link encap:Ethernet HWaddr 10:00:00:00:00:00
If the code in reaver draws on this field from ifconfig it could explain why its yielding somewhat strange results when viewed through airodump-ng and wireshark..and not associating. Would there be a way for the code in reaver to define only the usual first 12 hexdec values, perhaps its trying to grab the mac, but getting the extended address and is creating the strange results. Just a thought anyways...Im using a samsung n130 netbook, ubuntu 10.04, Network controller: Realtek Semiconductor Co., Ltd. Device 8192 (rev 01)
Had no problems injecting with aireplay-ng against wep targets in the past.
Wireless driver i'm using is
rtl819xE
what about RTL8192SE? $ lspci | grep Wireless 08:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10)
Alfa USB AWUS036NH mon0 Ralink RT2870/3070 rt2800usb - phy1?
root@IM-NOT-A-PC~# reaver -i mon0 -b 30:87:30:F0:BF:9B -vv
Reaver v1.3 WiFi? Protected Setup Attack Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
[+] Waiting for beacon from 30:87:30:F0:BF:9B [+] Switching mon0 to channel 1 [!] WARNING: Failed to associate with 30:87:30:F0:BF:9B (ESSID: 3Wireless-Modem-bf9b) [!] WARNING: Failed to associate with 30:87:30:F0:BF:9B (ESSID: 3Wireless-Modem-bf9b) [!] WARNING: Failed to associate with 30:87:30:F0:BF:9B (ESSID: 3Wireless-Modem-bf9b) [!] WARNING: Failed to associate with 30:87:30:F0:BF:9B (ESSID: 3Wireless-Modem-bf9b) [+] Associated with 30:87:30:F0:BF:9B (ESSID: 3Wireless-Modem-bf9b) [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Nothing done, nothing to save. [+] 0.00% complete @ 2012-01-08 17:04:57 (0 seconds/attempt) [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [!] WARNING: 10 failed connections in a row [+] Trying pin 73897026 [+] Nothing done, nothing to save. [+] 0.00% complete @ 2012-01-08 17:05:02 (0 seconds/attempt) [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Nothing done, nothing to save. [+] 0.00% complete @ 2012-01-08 17:05:07 (0 seconds/attempt) [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [!] WARNING: 10 failed connections in a row [+] Trying pin 73897026 [+] Nothing done, nothing to save. [+] 0.00% complete @ 2012-01-08 17:05:12 (0 seconds/attempt) [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Nothing done, nothing to save. [+] 0.00% complete @ 2012-01-08 17:05:17 (0 seconds/attempt) [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [!] WARNING: 10 failed connections in a row [+] Trying pin 73897026 [+] Nothing done, nothing to save. [+] 0.00% complete @ 2012-01-08 17:05:22 (0 seconds/attempt) [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Trying pin 73897026 [+] Nothing done, nothing to save. [+] 0.00% complete @ 2012-01-08 17:05:28 (0 seconds/attempt) [+] Trying pin 73897026 [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred ^C [+] Nothing done, nothing to save. [+] Session saved.
Make/Model: Alfa USB AWUS036NH Chipset: RT2870/3070 Driver: rt2800usb Working 1 attempt every 5 seconds, only on 1% I'll post if i crack
rt2500usb/rt2x00usb WORKS rndis_wlan DOES NOT WORK
Alfa USB AWUS036NH Chipset: RT2870/3070 Driver: rt2800usb works on bt5r1 in vmware.
Hey i have a Netgear WG111v3 and it works fine with reaver so you should probs put it into supported. managed to get passwords to two networks so far
@ thefeil, your WG111v3 has the rtl8187 chipset, and is listed ..
I have iwl4965 and keep getting failed to associate errors so +1 to confirm it not working. Any possible workarounds coming in the future or do I just need to buy a new card if I want it to work?
@arennh i think it is better to wait a while bevore you go out and buy staff, reaver is brand new and may be will work with other wlan chipset to in the future. I have 2 devices who are marked as working but only onw will do. So the best thing is to ask your friends if they have some USB Wlan adapters to play arround just for testing it is cheaper and you will see differences or not.
O.k feedback time.
Just compiled and ran reaver 1.4 (latest revision)
Wash works fine, like the way you dudes have given a few columns for various info. Wps locked e.t.c
Tried the program and i got one step further than i was at before. Reaver now associates (although only with -A and using aireplay-ng) and says sending eapol e.t.c. At this point it constantly times out.
Analysing the packet flow with wireshark yields some interesting results.
Running reaver with -A or not results in packets with odd to and from headers. I.e not from my mac-addy or to the bssid in question. It is definately reaver sending these packets. Source address begins with 34:00 and the destination address is 00:00:00_00 e.t.c. The destination address on its own looks like an invalid mac address. This could well explain why were not getting anywhere ;).
Upon running aireplay-ng and analysing the wireshark packet flow....immediately i notice an authentication packet from my mac to the source, and vice versa and this symbolises and accomplishes successful association.
After this and watching reaver once again it says trying pin......
At this point having successfully authenticated via aireplay, with the correct source and dest addresses, 34:00: etc suddenly tries to authenticate again (reaver) with 00:00:00_00,e.t.c what i assumed to be an invalid mac address which is strange because all of a sudden the target bssid starts churning out a shit load of deauthenticate packets to the 34:00 address. This continues for a while before 34:00 continues its normal association request behaviour.
Perhaps this may help someone debug a little.
- dan
Every time it does i notice an Association request from the invalid mac to the invalid source mac. I.e packets that will never return to one another.
This leads me to the reasonably informed conclusion that, some code somewhere in this program is not playing ball.
Strangely i seem to be getting further along with wpa_supplicant than with reaver.
I've managed to get wpa_supplicant to start the eapol transaction, by
Killing Network Manager & wpa_supplicant with this awesome little script i wrote ;) Note sarcasm and also theres no sort of error checking with this script, it works with my system but other people should be very wary....they could have different process names e.t.c which cause strange errors.
Before the scriptage though, you probably need to tweak a network configuration file, commenting out "respawn". Bloody spawn of the devil network manager is i swear. I can't remember exactly where...oh o.k found it..../etc/init/network-manager.conf Hashing out respawn, stops the bloody thing regenerating. By the way all this stuff, i'm not sure if its all neccesary, seems to work for me though ;).
You then need to edit the /etc/wpa_supplicant.conf file with the following
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP="your user name" update_config=1
And then the script....I just named it Net.sh...changed it to to executable via chmod, and then ran it.
#! /bin/bash
sudo kill -9 $(ps -A | grep Network | awk '{print $1}') && sleep 1
sudo kill -9 $(ps -A | grep wpa | awk '{print $1}') && sleep 1
echo 'Killing Network Manager & Wpa Supplicant' && sleep 1
echo "Done"
sudo ifconfig wlan0 up && sleep 1
sudo wpa_supplicant -Dwext -i wlan0 -c/etc/wpa_supplicant.conf -B
echo 'Bringing up Wpa Supplicant in interactive mode' && sleep 1
echo 'Done'
exit 0
o.k then you should be able to access wpa_cli as a non-root user...with wpa_cli....
says interactive mode or something....
Then i just typed
scan
scan_results
wps_pin "Your BSSID here"
reassociate.
Watching wireshark it then started initiating the procedure that has been mentioned by others, but has taken me hours and hours and hours to figure out up until now! (and haven't managed to get reaver to accomplish, feels like i'm learning it all au manuelle man =P. The target AP then relinquishes a metric f*ck ton of information. I'm guessing the way reaver then operates is to spot the difference in the acknowledgements between a successful wps pin attempt and a failed one.
Any thoughts from the reavers out there?
Thought i'd share my trials and tribulations anyways, might be of use to someone somewhere haha. ;)
RTL8187L is working with reaver???
YESS, read what it says it does not cost
Ipw2200 don't works. It works fine with walsh tool, but when you use reaver it always gives you the "Failed to associate" warning. The signal level in my tests is excelent. I did the airmon-ng start iface_name
It appears my card listed as
(with lspci), ie iwlagn-driven card, works perfectly fine. (And I'm on a thinkpad x200)stuck after association with ESSID,,,:(
TP-Link WN-7200ND Ver. 1.0 (Ralink RT2870/3070 - r2800usb) not work for me...
[+] Waiting for beacon from 1C:BD:B9:A7:29:98 [+] Switching mon0 to channel 6 [!] WARNING: Failed to associate with 1C:BD:B9:A7:29:98 (ESSID: dlink2) [!] WARNING: Failed to associate with 1C:BD:B9:A7:29:98 (ESSID: dlink2) ^C [+] Nothing done, nothing to save. [+] Session saved.
rtl8187L confirmed working.
driver r8187 not working, but driver rtl8187 working
WN-7200ND with v1.4 working but problems
WARNING: Receive timeout occurred WPS transaction failed (code: 0x03), re-trying last pin
Update: With v1.4 my TP-Link TL-WN7200ND has been cracked my D-Link DIR-600 Succesfully!!!
an update and i was dumbass.
Was using wps_pin instead of wps_reg.
Much more progress using wps_reg ;).
Seems a modified wpa_supplicant combined with an ean-8 calculator is the way forward for manual attempts at entering the wps pin. Just a bit time consuming haha.
Perhaps writing a simple bash script to advance the count-register via wpa_cli might be an alternate way forward, for people like me who can't seem to get the reaver working, but can get eap transactions going via wpa_supplicant.
I shall try some of the latest revisions though and see if things are working yet ;).
Keep up the good work dude.
Two problems I encountered
In one test, only received this error
WARNING: Failed to associate with
This was occurring because of AWUS036H, the antenna was an early version, and began to crack when the antenna interface mon0 crashed and disappeared.
Overwritten by another AWUS036H the same except that again, everything worked normally.
So if you're having this problem just check if the interface remains active when mon0 ends cracking, if not their active antenna that is crashing.
The second problem is that all APs is necessary to reach the 90 ~ 98% to finally get cracking.
There is no way to reverse the order of generation of PINs?
For if we reverse the order I would have cracked 10% in all APs that tested
For now it is just that.
Ipw2200 don't works........for me?
Atheros AR5212 with ath5k seems works fine.
To elaborate on thefeil and patricks' discussion:
I've also tried the WG111v3 and it works great. Confusingly though the chipset rtl8187 is listed as supported while the card is (erroneously) listed as not.
anyone give me a hand with this? using driver ath9k using a TL-WN822N.
When using reaver the only response i get from the router is either:
+] Waiting for beacon from 1C:AF:F7:69:70:54 [+] Switching mon0 to channel 2 [+] Switching mon0 to channel 3 [+] Switching mon0 to channel 4 [+] Switching mon0 to channel 5 [+] Switching mon0 to channel 6 [+] Switching mon0 to channel 7 [+] Switching mon0 to channel 8 [+] Switching mon0 to channel 9 [+] Switching mon0 to channel 10 [+] Switching mon0 to channel 11 [+] Switching mon0 to channel 12 [+] Switching mon0 to channel 13 [+] Switching mon0 to channel 14 [+] Switching mon0 to channel 1 [+] Switching mon0 to channel 2 (Cont Loop)
Or,
[+] Trying pin 37871802 [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: Receive timeout occurred [!] WARNING: 25 successive start failures [+] Trying pin 37871802 [!] WARNING: Receive timeout occurred (Cont Loop)
Iv tryed this on 10+ routers and its always the same, either one of those two loops.
Backtrack 5
What kind ath9k is it USB, mini PCI, PCMCIA ?
confirming that ath9k_htc works fine, Atheros AR9271 USB-adapter(TP-LINK TL-WN722N)
@ mikedunn i have the same TL-WN822N it does not work, but the mini pci who has the same chipset works, i do not know why.
RT2561/RT2561S/RT2661 supported. Works normal. SparkLAN WPIR-300 PCI Wireless B/G/Pre-N/Mimo
rtl2800usb - where can i download the drivers and install them i am a utter nub
After your card is supported here are some ideas of Antenna tuning Woktenna, doubble Yagi Uda or Parabolic with 24 dBi.....
http://www.patrickschlegel.ch/wifi.php
@patricks using USB
@ mikedunn I have almost same output with that TP Link so i stoped experimenting with because the internal mini pci was working even with the same chip like i wrote 5 comments up. And i don't really know where the difference is. But what i know is that Backtracks wicd manager does also not connect everytime and thats sucks too...
@patricks ah ok thanks, any recommendations on a different device, pref a usb which has been tested as it shows that just cause the driver is shown as supported not every device will work.
Mike: I use a TL-WN822N v3 (ath9k_htc driver) and it does work. Possible solutions: airmon-ng check kill download, patch, compile & install the latest compat-wireless make sure you use the 1.3 firmware for your device (suppisingly it's a v3/ath9k_htc)
@jo is this really a v3 i did even not found on TP Link's homepage there is only v2 like mine..
Sorry, typo. The TL-WN822N v2's chipset (AR7010+AR9287) is identical to TL-WN821N v3. I have the TL-WN821N v3.
trying iwlwifi wich is the new intel driver for centrino chipsets 6200 and 6300 (in old kernels the iwlagn driver was used, this one is now reserved for old chipsets)
No luck with this one. i tried many ap without success so far
@Jo this is great news thanks, iv tryed it and it seems alot more responive but still failing every time, patch ath9k_htc and unloaded ath9k but it still comes up saying its using
"wlan0 Atheros AR9287 ath9k - phy0?
How do i change this to htc
Also its the firmware update weezy or am i missing something? If you could possible send a link would be great.
I believe that the 'carl19170' driver mentioned at the top of this page is a typo for 'carl9170'.
noob here how do i find/install the rtl2800usb latest drivers?
Thanks !
I formatted and installed bt5r1, and now do not want to wash work?
I was with BT5 and wash functioned normally, but after a reformat and reinstall everything wash not think any more ap.
Card driver rtl8187 Card monitor mode OK inj OK
Everything is running fine, except the wash.
In any version of recover, 1.3 - 1.4 does not work.
Someone knows I might be happening?
thx
can you make it far faster?, how about for it to list vulnerable clients, that is needed
@leacocks - You really dont have a clue about how reaver functions, and what the WPS vulnerability is, do you ? Reaver has no use in listing to clients. Reaver is an active attack towards the vulnerability that exist in most routers WPS implementation. Try to read up on what the software does, what the WPS vulnerability involves and how it is is implemented in the Reaver tool.
RTL8187 B?? WORKS?
What do I need to do to wash work?
Need some updated lib? some more configuration?
BT5 newly installed, simply does not wash, and everything else is OK
I tried the chipset and runs rtl8188ru with rtl8192cu driver, you can add to the list of supported wireless drivers.
Intel Pro 3945 ABG works fine with Reaver no problems tested on few routers
AWUS036NHR works? is rtl8188ru
I can confirm it's working in my TP-Link TL-WN721N (ath9k_htc AR9271 802.11n) Linux Mint LMDE 32bit Kernel 3.0.0-1-686-pae #1 Compat Wireless Drivers with firmware 1.3
ubuntu 10.04 powerpc , wireless driver rtl 8187 shows only channel hoping....fixing channel results in "waiting for beacon..."
install the awus036nhr with compat-wireless
Can anyone recommend a cheap usb wireless adapter with a compatible chipset for reaver? Please list a link to the amazon page and the chipset if possible. Thanks!
Ubuntu 11.10, TP-LINK TL-WN722N v1.8 (AR9271) -> Supported
Ubuntu 11.10@Eee PC 1215B with BCM4313@brcmsmac (native Ubuntu driver) => WORKED! (note: I had to run wash with "-C" to be able to scan)
Ubuntu 11.10@MBP8.1 with BCM4331@b43 (self-compiled from compat-wireless) => WORKED! (I was not able to scan with wash at all but wpa_cli did the job instead)
Alfa AWUS036NH (rt2800usb) crew, what version (date) of the compat-wireless drivers are you having the best luck with for use with Reaver? What patches do you apply if any. I'm not having any luck with drivers from this month on. They wont compile correctly. I'm compiling compat-wireless-2012-01-24 right now. I'v tried most of them and I think these ones worked the best. I only apply the channel-negative-one-maxim.patch should I be applying any others?
Intel PRO/Wireless 3945ABG working great for me too. No problems whatsoever.
Tested on Debian Squeeze (6.0.3) with Debian 2.6.32-38 kernel build for AMD64.
RT73usb with Reaver 1.4 not working for me. Failure to authenticate, despite good signal strength. Anyone else have similar problem?
Ralink 2561 PCI rt61pci Does not work with Reaver
rt2800usb Works like a charm
I'm also using Ubuntu 11.10 I did not need to install any driver for rt2800usb
Reaver 1.4 on VirtualBox? 4.1.8 running Ubuntu 11.10 32-bit. ASUS USB-N13 USB adapter using the native rt2800usb driver built into Ubuntu. Used --channel and --no-nacks switches. WORKS! Cracked one in 5 hours.
bonjour a tous est ce tp-link 222 est compatible avec reaver
You dont need to post the RT3070L driver as "not supported" There is just an RT3070sta driver that fly out of the kernel. The opensource driver rt2800usb supports since many kernel versions the RT3070L chipset. I made it work together with the main developers of the rt2800usb driver ;)
Worked fine for me using iwl4965 drivers
[maci@T61 ~]$ lspci |grep 49 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Kedron? Network Connection (rev 61)
[maci@T61 ~]$ uname -a Linux T61 3.2.9-1-ARCH #1 SMP PREEMPT Thu Mar 1 09:31:13 CET 2012 x86_64 Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz GenuineIntel? GNU/Linux
all i did was airmon-ng start wlan0 and then ran reaver. no problems. took about 7 hours to recover the password.
b43 do not works for Broadcom BCM4322 card... 04:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
rtl819xSE not work? sudo airmon-ng start wlan0 #not create mon0 Found 4 processes that could cause trouble. If airodump-ng, aireplay-ng or airtun-ng stops working after a short period of time, you may want to kill (some of) them!
PID Name 1958 NetworkManager? 1969 avahi-daemon 1970 avahi-daemon 1976 wpa_supplicant
Interface Chipset Driver
wlan0 Unknown rtl819xSE (monitor mode enabled) reaver -i wlan0 -b MAC -v
Reaver v1.4 WiFi? Protected Setup Attack Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
[-] Failed to initialize interface 'wlan0' [-] Failed to recover WPA key
Netgear WNA1100 works fine, it has no antenna so don't expect to break an AP 3 houses away with it.
I DON'T KNOW WHY EXACTLY THIS ERROR APPEARS "WARNING FAILED TO ASSOCIATE WITH "bssid" BUT I KNOW WHEN YOU CAN MAKE THE ATTACK.
1. YOU MUST BE PATIENT AND TO BE NEAR THE ROUTER
2. DO THIS STEP ON WINDOWS BEFORE GOING ON BT5...TRY TO CONNECT YOURSELF ON THE AP WITH WPA/WPA2 AND IF YOU SEE THE SIGN THAT SHOWS YOU TO CONNECT BY PUSHING A BUTTON ON A ROUTER IT MEANS YOU'RE ON TO MAKE THE ATTACK!!!!!
3.GO ON BT5 AND DO THE STEPS YOU NEED TO DO TO GET THE WPS PIN!!
IF THE ERROR PERSIST IT MEANS THE WPS PIN LOCK IS TEMPORALLY UNAVAILABLE SO WAIT IT COULD TAKES DAYS I HAD TO WAIT 2 DAYS TO GET ONE!!!!
THANK YOU!!!
i have a problem with rtl 8187 driver...i use ubuntu 12.04 and i patched kernel so airmon works fine and don't have problem with negative channel...but...when i start reaver i get this hattrick@Series:~$ sudo reaver -i mon0 -b 00:18:4D:38:AB:FD --auto -c 10 -vv
Reaver v1.4 WiFi? Protected Setup Attack Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
[+] Switching mon0 to channel 10 [+] Waiting for beacon from 00:18:4D:38:AB:FD [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR) [!] WARNING: Failed to associate with 00:18:4D:38:AB:FD (ESSID: NETGEAR)
iwl4965 work for me fine, maybe sometimes get stuck bbut it's working. On Ubuntu 12.04
iwl4965 works fine for me, maybe sometimes get stuck but it's working. On Ubuntu 12.04
iwl4965 works fine for me, maybe sometimes get stuck but it's working. On Ubuntu 12.04
iwl4965 works for me as well only if I run the wpa_supplicant command with the proper config file for the autorization. Same thing needed to run an aireplay-ng deauth. I am running stock modules that came with my distro. I do notice it getting disconnected as well. I just have to restart the running wpa_supplicant command (wpa_supplicant -c wpa_supplicant.conf -Dwext -iwlan0 -dd) and it connects back up and proceeds to the next key.
For my fellow Intel 4965 owners if you need to learn more about that process you can find the process online with a search for Intel 4965+wpa_supplicant.conf+aircrack-ng. Or if you have questions feel free to ask.
Arch-Linux 64-Bit: Stock distro drivers for iwl4965.