Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: Reaver -- stucked at "Associated with bssid"

  1. #1
    Junior Member
    Join Date
    Jul 2013
    Posts
    11

    Reaver -- stucked at "Associated with bssid"

    Hi,

    when I crack WPS, Reaver is showing up this message: "Associated with XX:XX:XX:XX:XX" and it's just stucked like that forever.
    How to fix it?

  2. #2
    Junior Member
    Join Date
    Jul 2013
    Posts
    11

    Exclamation

    Quote Originally Posted by stagg250 View Post
    Hi,

    when I crack WPS, Reaver is showing up this message: "Associated with XX:XX:XX:XX:XX" and it's just stucked like that forever.
    How to fix it?
    C'MON, guys, it's really a hurry...
    It's TP Link WN722N involved, a Kali Linux 1.0.7. with Reaver 1.3.

  3. #3
    Junior Member
    Join Date
    Jul 2014
    Posts
    1
    Reaver 1.3 is not newest version, first try with Reaver 1.4 or better: https://code.google.com/p/reaver-wps-fork/. You could also try Bully https://github.com/bdpurcell/bully.

    Run reaver & bully in verbose modes and paste output.

  4. #4
    Junior Member
    Join Date
    Mar 2013
    Location
    Root
    Posts
    13
    Try updating reaver to the newest version 1.0.4
    https://code.google.com/p/reaver-wps/downloads/list

  5. #5
    Junior Member
    Join Date
    Jul 2013
    Posts
    11
    Thanks zerocool for a reply.
    In my previous post, I accidentally wrote "Reaver 1.3", as I already have version 1.0.4 installed (pre-installed with Kali Linux 1.0.7). So I am already cracking with lastest version of Reaver, 1.4. To emphasize, commands I'm using are standard Reaver commands:
    reaver -i monX -b XX:XX:XX:XX:XX -c X -vv

    What is the problem?

  6. #6
    Junior Member
    Join Date
    Jul 2013
    Posts
    11
    I forgot to mention, I have tried to associate with
    aireplay-ng mon0 -1 120 -a <XX:XX:XX:XX:XX> -e <AP_NAME>
    and after that run
    reaver -i monX -b XX:XX:XX:XX:XX -c X -vv

    but that also results with nothing - Reaver is just stucked at "Associated with XX:XX:XX:XX:XX" forever.

  7. #7
    Junior Member
    Join Date
    Jul 2013
    Posts
    11
    Oh c'mon guys, 211 views and nothing!
    Give me at least something, something else to try, some other commands or whatever...

    Where is the problem so Reaver is not trying PINs at all, just associated with AP!?

  8. #8
    Senior Member
    Join Date
    Jun 2013
    Posts
    125
    Quote Originally Posted by stagg250 View Post
    Oh c'mon guys, 211 views and nothing!
    Give me at least something, something else to try, some other commands or whatever...

    Where is the problem so Reaver is not trying PINs at all, just associated with AP!?
    it could be a library module pre-installed with kali and related to reaver is causing some confusion..try removing reaver
    #remove reaver
    apt-get remove reaver

    #install reaver from google site and download to your root/home folder
    wget http://code.google.com/p/reaver-wps/...ver-1.4.tar.gz

    #navigate to root/home folder and extract reaver
    cd ~ && tar -xvf reaver-1.4.tar.gz

    #install reaver
    cd reaver-1.4/src/
    ./configure && make && make install

    Now run reaver

    NOTE
    check to see if you bring your wireless adapter interface down before trying the above steps
    Last edited by repzeroworld; 2014-07-13 at 03:07 PM.

  9. #9
    Junior Member
    Join Date
    Jul 2013
    Posts
    11
    I have done all this steps, tried again - and guess what - nothing again!
    Again, the Reaver is just stucked at "ASSOCIATED WITH XX:XX:XX:XX:XX" forever.
    http://i.imgur.com/eSSKuTs.png

  10. #10
    Senior Member
    Join Date
    Jun 2013
    Posts
    125
    Quote Originally Posted by stagg250 View Post
    I have done all this steps, tried again - and guess what - nothing again!
    Again, the Reaver is just stucked at "ASSOCIATED WITH XX:XX:XX:XX:XX" forever.
    http://i.imgur.com/eSSKuTs.png
    you tried bringing your wireless adapter interface down a couple of times?

    ifconfig <wireless adapter name> down
    also try killing Network Manager
    killall NetworkManager

Posting Permissions

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