search

niyyate / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

Detected AP rate limiting #109

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
while running:

Portage 2.1.10.44 (default/linux/amd64/10.0, gcc-4.6.2, glibc-2.14.1-r2, 
3.2.0-rc7+ x86_64)
=================================================================
System uname: 
Linux-3.2.0-rc7+-x86_64-Intel-R-_Core-TM-_i5-2500K_CPU_@_3.30GHz-with-gentoo-2.1
Timestamp of tree: Sat, 07 Jan 2012 13:30:01 +0000
app-shells/bash:          4.2_p20
dev-java/java-config:     2.1.11-r3
dev-lang/python:          2.7.2-r3, 3.2.2
dev-util/cmake:           2.8.6-r4
dev-util/pkgconfig:       0.26
sys-apps/baselayout:      2.1
sys-apps/openrc:          0.9.8
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.68
sys-devel/automake:       1.11.2
sys-devel/binutils:       2.22-r1
sys-devel/gcc:            4.6.2
sys-devel/gcc-config:     1.5-r2
sys-devel/libtool:        2.4.2
sys-devel/make:           3.82-r3
sys-kernel/linux-headers: 3.2 (virtual/os-headers)
sys-libs/glibc:           2.14.1-r2

there seems 2 be bugs/issues with svn rev 76, seems that once it gets a 
WARNING: Detected AP rate limiting from one ap this is continued onto the next 
test ap

Original issue reported on code.google.com by lauriepa...@gmail.com on 8 Jan 2012 at 4:16

GoogleCodeExporter commented 8 years ago 
So if you are attacking one AP and the AP locks you out (aka, you get the rate 
limiting warning), then you stop reaver and re-start it against a completely 
different AP and reaver sees the new AP as locked also? How do you know that 
both APs aren't locked? Can you provide reaver output and pcaps?

Original comment by cheff...@tacnetsol.com on 8 Jan 2012 at 4:58

GoogleCodeExporter commented 8 years ago

Original comment by cheff...@tacnetsol.com on 9 Jan 2012 at 6:53

GoogleCodeExporter commented 8 years ago

Original comment by cheff...@tacnetsol.com on 11 Jan 2012 at 4:56

GoogleCodeExporter commented 8 years ago 
sorry want home 2 try get it do it again:

 (one app)

[+] Trying pin 92575097
[!] WARNING: Receive timeout occurred
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
^C^
[+] Session saved.

root@UniMatrix0: pts/1: 2 files 676Kb -> reaver -i mon0 -a -vv 0 -b 
00:11:22:33:44:55

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

[+] Restored previous session
[+] Waiting for beacon from 00:11:22:33:44:55
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 11
[+] Associated with 00:11:22:33:44:55 (ESSID: xxxx-xxxxx)
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying

that seem right ? didnt even seem to try on the next ap

Original comment by lauriepa...@gmail.com on 11 Jan 2012 at 5:23

GoogleCodeExporter commented 8 years ago 
The "AP rate limiting" message reflects the fact that the target AP is 
reporting in its beacon packets that WPS is locked. Some APs lock themselves 
indefinitely after X number of failed attempts. Some APs provide the option to 
lock WPS in the administrative interface, so it can be indefinitely locked by 
the user. Some APs incorrectly report that they are locked when they aren't.

You can specify the --ignore-locks option to tell Reaver to attempt the attack 
even if WPS is reportedly locked. YMMV, if the AP really has locked WPS then 
the attack will not succeed.

Original comment by cheff...@tacnetsol.com on 11 Jan 2012 at 5:34

GoogleCodeExporter commented 8 years ago 
i see, that seems to of done something different ie :

[+] 0.78% complete @ 2012-01-11 18:15:21 (6 seconds/attempt)
[+] Trying pin 73665670
[+] Sending EAPOL START request
[+] Sending identity response
[+] Sending M2 message
[+] Sending M4 message
[+] Sending WSC NACK
[+] Trying pin 79315678

