[!] WARNING: Last message not processed properly, reverting state to previous message

[GoogleCodeExporter]

What steps will reproduce the problem?

My wireless card:

TP-LINK TL-WN422G

Using Backtrack 5

What is the expected output? What do you see instead?

root@bt:~/reaver-1.3/src# ./reaver -i mon0 -b 00:19:7X:XX:XX:XX -vv

Reaver v1.3 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>
[?] Restore previous session? [n/Y] n
[+] Waiting for beacon from 00:19:7X:XX:XX:XX
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 1
[+] Associated with 00:19:7X:XX:XX:XX (ESSID: ADSL****)
[+] Trying pin 62449380
[!] WARNING: Receive timeout occurred
[+] Trying pin 75409388
[!] WARNING: Receive timeout occurred
[+] Trying pin 75409388
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[+] Trying pin 61249387
[+] Trying pin 23569386
[+] Trying pin 49579383
[+] 0.05% complete @ 2012-01-04 02:54:23 (7 seconds/attempt)
[+] Trying pin 16389380
[+] Trying pin 11509387
[+] Trying pin 63129380
[+] Trying pin 83249389
[+] Trying pin 54019386
[+] 0.09% complete @ 2012-01-04 02:54:42 (5 seconds/attempt)
[+] Trying pin 78479388
[+] Trying pin 49939385
[+] Trying pin 24139380
[+] Trying pin 43009381
[+] Trying pin 95559384
[+] 0.14% complete @ 2012-01-04 02:55:01 (4 seconds/attempt)
[+] Trying pin 35039389
[+] Trying pin 42599388
[+] Trying pin 60479389
[+] Trying pin 30519381
[+] Trying pin 68219383
[+] 0.18% complete @ 2012-01-04 02:55:20 (4 seconds/attempt)
[+] Trying pin 41919385
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying

What version of the product are you using? On what operating system?

Reaver 1.3.

Please provide any additional information below.

Please i need your Help :'(

Original issue reported on code.google.com by Smart...@gmail.com on 6 Jan 2012 at 10:56

[GoogleCodeExporter]

It looks like the AP is locking WPS; depending on the AP this could be a 
temporary or a permanent lock. Reaver 1.3 has a known bug where it does not 
recognize when the AP has unlocked WPS, try using the SVN code.

Original comment by cheff...@tacnetsol.com on 6 Jan 2012 at 12:57

[GoogleCodeExporter]

i have same problem last three days since i started to use reaver code. it 
works fine, somtimes it comes to 40%, sometimes to 85%... but always finish 
with same warning:
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
that repeats all time after it shows first time.
i use Alfa AWUS036H 1000mW with rtl8187 driver in Backtrack 5.

is that bug where it does not recognize when the AP has unlocked WPS can(will) 
be fixed?
what do you mean when you say to try using the SVN code?

Original comment by virtualw...@gmail.com on 7 Jan 2012 at 9:45

[GoogleCodeExporter]

The bug has already been fixed and verified. The next release will include this 
fix. If you don't want to wait for the next release, see the instructions on 
how to check out the latest SVN code: 
http://code.google.com/p/reaver-wps/source/checkout

Original comment by cheff...@tacnetsol.com on 9 Jan 2012 at 6:33

• Changed state: Invalid

[GoogleCodeExporter]

thanks, continue great work

Original comment by virtualw...@gmail.com on 10 Jan 2012 at 12:01