> 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/packet-analysis.md).
# 数据包分析
用于 WPA/WPA2 评估的 802.11 数据包分析笔记。
这些注释解释了常见的 802.11 管理帧，以及在无线抓包审查时如何解读它们。
| | | |
|---|
:boxes-stacked: | 探测请求数据包分析 | 解读数据包捕获中的客户端发现帧。 | 探测请求数据包分析 |
:boxes-stacked: | 探测响应数据包分析 | 分析接入点对无线发现请求的响应。 | 探测响应数据包分析 |
:boxes-stacked: | 关联请求数据包分析 | 检查客户端关联请求及其声明的能力。 | 关联请求数据包分析 |
:boxes-stacked: | 关联响应数据包分析 | 读取接入点关联响应和状态代码。 | 关联响应数据包分析 |
:boxes-stacked: | 信标数据包分析 | 解码信标帧、SSID、信道和安全能力。 | 信标数据包分析 |
:boxes-stacked: | 认证数据包分析 | 解读数据包捕获中的 802.11 认证交换。 | 身份验证数据包分析 |
:boxes-stacked: | 去认证数据包分析 | 识别去认证帧和原因代码。 | 取消身份验证数据包分析 |
:boxes-stacked: | 去关联数据包分析 | 分析去关联帧和客户端断开行为。 | 解除关联数据包分析 |
---
# 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/packet-analysis.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.