Alpha AWUS036NH card problem with reaver

Hi to all,

I'm a long term user of Backtrack: for about 3 years I was using the 5.x version on my computer combined with Alpha AWUS036NH network card.

Few days ago I decided to upgrade to the new Kali 1.1 to try the new reaver with pixiedust attack.

So the probem started: my card is recognized out of the box with the driver "rt2800usb". Airmon seems to work, airodump and wash seem to work too, showing networks, access points and so on.

But when I start reaver, without the "k" parameter, it can't test the pins successfully, continuing on the pin 12345678 forever.

Using back the old backtrack, reaver was working fine.

My laptop is an Flybook Dialogue V33i with an old celeron CPU. To use Kali, it was necessary to recompile it for non PAE computer.

Obiusly the system is up to date (22 of may, 2015).

This is the output of airmon

Code:

---

root@kali:~# airmon-ng start wlan1
Found 3 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
 2197 NetworkManager
 2916 wpa_supplicant
 3447 dhclient

PHY        Interface        Driver                Chipset

phy1        wlan1                rt2800usb        Ralink Technology, Corp. RT2870/RT3070
                (mac80211 monitor mode vif enabled for [phy1]wlan1 on [phy1]wlan1mon)
                (mac80211 station mode vif disabled for [phy1]wlan1)

---

This is the output of airodump (BSSID and ESSID were modified by me)

Code:

---

root@kali:~# airodump-ng wlan1mon --wps

CH  6 ][ Elapsed: 42 s ][ 2015-05-23 13:18                                       
                                                                                                             
 BSSID              PWR  Beacons    #Data, #/s  CH  MB  ENC  CIPHER AUTH WPS          ESSID
                                                                                                             
 E2:21:22:00:00:00  -1        3        0    0  11  11  OPN                            name1             
 78:54:2E:00:00:00  -24      17        0    0  7  54e  WPA  CCMP  PSK  1.0 DISP,PBC  name1             
 C4:A8:1D:00:00:00  -51        9        0    0  6  54e  WPA  CCMP  PSK  1.0 DISP,PBC  name1         
 FA:D1:11:00:00:00  -53      13        0    0  7  54e  WPA  CCMP  PSK                name1           
 78:54:2E:00:00:00  -54      24      112    0  11  54e  WPA2 CCMP  PSK  1.0 DISP,PBC  name1                 
 DE:71:44:00:00:00  -54      16        0    0  6  54e  WPA2 CCMP  PSK  1.0          name1
 1C:7E:E5:00:00:00  -58      13      344    7  6  54e. WPA2 CCMP  PSK                name1           
 EC:43:F6:00:00:00  -58      24        3    0  11  54e  WPA2 CCMP  PSK  1.0 LAB,DISP  name1                 
 00:17:C5:00:00:00  -61        2        0    0  5  54e  WPA  TKIP  PSK                name1         
 FC:B0:C4:00:00:00  -62        5        0    0  1  54e. WPA2 CCMP  PSK  1.0          name1               
 00:17:C5:00:00:00  -62        2        0    0  5  54e  WPA  TKIP  PSK                name1           
 A8:9D:D2:00:00:00  -64      17        4    0  1  54e. WPA2 CCMP  PSK  1.0 LAB      name1       
 78:44:76:00:00:00  -64      10        2    0  6  54  OPN                            name1           
 FC:B0:C4:00:00:00  -64      20        0    0  9  54e  WPA2 CCMP  PSK  1.0          name1                   
 78:54:2E:00:00:00  -65        3        1    0  1  54e. WPA  CCMP  PSK                name1               
 A8:A6:68:00:00:00  -66        9        0    0  1  54e  WPA2 CCMP  PSK                name1         
 C8:91:F9:00:00:00  -66      12      52    0  1  54e  WPA2 CCMP  PSK  1.0 LAB      name1                   
 78:44:76:00:00:00  -66      17        1    0  11  54  OPN                            name1           
 FC:B0:C4:00:00:00  -67      10        3    0  1  54e  WPA2 CCMP  PSK  1.0 LAB,PBC  name1                   
 C8:BE:19:00:00:00  -67        0        0    0  9  54e  WPA  CCMP  PSK  1.0 DISP,PBC  name1

---

Thanks to all!

Did you find more on this ? I have some similar issues with same card.

I wish [email protected] would chime in on this one.

I'm experiencing the same issue. Reaver always stuck on re-trying the same PIN.

My pertinents:
Linux kali ver:[/B] 3.14-kali1-686-pae #1 SMP Debian 3.14.5-1kali1 (2014-06-07) i686 GNU/Linux
WIFI NIC: ALFA AWUS036NH
Drivers info using LSMOD to retreive:
rt2800usb 21813 0
rt2x00usb 17426 1 rt2800usb
rt2800lib 72679 1 rt2800usb
rt2x00lib 41387 3 rt2x00usb,rt2800lib,rt2800usb
crc_ccitt 12331 1 rt2800lib
Power level to my AP: -42 (is this sufficient to rule it out as probable cause?)

I've seen much oldter threads where many have experienced this before with similar or same type of Alfa cards, thing is, they all suggest workarounds based on changing or adding swtiches to the reaver command that, I believe, only weigh the execution of this down that much more since a very lightweight simple execution of the reaver command with minimal switches would be more elegant and less involved. In either case, nothing seems to resolve the issue where Reaver re-tries the same PIN at every following attempt after the first failure attempt.

Thanks for any help that could progress this issue in the right direction!

Update:

Tested with kali 2.0: still the same problem!