> 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/pt-br/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/bettercap-attack-process.md). # Processo de Ataque com Bettercap Fluxo básico de trabalho do Bettercap para reconhecimento e testes em Wi-Fi. Bettercap é um binário compilado. O fluxo de trabalho a seguir mostra seu processo básico de ataque WiFi. {% embed url="" %} ### Iniciar o Bettercap Inicie o Bettercap com a interface em modo monitor: ```bash ./bettercap -iface wlan0mon ``` ### Iniciar o reconhecimento Uma vez dentro do Bettercap, habilite o reconhecimento WiFi: ```bash wifi.recon on ```

### Ordenar clientes Ordene os clientes detectados em ordem decrescente: ```bash set wifi.show.sort clients desc ```

### Configurar o ticker Configure um ticker para atualizar as informações na tela: ```bash set ticker.commands 'clear; wifi.show' ticker on ``` Isso exibe as informações detectadas em uma visualização continuamente atualizada.

### Filtrar por canal Filtre o reconhecimento para o canal de interesse: ```bash wifi.recon.channel 1 ```

### Executar um ataque de desautenticação Para executar um ataque de desautenticação contra um ponto de acesso: ```bash wifi.deauth ``` Substituir `` com o BSSID do ponto de acesso alvo. O handshake é salvo em: ``` /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/pt-br/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.