> 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/disassociation-packet-analysis.md).
# Disassociation Packet Analysis
Identify and interpret Wi-Fi disassociation frames in an authorized capture.
### Overview
A disassociation frame ends a client's association with an access point. The client can no longer exchange regular data through that association.
Unlike deauthentication, disassociation does not end the 802.11 authentication relationship. A client may authenticate and associate again afterward.
Analyze captures from networks you own or are authorized to assess.
### Filter disassociation frames
Disassociation frames use management-frame subtype `10`. Filter a saved capture with Tshark:
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 10" 2>/dev/null
```
{% endcode %}
### List destination MAC addresses
Extract the destination address from each matching frame:
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 10" -Tfields -e wlan.da 2>/dev/null | sort -u
```
{% endcode %}
### 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 == 10 && 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 frame details:
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 10" -V 2>/dev/null
```
{% endcode %}
Review these fields:
* **Source address** identifies the frame sender.
* **Destination address** identifies the affected client or broadcast destination.
* **BSSID** identifies the related access point.
* **Reason code** identifies the stated cause of the disassociation.
### Interpret the results
A disassociation frame confirms that an association ended. It does not show whether the client subsequently reconnected.
Review the reason code, source address, and nearby frames. Correlate the event with later authentication and association traffic for the same client.
---
# 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/disassociation-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.
