> 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/reconnaissance-and-capture.md). # Reconnaissance and Capture Wireless reconnaissance, capture, and observation workflows. Use these pages to map nearby networks, focus captures, export evidence, inspect hidden SSIDs, and run Bettercap-based wireless workflows.

:magnifying-glass:

Airodump Environment Analysis

Identify access points, clients, channels, encryption, and signal data.Airodump Environment Analysis

:filter:

Airodump Filter Modes

Focus captures by channel, BSSID, ESSID, or target scope.Airodump Filter Modes

:file-export:

Exporting Evidence with Airodump

Save capture files and understand Airodump-ng output artifacts.Exporting Evidence with Airodump

:ear-listen:

Passive Exploitation Techniques

Review passive observation paths and risks in wireless traffic.Passive Exploitation Techniques

:ear-listen:

Wireless Sniffing Techniques

Review capture workflows for wireless traffic inspection.Wireless Sniffing Techniques

:eye-slash:

Assessing Hidden Wireless Networks

Discover hidden SSIDs and assess their real security value.Assessing Hidden Wireless Networks

:terminal:

Bettercap Attack Process

Use Bettercap for wireless reconnaissance and validation.Bettercap Attack Process

:terminal:

Wireless Assessment with Bettercap

Run Bettercap-based wireless tests and capture workflows.Wireless Assessment with Bettercap
--- # 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/reconnaissance-and-capture.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.