jpeasleythedon / reaver-wps

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

WARNING: Failed to associate with.. #75

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

I use reaver 1.3 and backtrack 4 r2 

2 wificards:

1) ath5k
2) rt2800usb

What is the expected output? What do you see instead?

---> Using Ath5k i can see this:

reaver -i mon0 -b 00:21:63:XX:XX:XX -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:21:63:XX:XX:XX
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 10
[+] Switching mon0 to channel 11
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[+] Associated with 00:21:63:XX:XX:XX (ESSID: VodafoneXXX)
[+] Trying pin 70211382
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)
[+] Switching mon0 to channel 11
[!] WARNING: Failed to associate with 00:21:63:XX:XX:XX (ESSID: VodafoneXXXX)

---> Using rt2800usb this:

root@bt:~/WPS/reaver-1.3/src# reaver -i mon0 -b 00:21:63:EF:F7:26 -vv

Reaver v1.3 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetso
l.com>

[+] Waiting for beacon from 00:21:63:EF:F7:26
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 10
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 11
[+] Associated with 00:21:63:EF:F7:26 (ESSID: VodafoneF725)
[+] Trying pin 15055972
[!] WARNING: Failed to associate with 00:21:63:EF:F7:26 (ESSID: VodafoneF725)
[+] Switching mon0 to channel 12
[!] WARNING: Failed to associate with 00:21:63:EF:F7:26 (ESSID: VodafoneF725)
[+] Switching mon0 to channel 13
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
.
.
.
[!] WARNING: 25 successive start failures

What version of the product are you using? On what operating system?

Reaver 1.3 download from here.

Please provide any additional information below.

I upload the pcap of the 2 wificards.

Any idea of the error, the AP is not vulnerate?

Thanks a lot for your work..

Original issue reported on code.google.com by mikereav...@gmail.com on 4 Jan 2012 at 7:39

Attachments:

GoogleCodeExporter commented 8 years ago
The Vodafone AP in your pcaps does support WPS, but as with your other issue, 
this AP has a very low signal strength (-85dbm). You'll need better signal 
strength in order to perform a reliable active attack.

Original comment by cheff...@tacnetsol.com on 4 Jan 2012 at 7:44

GoogleCodeExporter commented 8 years ago
The Vodafone AP in your pcaps does support WPS, but as with your other issue, 
this AP has a very low signal strength (-85dbm). You'll need better signal 
strength in order to perform a reliable active attack.

Original comment by cheff...@tacnetsol.com on 4 Jan 2012 at 7:44