> 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/fundamentals/what-is-monitor-mode.md).
# What Is Monitor Mode?
How monitor mode captures wireless frames for authorized WiFi analysis.
Monitor mode lets a wireless adapter capture nearby 802.11 frames. It supports passive analysis during scoped WiFi assessments.
{% hint style="warning" %}
Capture traffic from equipment you own or are authorized to assess.
{% endhint %}
### Why it is needed
Most wireless assessment workflows require monitor mode. The adapter listens without joining the access point.
This exposes wireless management and data frames for inspection. It does not grant network access.
### What you can observe
Monitor mode can reveal metadata from nearby wireless traffic:
* Access point and client MAC addresses.
* Network names, channels, and signal strength.
* Authentication, association, and other management frames.
### Important limitations
Capture depends on range, channel, and adapter support. Encrypted payloads remain unreadable without the required keys.
---
# 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/fundamentals/what-is-monitor-mode.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.
