phoenixbai / reaver-wps

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

Very strange comportment of reaver on 2 PCs #202

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hello,

I think I have big problem but I don't know which.

I have one PC with VirtualBox and Backtrack 5 R1. On this virtual machine, 
reaver founds PIN code and WPA2 Key, successfully in 100% of cases, which is 
incredible!

I have 3 others PCs, and reaver had never found PIN code and WPA key.

So, I decided to make a full copy of VirtualBox VM on another laptop. I put the 
SAME Alfa AWUS036h, so this is exactly 100% SAME config as original PC where 
reaver function correctly.

On this laptop, it's same problem, reaver cannot found PIN or WPA key !!!! 
That's IN-CRE-DI-BLE....
I think I'll become crazy, I don't know what's the problem.

Commands are exactly the same on original PC and other laptop :
reaver -i mon0 -b 00:25:9C:CA:AC:8A -vv

- On original laptop where reaver is OK, I have some "WPS transaction failed 
(code: 0x02)" about 4 times per minutes.
- On copy laptop, I have the sequence, but very quickly (after 3 minutes), all 
is down, it begins by this error and continue forever :
[+] Trying pin 00405676
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] 0.47% complete @ 2012-01-30 10:20:18 (3 seconds/pin)
[+] Trying pin 00415675
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 00415675
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 00415675
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 00415675
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
^C
[+] Session saved.

I can see when 0x03 error appears, this is the end, I have timeout after 
sending identity response, and 0x02 avec sending NACK forever..

Help !

Original issue reported on code.google.com by thecle...@free.fr on 30 Jan 2012 at 9:37

GoogleCodeExporter commented 9 years ago
#wps transaction failed (code: 0x02), re-trying last pin
#wps transaction failed (code: 0x03), re-trying last pin

I've experienced the same issues using an Alfa rtl8187. I've found the solution 
to the problem is to play with the "-d" flag.

Start at "-d 15" or higher until you stop receiving the (code: 0x02) (code: 
0x03) errors. Then work your way down. Each router I've tested likes a 
different value. 

I was also using the "--no-nacks" argument.

Original comment by cryptom...@gmail.com on 4 Feb 2012 at 6:07

GoogleCodeExporter commented 9 years ago
Hello,

- What is strange, it's OK with other PC with same alfa without -d option (2 
pin/second)... So I will try with -d 15 but I'm not sure it will be OK.
- When I use --no-nacks option, I always have NACKS appears on the verbose 
mode, is this option works ?
- I've seen something strange... If I power off my WRT320N during 4~5 days and 
try to use Reaver after, it can go up to 20% without problem ! When it have 
timeouts, I power off/on router and re-launch Reaver, and at this time it 
cannot go up more than 1% !!!

Original comment by thecle...@free.fr on 5 Feb 2012 at 12:12

GoogleCodeExporter commented 9 years ago
I've updated WRT320N firmware from 1.03 to last 1.05.
Result : Reaver without any parameter, 100% success.

Wanna crack WPS ? Flash your router to last FW version ! lol

Original comment by thecle...@free.fr on 5 Feb 2012 at 9:47