search

arismelachroinos / lscript

The LAZY script will make your life easier, and of course faster.
GNU General Public License v3.0
4.03k stars 1.07k forks source link

Reaver stuck trying the same pin #227

Open temptah opened 4 years ago

temptah commented 4 years ago

Describe the bug Running kali linux 2019.3 64bit on Virtual Box (win10 machine).

While running VMR in lscript, reaver 1.6.6 is stuck trying the first pin. I have tried multiple targeted routers, the same issue keeps happening. I have also reverted to previous version (1.6.1.), without result.

reaver loop

arismelachroinos commented 4 years ago

Have you tried option 11?

temptah commented 4 years ago

Have you tried option 11?

hello there aris,

thank you for your great work.

What do you mean by option 11? If you do mean running VMR from option 11 in lscript (find WPS Pin), yes i have, with the same results as i have described above.

To provide some more information in case it is needed, I am using an ALFA AWUS036NHA adapter and i am currently experimenting on 3 different AP modem/routers. One is a Tp-link archer D2 , the second one a SERCOM speedport Plus, third one is a ZTE speedport entry 2i (last two are the most common devices provided from the best established ISP nationwide here).

Back to explaining the issue i am facing, I have also tried option 11 in lscript (find WPS Pin). I am able to run a WASH scan and select the targeted network. While running Pixie Dust attack, reaver (1.6.1.) is stuck on waiting beacon from the selected AP and after about 5 minutes it displays a failed to associate with device error. Reaver DOES initially, reports effectively associating with one of the aforementioned devices, proceeds to try the first pin 12345670, then is stuck and shows a failed to associate with device error. Same thing when trying WPS Bruteforce.

Any ideas on what is going on here?