search

donjony / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

Reaver Not Working on Most of Zyxel Routers. #712

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
A few things to consider before submitting an issue:

0. We write documentation for a reason, if you have not read it and are
having problems with Reaver these pages are required reading before
submitting an issue:
http://code.google.com/p/reaver-wps/wiki/HintsAndTips
http://code.google.com/p/reaver-wps/wiki/README
http://code.google.com/p/reaver-wps/wiki/FAQ
http://code.google.com/p/reaver-wps/wiki/SupportedWirelessDrivers
1. Reaver will only work if your card is in monitor mode.  If you do not
know what monitor mode is then you should learn more about 802.11 hacking
in linux before using Reaver.
2. Using Reaver against access points you do not own or have permission to
attack is illegal.  If you cannot answer basic questions (i.e. model
number, distance away, etc) about the device you are attacking then do not
post your issue here.  We will not help you break the law.
3. Please look through issues that have already been posted and make sure
your question has not already been asked here: http://code.google.com/p
/reaver-wps/issues/list
4. Often times we need packet captures of mon0 while Reaver is running to
troubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap).  Issue
reports with pcap files attached will receive more serious consideration.

Answer the following questions for every issue submitted:

0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)
Reaver 1.5/1.4
1. What operating system are you using (Linux is the only supported OS)?
Linux Mint/Kali Linux
2. Is your wireless card in monitor mode (yes/no)?
yes
3. What is the signal strength of the Access Point you are trying to crack?
-70
4. What is the manufacturer and model # of the device you are trying to
crack?
Zyxel F4:3E:61:XX:XX:XX
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b [bssid] -vv
6. Please describe what you think the issue is.
i tried reaver on My Router and getting the Below Output and when i try reaver 
attack on my Friend's Router again same output. But the WPS/WSC enabled and 
having this issue only with Zyxel Routers (Whose Bssid F4:3E:61:XX:XX:XX). i 
Tried Bully But still No Luck , Getting Unexpected Packet Recieve Error.. (i 
tried every available command and method available on Google but no Luck.. :(  
)  (Zyxel Routers are Pretty Cheap , i think it would be good if developer 
purchase it and check by it's own)
(See the Link Below for ScreenShot of Bully and Router WPS configuration)

http://i.imgur.com/uSdk9wE.png
http://i.imgur.com/NngbBZ7.png

Thanks in Advance.

7. Paste the output from Reaver below.

reaver -i mon0 -b F4:3E:61:9C:80:xx -vv
Reaver v1.5 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>
[+] Waiting for beacon from F4:3E:61:9C:80:xx
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: (null))
[+] Switching mon0 to channel 11
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Associated with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Starting Cracking Session. Pin count: 0, Max pin attempts: 11000
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Nothing done, nothing to save.
[+] 0.00% complete. Elapsed time: 0d0h0m8s.
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[!] WARNING: 10 failed connections in a row
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Nothing done, nothing to save.
[+] 0.00% complete. Elapsed time: 0d0h0m15s.
[+] Trying pin 12345670.
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[!] WARNING: Failed to associate with F4:3E:61:9C:80:xx (ESSID: TOILET)
[+] Sending EAPOL START request
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670.
^C
[+] Nothing done, nothing to save.

Original issue reported on code.google.com by furqanha...@gmail.com on 14 Mar 2015 at 5:55

GoogleCodeExporter commented 8 years ago 
try with -A option and some times with triple -v

reaver -i mon0 -b xx:xx:xx:xx:xx -A -vv
reaver -i mon0 -b xx:xx:xx:xx:xx -v -v -A -vv

Original comment by deltomaf...@gmail.com on 8 Aug 2015 at 11:15