bktruss / reaver-wps

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

[!] WARNING: Failed to associate with #311

Open GoogleCodeExporter opened 9 years ago

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

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

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?
-85 PWR

4. What is the manufacturer and model # of the device you are trying to
crack?
I don't know. The BSSID name is TP-LINK_AF31FC. i guess this is the model

5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b F4:EC:38:AF:31:FC -c 1 -vv -a

6. Please describe what you think the issue is.

7. Paste the output from Reaver below.
[+] Switching mon0 to channel 1
[+] Restored previous session
[+] Waiting for beacon from F4:EC:38:AF:31:FC
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[+] Associated with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)
[+] Trying pin 88885674
[!] WARNING: Failed to associate with F4:EC:38:AF:31:FC (ESSID: TP-LINK_AF31FC)

root@bt:~/Desktop/reaver/src# wash -i mon0 --ignore-fcs

Wash v1.4 WiFi Protected Setup Scan Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

BSSID                  Channel       RSSI       WPS Version       WPS Locked    
    ESSID
--------------------------------------------------------------------------------
-------------------------------
F4:EC:38:AF:31:FC       1            -84        1.0               No            
    TP-LINK_AF31FC

I am using Edimax EW-7318Ug with rt73usb driver

Original issue reported on code.google.com by beepcho...@gmail.com on 16 May 2012 at 10:53

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Signal is to weak. Reaver needs a good signal. You have to have at least -70.

Original comment by BHT...@gmail.com on 2 Jun 2012 at 3:04