> 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/password-auditing/attacking-with-hcxdumptool.md).
# Capture sans fil avec hcxdumptool
Capturer le trafic d’authentification WPA/WPA2 pour une analyse hors ligne.
hcxdumptool capture le trafic sans fil pour des évaluations de sécurité WPA/WPA2.
La capture peut contenir des éléments d’authentification. Elle ne révèle pas un mot de passe à elle seule.
### Créer une capture
Démarrez une capture sur l’interface en mode moniteur :
```bash
sudo hcxdumptool -i wlan0mon -w Capture.pcapng
```
La commande écrit les données des paquets dans `Capture.pcapng`.
Utilisez un canal dédié chaque fois que possible. Cela réduit la collecte de trafic non pertinent.
### Valider les preuves
Confirmez que le fichier de sortie existe et contient du trafic d’authentification.
Consignez l’interface, le canal, le BSSID et la durée de capture avec les preuves.
Protégez la capture comme des données d’évaluation sensibles. Supprimez-la lorsque la période de conservation prend fin.
---
# 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/password-auditing/attacking-with-hcxdumptool.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.
