> 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/beacon-packet-analysis.md).
# 信标数据包分析
在授权捕获中识别并分析 Wi-Fi 信标帧。
### 概述
接入点会定期广播信标帧。这些帧向附近客户端通告网络。
信标可以包含 SSID、BSSID、支持的速率、信道和安全功能。客户端可以在发送探测或关联请求之前使用这些信息。
分析你拥有或已获授权评估的网络中的捕获数据。
### 过滤信标帧
信标帧使用管理帧子类型 `8`。它们通常被广播：
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 8" 2>/dev/null
```
{% endcode %}
### 检查特定接入点
按 BSSID 过滤信标帧：
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 8 && 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 == 8" -V 2>/dev/null
```
{% endcode %}
查看这些字段：
* **BSSID** 标识广播该信标的接入点。
* **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/beacon-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.
