> 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/password-auditing/attacking-with-hcxdumptool.md).

# 使用 hcxdumptool 进行无线捕获

捕获 WPA/WPA2 认证流量以供离线分析。

hcxdumptool 用于在 WPA/WPA2 安全评估中捕获无线流量。

该捕获文件可能包含认证材料。它本身不会泄露密码。

### 创建捕获

在监控模式接口上开始捕获：

```bash
sudo hcxdumptool -i wlan0mon -w Capture.pcapng
```

该命令将数据包数据写入 `Capture.pcapng`.

尽可能使用专用信道。这可以减少无关数据的收集。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FVKaQBXkIl9yZYWqEUP7U%2Fimage.png?alt=media&amp;token=7bbb4347-456a-4fa1-b271-d25e237e515d" alt=""><figcaption></figcaption></figure>

### 验证证据

确认输出文件存在并包含认证流量。

将接口、信道、BSSID 和捕获时长与证据一并记录。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FoEis3DU4BUNb4q2IEhjE%2Fimage.png?alt=media&amp;token=42ba60a8-ff36-45c8-b9a4-ae71c323e871" 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/password-auditing/attacking-with-hcxdumptool.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.
