Run another AP while waiting for the primary to finish rate limiting

[GoogleCodeExporter]

I am really curious why this was not implemented a function - to run two (or 
more) APs at once, but not at the same time. 

Often, when you run one AP, after few PINs it will encounter 
" WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking"

This lasts anywhere between 3 and 60 minutes (depending on AP). This time 
wasted on waiting could be used to run alternative AP, and return to the 
primary when X number of minutes elapses.

What do you think about adding such a function?

Original issue reported on code.google.com by conrad.f...@googlemail.com on 24 Aug 2013 at 6:28

[GoogleCodeExporter]

not all AP auto unlocks after 60 minutes.
in this case, nothing prevents using another terminal. 
indeed until today, when it occurs, only unlocks with reboot router.

Original comment by deltomaf...@gmail.com on 24 Aug 2013 at 11:54

[GoogleCodeExporter]

>>>>> not all AP auto unlocks after 60 minutes.

Sure. Many unlock after 3 minutes, other after 10, others after 60, etc.

>>>>> in this case, nothing prevents using another terminal. 

Nothing, if someone wants to spend hours in front of computer, manually 
switching two instances raver every ~6 minutes.

>>>>> indeed until today, when it occurs, only unlocks with reboot router.

In my experience, only 50% of routers lock until reboot. Others unlock after 
several mintues to tens of minutes.

Original comment by conrad.f...@googlemail.com on 25 Aug 2013 at 7:14

[GoogleCodeExporter]

Sure. since it has a standard time, with the parameters that exist in Reaver
can not manage this time
maintaining two instances active?

Original comment by deltomaf...@gmail.com on 25 Aug 2013 at 2:37