> 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/airodump-environment-analysis-pt-1.md).
# Airodump Environment Analysis
Passively identify authorized access points and clients with Airodump-ng.
`airodump-ng` passively displays nearby wireless access points and clients. Keep collection aligned with the approved assessment scope.
{% hint style="warning" %}
Limit captures to authorized equipment. Nearby networks may appear in the output.
{% endhint %}
### Start a passive scan
Run Airodump-ng against the monitor-mode interface:
```bash
airodump-ng wlan0mon
```
The scan hops across channels. The `CH` column shows each access point's channel.
### Read the access point table
Each row represents a discovered access point.
* `BSSID` identifies the access point radio by MAC address.
* `PWR` estimates signal strength. `-1` means the value is unavailable.
* `Beacons` counts observed beacon frames.
* `#Data` counts captured data frames.
* `CH` shows the operating channel.
* `MB` shows the advertised maximum data rate.
* `ENC`, `CIPHER`, and `AUTH` summarize the advertised security configuration.
* `ESSID` shows the network name, when broadcast.
WPA2 with `CCMP` and `PSK` is a common home and small-office configuration.
### Read the client table
The lower table lists observed wireless client stations. `STATION` shows the client MAC address.
`BSSID` links a client to the access point it uses. A client marked as `not associated` is visible but not currently connected to an access point.
The `Probes` field can list network names requested by a client. Treat this information as sensitive assessment data.
### Build an assessment baseline
Record only authorized access points and clients. Include their channels, security settings, and observed association state.
This baseline supports later validation and reporting.
---
# 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/airodump-environment-analysis-pt-1.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.
