[cha0s619]

Hello Everyone!

I'm wonding if performing a deauthentication attack - the kind that kicks everyone off of the wifi network - also affects the attacker. As in, can I kick out everyone from my work network and use all the bandwidth myself?

Unfortunately I can't test this myself yet as I am waiting for my new laptop to be delivered.

Thanks

---

So I read a comment on youtube that said that you don't even need to be connected to the wifi network to perform a deauth attack. So I'm figuring that it would also affect my machine should I be connected. Is there a way to prevent my machine from being affected while everyone else is kicked out?

---

Nothing yet??

From further research I believe everyone will be kicked out (including the attacker). Haven't heard this explicitly, but that's what I gather. So it begs the question, how can I kick everyone out but me. I've found something that looks like it might work, though haven't tried it myself, hopefully this will be useful for someone

https://forums.hak5.org/index.php?/topic...sing-mdk3/

[HomeSen]

You can use aireplay-ng from the aircrack-ng suite to deauthenticate each client individually:

Code:

aireplay-ng -0 <num> -a <AP MAC> -c <client MAC> <interface> -0 means "deauthenticate" <num> is the number of deauth packets to send (in most cases, 1 is enough to get the client kicked out) <AP MAC> is the access point's MAC address (also called: BSSID) <client MAC> is the client's (that you want to kick out) MAC address <interface> is the WiFi NIC's name that you want to use (e.g. "wlan0")

You can use airmon-ng to discover all connected clients
To keep those clients out you will, though, have to repeat the deauthentication "infinitely", since they otherwise simply (automatically) reconnect.
This will, at the same time, clutter up your WiFi's channel, and thus effectively lower your available bandwidth.[/code]

[cha0s619]

You can use aireplay-ng from the aircrack-ng suite to deauthenticate each client individually:

Code:

aireplay-ng -0 <num> -a <AP MAC> -c <client MAC> <interface> -0 means "deauthenticate" <num> is the number of deauth packets to send (in most cases, 1 is enough to get the client kicked out) <AP MAC> is the access point's MAC address (also called: BSSID) <client MAC> is the client's (that you want to kick out) MAC address <interface> is the WiFi NIC's name that you want to use (e.g. "wlan0")

You can use airmon-ng to discover all connected clients
To keep those clients out you will, though, have to repeat the deauthentication "infinitely", since they otherwise simply (automatically) reconnect.
This will, at the same time, clutter up your WiFi's channel, and thus effectively lower your available bandwidth.[/code]

Yeah. So I was thinking I could write a shell script to iterate through the list of connected MACs from the output of airmon-ng and feed that into aireplay to send the deauth packets.

[HomeSen]

Just make sure to either create the list before connecting to the AP your-self. Or remember to remove your MAC from the list, before iterating through all entries

I think that you can even add a small sleep after each iteration, since reconnection takes a few seconds, and that way you won't clutter the WiFi's channel with "useless" packets (since a deauth only works, when the client is connected; it can't be used to "interrupt" the connection establishing phase).

[Ex094]

Add your MAC address to the Whitelist and your device will not be attacked

[An1cetu5]

I'm fairly certain this "attack" is simply an inherent vulnerability in one of the protocols. I can link the RFC doc for 802.11 if anyone is interested and replies.

I believe only one user can be kicked off at time (or multiple simultaneously), but to achieve this is a simple packet is forged which pretends to be from the targets default gateway (router) which says it has been deauthenticated. Normally deauthenication packets proceed the clients request, but it's important to remember that these sessions are stateless and so it does not matter.

It's good to run a deauth attack to:

1. Capture handshakes to better crack the wireless passphrase.
2. Not all station IDs re transmitted in beacon frames, but they will *always* be when they reauthenticate.
3. DoS attack. This sounds like what you're trying to do.

Let me know if you need anymore help.