Out of order packet received, re-trasmitting last message error

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start reaver (reaver -i mon0 -b *BSSID* -c 11 -vv)
2. Wait for it to associate and try one pin.
3. Receive the error

What is the expected output? What do you see instead?
[+] Waiting for beacon from 00:1D:7E:B5:0C:66
[+] Switching mon0 to channel 11
[+] Associated with *BSID* (ESSID: net)
[+] Trying pin 86274814

Clearly the above is OK but after it tries the following it constantly outputs 
the follow.

[!] Warning: Out of order packet received, re-trasmitting last message
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] Warning: Out of order packet received, re-trasmitting last message
[!] WARNING: Last message not processed properly, reverting state to previous 
message

What version of the product are you using? On what operating system?
Reaver 1.1 in Backtrack 4 R2
Alfa AWUS036NH with rt2800usb
Linksys WAG160N

Please provide any additional information below.

Sorry if this has already been discussed however I could not find mention of it 
in other bug reports. Many thanks.

Original issue reported on code.google.com by tomrile...@gmail.com on 30 Dec 2011 at 12:38

[GoogleCodeExporter]

Same warning messages in "Repeating same pin" reports:

http://code.google.com/p/reaver-wps/issues/detail?id=8
http://code.google.com/p/reaver-wps/issues/detail?id=10

Original comment by eb4...@gmail.com on 30 Dec 2011 at 1:21

[GoogleCodeExporter]

This has probably been fixed with the latest svn check in - there were similar 
reports while working on issue #6. Try the latest code and see if you still get 
these warnings.

Original comment by cheff...@tacnetsol.com on 30 Dec 2011 at 3:09

[GoogleCodeExporter]

r34 on Ubuntu 10.04 32bits and ath5k
TPlink AP with lots of traffic received at -56dBm.

Lots of out of order packets and timeouts: http://pastebin.com/YX7vYc7f

Original comment by eb4...@gmail.com on 31 Dec 2011 at 11:54

[GoogleCodeExporter]

Problem detected, it was due a strong interference. Changed AP channel and it's 
now running at 2sec/attemp.

Thanks!

Original comment by eb4...@gmail.com on 31 Dec 2011 at 12:03

[GoogleCodeExporter]

Glad you got it figured out eb4fbz! tomriley, is this the cause of your issues 
as well?

Original comment by cheff...@tacnetsol.com on 31 Dec 2011 at 1:25

[GoogleCodeExporter]

I tried the SVN copy yesterday when you suggested but forgot to post back 
immediately.

That SVN build from yesterday resolved the original problem, however it was 
still not working (completely different issue). Will be trying it again very 
soon.

So as far as this bug report goes, the code fix from yesterday fixed it.

Maybe the interference issue can also cause this same problem?

Original comment by tomrile...@gmail.com on 31 Dec 2011 at 3:20

[GoogleCodeExporter]

The out of order warnings essentially mean that Reaver received a WPS packet, 
but it wasn't the one it was expecting, so yes, this can be caused by 
interference or weak signal strength.

Fix confirmed, closing.

Original comment by cheff...@tacnetsol.com on 2 Jan 2012 at 12:47

• Changed state: Fixed