> 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/ja/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/attacking-from-bettercap.md).

# Bettercap による無線評価

Bettercap を使用して WiFi の露出を検証する。

Bettercap は無線の探索およびクライアント関連付けテストをサポートします。

### Bettercap をインストールする

公式リポジトリから Bettercap をビルドしてインストールします:

```bash
git clone https://github.com/bettercap/bettercap

cd bettercap

make build

ls -la bettercap

sudo make install
```

### 無線偵察を開始する

モニターモードのインターフェースで Bettercap を起動します:

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

WiFi 偵察を有効にして、アクセスポイントと接続中のクライアントを特定します:

```bash
wifi.recon on
```

検出された無線デバイスを確認し、関連する識別子を記録します。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FwOB3as3CutLnG3JJTJro%2Fimage.png?alt=media&amp;token=98dae0e8-61b3-476c-a56e-662aae6f2419" alt=""><figcaption></figcaption></figure>

### 関連付け処理を検証する

選択したアクセスポイントに関連付け要求を送信します:

```bash
wifi.assoc all
```

この手順を使って、監視、レート制限、およびアラートを検証します。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FCSdcaIi1wV69dldWwdm0%2Fimage.png?alt=media&amp;token=1ee70253-953d-4122-9334-d351228f3e98" alt=""><figcaption></figcaption></figure>

### 結果を記録する

テストした BSSID、チャネル、時間範囲、および観測された応答を文書化します。

検証後、テスト環境を削除し、通常の無線動作を復元します。


---

# 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/ja/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/attacking-from-bettercap.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.
