No reaver progress

[GoogleCodeExporter]

Please admins and tech people,
help me find out what could possible be wrong. I've been trying to find out for 
days now and can't seem to solve nor find any solutions to what to do...
Everytime I use Reaver it keeps getting:
[!] WPS transaction failed (code: 0x02), re-trying last pin
or 
[!] WARNING: Receive timeout occurred 'spam'

I've solved the (code: 0x03) errors by adding -N (or --no-nacks) but I can't 
seem to get rid of the other one nor the Time outs.

What I do in advance is:
# airmon-ng start wlan0
# airodump-ng mon0
# wash -i mon0
# reaver -i mon0 -f -c 11 -b xx:xx:xx:xx:xx:xx -vv --no-nacks

0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)

I'm using version 1.4

1. What operating system are you using (Linux is the only supported OS)?

Ubuntu which is running on Linux 2.3.6

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?

87-100% if necessairy, but most of the time around 87%

4. What is the manufacturer and model # of the device you are trying to
crack?

Linksys

5. What is the entire command line string you are supplying to reaver?

reaver -i mon0 -f -c 11 -b xx:xx:xx:xx:xx:xx -vv --no-nacks

6. Please describe what you think the issue is.

I think Reaver is not reaching the device I'm trying to crack. It's my own 
modem so I thought it wouldn't have any problems to reach or crack it.

7. Paste the output from Reaver below.

[+] Waiting for beacon from 00:1C:F0:F2:4A:42
[+] Associated with 00:1C:F0:F2:4A:42 (ESSID: dierckx)
[+] Trying pin 00255677
[+] 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 EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 00255677
[+] 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
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 00255677
[+] 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
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 00255677
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 00255677
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 00255677
[+] 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
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] 0.33% complete @ 2012-06-15 18:46:33 (0 seconds/pin)

I'm at 0.33% because I keep rebooting reaver process and eventually it starts 
switching to new pins.

I've tried using the 
# aireplay-ng mon0 -1 120 -a XX:XX:XX:XX:XX:XX -e <exact name of the target AP>

This helped once ! and boosted the process from 0.05 to 0.33% but after that it 
got stuck again. I tried to reboot it that way but it went back to the buggy 
previous output.

Any help  will be MUCH appreciated :)

Original issue reported on code.google.com by maasever...@gmail.com on 15 Jun 2012 at 5:02

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

how far are you from this AP?
It looks like the AP is NOT hearing you well.
You are not trying to crack your own AP. You specified that your AP is Linksys. 
The AP ESSID: dierckx is a D-Link. ;)
To get it going: 
Open a window or two. 
Get closer to the AP.
Start reaver over the night when the WiFi spectrum is not utilized that much 
and you will be able to hear the remote AP better. 
Get a better antenna. 
get an external WiFi USB card. 
Upgrade the external USB cad antenna.
Enhance the antenna with some tin foil.
Do a DIY Cantenna for directional cracking.
Buy a factory made yagi omnidirectional 60cm 28dBi Antenna.
Modify that old satellite dish by adding the cantenna you created to it and 
point it in to the direction of the AP.
Get a old van, mount the modified old satellite dish on top of it and start 
driving slow in your neighbourhood.
Go to the next neighbourhood.

;)  

Original comment by BHT...@gmail.com on 17 Jun 2012 at 4:02

[GoogleCodeExporter]

@ BHT
Ah, yes. the dierckx is my neighbour's modem I tried him to see if that gave 
any results but unfortunatly no succes either.
I will try the neighboorhoud stalking project then ... :p

And I'm right underneath my AP and I've already tried sitting right next to it, 
makes no difference. 
Starting Reaver at night is no help either, it keeps giving the same errors etc.

Original comment by maasever...@gmail.com on 19 Jun 2012 at 7:15