> 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/de/hacking-wifi/wpa-wpa2-psk-network-attacks/evil-twin/eviltwin-mounting-the-access-point-with-airbase.md).

# EvilTwin - Den Access Point mit Airbase einrichten

Den Ziel-Access-Point mit Airbase-ng erstellen.

## Erstellen Sie den Zugangspunkt

Verwenden Sie `airbase-ng` um den Ziel-Zugangspunkt zu erstellen.

{% code overflow="wrap" %}

```bash
airbase-ng -e jordan -c 6 -P wlan0mon
```

{% endcode %}

### Befehlszweck

Dieser Befehl startet Airbase-ng über die `wlan0mon` WLAN-Schnittstelle.

Der Zugangspunkt verwendet den Netzwerknamen `jordan`.

Er arbeitet auf Kanal `6`.

### Konfigurationswerte

* `jordan` ist der konfigurierte Netzwerkname.
* `6` ist der ausgewählte WLAN-Kanal.
* `wlan0mon` ist die WLAN-Schnittstelle im Monitor-Modus.
* `-P` wird aus der bestehenden Zugangspunktkonfiguration übernommen.

### Was zu überprüfen ist

Bestätigen Sie, dass Airbase-ng ohne Terminalfehler startet.

Bestätigen Sie, dass die Ausgabe den erwarteten Netzwerknamen und Kanal anzeigt.

Lassen Sie das Terminal laufen, solange der Zugangspunkt aktiv ist.

### Ergebnis

Airbase-ng hält den konfigurierten Zugangspunkt aktiv, bis der Prozess beendet wird.

<figure><img src="https://2955439919-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fm8rDeAk03bOlb3ElOV47%2Fimage.png?alt=media&amp;token=41873bfe-2714-43ce-a21a-7751f33699e2" 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/de/hacking-wifi/wpa-wpa2-psk-network-attacks/evil-twin/eviltwin-mounting-the-access-point-with-airbase.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.
