I have tried to google the solution for 2 days now with no progress, please
help. I get this error on 4/5 networks! I've only had 1 successful attack in
reaver so far the rest have gotten errors like this one.
0. What version of Reaver are you using? (Only defects against the latest
version will be considered.)
Im using verison 1.4.
1. What operating system are you using (Linux is the only supported OS)?
Backtrack 5, so linux yes.
2. Is your wireless card in monitor mode (yes/no)?
Yes it is.
3. What is the signal strength of the Access Point you are trying to crack?
Pretty good RSSI: -56.
4. What is the manufacturer and model # of the device you are trying to
crack?
D-Link DIR-655
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b 00:22:75:25:CC:6D -vv
6. Please describe what you think the issue is.
Well it retries the same pin over and over again.
7. Paste the output from Reaver below.
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
and so it goes over and over again ;(
Original issue reported on code.google.com by filip.ba...@gmail.com on 9 Aug 2013 at 11:44
Original issue reported on code.google.com by
filip.ba...@gmail.com
on 9 Aug 2013 at 11:44