Closed GoogleCodeExporter closed 8 years ago
I assume that you do not have MAC filtering enabled on your AP? You can also
tell Reaver to skip the association with the -A option and use aireplay-ng to
associate to the AP.
Original comment by cheff...@tacnetsol.com
on 16 Jan 2012 at 5:15
And have you uses wash before to ensure the AP supports WPS?
Try to update to last revision too, it may fix it.
Original comment by andremeg...@hotmail.com
on 16 Jan 2012 at 5:24
Thank you for responding me.
No there is no MAC filtering. I verified it.
This for the -A option:
root@bt:~/test/reaver-1.3/src# reaver -i mon0 -b 00:26:50:47:4A:19 -A -vv
Reaver v1.3 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
reaver: invalid option -- 'A'
Required Arguments:
-i, --interface=<wlan> Name of the monitor-mode interface to use
-b, --bssid=<mac> BSSID of the target AP
Optional Arguments:
-m, --mac=<mac> MAC of the host system
-e, --essid=<ssid> ESSID of the target AP
-c, --channel=<channel> Set the 802.11 channel for the interface (implies -f)
-o, --out-file=<file> Send output to a log file [stdout]
-s, --session=<file> Restore a previous session file
-a, --auto Auto detect the best advanced options for the target AP
-f, --fixed Disable channel hopping
-5, --5ghz Use 5GHz 802.11 channels
-v, --verbose Display non-critical warnings (-vv for more)
-q, --quiet Only display critical messages
-h, --help Show help
Advanced Options:
-p, --pin=<wps pin> Use the specified 4 or 8 digit WPS pin
-d, --delay=<seconds> Set the delay between pin attempts [1]
-l, --lock-delay=<seconds> Set the time to wait if the AP locks WPS pin attempts [315]
-g, --max-attempts=<num> Quit after num pin attempts
-x, --fail-wait=<seconds> Set the time to sleep after 10 unexpected failures [0]
-r, --recurring-delay=<x:y> Sleep for y seconds every x pin attempts
-t, --timeout=<seconds> Set the receive timeout period [5]
-T, --m57-timeout=<seconds> Set the M5/M7 timeout period [0.20]
-S, --dh-small Use small DH keys to improve crack speed
-L, --ignore-locks Ignore locked state reported by the target AP
-E, --eap-terminate Terminate each WPS session with an EAP FAIL packet
-n, --nack Target AP always sends a NACK [Auto]
-w, --win7 Mimic a Windows 7 registrar [False]
Example:
reaver -i mon0 -b 00:90:4C:C1:AC:21 -vv
root@bt:~/test/reaver-1.3/src# reaver -i mon0 -b 00:26:50:47:4A:19 -a -vv
Reaver v1.3 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+] Waiting for beacon from 00:26:50:47:4A:19
[+] Switching mon0 to channel 2
[!] WARNING: Failed to associate with 00:26:50:47:4A:19 (ESSID: BELL999)
^C
[+] Nothing done, nothing to save.
[+] Session saved.
root@bt:~/test/reaver-1.3/src#
---Sorry but what is the wash command ? and where can i download the last
revision since i downloaded the last reaver 1.3 from this site ?
Original comment by voleuse....@gmail.com
on 16 Jan 2012 at 2:41
Ah, there's your problem. :)
The -A option was not included until after version 1.3. You'll have to check
out the latest SVN code (instructions here:
http://code.google.com/p/reaver-wps/source/checkout).
Original comment by cheff...@tacnetsol.com
on 16 Jan 2012 at 2:44
i ve done the walsh command. it seems working and trying pins.
but why it is not working on my AP ? and where can i find the last revision.
i want to help for tests for this project.i find it very nice.
Original comment by voleuse....@gmail.com
on 16 Jan 2012 at 3:29
Enter in the command line:
svn checkout http://reaver-wps.googlecode.com/svn/trunk/ reaverlatest
reaverlatest will be a new folder containing latest revision
then goto into this directory change into src
./configure
make
make install
Original comment by patricks...@gmail.com
on 16 Jan 2012 at 3:39
thank you very much.
now i am trying reaver 1.4.
this defect should be close.
i ll get beack to you.
Original comment by voleuse....@gmail.com
on 16 Jan 2012 at 7:36
Original comment by cheff...@tacnetsol.com
on 17 Jan 2012 at 1:18
Original issue reported on code.google.com by
voleuse....@gmail.com
on 16 Jan 2012 at 5:10