> 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/es/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/bettercap-attack-process.md). # Proceso de ataque con Bettercap Flujo de trabajo básico de Bettercap para reconocimiento y pruebas WiFi. Bettercap es un binario compilado. El siguiente flujo de trabajo muestra su proceso básico de ataque WiFi. {% embed url="" %} ### Iniciar Bettercap Inicie Bettercap con la interfaz en modo monitor: ```bash ./bettercap -iface wlan0mon ``` ### Iniciar reconocimiento Una vez dentro de Bettercap, habilita el reconocimiento WiFi: ```bash wifi.recon on ```

### Ordenar clientes Ordena los clientes detectados en orden descendente: ```bash set wifi.show.sort clients desc ```

### Configurar el ticker Configura un ticker para refrescar la información en pantalla: ```bash set ticker.commands 'clear; wifi.show' ticker on ``` Esto muestra la información detectada en una vista que se actualiza continuamente.

### Filtrar por canal Filtra el reconocimiento al canal de interés: ```bash wifi.recon.channel 1 ```

### Ejecutar un ataque de desautenticación Para ejecutar un ataque de desautenticación contra un punto de acceso: ```bash wifi.deauth ``` Reemplace `` con el BSSID del punto de acceso objetivo. El handshake se guarda en: ``` /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/es/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.