1.4 reaver issue with AWUS036H.

[GoogleCodeExporter]

I have gone through just about ever post out there about wireless not working 
after 2 minutes etc. Here are my findings from the past week of fiddling around 
with this.
I have installed two AWUS036H usb cards on the same laptop running backtrack 5 
r3 (i have also tested this with Kali linux 1.0.7 with same results) Hard drive 
and live cd. all the findings are exactly the same.
all of the operating systems have 1.4 reaver on them.
My problem is, when i start using reaver 1.4 within couple minutes my awus036h 
card rtl8781L along with all the wireless cards stop working. I know its 
difficult to imagine. The only real work around i have found is when reaver 
comes up with error Warning! Received timeout occured (then reaver hangs and 
stops working) is to unplug the card from usb, plug it back in and put it in 
monitor mode then continue the attack until it locks up again.
Things that i have tried:
1) rule out all software conflicts, did airmon-ng start (wlan0 and wlan1 cards 
which are both my awus036h cards).. kill all possible conflicts.. run 
airodump-ng on one of the cards while keeping the other card on another 
terminal window so i have two terminals running airdump while on one of those 
runs reaver as well. when reaver locks up, both of the monitored interfaces go 
down and by going down i mean all input like packet, data, and all that goes 
flat dead. there is no software conflict. i have ran iwconfig before and after 
reaver takes a shit and no configuration has been changed with interfaces. 
nothing got switched between managed or monitored modes, there is plenty of 
power to both cards, i have used the Y adapter cables to input additional power 
to the cards so thats not the issue as well. I should also mention i have an 
internal wireless card that is intel something.. which still continued to run 
airdump after reaver has taken out my awus036h card driver. (while both of the 
cards are seased, i switched reaver to my intel wireless card mon3 interface 
(actual adapter is wlan3) it locked that up too! within 2 mins use. I have 
pretty much done all i can but it seems reaver 1.4 triggers some kind of glitch 
when used with awus036h card which brings down all the wireless interfaces no 
matter that they are if you point reaver to the divice.. it will bring it down 
until you physically unplug it and put it back in OR reboot. then you have 
another 1-2 minutes before it locks up again. I have not had any issues using 
awus036hA the aerthos chipset that keeps running just fine. but rtl8717l is 
another story. oh and also i have completely uninstalled dhcp client, disabled 
network monitor, suplements, configured /network/interface so none of any 
software causes any kind of conflit or even looks at the wireless interfaces. 
is there anything else i've missed? and no i have not been able to find an 
actual solution to this problem although i have read a lot of posts and 
problems may sound similar but not in their entirety. yes i have tried every 
single one of the suggested fixes and ran out of options but to stock up on new 
wireless cards. any suggestions? 

Original issue reported on code.google.com by berezini...@gmail.com on 9 Jul 2014 at 9:50

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Try this fix: https://code.google.com/p/reaver-wps/issues/detail?id=630#c41
i know this fix is for problem of "Can't associate reaver with "newer" kernel 
versions"
but try...

Original comment by deltomaf...@gmail.com on 13 Jul 2014 at 11:43

[GoogleCodeExporter]

Turn power management off.

Original comment by ancutabu...@gmail.com on 8 Feb 2015 at 1:23