0phoi5 Posted January 12, 2016 Share Posted January 12, 2016 Pretty sure the ap won't accept any requests from anything after the limit is reached. Tested on BT HomeHub 2 (yeh, rubbish, ikr!). Confirmed that this happens after around 20/21 times. Nothing can connect until resetting the hub, which you have to do via actually pressing the button on it using your actual finger. At least I know no one can bruteforce the thing. Quote Link to comment Share on other sites More sharing options...
0phoi5 Posted January 12, 2016 Share Posted January 12, 2016 (edited) Could you set up a shell script to do this for you? 1.) Check status of AP. 2.) Send x [MAXIMUM NO. OF ATTACKS BEFORE LOCKDOWN] to AP 3.) Check status of AP. 4.) If not locked down, then step 1. If locked down, wait x number of seconds, then step 3. 5.) Leave it running until success. 6.) Profit. *Edit* Hope you're very patient, because this could take a while. Like, a long while. Edited January 12, 2016 by haze1434 Quote Link to comment Share on other sites More sharing options...
DataHead Posted February 5, 2016 Share Posted February 5, 2016 Avoid a lockout in reaver ( our modified fork on t6x github ) with -P option. It will loop upto m4 message. Which in return never fully pins the target ap, but just collects all the pertinent hashes for pixiewps. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.