> 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-response-packet-analysis.md).
# 探测响应数据包分析
在授权捕获中识别并分析 Wi-Fi 探测响应数据包。
### 概述
接入点在收到匹配的探测请求后会发送探测响应。该响应向请求客户端提供网络详情。
探测响应可包含 SSID、支持的速率、信道信息和安全能力。它们帮助客户端决定是否加入网络。
分析您拥有或被授权评估的网络中的抓包。
### 过滤探测响应
探测响应使用管理帧子类型 `5`。使用 Tshark 过滤已保存的捕获：
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 5" 2>/dev/null
```
{% endcode %}
### 检查特定接入点
按接入点 BSSID 过滤响应：
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 5 && wlan.bssid == AA:BB:CC:DD:EE:FF" 2>/dev/null
```
{% endcode %}
替换 `AA:BB:CC:DD:EE:FF` 使用你授权捕获中的 BSSID。
### 查看数据包字段
使用详细输出检查响应细节：
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 5" -V 2>/dev/null
```
{% endcode %}
查看这些字段：
* **源地址** 标识响应的接入点。
* **目的地址** 标识请求的客户端。
* **SSID** 标识该响应所公布的网络。
* **BSSID** 标识该网络对应的接入点。
### 解读结果
将探测响应与先前的探测请求关联起来。检查客户端地址、时间戳和 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-response-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.
