search

Sbeiersc / reaver-wps

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

Reaver locks after receiving packet types 21 & 19 #154

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I've been running reaver for a couple of days in the real world and after 
getting packets type 21 and 19 it quit responding:

[!] WPS transaction failed (code: 0x2), re-trying last pin
[+] 36.75% complete @ 2012-01-19 02:03:46 (95 seconds/attempt)
[+] Trying pin 33365671
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Sending identity response
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x2), re-trying last pin
[+] Trying pin 33365671
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Sending identity response
[+] Sending M2 message
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Out of order packet received, re-trasmitting last message
[+] Sending M2D 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
[+] Sending WSC ACK
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Got packet type 21 (0x15), but haven't broken the first half of 
the pin yet!
[!] WARNING: Last message not processed properly, reverting state to previous 
message
[!] WARNING: Got packet type 19 (0x13), but haven't broken the first half of 
the pin yet!

Original issue reported on code.google.com by hoboab...@gmail.com on 19 Jan 2012 at 3:29

GoogleCodeExporter commented 8 years ago 
It would be a nice if reaver had the ability to pickup where it left off, 
possibly keep a log of the keys already tried and progress made?

Original comment by hoboab...@gmail.com on 19 Jan 2012 at 3:34

GoogleCodeExporter commented 8 years ago 
@hoboab
analyze the files /etc/reaver/
there you find the awnser of progress

Original comment by patricks...@gmail.com on 19 Jan 2012 at 3:39

GoogleCodeExporter commented 8 years ago 
hoboabode, it sounds like you're using Reaver 1.3 or earlier; these issues 
should be cleared up in the latest SVN code. Try that and see if it fixes your 
problems.

Original comment by cheff...@tacnetsol.com on 19 Jan 2012 at 4:49

GoogleCodeExporter commented 8 years ago 
I'm using a SVN build from last Friday, I just updated and did a distclean and 
rebuild so we'll see what it does

Original comment by hoboab...@gmail.com on 19 Jan 2012 at 9:51

GoogleCodeExporter commented 8 years ago 
BTW would there be a way to make the progress resumable?

Thanks

Original comment by hoboab...@gmail.com on 19 Jan 2012 at 9:51

GoogleCodeExporter commented 8 years ago 
The resume feature was introduced in version 1.3.

Original comment by cheff...@tacnetsol.com on 20 Jan 2012 at 2:29

GoogleCodeExporter commented 8 years ago 
Any results for this issue?

Thanx a lot in advance

Original comment by rag...@gmail.com on 28 Jan 2012 at 3:02