Sorry, cant get it out of the VM I am running. I am using an alfa AWUS036nh, if that makes any difference, a few people mentioned it. I have read several articles on here all saying different solutions but none of them seem to work for me. reaver keeps trying the 12345670 pin over and over again always giving the exact same error as in the title 0x02. Please describe what you think the issue is. vv (have also tried -mac= -n -w and -a) 6. What is the entire command line string you are supplying to reaver? reaver -i mon0 -c 11 -b. What is the manufacturer and model # of the device you are trying to crack? linksys e2000 5. What is the signal strength of the Access Point you are trying to crack? -50 4. Is your wireless card in monitor mode (yes/no)? yes 3. What operating system are you using (Linux is the only supported OS)? backtrack 5 r3 2. What version of Reaver are you using? (Only defects against the latest version will be considered.) latest, just downloaded 1. Answer the following questions for every issue submitted: 0. Issue reports with pcap files attached will receive more serious consideration. Often times we need packet captures of mon0 while Reaver is running to troubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap). Please look through issues that have already been posted and make sure your question has not already been asked here: /reaver-wps/issues/list 4. model number, distance away, etc) about the device you are attacking then do not post your issue here. If you cannot answer basic questions (i.e. Using Reaver against access points you do not own or have permission to attack is illegal. If you do not know what monitor mode is then you should learn more about 802.11 hacking in linux before using Reaver. Reaver will only work if your card is in monitor mode. 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: 1.
Created by: GoogleCodeExporter A few things to consider before submitting an issue: 0.
0 kommentar(er)
