> 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/fr/hacking-wifi/wpa-wpa2-psk-network-attacks/evil-twin/eviltwin-mounting-the-access-point-with-airbase.md).
# EvilTwin - montage du point d’accès avec Airbase
Créer le point d’accès cible avec Airbase-ng.
## Créer le point d’accès
Utilisez `airbase-ng` pour créer le point d’accès cible.
{% code overflow="wrap" %}
```bash
airbase-ng -e jordan -c 6 -P wlan0mon
```
{% endcode %}
### Objet de la commande
Cette commande lance Airbase-ng via l’ `wlan0mon` interface sans fil.
Le point d’accès utilise le nom du réseau `jordan`.
Il fonctionne sur le canal `6`.
### Valeurs de configuration
* `jordan` est le nom du réseau configuré.
* `6` est le canal sans fil sélectionné.
* `wlan0mon` est l’interface sans fil en mode moniteur.
* `-P` est conservé à partir de la configuration du point d’accès existant.
### Ce qu’il faut vérifier
Confirmez qu’Airbase-ng démarre sans erreur dans le terminal.
Confirmez que la sortie affiche le nom du réseau et le canal attendus.
Laissez le terminal ouvert pendant que le point d’accès est actif.
### Résultat
Airbase-ng maintient le point d’accès configuré actif jusqu’à l’arrêt du processus.
---
# 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/fr/hacking-wifi/wpa-wpa2-psk-network-attacks/evil-twin/eviltwin-mounting-the-access-point-with-airbase.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.
