search

hhu11286 / reaver-wps

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

WPS transaction failed #633

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)

Reaver v1.4 WiFi Protected Setup Attack Tool

1. What operating system are you using (Linux is the only supported OS)?

BackBox

2. Is your wireless card in monitor mode (yes/no)?

Yes

3. What is the signal strength of the Access Point you are trying to crack?

60-75

4. What is the manufacturer and model # of the device you are trying to
crack?

Sagem_XXXX

5. What is the entire command line string you are supplying to reaver?

reaver -i mon0 -c 11 -b 7C:03:4C:48:AA:95 -vv -p 43944552

6. Please describe what you think the issue is.

The Reaver always output the same error even if the signal is Good

7. Paste the output from Reaver below.

[!] WPS transaction failed (code: 0x02), re-trying last pin

Original issue reported on code.google.com by countv...@gmail.com on 15 Apr 2014 at 9:01

GoogleCodeExporter commented 8 years ago 
The Complete Reaver Output :

[+] Waiting for beacon from 7C:03:4C:48:AA:95
[+] Switching mon0 to channel 11
[+] Associated with 7C:03:4C:48:AA:95 (ESSID: Sagem_AA94)
[+] Trying pin 43944552
[+] 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

Original comment by countv...@gmail.com on 15 Apr 2014 at 9:10