Infinite AP rate detect delay

[GoogleCodeExporter]

A few things to consider before submitting an issue:

0. We write documentation for a reason, if you have not read it and are
having problems with Reaver these pages are required reading before
submitting an issue:
http://code.google.com/p/reaver-wps/wiki/HintsAndTips
http://code.google.com/p/reaver-wps/wiki/README
http://code.google.com/p/reaver-wps/wiki/FAQ
http://code.google.com/p/reaver-wps/wiki/SupportedWirelessDrivers
1. Reaver will only work if your card is in monitor mode.  If you do not
know what monitor mode is then you should learn more about 802.11 hacking
in linux before using Reaver.
2. Using Reaver against access points you do not own or have permission to
attack is illegal.  If you cannot answer basic questions (i.e. model
number, distance away, etc) about the device you are attacking then do not
post your issue here.  We will not help you break the law.
3. Please look through issues that have already been posted and make sure
your question has not already been asked here: http://code.google.com/p
/reaver-wps/issues/list
4. Often times we need packet captures of mon0 while Reaver is running to
troubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap).  Issue
reports with pcap files attached will receive more serious consideration.

Answer the following questions for every issue submitted:

0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)
Latest

1. What operating system are you using (Linux is the only supported OS)?
BT5
2. Is your wireless card in monitor mode (yes/no)?
Yes, mon0
3. What is the signal strength of the Access Point you are trying to crack?
RSSI = -37
4. What is the manufacturer and model # of the device you are trying to
crack?
Unsure
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b 20:CF:30:B7:35:08 -vv
6. Please describe what you think the issue is.
AP rate limiting is detected, when retried it is detected again and again 
infinitely 
7. Paste the output from Reaver below.
(Restoring has nothing to do with it FYI)

[+] Restored previous session
[+] Waiting for beacon from 20:CF:30:B7:35:08
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 2
[+] Associated with 20:CF:30:B7:35:08 (ESSID: MUSTANG)
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking

Original issue reported on code.google.com by CalebGt...@gmail.com on 25 Apr 2012 at 2:57

[GoogleCodeExporter]

I am having the same problem, in the start it associates, tries a few pins, 
gets timeouts but then resumes, after it starts getting these 60 second 
messages, 1st i get 4 in a row, then attack continues, then i get 5 times the 
error, continues, i left it running all night, like 14 hours, and when i went 
to see the progress i had a huge amount of "[!] WARNING: Detected AP rate 
limiting, waiting 60 seconds before re-checking" , equivalent to 1 window and a 
half without any progress, i thing my total progress didn't even reach o,5%...
This seems to be happenning with all newtworks i try (only for educational 
purposes, no damage or illegal activity involved)...So please i would 
appreciate some help, please, i really want to succeed at this.

Original comment by 3litega...@gmail.com on 21 May 2012 at 4:07

[GoogleCodeExporter]

Same here. It started out well, tried several pins, and then "[!] WARNING: 
Detected AP rate limiting, waiting 60 seconds before re-checking". Tried using 
--ignore-locks, the AP rate limiting warning doesn't show up anymore, but fails 
the same pin over and over.

Original comment by drl.ice...@gmail.com on 27 May 2012 at 3:16

[GoogleCodeExporter]

Yes i had the same thing...Like i said i left it over the night to see if it 
progressed, but it just kept looping the same "waiting 60 seconds before 
re-checking".
And yeah, if i write ignore locks it retries the same pin...
Man i sure need some help.

Original comment by 3litega...@gmail.com on 27 May 2012 at 6:56

[GoogleCodeExporter]

I'm not sure if that's the AP locking me out after several failed tries (I did 
try using a different mac address and that failed too), or if that's an issue 
with reaver.

Original comment by drl.ice...@gmail.com on 28 May 2012 at 3:58

[GoogleCodeExporter]

definitely a step ahead of reaver...i succeeded about a month ago ...same 
set-up and command lines....but now it seems reaver itself locks the routers 
endlessly after the routers unlocks...it is obvious that the service providers 
were able to detect the AP rates through their fiber optic cables and locks the 
routers endlessly
hope the reaver developers could respond to this

Original comment by abetbr...@gmail.com on 28 Jul 2012 at 3:00