Jeff-Lewis / reaver-wps

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

I BIG TO EVERY ONE TO HELP ME #528

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 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.)
1.4

1. What operating system are you using (Linux is the only supported OS)?
Ubuntu 

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?
TP-LINK --WR741ND

5. What is the entire command line string you are supplying to reaver?
(sudo reaver -i mon0 -b XX:XX:XX:XX:XX -vv --no-nacks -A)

6. Please describe what you think the issue is.
Can't associate when SSID is not broadcasting ( Hidden )

7. Paste the output from Reaver below.

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

[+] Waiting for beacon from C0:C1:C0:A5:73:F7
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 11
[+] Associated with C0:C1:C0:A5:73:F7 (ESSID:XXXX)
[+] Trying pin 12345678
[+] Sending EPEAL REQUEST
[!] WARNING: Receive timeout occurred
[+] Sending EPEAL Requst
[!] WARNING: Receive timeout occurred
[+] Sending EPEAL RequstT
[!] WARNING: Receive timeout occurred
[+] Sending EPEAL Requst
[!] WARNING: Receive timeout occurred
[+] Sending EPEAL Requst
[!] WARNING: Receive timeout occurred
and So on >>> :(
----------------------------------
without the flag -A never will show ( failed to associate )

the router was cracked 1000 times until (SSID broadcasting) was Disabled
please help me i beg to all 

Original issue reported on code.google.com by mustafas...@gmail.com on 30 Jul 2013 at 5:22

GoogleCodeExporter commented 9 years ago
you tried opening two terminals?
1. run: aireplay-ng mon0 -1 120 -a 68:7F:74:E2:4A:1C -e kitty-Home
2. then: reaver -i mon0 -A -b 68:7F:74:E2:4A:1C -c 6 -vv --no-nacks 

Original comment by deltomaf...@gmail.com on 1 Aug 2013 at 6:07