[Reaver "AP rate limiting detected" and automatic mdk3 solution]

The EAPOL Start attack seems to be ineffective against the newer TP-Link routers. I tried it against an Archer8 type and although I sent about 40000 packages on each interface, the router just kept happily going.

So it would seem that the manufacturers has found a way to protect against this kind of attack.

 

Btw, the script seems to work flawlessly on my machine with the new editions.

[Reaver "AP rate limiting detected" and automatic mdk3 solution]

I would like to offer the following humle recommendations for the ReVdK3-r2.sh script.

First is the section where we create the three new monitor segments. The problem is that the wlan0mon is defined, which is silly since we already define WLAN as a string.

So I changed this:

airmon-ng start wlan0;
iw wlan0mon interface add mon0 type monitor & iw wlan0mon interface add mon1 type monitor & iw wlan0mon interface add mon2 type monitor;

 

to this:

airmon-ng start $WLAN;

WLANxMON=$WLAN
WLANxMON+="mon"

iw $WLANxMON interface add mon0 type monitor & iw $WLANxMON interface add mon1 type monitor & iw $WLANxMON interface add mon2 type monitor;

 

The same problem arise when we want to spoof the mac address. Again we have a segment where the wlanXmon is predefined for us (which is a problem if we use wlan1)

WLAN='wlan0mon';
MON1='mon0';
MON2='mon1';
MON3='mon2';

which can be changed to this:

WLAN=$WLANxMON;
MON1='mon0';
MON2='mon1';
MON3='mon2';

I would also like to suggest a replacement where this

macchanger -m '78:03:40:02:94:8f' "$WLAN"> /dev/null;
macchanger -m '78:03:40:02:94:8f' "$MON1"> /dev/null;
macchanger -m '78:03:40:02:94:8f' "$MON2"> /dev/null;
macchanger -m '78:03:40:02:94:8f' "$MON3"> /dev/null;

can be replaced with this

macchanger -a "$WLAN"> /dev/null;
macchanger -a "$MON1"> /dev/null;
macchanger -a "$MON2"> /dev/null;
macchanger -a "$MON3"> /dev/null;

but this is only relevant in the case where we want all the macs to be different. Furthermore, I am not that well into the mdk3 code so I am not sure whether it is mandatory to have the same mac on all three monitors.