phukov87 / reaver-wps

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

Every time it is giving eapol error #626

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
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 commented 8 years ago
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 commented 8 years ago
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 commented 8 years ago
channel 1 ?? wash say channel 11.

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

GoogleCodeExporter commented 8 years ago
Giving the same issue on changing the channel to 11.

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

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
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 commented 8 years ago
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 commented 8 years ago
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 commented 8 years ago
what is the output of command:
# airmon-ng

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

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]