I'm having one particular issue using Reaver
Everything is working perfectly, except for one thing.
I start using Reaver, it starts testing pins, everything is working perfectly. After a while, the router hops to another channel, and Reaver gives me this warning
Code:
Sending EAPOL START request
WARNING: Receive timeout occurred
Sending EAPOL START request
WARNING: Receive timeout occurred
Sending EAPOL START request
WARNING: Receive timeout occurred
...
And it loops forever. The reason for this is because Reaver can't associate with the network, because the network is now on a different channel.
Reaver has a feature to scan different channels for the BSSID or ESSID, but only does so in the beginning to find the network its looking for. This is a problem. I wish there was a way to set Reaver to scan the channels again after X amount of timeouts. This would solve the problem
I have a workaround for this. I use airodump-ng on the same interface as Reaver is using, and makes airodump-ng lock on to the target. Now Reaver will constantly be associated with the network.
But there's a problem here as well. After airodump-ng finds the network on a specific channel, it will still continue hopping through the channels constantly searching - making nearly 90% of Reaver's attack miss the target, because airodump-ng is using the same same interface and is constantly switching its channels. The solution here would also give airodump-ng a very similar feature, which is to stop searching through all the channels when it found the network, and start searching again when it loses connection to the network.
I might have missed something. I looked through both programs carefully, and couldn't find any useful commands to this.
So I was wondering if any of you might recommend a program that is equal to airodump-ng, but STOPS searching through channels when it finds the network, and would rather search again when it loses it