> 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/probe-response-packet-analysis.md).
# Probe Response Packet Analysis
Identify and analyze Wi-Fi probe response packets in an authorized capture.
### Overview
An access point sends a probe response after receiving a matching probe request. The response provides network details to the requesting client.
Probe responses can include the SSID, supported rates, channel information, and security capabilities. They help the client decide whether to join the network.
Analyze captures from networks you own or are authorized to assess.
### Filter probe responses
Probe responses use management-frame subtype `5`. Filter a saved capture with Tshark:
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 5" 2>/dev/null
```
{% endcode %}
### Inspect a specific access point
Filter responses by the access point 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 %}
Replace `AA:BB:CC:DD:EE:FF` with the BSSID from your authorized capture.
### Review packet fields
Use verbose output to inspect the response details:
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 5" -V 2>/dev/null
```
{% endcode %}
Review these fields:
* **Source address** identifies the responding access point.
* **Destination address** identifies the requesting client.
* **SSID** identifies the network advertised by the response.
* **BSSID** identifies the access point for that network.
### Interpret the results
Correlate a probe response with an earlier probe request. Check the client address, timestamps, and SSID.
A response confirms that an access point advertised network information. It does not confirm that the client connected successfully.
Compare these frames with authentication and association traffic in the same capture.
---
# 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/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.
