search

h-eibot / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

Not working on SheevaPlug (ARM Kirkwood 88F6281): WPS transaction failed (code: 0x04) #320

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Hello,
I'm having issues with reaver in SheevaPlug. Before you ask, the aircrack-ng 
suite is installed and everything is working fine. 
My wireless card is an Alfa awus036h (RTL8187L).

I'm able to crack the AP with my computer, backtrack 5 and the same wireless 
card. So this issue must be related to the platform.

I saw a bunch of warning upon compilation but since I'm not an expert I can 
really tell if they interfere with reaver or not. 
You can read my installation log here: http://pastebin.com/Z2PaZ2E5

0. What version of Reaver are you using?

Version 1.4.

1. What operating system are you using (Linux is the only supported OS)?

Debian, kernel 3.3.7 (sheeva.with-linux.com version).

2. Is your wireless card in monitor mode (yes/no)?

Yes, and injection also works fine.

3. What is the signal strength of the Access Point you are trying to crack?

The AP is in my desk.

4. What is the manufacturer and model # of the device you are trying to
crack?

Alfa R36.

5. What is the entire command line string you are supplying to reaver?

reaver -i mon0 -b XX:XX:XX:XX:XX:XX -S -vv

6. Please describe what you think the issue is.

Platform related issues / compilation problem I'm not seeing.
You can read my installation log here: http://pastebin.com/Z2PaZ2E5

7. Paste the output from Reaver below.

[+] Waiting for beacon from XX:XX:XX:XX:XX:XX
[+] Switching mon0 to channel 6
[+] Associated with XX:XX:XX:XX:XX:XX (ESSID: TestWiFi)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin

And keeps looping on the error.

Original issue reported on code.google.com by tc...@iklive.org on 30 May 2012 at 10:20

GoogleCodeExporter commented 8 years ago 
Someone?

Original comment by tc...@iklive.org on 12 Jun 2012 at 7:23

GoogleCodeExporter commented 8 years ago 
I'm having the same issue here on a pogoplug on wheezy debian.

I suppose it's some problem dealing with the armel architecture. Let's hope 
someone notices and knows how to solve it.

Original comment by bseo...@gmail.com on 26 Aug 2012 at 7:35

GoogleCodeExporter commented 8 years ago 
Hey! I'm running reaver-wps on a raspberry pi (also ARM) and it works fine... I 
think the issue is that the Sheevaplug CPU is an ARM compatible old CPU not a 
real ARM from nowadays... 

Anyway, if you try it on raspberry pi don't forget to get a powered USB Hub to 
power your Alfa cards, because the USB ports on the raspberry pi are actually 
limited to 140mA.

Original comment by tc...@iklive.org on 26 Aug 2012 at 8:53

GoogleCodeExporter commented 8 years ago 
I have a Raspberry Pi and reaver does not work. It just keeps going though the 
channels and never gets a beacon. Exact same command on x86 machine with exact 
same USB wireless card cracks the pin in a couple hours.

Original comment by jedgai...@gmail.com on 12 Jul 2013 at 10:00