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

[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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected] on 2 Jan 2012 at 12:47

• Changed state: Fixed