satana77 Posted April 9, 2013 Share Posted April 9, 2013 I start to think that my MK4 is broken,reflashed many-many times different firmware versions and Rever still "Waiting for beacon" no matter how to start it through web UI or ssh. Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted April 9, 2013 Share Posted April 9, 2013 I start to think that my MK4 is broken,reflashed many-many times different firmware versions and Rever still "Waiting for beacon" no matter how to start it through web UI or ssh. This module hasn't been updated in a long time. I doubt it is your pineapple. Try the command line. Quote Link to comment Share on other sites More sharing options...
demonjester Posted April 9, 2013 Share Posted April 9, 2013 (edited) I start to think that my MK4 is broken,reflashed many-many times different firmware versions and Rever still "Waiting for beacon" no matter how to start it through web UI or ssh. I also forgot to ask are you sure you are choosing a router that has the wps feature? Cause I know hackrylix is using airodump-ng to do the access point scan and not using wash to do the scan. and airodump scans for all ap and wash only scans for wps featured ap Edited April 9, 2013 by demonjester Quote Link to comment Share on other sites More sharing options...
kevambert Posted April 9, 2013 Share Posted April 9, 2013 (edited) I just tested you have to bring down wlan0, if you ssh in and issue airmon-ng start wlan0 ifconfig wlan0 down and then run reaver from the gui it will work Edit: another option is go to the gui/reaver-module scan for and select the AP you want to attack, start mon0 and then disable wlan0 then click attack. Edited April 9, 2013 by kevambert Quote Link to comment Share on other sites More sharing options...
demonjester Posted April 9, 2013 Share Posted April 9, 2013 I just tested you have to bring down wlan0, if you ssh in and issue airmon-ng start wlan0 ifconfig wlan0 down and then run reaver from the gui it will work Edit: another option is go to the gui/reaver-module scan for and select the AP you want to attack, start mon0 and then disable wlan0 then click attack. Yep, I mentioned this on page 5 or 6 Quote Link to comment Share on other sites More sharing options...
satana77 Posted April 9, 2013 Share Posted April 9, 2013 Still warnings and "Failed to associate with......" Tried to do all above. Quote Link to comment Share on other sites More sharing options...
satana77 Posted April 9, 2013 Share Posted April 9, 2013 (edited) This module hasn't been updated in a long time. I doubt it is your pineapple. Try the command line. Tried many times. And what may be wrong with MK4? PS http://code.google.com/p/reaver-wps/issues/detail?id=46 a lot of people have this trouble Edited April 9, 2013 by satana77 Quote Link to comment Share on other sites More sharing options...
satana77 Posted April 9, 2013 Share Posted April 9, 2013 (edited) I also forgot to ask are you sure you are choosing a router that has the wps feature? Cause I know hackrylix is using airodump-ng to do the access point scan and not using wash to do the scan. and airodump scans for all ap and wash only scans for wps featured ap I'm sure about wps because tried that AP with reaver on nokia N900. Strange that airodump-ng catches Beacons(ssh),wash can detect wps enabled APs(ssh), but reaver(ssh and gui)....is cursed. Edited April 9, 2013 by satana77 Quote Link to comment Share on other sites More sharing options...
demonjester Posted April 10, 2013 Share Posted April 10, 2013 Satana can you provide detailed steps that you take? Also you said warnings in a earlier post, what kind of warnings? Could help us narrow this down. Quote Link to comment Share on other sites More sharing options...
satana77 Posted April 11, 2013 Share Posted April 11, 2013 "Warning:Failed to associate to ......" 1)Install reaver module on usb 2)install reaver on usb from the module page 3)Disable AP from status page 4)enable wlan0 on reaver page 5)start mon0 from page 6)scan APs,choose target 7)disable wlan0 8)Start attack Three last steps were advised earlier. And wash is working after disabling wlan0. Quote Link to comment Share on other sites More sharing options...
demonjester Posted April 11, 2013 Share Posted April 11, 2013 To be honest I have couple of things. 1. The ap will refuse to associate with you (uknown reasons this has happened to me before) did you try different wps enabled access point? Quote Link to comment Share on other sites More sharing options...
satana77 Posted April 12, 2013 Share Posted April 12, 2013 Yes ,i tried brute forcing 3 different APs with enabled wps,that i cracked before. One of them mine.(enabled wps for testing) Quote Link to comment Share on other sites More sharing options...
demonjester Posted April 12, 2013 Share Posted April 12, 2013 To be honest I have no idea. Like I said usually wps routers will a while refuse to receive keys. Quote Link to comment Share on other sites More sharing options...
TwistedPacket Posted April 12, 2013 Share Posted April 12, 2013 I am getting a libpcap error via ssh what could be wrong? Quote Link to comment Share on other sites More sharing options...
satana77 Posted April 13, 2013 Share Posted April 13, 2013 is there any TEch Support?reaver is what i need. MK4 will be perfect for hidding in a dark corner for a long time with battery pack and reaver running. Quote Link to comment Share on other sites More sharing options...
TwistedPacket Posted April 13, 2013 Share Posted April 13, 2013 is there any TEch Support?reaver is what i need. MK4 will be perfect for hidding in a dark corner for a long time with battery pack and reaver running. Have you tried to run it from the command line? Quote Link to comment Share on other sites More sharing options...
demonjester Posted April 13, 2013 Share Posted April 13, 2013 Ya he has. I run it on cli just fine. Satana provide video of what you do. If you can. Quote Link to comment Share on other sites More sharing options...
satana77 Posted April 15, 2013 Share Posted April 15, 2013 ok.i will. Quote Link to comment Share on other sites More sharing options...
deviney Posted April 26, 2013 Share Posted April 26, 2013 (edited) Am having the same problem! am forever on the waiting for beacon :( tried just about everything... really want reaver too. Has anyone found the cause? Iv tried with the inbuilt AP and with a Alfa card, i either get constant channel hopping or if i use the non hop option i get waiting for beacon for a infinite time Edited April 26, 2013 by deviney Quote Link to comment Share on other sites More sharing options...
demonjester Posted April 26, 2013 Share Posted April 26, 2013 Am having the same problem! am forever on the waiting for beacon :( tried just about everything... really want reaver too. Has anyone found the cause? Iv tried with the inbuilt AP and with a Alfa card, i either get constant channel hopping or if i use the non hop option i get waiting for beacon for a infinite time are you doing it through the GUI or CLI Quote Link to comment Share on other sites More sharing options...
deviney Posted April 26, 2013 Share Posted April 26, 2013 (edited) are you doing it through the GUI or CLI I am using the GUI, its even managed to associate with the AP but it wont try pins now :o This would be such a good tool if it worked. How do you use the CLI because if you go to advanced an used reaver -i mon0 -b (MAC) -vv it would not show output as screen :/ Also everyone who has posted a pic seems to have their logs going to USB??? how did they change it to that? Edited April 26, 2013 by deviney Quote Link to comment Share on other sites More sharing options...
demonjester Posted April 27, 2013 Share Posted April 27, 2013 Here is enough things to remember, when you use the scan in the GUI it does a regular scan it will scan all access points not just wps only scans. If you're using 2 second refresh rate switch it to 5 seconds, and enable it. Quote Link to comment Share on other sites More sharing options...
airman_dopey Posted May 29, 2013 Share Posted May 29, 2013 (edited) Has anyone else worked out the "failed to associate" issue with Reaver? I have tried the following: Firmware at 2.8.1 stable Installed the reaver 0.4 module ~In Module~ Stopped wlan0 started wlan0 started mon0 scanned for APs selected my AP (WPS enabled, good signal) Selected auto detect and set channel choices Started attack At this point I get the failed to associate message. So I switched to the CLI via SSH. ~CLI~ ifconfig wlan0 down airmon-ng start wlan0 ifconfig wlan0 up ifconfig mon0 down ifconfig mon0 up reaver -i mon0 -b XX:XX:XX:XX:XX:XX -a -c 11 -vv and I get failed to associate. So I tried using aireplay-ng ~CLI~ aireplay -1 5 (or 120) -a XX:XX:XX:XX:XX:XX -e ESSID mon0 comes back with "could not determine channel". Tried setting channel by dropping wlan0 and changing it using "iw wlan0 set channel 11" and still nothing. Tried doing the same for mon0 but regardless of the interface being up or down the interface states that it is busy when I try to change the channel of mon0. At this point I am completely out of ideas. Any ideas? *edit* I have also tried using the exact same reaver command on my Kali build running side by side and the reaver attack through Kali works fine. So I know my AP is not immune to the attack Edited May 29, 2013 by airman_dopey Quote Link to comment Share on other sites More sharing options...
SymPak Posted May 30, 2013 Share Posted May 30, 2013 I prefer using reaver and wash from terminal. I have had better luck this way. The commands I use are: airmon-ng start wlan0 ifconfig wlan0 down wash -i mon0 reaver -i mon0 -b XX:XX:XX:XX:XX:XX -a -c XX -vv If you don't know what wash does, it displays only WPS enabled access points. Hope this helps. -SymPak Quote Link to comment Share on other sites More sharing options...
airman_dopey Posted May 30, 2013 Share Posted May 30, 2013 (edited) I prefer using reaver and wash from terminal. I have had better luck this way. The commands I use are: airmon-ng start wlan0 ifconfig wlan0 down wash -i mon0 reaver -i mon0 -b XX:XX:XX:XX:XX:XX -a -c XX -vv If you don't know what wash does, it displays only WPS enabled access points. Hope this helps. -SymPak Thank you for your response. I tried following your commands and get the same thing. When I leave wlan0 up the "failed to associate" messages appear approx. once every 10-12 seconds. With having wlan0 down and only mon0 up the failed messages spam every second. With that being said, wash displays the proper APs in my area properly. I think I am going to attempt to reflash my pineapple and start over and see if that makes a difference. *EDIT* Reflashed, did an opkg update, opkg install reaver, and then ran the commands listed above, same thing. Tried bringing wlan0 back up, no change (other than the time between error messages again). *EDIT 2* Tried on a seperate AP and same result. Edited May 30, 2013 by airman_dopey Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.