AWUS051NH Raspberry Pi No injection?

[Dosk3n]

Afternoon guys hope you can help.

I have an older ALFA wifi card, 2g only and this works great but wanted to get a new card for my new set up on my Raspberry pi.
So I now have an AWUS051NH which I am having a nightmare with as I cant seem to get injection working.

Any time I run Reaver on my access point (Already cracked with other card) I keep getting the same errors over and over again:

[!] WPS transaction failed (code: 0x03), re-trying last pin
[!] WARNING: Failed to associate with XX:XX:X:XX:E9:BC (ESSID: TALKTALKXXXXXX)

I have ran airmon-ng to get the current driver listed:

root@kali:~# airmon-ng 

PHY	Interface	Driver		Chipset

phy0	wlan0		??????		Broadcom 43430
phy1	wlan1mon	rt2800usb	Ralink Technology, Corp. RT3572

and lsusb to confirm the chip:

root@kali:~# lsusb
Bus 001 Device 004: ID 148f:3572 Ralink Technology, Corp. RT3572 Wireless Adapter
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

airodump-ng runs fine and shows all access points in the area but any time I run reaver I keep getting [!] WPS transaction failed (code: 0x03), re-trying last pin and [!] WARNING: Failed to associate with xx:xx:xx:5B:E9:BC (ESSID: TALKTALKxxxxxx).

This router does have WPS on as I have cracked it with the other ALFA card I have both with regular reaver attack and it is also vulnrable to the pixie dust attack however with this card neither of these will work due to these errors.

Hope you can help

-D

[Davelister]

You have a similar problem to everyone else with the card and Kali.

You have the V2 version of the adapter which uses the RT3572 chipset, but Kali has the V1 version driver rt2800usb for the RT2870 chipset.

I am currently searching for the same answer. I am running the veyron armhf image of kali, I assume you are also using some armhf version.

This makes it exceptionally diffcult just to head over to Realtek, download and compile the drivers.

I am awaiting help with this also. If I hear something before you, I'll come back here and hit you with their suggestions.

At this moment in time I don't know how to fix this.

Do me a favour.

Take you card down => ifconfig <yourcardhere wlan0/1/2/etc> down
Try to alter the mac => macchanger -r <yourcardhere wlan0/1/2/etc>

To bring your card back up afterwards:

ifconfig <yourcardhere wlan0/1/2/etc> up

Do it let you change the mac? Or does it tell you your interface is still up and therefore it can't change the mac address? Does the blue LED remain flashing even though the card is supposed to be down?

[Dosk3n]

For me its not a major rush or inconvenience since my other card is supported but more of an annoyance and something I wont get off my mind until its working.

However I have did as you asked and it seems to have worked ok. The light on my card did stay on though even though I had brought the interface down.



Its must certainly be a driver issue I just have no idea where to go from here. Searched all over and seems theres no solution at the moment.

The card did come with a drivers disk that has linux drivers on but they wont compile so Im assuming this is due to it being on the pi?

[Dosk3n]

UPDATE:

I have started running reaver with the no nacks tag

reaver -i wlan2mon -b BSSIDGOESHERE -vv --no-nacks -c 11

And this now starts to progress the pin change in reaver. Is this a real pin increase? What I mean by this is that is reaver actually getting the correct response from the router to say the pin was incorrect and try another one? The router hits its failed attempts limit and locks so I am assuming the wifi card is communicating with the router correctly.

Also previously I was running aireplay with an injection test and it failed. Today I got this:

root@kali:~# aireplay-ng -9 wlan2mon
06:25:45  Trying broadcast probe requests...
06:25:45  Injection is working!
06:25:46  Found 10 APs

06:25:46  Trying directed probe requests...
06:25:46  XXXXXXXXXX - channel: 11 - 'BTHubXXXX'
06:25:47  Ping (min/avg/max): 1.163ms/13.187ms/36.924ms Power: -80.23
06:25:47  26/30:  86%

06:25:47  XXXXXXXXXX - channel: 11 - 'SKY8XXXX'
06:25:48  Ping (min/avg/max): 2.672ms/10.443ms/20.810ms Power: -64.80
06:25:48  30/30: 100%

06:25:48  XXXXXXXXXX - channel: 11 - 'BTXXXXX'
06:25:49  Ping (min/avg/max): 1.254ms/9.604ms/70.840ms Power: -80.92
06:25:49  26/30:  86%

So i am going to go ahead and assuming its working slightly.

The difference between todays test and the other day is I changed to a closer router for testing.

It seems that this router is very hit and miss and until we can get the correct driver installed its going to stay that way. Shame as it looked like this used to be a great card.



PIXIE PROBLEM!

Now using no nacks allows me to run pixie but freezes at the reaver test because it doesnt use no nacks. Even if I run the command with no nacks it freezes.

[Pixie-Dust]  
[Pixie-Dust]   Pixiewps 1.2
[Pixie-Dust]  
[Pixie-Dust][*] Mode:       3 (RTL819x)
[Pixie-Dust][*] PSK1:       15:e2:8b:7e:7f:29:fc:dc:4xxxxxxxxxxxxxxxxxx
[Pixie-Dust][*] PSK2:       c0:d3:f1:c0:a7:40:eb:c7:6exxxxxxxxxxxxxxxxxx
[Pixie-Dust][*] E-S1:       6e:18:f6:05:96:94:90:53:xxxxxxxxxxxxxxxxxxx
[Pixie-Dust][*] E-S2:       6e:18:f6:05:96:9xxxxxxxxxxxxxxxxxxxxxxxx
[Pixie-Dust]   [+] WPS pin:    1672xxxx
[Pixie-Dust]  
[Pixie-Dust][*] Time taken: 0 s 120 ms
[Pixie-Dust]  
Running reaver with the correct pin, wait ...
Cmd : reaver -i wlan2mon -b xxxxxxxxxxxxxx -c 1 -s y -vv -p 1672xxxx

[Reaver Test] BSSID: xxxxxxxxxxxxx
[Reaver Test] Channel: 1

[Davelister]

Just to confirm, did it actually change the mac?

Also according to debian, the rt2800usb is the CORRECT driver for the RT3572 chipset =>

https://wiki.debian.org/rt2800usb

Also FYI the RT3572 is EOL =>

https://forums.kali.org/showthread.p...ed-replacement

[Dosk3n]

Yes I can confirm the MAC did change.

I think for now then the version 2 of this card should be classed as not working for Kali as some parts work and some dont. I can change mac, I can even get a WPS pin with Reaver using --no-nacks but can not use that pin to get the password since it just hangs at that point since it cant be done with no nacks and without that option it fails to communicate with the router. For regular use the card works though.