Hello there, I'm testing to break up AP with WPS rate check limiting but when I try followed command: Code: Select All reaver -i mon0 -b [AP MAC] -a -c 1 -e "[AP name]" -d 80 -T 1 -v ...I have got message that I have reach AP limiting rate Can anybody helps me what I should to do or what I have to try? Thx for any info.
Hello, firstly thx for your info a interesting... I tried it with two wireless card. The first one is integrated into my notebook. The second one is as a external USB device. Ralink RT2790 802.11n 1T/2R miniCard Wireless Network Adapter Realtek RTL8187(b or l -- I don't know that exactly) Signal is quite strength - about 80%. Thx alot for any information that could help...
It depends on the router sometimes you can get locked out for 5 min sometimes you have to reset the router, can be done with mdk. You can try Code: Select All --ignore-locks or reduce pins per second, you can also capture a clients mac address fake your mac "with macchanger" and try then.
to Mr. Penguin: 80% (not -80). to meknb: What is please mdk and macchanger? It's some tools which contain xiaopan os? I think that macchanger is some kind of tool to get info about AP's connected clients... right? Anyway thx for your patience, both of you.
Yer i think there on xiaopan just search here or google them how to use, macchanger does what it says changes mac address, mdk murder death kill can reboot routers amongst other things.
Hello again... so firstly I try Code: Select All --ignore-locks but reaver sends only one PIN again and again... Another trying is followed command: Code: Select All reaver -i mon0 -b [AP MAC] -a -c 1 -e "[AP name]" -d 15 -l 315 -v but seems to AP sends me info about rate limiting and have to wait 315 sec. After that another rate limiting message will appear and have to wait 315 sec again and again... Before any attempt I use macchanger to generate random MAC and use it before trying penetrating. --- Double Post Merged, 28 Mar 2013 --- Hmmm... nobody has any idea?
AP rate limiting is a feature of the access point you are testing. Manufactures are employing more and more features to defeat this type of testing . Both Reaver and the access point are responding correctly. Basically you are going to have to be patient for this access point. This line -a -v -s -x 20 -v 100:10 -l 300 is the default used by Minidwep and works very well . The last argument is the d 15 argument. This will set the delay between pin attempts with a value of like 15 to see if that prevents triggering the AP limit. Probably not and if that is the case then remove the delay and be patient. It could be worse some APs lock out for 24 hours or more. Here is a list of arguments that can be added to the Reaver command line : -l Set the time to wait if the AP locks WPS pin attempts -x Set the time to sleep after 10 unexpected failures -v Real time progress -vv Verbose mode that shows detailed progress / errors. Great for troubleshooting -p Specify 4 or 8 digits of the pin -t Receive timeout period -d Set the delay between pin attempts -t Receive timeout period -T Set the M5 / M7 timeout period -r Load previous session -n --nack -A --no associate (you still will need aireplay or something to associate. E.g: new window) -w --win7 -L --ignore-locks -E --eap-terminate -N --no-nacks -S --dh-small -c --fix interface channel. I.e: select channel -s --scan mode -C --ignore frame checksum errors (select if finding no APs) -5 --search 5Ghz channels
