cristianct87 / reaver-wps

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

WARNING: Last message not processed properly, reverting state to previous message #74

Closed GoogleCodeExporter closed 8 years ago

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

I have 2 wireless card:

1)awus036nh
2)ath5k

Using Backtrack 4 r2

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

root@bt:~/WPS/reaver-1.3/src# reaver -i mon0 -b 00:19:70: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:19:70: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 6
[!] WARNING: Failed to associate with 00:19:70:XX:XX:XX (ESSID: Orange-XXXX)
[+] Associated with 00:19:70:XX:XX:XX (ESSID: Orange-XXXX)
[+] Trying pin 60590695
[!] WARNING: Receive timeout occurred
[+] Trying pin 60590695
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Out of order packet received, re-trasmitting last message
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Out of order packet received, re-trasmitting last message
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Out of order packet received, re-trasmitting last message
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Out of order packet received, re-trasmitting last message
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Out of order packet received, re-trasmitting last message
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Out of order packet received, re-trasmitting last message
[+] Trying pin 82592387
[!] WARNING: Receive timeout occurred

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 pcap of the 2 cards, and message Error. Any idea of the error. 
I'm very near to the AP. Perhaps the AP is not vulnerate?

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

Attachments:

GoogleCodeExporter commented 8 years ago
The AP is vulnerable, but the received signal strength (RSSI) is almost -90dbm. 
This is very low. You will need to get closer to the AP or boost your signal 
with a directional antenna in order to perform this attack.

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

GoogleCodeExporter commented 8 years ago
Thanks for response, but the signal is nearly -65 dBm as you can see in
this picture...

Excuse me for me English, because is not very fluently...

I try to boost my signal with antenna but the result is the same..

Another idea ?

Original comment by mikereav...@gmail.com on 4 Jan 2012 at 10:29

GoogleCodeExporter commented 8 years ago
I've found that even -60dbm is not always enough for a reliable attack. It 
depends on the AP and your environment. 

Original comment by cheff...@tacnetsol.com on 4 Jan 2012 at 10:54

GoogleCodeExporter commented 8 years ago
Ok,

Thanks for your help, i don�t give up, the next week i�ll try to use your
tool, but with the AWUS036H wifi card, because this has rtl8187 driver...

I hope with this driver, the issue would be fix ..

I�ve read in a foro, that one user have diferent wificards  AWUS036NH,
AWUS036NHA, AWUS036NHR, AWUS051NH but didn�t work properly, but with
AWUS036H work perfect !!! with the same environment..!!!

I'll keep you informed...

Regards...

Mike

Original comment by mikereav...@gmail.com on 5 Jan 2012 at 11:23

GoogleCodeExporter commented 8 years ago
I've seen this with a spoofed MAC.  Try with your default MAC.

Original comment by alex.lau...@gmail.com on 11 Jan 2012 at 2:47