Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

Wireless How To

Verifying the deauth

While void11 is running on Auditor-B, let's look at what's happening on the Target client. Normally, anyone using a Target client will be happily be surfing websites or checking email, when suddenly the network will get very slow and eventually come to a halt. A few seconds later, the Target will be completely disconnected from the network.

You can check this out for yourself by running a continuous ping from TARGET to the wireless access point. Figures 7 and 8 show a ping before and during a void11 deauth attack.

Successful pings before void11

Figure 7: Successful pings before void11
(click image to enlarge

Figure 8 shows that the pings will time out while void11 is running. If you do a Control-C on Auditor-B to stop the void11 attack, the pings will come back to life after a few seconds.

Pings die after void11 is started

Figure 8: Pings die after void11 is started
(click image to enlarge)

You can see if you are being deauthenticated from an AP by looking at your wireless client's utility program, which usually indicates the connection status. Figures 9 and 10 show the wireless client utility built into Windows WP. Before the void11 attack starts, everything will seem normal, and Windows will show that you are connected to the AP (Figure 9).

Now you are connected

Figure 9: Now you are connected

After void11 starts, the network status will change from connected to disconnected (Figure 10). After void11 is stopped on Auditor-B, the Target will reconnect back to the AP in a few seconds or so.

Now you aren't!

Figure 10: Now you aren't!
(click image to enlarge)

If you look back at Auditor-A - which we last left running airodump - while void11 is running, the IV count in airodump should increase to around 100-200 with a few seconds. This is due to the traffic generated by the Target client as it repeatedly tries to reassociate with its AP.

More Wireless

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

Device: RT-N66UFirmware: 380.69Hello everyone,i attached a tp-link access point to my router and created vlans for several SSIDs.In addition i would l...
Hello, I'm looking for advice for the build in the subject line. I'm a landscape architect starting my own small office. It will be two people at firs...
Is this ok to do ? Also allow only specified ip address.I want to do this my for cousins so i don't have to go over there every time.I notice the 86u ...
Hi,I want to assign my virtual machines to a certain dhcp range.I have been playing around with dnsmasq.conf.add but cant get it to work.This is what ...
Hi allIt seems that devices on 5G-1 and 5G-2 cannot "see" each other.On Wireshark it seems some packets can't traverse from one 5G band to the other. ...

Don't Miss These

  • 1
  • 2
  • 3