> 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/attacking-from-bettercap.md).
# Évaluation sans fil avec Bettercap
Utiliser Bettercap pour valider l’exposition Wi-Fi.
Bettercap prend en charge la découverte sans fil et les tests d’association client.
### Installer Bettercap
Compilez et installez Bettercap depuis son dépôt officiel :
```bash
git clone https://github.com/bettercap/bettercap
cd bettercap
make build
ls -la bettercap
sudo make install
```
### Démarrer la reconnaissance sans fil
Démarrez Bettercap avec l’interface en mode moniteur :
```bash
./bettercap -iface wlan0mon
```
Activez la reconnaissance Wi‑Fi pour identifier les points d’accès et les clients connectés :
```bash
wifi.recon on
```
Examinez les périphériques sans fil découverts et notez les identifiants pertinents.
### Valider la gestion des associations
Envoyez des requêtes d’association aux points d’accès sélectionnés :
```bash
wifi.assoc all
```
Utilisez cette étape pour valider la supervision, les limites de débit et les alertes.
### Enregistrer le résultat
Documentez le BSSID testé, le canal, la fenêtre temporelle et la réponse observée.
Supprimez la configuration de test et rétablissez le fonctionnement normal du sans-fil après 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/fr/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.
