reaver continues to switch channels waiting for beacon

[GoogleCodeExporter]

I'm using the newest install of reaver (1.4) on Ubuntu 14.04. My wireless card 
is in monitor mode and the sign of the access point is -59. The commands I 
enter are as follows: 
airmon-ng start wlan0
airodump-ng mon0
reaver -i mon0 -b 00:1D:D3:64:3B:00 -vv

I believe the issue has something to do with my libpcap or my wifi drivers. But 
am newer to the reaver troubleshooting process [don't know where to start]

Below is my output. 

 BSSID              PWR  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH ESSID

 1C:99:4C:35:2C:5A  -47       19        0    0  11  54e  OPN              FoxFi
 00:1D:D3:64:3B:00  -59       14        0    0   6  54e  WPA2 CCMP   PSK  Ghost
 30:60:23:9F:FA:A0  -79        7        0    0  11  54e  WPA2 CCMP   PSK  ATT4v
 00:13:F7:7A:54:7E  -83        3        0    0   6  54 . WPA2 CCMP   PSK  SCHRO
 B4:75:0E:77:7E:3F  -85        4        0    0  11  54e  WPA2 CCMP   PSK  Under
 00:14:A5:90:A3:82  -87        2        0    0  11  54   WEP  WEP         Motor

 BSSID              STATION            PWR   Rate    Lost  Packets  Probes      

 (not associated)   30:59:B7:EC:CE:20  -57    0 - 1     16        6  House      
 00:1D:D3:64:3B:00  20:16:D8:13:C9:3D  -49    0 - 1     16        5             

root@junk-HP-Pavilion-dv7-Notebook-PC:/home/junk# ifconfig wlan0 up
root@junk-HP-Pavilion-dv7-Notebook-PC:/home/junk# reaver -i mon0 -b 
00:1D:D3:64:3B:00 -vv

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[+] Waiting for beacon from 00:1D:D3:64:3B:00
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 10
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 12
[+] Switching mon0 to channel 13
[+] Switching mon0 to channel 14
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 10
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 12
[+] Switching mon0 to channel 13
[+] Switching mon0 to channel 14
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 10
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 12
[+] Switching mon0 to channel 13
[+] Switching mon0 to channel 14
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
^C
[+] Nothing done, nothing to save.
root@junk-HP-Pavilion-dv7-Notebook-PC:/home/junk# ^C

Original issue reported on code.google.com by ethanly...@gmail.com on 9 Jan 2015 at 5:20

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

airmon-ng start wlan0
wash -i mon0 -c 6
reaver -i mon0 -b 00:1D:D3:64:3B:00 -a -S -vv -c 6

Original comment by deltomaf...@gmail.com on 9 Jan 2015 at 2:17

[GoogleCodeExporter]

Still no luck. Wash just sits there. After a while I cancel.  

Original comment by ethanly...@gmail.com on 9 Jan 2015 at 10:46

[GoogleCodeExporter]

airmon-ng start wlan0
open 2 terminal leave run:
1 with: airodump-ng mon0 --ignore-negative-one -d 00:1d:d3:64:3b:00 -c 6
2 with: reaver -i mon0 -b 00:1D:D3:64:3B:00 -a -S -vv -c 6

Original comment by deltomaf...@gmail.com on 14 Jan 2015 at 6:39

[GoogleCodeExporter]

I get an error with the command --ignore portion of the code.  Do you think it 
has something to do with the limited amount of beacons?

Original comment by ethanly...@gmail.com on 19 Jan 2015 at 11:13