Every time it is giving eapol error

[GoogleCodeExporter]

A few things to consider before submitting an issue:

0. We write documentation for a reason, if you have not read it and are
having problems with Reaver these pages are required reading before
submitting an issue:
http://code.google.com/p/reaver-wps/wiki/HintsAndTips
http://code.google.com/p/reaver-wps/wiki/README
http://code.google.com/p/reaver-wps/wiki/FAQ
http://code.google.com/p/reaver-wps/wiki/SupportedWirelessDrivers
1. Reaver will only work if your card is in monitor mode.  If you do not
know what monitor mode is then you should learn more about 802.11 hacking
in linux before using Reaver.
2. Using Reaver against access points you do not own or have permission to
attack is illegal.  If you cannot answer basic questions (i.e. model
number, distance away, etc) about the device you are attacking then do not
post your issue here.  We will not help you break the law.
3. Please look through issues that have already been posted and make sure
your question has not already been asked here: http://code.google.com/p
/reaver-wps/issues/list
4. Often times we need packet captures of mon0 while Reaver is running to
troubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap).  Issue
reports with pcap files attached will receive more serious consideration.

Answer the following questions for every issue submitted:

0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)
Reaver 1.4
1. What operating system are you using (Linux is the only supported OS)?
Ubuntu 12.04
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?
-63 to -67
4. What is the manufacturer and model # of the device you are trying to
crack?
Dont know
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b essid c8:3a:35:33:xx:xx -vv
6. Please describe what you think the issue is.
Eapol recieve timeout error. I don't know what it is.
7. Paste the output from Reaver below.
[+] 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

Dont know what is happening to it. I facing this problem with 2 Aps well oghers 
are working very well.

Original issue reported on code.google.com by mannankh...@gmail.com on 20 Mar 2014 at 3:10

[GoogleCodeExporter]

change command line:
reaver -i mon0 -b essid c8:3a:35:33:xx:xx -vv
for:
reaver -i mon0 -b c8:3a:35:33:xx:xx -a -S -N -c <channel> -vv -w

Original comment by deltomaf...@gmail.com on 22 Mar 2014 at 1:03

[GoogleCodeExporter]

It is again giving same issue:
I have also use wash command and result you can see that:

root@ubuntu:~# wash -i mon0

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

BSSID                  Channel       RSSI       WPS Version       WPS Locked    
    ESSID
--------------------------------------------------------------------------------
-------------------------------
c8:3a:35:33:xx:xx      11            -69        1.0               No            
    Evxxxxxx

And when I use it is giving Eapol error:

root@ubuntu:~# reaver -i mon0 -b c8:3a:35:33:xx:xx -a -S -N -c 1 -vv -w

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

[+] Switching mon0 to channel 1
[+] Waiting for beacon from c8:3a:35:33:xx:xx
[+] Associated with c8:3a:35:33:xx:xx (ESSID: Evxxxxxx)
[+] Trying pin 12345670
[+] 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
[!] 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
[!] 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
[!] WARNING: 25 successive start failures
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
^C
[+] Nothing done, nothing to save.

Why this is happening I don't know.

Original comment by mannankh...@gmail.com on 22 Mar 2014 at 7:36

[GoogleCodeExporter]

channel 1 ?? wash say channel 11.

Original comment by deltomaf...@gmail.com on 23 Mar 2014 at 12:49

[GoogleCodeExporter]

Giving the same issue on changing the channel to 11.

Original comment by mannankh...@gmail.com on 23 Mar 2014 at 8:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

ok try this:
leaving running in a terminal:
airodump-ng mon0 -d <mac> -c <channel> --ignore-negative-one
in another terminal try run Reaver:
reaver -i mon0 -b c8:3a:35:33:xx:xx -a -S -N -c <channel> -vv -w

Original comment by deltomaf...@gmail.com on 24 Mar 2014 at 12:04

[GoogleCodeExporter]

Giving same error:
In one terminal I type airodump-ng mon0 -d 00:13:CE:33:08:7C  -c 11 
--ignore-negative-one and it is showing nothing as you can see it.

