> 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/probe-request-packet-analysis.md).
# 探测请求数据包分析
在授权捕获中识别并分析 Wi-Fi 探测请求数据包。
### 概述
客户端在主动 Wi‑Fi 扫描期间发送探测请求。它可以在加入网络之前发送，也可以在已经连接时发送。
这些管理帧可帮助客户端发现附近的接入点。请求可以指定某个特定的 SSID，也可以使用通配 SSID 来请求任意可用网络。
仅分析你拥有或已获授权评估的网络捕获数据。探测请求可能暴露设备标识符和所请求的网络名称。
### 使用 Airodump-ng 观察探测
在监控模式接口上运行 Airodump-ng：
{% code overflow="wrap" %}
```bash
airodump-ng wlan0mon
```
{% endcode %}
在 **站点** 部分，请查看 **探测** 列。它列出了被观察到的客户端所请求的 SSID。
空值并不排除存在探测活动。客户端可能使用通配请求。捕获数据也可能遗漏该帧。
### 过滤探测请求
探测请求使用管理帧子类型 `4`。使用 Tshark 过滤已保存的捕获：
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 4" 2>/dev/null
```
{% endcode %}
### 检查特定客户端
按客户端源地址筛选结果：
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 4 && wlan.sa == AA:BB:CC:DD:EE:FF" 2>/dev/null
```
{% endcode %}
替换 `AA:BB:CC:DD:EE:FF` 使用你授权捕获中的客户端 MAC 地址。
### 查看数据包字段
在 Wireshark 中打开匹配的帧，或使用详细的 Tshark 输出：
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 4" -V 2>/dev/null
```
{% endcode %}
查看以下字段：
* **源地址** 标识发送客户端。
* **目的地址** 在一般发现过程中通常以广播方式发送。
* **SSID** 标识定向请求，或在通配请求时保持为空。
### 解读结果
探测请求表明客户端在当时正在扫描，但并不证明连接成功。
使用时间戳、源地址和 SSID 值来关联请求，并将它们与同一捕获中的信标、探测响应和关联帧进行比较。
---
# 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/probe-request-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.
