Ok so I tested this with many different setups and all the wlan adapter and
systems I used worked before.
When you run reaver on a kernel version >3.10 (didn't test 3.0-3.9 yet so I
don't know when this bug occured first) you get a few
[!] WARNING: Failed to associate with AA:BB:CC:DD:EE:FF (ESSID: (null))
first and when it finally finds the AP you are looking for it just changes to
[!] WARNING: Failed to associate with AA:BB:CC:DD:EE:FF (ESSID: Foobar)
It doesn't associate in 99 out of 100 tries (no matter what the distance
between you and the ap) but when it does it can't try any pins. (I will later
check again to get the exact error message)
Anyway I associated (successfully) with the ap with aireplay-ng and tried it
with it, without success as well.
To eliminate any error from my part I tried it with a 2.6 kernel I had and it
worked without any problems.
Original issue reported on code.google.com by blackhua...@gmail.com on 3 Apr 2014 at 8:05
Original issue reported on code.google.com by
blackhua...@gmail.com
on 3 Apr 2014 at 8:05