CH 11 ][ BAT: 1 hour 11 mins ][ Elapsed: 2 min ][ 2014-03-24 11:56

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

BSSID              STATION             PWR   Rate    Lost   Frames  Probes

On other terminal I type reaver -i mon0 -b c8:3a:35:33:xx:xx -a -S -N -c 11 -vv 
-w. Again it is giving the same Eapol error:

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

[+] Switching mon0 to channel 11
[+] Waiting for beacon from c8:3a:35:33:xx:xx
[+] Associated with c8:3a:35:33:xx:xx (ESSID: Evxxxxxx)
[+] Trying pin 12345670
[+] 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
[!] 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
[!] 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
[!] WARNING: 25 successive start failures
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
^C
[+] Nothing done, nothing to save.

Original comment by mannankh...@gmail.com on 24 Mar 2014 at 7:29

[GoogleCodeExporter]

that strange.....
Wash the continued reporting that the channel is 11?
was to appear in something in airodump...

Original comment by deltomaf...@gmail.com on 26 Mar 2014 at 1:44

[GoogleCodeExporter]

what is the output of command:
# airmon-ng

Original comment by deltomaf...@gmail.com on 26 Mar 2014 at 1:48

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The output command of airmon-ng is:

Interface        Chipset         Driver

eth1             Intel 2200BG    ipw2200

wlan0            Atheros Ar9271  ath9k - [phy1]

putting it in monitor mode.

Interface        Chipset         Driver

eth1             Intel 2200BG    ipw2200

wlan0            Atheros Ar9271  ath9k - [phy1]
                                 (monitor mode enabled on mon0)

After that I use the command reaver -i mon0 -b c8:3a:35:33:xx:xx -a -S -N -c 11 
-vv -w which is giving the same EAPOL error. Then on other terminal I use 
command airodump-ng mon0 -d 00:13:CE:33:08:7C  -c 11 --ignore-negative-one 
which is showing nothing. On another terminal I uses the wash, which is showing 
output as:

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

BSSID                  Channel       RSSI       WPS Version       WPS Locked    
    ESSID
--------------------------------------------------------------------------------
-------------------------------
c8:3a:35:33:xx:xx      11            -69        1.0               No            
    Evxxxxxx

So suggest me what can I do. This error is showing on some APs. With my opinion 
this error mostly occurs on 3g usb dongles while others are working well. But 
help me on solving this problem. 

Original comment by mannankh...@gmail.com on 26 Mar 2014 at 5:41

[GoogleCodeExporter]

it seems that the module ath9k is not correct for this device.
check which module is loading with command:
# lsmod
locate if the ath9k_htc is present in the list.
or just have ath9k.

Original comment by deltomaf...@gmail.com on 27 Mar 2014 at 3:23

[GoogleCodeExporter]

It is locating ath9k_htc.

Original comment by mannankh...@gmail.com on 27 Mar 2014 at 6:48

[GoogleCodeExporter]

then check if the problem the firmware
/lib/firmware
download of http://wireless.kernel.org/download/htc_fw/1.3/
firmware htc_9271.fw put in /lib/firmware
reboot and test again.

Original comment by deltomaf...@gmail.com on 29 Mar 2014 at 1:07

[GoogleCodeExporter]

Showing same issue: 

I have also tried xiaopan and beini but facing same EAPOL issue.

Original comment by mannankh...@gmail.com on 30 Mar 2014 at 2:38

[GoogleCodeExporter]

although the signal level to be good
maybe some interference
try disable temporarily eth1:

eth1             Intel 2200BG    ipw2200

with:
# modprobe -r ipw2200

sure that airmon-ng not show eth1 more and test again.

Original comment by deltomaf...@gmail.com on 30 Mar 2014 at 10:05

[GoogleCodeExporter]

I have tried the command modprobe -r ipw2200. After that I uses command 
iwconfig, which is showing no wireless card accept wlan0. But when i try reaver 
it is again showing EAPOL error. Nothing changes.

Original comment by mannankh...@gmail.com on 31 Mar 2014 at 7:53

[GoogleCodeExporter]

ok! let's try using airmon-zc, install  ethtool and put wlan0 with airmon-zc:
# airmon-zc start wlan0 11
try Reaver again.
if not work then...try generate new interface ex: mon1 mon2.
run airmon-ng start wlan0 which changed the monitor interface to mon0.
running again airmon to change monitor interface number up one every time it's
done. for example running airmon-ng start wlan0 again would switch it to
mon2. just do that and the new interface should respond well to the router.
so try run Reaver with mon1 and specify the channel in command airmon-ng
# airmon-ng start wlan0 11
# reaver -i mon1 -b c8:3a:35:33:xx:xx -a -S -N -c <channel> -vv -w

Original comment by deltomaf...@gmail.com on 1 Apr 2014 at 12:16

[GoogleCodeExporter]

AP's often change their channel during attacks as a defence mechanism. When you 
use reaver don't put the -c option. Reaver will automatically hop channels and 
find the one the AP has gone to... 

Original comment by OcarinaI...@gmail.com on 10 Jan 2015 at 12:50