thanks for the reply/help

Original comment by lauriepa...@gmail.com on 11 Jan 2012 at 6:16

GoogleCodeExporter commented 8 years ago 
That is what you should see during a successful attack. Looks like the AP was 
lying and hadn't really locked WPS. :)

Original comment by cheff...@tacnetsol.com on 11 Jan 2012 at 6:19

GoogleCodeExporter commented 8 years ago 
me too i have same problem 
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying

what i do. please help me

Original comment by brahimr...@gmail.com on 18 Jan 2012 at 7:38

GoogleCodeExporter commented 8 years ago 
@ love
you can try -L, and if nothing happens you have to wait there is no work 
arround if
the AP locks you.

Original comment by patricks...@gmail.com on 18 Jan 2012 at 7:41

GoogleCodeExporter commented 8 years ago 
wait 30 minutes and nothing changed

Original comment by brahimr...@gmail.com on 18 Jan 2012 at 7:56

GoogleCodeExporter commented 8 years ago 
Choose another victim

Original comment by patricks...@gmail.com on 18 Jan 2012 at 8:00

GoogleCodeExporter commented 8 years ago 
all victims it have same problem 
thank you so much

Original comment by brahimr...@gmail.com on 18 Jan 2012 at 8:46

GoogleCodeExporter commented 8 years ago 
Is your adapter supported? loock in supported wlan devices, what version of 
reaver
you are using what linux you use?

if you have a capture file may be Craig can help you

Original comment by patricks...@gmail.com on 18 Jan 2012 at 8:50

GoogleCodeExporter commented 8 years ago 
I have been running reaver for 24 hours now only at 22% I keep getting the 
lockedout warning as well. Ive tried the --ignore-locks but it just throws 
reaver into a loop trying the same pin. is there a way I can tell reaver to try 
pins from a selected range?

Original comment by Mario.Ba...@gmail.com on 12 Jul 2012 at 10:06

GoogleCodeExporter commented 8 years ago 
 Mario.Ba...@gmail.com
so you are in a better position then me for me the same thing is on but after 
24 hours i got only to 8% help please
:)

Original comment by gergo.la...@gmail.com on 13 Oct 2012 at 7:14

GoogleCodeExporter commented 8 years ago 
I am being affected by a rate limiter but it stops at exactly 5 60 second wait 
period. So im guessing the AP has a wait 5 minute setting when too many 
attempts have been detected. If you continuously get the AP rate limiter 
detection, then it may be set to permanent lockout. I am just letting mine bang 
away. Patience is part of this game.

Original comment by rbuck...@gmail.com on 7 Dec 2012 at 2:10

GoogleCodeExporter commented 8 years ago 
i have same problem with AP is locked and i was waiting for nearly 4 hours 
which i have  same massage [!] WARNING: Detected AP rate limiting, waiting 60 
seconds before re-trying any suggestion ?

Original comment by trico...@gmail.com on 18 Dec 2012 at 12:22

GoogleCodeExporter commented 8 years ago 
Hey Craig,can we try to maintain the AP without locking wps is there any wayout?

Original comment by techch...@gmail.com on 3 Jun 2013 at 9:21

GoogleCodeExporter commented 8 years ago 
hey, can someone help me! reaver 1.4 find  the PIN but don't reveal the wpa. i 
tried find wpa psk using reaver 1.4 but i got same issue. Any suggestions?

Original comment by jahja.tr...@gmail.com on 23 Oct 2013 at 9:57

GoogleCodeExporter commented 8 years ago 
hey, can someone help me! reaver 1.4 find  the PIN but don't reveal the wpa. i 
tried find wpa psk using reaver 1.4 but i got same issue. Any suggestions?

Original comment by sothseng...@gmail.com on 5 Dec 2013 at 7:09

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
https://www.youtube.com/watch?v=8qh9813L59A

Original comment by slma...@abv.bg on 29 Sep 2014 at 12:33