> 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/attacking-from-bettercap.md).
# Wireless Assessment with Bettercap
Use Bettercap to validate WiFi exposure.
Bettercap supports wireless discovery and client-association testing.
### Install Bettercap
Build and install Bettercap from its official repository:
```bash
git clone https://github.com/bettercap/bettercap
cd bettercap
make build
ls -la bettercap
sudo make install
```
### Start wireless reconnaissance
Start Bettercap with the monitor-mode interface:
```bash
./bettercap -iface wlan0mon
```
Enable WiFi reconnaissance to identify access points and connected clients:
```bash
wifi.recon on
```
Review the discovered wireless devices and record the relevant identifiers.
### Validate association handling
Send association requests to the selected access points:
```bash
wifi.assoc all
```
Use this step to validate monitoring, rate limits, and alerting.
### Record the outcome
Document the tested BSSID, channel, time window, and observed response.
Remove the test setup and restore normal wireless operation after validation.
---
# 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/attacking-from-bettercap.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.
