> 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/authentication-packet-analysis.md).

# 身份验证数据包分析

在授权捕获中识别并解读 802.11 身份验证帧。

### 概述

认证帧是 802.11 连接序列的一部分。它们通常出现在关联请求和关联响应之前。

在典型的 WPA/WPA2 连接中，客户端先在 802.11 层进行认证，然后与接入点建立关联。WPA/WPA2 四次握手在关联之后进行。

分析您拥有或被授权评估的网络中的抓包。

### 筛选认证帧

认证帧使用管理帧子类型 `11`。使用 Tshark 过滤已保存的捕获：

{% code overflow="wrap" %}

```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 11" 2>/dev/null
```

{% endcode %}

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FlCeW0vMw8aszgYvazZuI%2F%7B0AD63116-17AC-47A7-8DFB-AAAEB44FB296%7D.png?alt=media&amp;token=32edd5bb-5b15-45c2-be71-051607c7ac78" alt=""><figcaption></figcaption></figure>

### 示例输出

> 22263 114.703031 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2673, FN=0, Flags=....R...\
> 22266 114.709466 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2673, FN=0, Flags=....R...\
> 22269 114.717582 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2673, FN=0, Flags=....R...\
> 22272 114.724416 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2673, FN=0, Flags=....R...\
> 22285 114.756941 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2673, FN=0, Flags=....R...\
> 22293 114.780154 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2673, FN=0, Flags=....R...\
> 22295 114.784290 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2674, FN=0, Flags=........\
> 22297 114.789547 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2674, FN=0, Flags=....R...\
> 22303 114.806150 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2674, FN=0, Flags=....R...\
> 22307 114.816975 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2674, FN=0, Flags=....R...\
> 22320 114.852622 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2674, FN=0, Flags=....R...\
> 22323 114.859488 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2675, FN=0, Flags=....R...\
> 22324 114.861193 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2675, FN=0, Flags=....R...\
> 22327 114.868343 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2675, FN=0, Flags=....R...\
> 22336 114.893840 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2675, FN=0, Flags=....R...\
> 22340 114.903089 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2675, FN=0, Flags=....R...\
> 22344 114.910651 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2675, FN=0, Flags=....R...\
> 22345 114.918244 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2676, FN=0, Flags=....R...\
> 22346 114.921532 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2676, FN=0, Flags=....R...\
> 22347 114.925145 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=2676, FN=0, Flags=....R...\
> 22485 116.713719 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 65 认证, SN=880, FN=0, Flags=........\
> 22487 116.715413 TpLinkTechno\_62:45:e7 → 9e:8c:fb:49:d4:52 802.11 41 认证, SN=3566, FN=0, Flags=....R...

源和目的地址显示了每次交换中涉及的客户端和接入点。重复帧可能表示抓包中的重传。

### 检查特定客户端

过滤包含客户端 MAC 地址的帧：

{% code overflow="wrap" %}

```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 11 && wlan.addr == AA:BB:CC:DD:EE:FF" 2>/dev/null
```

{% endcode %}

替换 `AA:BB:CC:DD:EE:FF` 使用你授权捕获中的客户端 MAC 地址。

### 查看数据包字段

使用详细输出检查认证交换：

{% code overflow="wrap" %}

```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 11" -V 2>/dev/null
```

{% endcode %}

查看以下字段：

* **源和目的地址** 识别双方。
* **认证算法** 用于标识 802.11 认证方法。
* **事务序列号** 显示交换步骤。
* **状态码** 指示接入点是否接受了请求。

### 解读结果

认证帧确认了一次尝试进行的 802.11 认证交换。它不能确认客户端已建立关联或获得网络访问权限。

将该帧与后续的关联和 EAPOL 流量关联起来。使用时间戳和 MAC 地址沿着连接序列跟踪同一个客户端。


---

# 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/authentication-packet-analysis.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.