> 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/hacking-wifi/wpa-wpa2-psk-network-attacks/packet-analysis/authentication-packet-analysis.md).

# Authentication Packet Analysis

Identify and interpret 802.11 authentication frames in an authorized capture.

### Overview

Authentication frames are part of the 802.11 connection sequence. They usually appear before association requests and association responses.

In a typical WPA/WPA2 connection, the client authenticates at the 802.11 layer, then associates with the access point. The WPA/WPA2 four-way handshake follows association.

Analyze captures from networks you own or are authorized to assess.

### Filter authentication frames

Authentication frames use management-frame subtype `11`. Filter a saved capture with Tshark:

{% code overflow="wrap" %}

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

{% endcode %}

<figure><img src="https://131707722-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>

### Example output

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

The source and destination addresses show the client and access point involved in each exchange. Repeated frames can indicate retransmissions in the capture.

### Inspect a specific client

Filter frames that contain a client MAC address:

{% 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 %}

Replace `AA:BB:CC:DD:EE:FF` with the client MAC address from your authorized capture.

### Review packet fields

Use verbose output to inspect the authentication exchange:

{% code overflow="wrap" %}

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

{% endcode %}

Review these fields:

* **Source and destination addresses** identify both parties.
* **Authentication algorithm** identifies the 802.11 authentication method.
* **Transaction sequence number** shows the exchange step.
* **Status code** indicates whether the access point accepted the request.

### Interpret the results

An authentication frame confirms an attempted 802.11 authentication exchange. It does not confirm that the client associated or gained network access.

Correlate the frame with later association and EAPOL traffic. Use timestamps and MAC addresses to follow the same client through the connection sequence.


---

# 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/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.