{"action":"created","issue":{"url":"https://api.github.com/repos/chrsmith/reaver-wps/issues/142","labels_url":"https://api.github.com/repos/chrsmith/reaver-wps/issues/142/labels{/name}","comments_url":"https://api.github.com/repos/chrsmith/reaver-wps/issues/142/comments","events_url":"https://api.github.com/repos/chrsmith/reaver-wps/issues/142/events","html_url":"https://github.com/chrsmith/reaver-wps/issues/142","id":59191931,"number":142,"title":"r92 stops trying PINs after a few minutes","user":{"login":"GoogleCodeExporter","id":9614759,"avatar_url":"https://avatars.githubusercontent.com/u/9614759?v=3","gravatar_id":"","url":"https://api.github.com/users/GoogleCodeExporter","html_url":"https://github.com/GoogleCodeExporter","followers_url":"https://api.github.com/users/GoogleCodeExporter/followers","following_url":"https://api.github.com/users/GoogleCodeExporter/following{/other_user}","gists_url":"https://api.github.com/users/GoogleCodeExporter/gists{/gist_id}","starred_url":"https://api.github.com/users/GoogleCodeExporter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GoogleCodeExporter/subscriptions","organizations_url":"https://api.github.com/users/GoogleCodeExporter/orgs","repos_url":"https://api.github.com/users/GoogleCodeExporter/repos","events_url":"https://api.github.com/users/GoogleCodeExporter/events{/privacy}","received_events_url":"https://api.github.com/users/GoogleCodeExporter/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/chrsmith/reaver-wps/labels/auto-migrated","name":"auto-migrated","color":"ededed"},{"url":"https://api.github.com/repos/chrsmith/reaver-wps/labels/Priority-Triage","name":"Priority-Triage","color":"ededed"},{"url":"https://api.github.com/repos/chrsmith/reaver-wps/labels/Type-Defect","name":"Type-Defect","color":"ededed"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-02-27T05:24:14Z","updated_at":"2015-02-27T05:24:15Z","closed_at":"2015-02-27T05:24:15Z","body":"```\nA few things to consider before submitting an issue:\n\n0. We write documentation for a reason, if you have not read it and are\nhaving problems with Reaver these pages are required reading before\nsubmitting an issue.\n1. Reaver will only work if your card is in monitor mode.  If you do not\nknow what monitor mode is then you should learn more about 802.11 hacking\nin linux before using Reaver.\n2. Using Reaver against access points you do not own or have permission to\nattack is illegal.  If you cannot answer basic questions (i.e. model\nnumber, distance away, etc) about the device you are attacking then do not\npost your issue here.  We will not help you break the law.\n3. Please look through issues that have already been posted and make sure\nyour question has not already been asked here: http://code.google.com/p\n/reaver-wps/issues/list\n4. Often times we need packet captures of mon0 while Reaver is running to\ntroubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap).  Issue\nreports with pcap files attached will receive more serious consideration.\n\nAnswer the following questions for every issue submitted:\n\n0. What version of Reaver are you using?  (Only defects against the latest\nversion will be considered.)\n\nLatest svn r92.  The error was not manifested on my previous version r90.\n\n1. What operating system are you using (Linux is the only supported OS)?\n\nUbuntu 11.10\n\n2. Is your wireless card in monitor mode (yes/no)?\n\nCard is in monitor mode w/ airmon-ng start wlan0 and capture was already \nongoing on mono using reaver r90.\n\n3. What is the signal strength of the Access Point you are trying to crack?\n\nSignal strength is admittedly very low (~ -82 dBm).  But PINs are successfully \nnegotiated and the process did not stop on r90, just a few repeated trials on \nthe same PIN every now and then, and successfully continued to 64%.\n\n4. What is the manufacturer and model # of the device you are trying to\ncrack?\n\nIt is an old D-Link AP, but I am not sure about the model number.\n\n5. What is the entire command line string you are supplying to reaver?\n\n sudo reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv -c x -a\n(with masked MAC and channel)\n\n6. Please describe what you think the issue is.\n\nReaver gives up and returns to the command line with any error or warning.  It \nquits every time a run it.  And the time from execution to quit is \napproximately the same every time, possibly the same number of PIN tests.  See \noutput with -v to see how many PINs are tried before quitting.  Not a lot of \nPINs tried before quitting.  Again, previous version r90 was not quitting.\n\n7. Paste the output from Reaver below.\n\nAs soon as I updated to svn r92 I noticed that the ongoing process would stop \nand reaver would quit without any warning messages, just back to the command \nline.  So I added the second -v to get a more detailed output and it did it \nagain.  Here is the output with -vv.\n\n[+] Sending WSC NACK\n[+] Trying pin 70355673\n[+] Sending EAPOL START request\n[!] WARNING: Receive timeout occurred\n[+] Sending EAPOL START request\n[!] WARNING: Receive timeout occurred\n[+] Sending EAPOL START request\n[+] Sending identity response\n[+] Received M1 message\n[+] Sending M2 message\n[+] Received M3 message\n[+] Sending M4 message\n[+] Received WSC NACK\n[+] Sending WSC NACK\n[+] Trying pin 33665672\n[+] Sending EAPOL START request\n[!] WARNING: Receive timeout occurred\n[+] Sending EAPOL START request\n[!] WARNING: Receive timeout occurred\n[+] Sending EAPOL START request\n[+] Sending identity response\n[+] Received M1 message\n[+] Sending M2 message\n[+] Received M1 message\n[+] Sending M2 message\n[+] Received M3 message\nmyname@vubuntu:~/src/reaver$\n\nAnd here is the output with just one -v (longer period of time):\n\nReaver v1.4 WiFi Protected Setup Attack Tool\nCopyright (c) 2011, Tactical Network Solutions, Craig Heffner \n<cheffner@tacnetsol.com>\n\n[+] Restored previous session\n[+] Waiting for beacon from xx:xx:xx:xx:xx:xx\n[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: xxxxxxxxxx)\n[+] Trying pin 21155673\n[+] Trying pin 23735675\n[+] Trying pin 34935675\n[+] Trying pin 70355673\n[+] Trying pin 33665672\n[+] Trying pin 85885677\n[+] 64.93% complete @ 2012-01-16 02:21:13 (10 seconds/attempt)\n[+] Trying pin 71325675\n[+] Trying pin 02955674\n[+] Trying pin 02955674\n[+] Trying pin 02955674\n[+] Trying pin 67965670\n[+] 64.95% complete @ 2012-01-16 02:22:08 (13 seconds/attempt)\n[+] Trying pin 06395674\nmyname@vubuntu:~/src/reaver$\n\nAnd, here is a second, consecutive run with -v (showing about same length \nbefore quitting):\n\n[+] Restored previous session\n[+] Waiting for beacon from xx:xx:xx:xx:xx:xx\n[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: xxxxxxxxxx)\n[+] Trying pin 26275673\n[+] Trying pin 20485672\n[+] Trying pin 23455672\n[+] Trying pin 94765670\n[+] Trying pin 42505679\n[+] Trying pin 93525671\n[+] 65.03% complete @ 2012-01-16 02:29:43 (9 seconds/attempt)\n[+] Trying pin 17005678\n[+] Trying pin 64955674\n[+] Trying pin 62695671\n[+] Trying pin 60345677\n[+] Trying pin 57175676\n[+] 65.07% complete @ 2012-01-16 02:30:06 (7 seconds/attempt)\n[+] Trying pin 56065671\nmyname@vubuntu:~/src/reaver$ \n\n\n```\n\nOriginal issue reported on code.google.com by `vsil...@gmail.com` on 16 Jan 2012 at 8:36"},"comment":{"url":"https://api.github.com/repos/chrsmith/reaver-wps/issues/comments/76337507","html_url":"https://github.com/chrsmith/reaver-wps/issues/142#issuecomment-76337507","issue_url":"https://api.github.com/repos/chrsmith/reaver-wps/issues/142","id":76337507,"user":{"login":"GoogleCodeExporter","id":9614759,"avatar_url":"https://avatars.githubusercontent.com/u/9614759?v=3","gravatar_id":"","url":"https://api.github.com/users/GoogleCodeExporter","html_url":"https://github.com/GoogleCodeExporter","followers_url":"https://api.github.com/users/GoogleCodeExporter/followers","following_url":"https://api.github.com/users/GoogleCodeExporter/following{/other_user}","gists_url":"https://api.github.com/users/GoogleCodeExporter/gists{/gist_id}","starred_url":"https://api.github.com/users/GoogleCodeExporter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GoogleCodeExporter/subscriptions","organizations_url":"https://api.github.com/users/GoogleCodeExporter/orgs","repos_url":"https://api.github.com/users/GoogleCodeExporter/repos","events_url":"https://api.github.com/users/GoogleCodeExporter/events{/privacy}","received_events_url":"https://api.github.com/users/GoogleCodeExporter/received_events","type":"User","site_admin":false},"created_at":"2015-02-27T05:24:15Z","updated_at":"2015-02-27T05:24:15Z","body":"```\nReaver is actually seg faulting. Had the same thing happen to me last night, \nlooking in to it now. Appears to happen after re-transmitting the M2 packet and \nwhile trying to build an M4 packet.\n```\n\nOriginal comment by `cheff...@tacnetsol.com` on 16 Jan 2012 at 12:10\n* Changed state: **Started**"}}