> 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/beacon-packet-analysis.md).
# Beacon Packet Analysis
Identify and analyze Wi-Fi beacon frames in an authorized capture.
### Overview
Access points periodically broadcast beacon frames. These frames advertise the network to nearby clients.
Beacons can include the SSID, BSSID, supported rates, channel, and security capabilities. A client can use this information before sending a probe or association request.
Analyze captures from networks you own or are authorized to assess.
### Filter beacon frames
Beacon frames use management-frame subtype `8`. They are commonly broadcast:
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 8" 2>/dev/null
```
{% endcode %}
### Inspect a specific access point
Filter beacon frames by 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 %}
Replace `AA:BB:CC:DD:EE:FF` with the BSSID from your authorized capture.
### Review packet fields
Use verbose output to inspect the advertised network details:
{% code overflow="wrap" %}
```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype == 8" -V 2>/dev/null
```
{% endcode %}
Review these fields:
* **BSSID** identifies the broadcasting access point.
* **SSID** identifies the advertised network name.
* **Beacon interval** shows how often the access point advertises.
* **Channel and security information** describe the network configuration.
### Interpret the results
A beacon confirms that an access point advertised at the captured time. It does not confirm that any client joined the network.
An empty SSID field can indicate a hidden network name. Compare beacon frames with probe responses and association traffic to build the full 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/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.
