Reaver - Warning: Failed to associate with [BSSID] - (BT5 r3)

Hello,

So I just downloaded a LiveCD (r3) and decided to give Reaver a go on my Macbook Pro using an RT73 USB wireless device I had.

I booted into the GUI and identified my wireless card on wlan1

I then ran

Code:

---

airmon-ng start wlan1

---

to put it in monitor mode on mon0.

I used

Code:

---

airodump-ng wlan1

---

and picked the appropriate WPA encrypted MAC Address.

I ran reaver with

Code:

---

reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv

---

I got a bunch of

Code:

---

[!] WARNING: Failed to associate with xx:xx:xx:xx:xx:xx (ESSID: yyyyy)

---

I then tried another WPA network and received the same error six times, and then was told

Code:

---

[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: yyyyy)

---

However, after this output Reaver did not do anything else (I waited an hour).

I exited that request and ran it again. The same thing happened. It managed to associate after several failures and then didn't do anything.

I'm not sure I understand the concept of associating with an AP or why this is happening.

Does anyone have any suggestions?

Thank you.

This is probably more suited for the beginners sub-forum, but whatever.
Read up on how wireless networks and wireless authentication works. Without knowing the basics, you're never going to be able to do what you want to. Or at least, not well.
As for the issue you're getting. I've received the same problem, and I used aireplay-ng to handle the association, which seemed to fix the problem.
Hope that helps!

You can't check if an AP has WPS enabled, on Airodump-ng. You'll have to use "wash -i monX".

Is the AP security set to TKIP?
They seem to be a problem for reaver.

Quote:

---

Originally Posted by unicornfarmer

Hello,

So I just downloaded a LiveCD (r3) and decided to give Reaver a go on my Macbook Pro using an RT73 USB wireless device I had.

I booted into the GUI and identified my wireless card on wlan1

I then ran

Code:

---

airmon-ng start wlan1

---

to put it in monitor mode on mon0.

I used

Code:

---

airodump-ng wlan1

---

and picked the appropriate WPA encrypted MAC Address.

I ran reaver with

Code:

---

reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv

---

I got a bunch of

Code:

---

[!] WARNING: Failed to associate with xx:xx:xx:xx:xx:xx (ESSID: yyyyy)

---

I then tried another WPA network and received the same error six times, and then was told

Code:

---

[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: yyyyy)

---

However, after this output Reaver did not do anything else (I waited an hour).

I exited that request and ran it again. The same thing happened. It managed to associate after several failures and then didn't do anything.

I'm not sure I understand the concept of associating with an AP or why this is happening.

Does anyone have any suggestions?

Thank you.

---

First thing: the AP signal must be good, second: you must do << wash -i mon0 -C -s >> on your terminal to unsure that AP use WPS, third: river dose not work with TKIP auth.

wash -i mon0 doesn't always show every vulnerable router.

You must have a decent signal.

I can't say for sure it doesn't work with TKIP, but I can say it does work with AES+TKIP.

Some routers are somewhat pickier than others and alternative association methods (aireplay) are imperative to a successful attack

Check the power of the targeted AP..........!!!! in dB or in % then your wireless adapter must has good enough power to TX back to the victim AP!! maybe......



happy hunting!

Quote:

---

Originally Posted by unicornfarmer

Hello,

So I just downloaded a LiveCD (r3) and decided to give Reaver a go on my Macbook Pro using an RT73 USB wireless device I had.

I booted into the GUI and identified my wireless card on wlan1

I then ran

Code:

---

airmon-ng start wlan1

---

to put it in monitor mode on mon0.

I used

Code:

---

airodump-ng wlan1

---

and picked the appropriate WPA encrypted MAC Address.

I ran reaver with

Code:

---

reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv

---

I got a bunch of

Code:

---

[!] WARNING: Failed to associate with xx:xx:xx:xx:xx:xx (ESSID: yyyyy)

---

I then tried another WPA network and received the same error six times, and then was told

Code:

---

[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: yyyyy)

---

However, after this output Reaver did not do anything else (I waited an hour).

I exited that request and ran it again. The same thing happened. It managed to associate after several failures and then didn't do anything.

I'm not sure I understand the concept of associating with an AP or why this is happening.

Does anyone have any suggestions?

Thank you.

---

before the reaver try first
wash -i mon0
this will open all the routers that doesn't have WPS lock.
you are using airodump-ng mon0, yes you can see all the routers with in your range and their
BSSID and channels but you can never specify which one doesn't have a WPS lock.
NOTE: we can use only reaver to does routers that doesn't have WPS lock.

thats why,,,
first
wash -i mon0

then
reaver -i mon0 -c (channel) -b (bssid) -vv

if wps is NOT locked, will reaver crack the password 100% of the time?

Quote:

---

Originally Posted by Sohrab

if wps is NOT locked, will reaver crack the password 100% of the time?

---

Environmental factors aside; Yes. Although the time varies greatly.