Reaver will many times after working fine, suddenly report that it cannot
associate with the router. Starting airodump-ng shows that there is no
reception problem as both the AP and client can been seen and the reception
strength is fine.
Again we find as indicated in previous posts that stopping reaver, then deauthing any client with aireplay-ng or a general deauth aimed at the router will solve the problem. When restarting reaver the program runs fine.
We are begining to think that besides sending variable mac codes we might occassionally send a short deauth burst at the router to reset everything to zero so to speak. We may write an appendum to the previous variablemacs.sh and add an occasional short deauth burst.
Note initially tried stoping reaver and then restarting but that worked only in a very few times while the deauth approach produced almost 100 percent success
Musket Team Alpha
Original issue reported on code.google.com by muske...@yahoo.com on 31 Jul 2012 at 10:16
Original issue reported on code.google.com by
muske...@yahoo.comon 31 Jul 2012 at 10:16