> 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/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests/beacon-flood-mode-attack.md).

# 信标洪泛模式攻击

分析在限定范围无线评估中信标洪泛的影响。

接入点会广播信标帧来宣传无线网络。客户端使用这些帧来发现可用网络并进行连接。

信标泛洪会在某个信道上广播大量伪造的信标帧。这些帧可以宣传多个网络名称并占用空口时间。

{% hint style="warning" %}
在运行信标泛洪测试之前，请确认目标信道、受影响设备、授权以及恢复窗口。该技术可能会干扰附近的无线网络。
{% endhint %}

### 创建网络名称列表

创建一个包含测试网络名称的文本文件：

{% code overflow="wrap" %}

```bash
for i in $(seq 1 10); do echo "whoami$i" >> whoami.txt ;done
```

{% endcode %}

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2F39WOM6Q4QzKH8SMUjTMx%2F%7BD0129F22-A742-423B-A387-175DB8E3B4D1%7D.png?alt=media&amp;token=b7686964-99e1-4eb5-891c-d1ea6a878852" alt=""><figcaption></figcaption></figure>

### 在某个信道上广播测试信标

使用 `mdk3` 在信道 4 上宣传测试网络名称：

{% code overflow="wrap" %}

```bash
mdk3 wlan0mon b -f whoami.txt -a -s 1000 -c 4
```

{% endcode %}

所宣传的测试网络会出现在客户端的可用网络列表中。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fv3rGRAgPDKhLaUepiI3u%2FWhatsApp%20Image%202026-08-06%20at%209.37.40%20PM.jpeg?alt=media&amp;token=48ae292b-a93c-4d4a-b104-e13fdbe2af5b" alt="" width="370"><figcaption></figcaption></figure>

### 在没有名称列表的情况下广播

你也可以在不指定网络名称文件的情况下运行测试：

{% code overflow="wrap" %}

```bash
mdk3 wlan0mon b -c 4
```

{% endcode %}

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FfGs9zc5Kb4rJgCc6zQBm%2F%7B9F8C417E-AB1B-4DDE-84A7-8B1E9DE4459A%7D.png?alt=media&amp;token=187c0af3-3abf-49d7-9b86-228fd63bf259" 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/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests/beacon-flood-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.
