> 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/evil-twin/eviltwin-mounting-the-access-point-with-airbase.md).
# EvilTwin - Montando o Ponto de Acesso com Airbase
Crie o ponto de acesso alvo com o Airbase-ng.
## Criar o ponto de acesso
Use `airbase-ng` para criar o ponto de acesso de destino.
{% code overflow="wrap" %}
```bash
airbase-ng -e jordan -c 6 -P wlan0mon
```
{% endcode %}
### Objetivo do comando
Este comando inicia o Airbase-ng por meio da `wlan0mon` interface sem fio.
O ponto de acesso usa o nome de rede `jordan`.
Ele opera no canal `6`.
### Valores de configuração
* `jordan` é o nome de rede configurado.
* `6` é o canal sem fio selecionado.
* `wlan0mon` é a interface sem fio em modo monitor.
* `-P` é mantido da configuração existente do ponto de acesso.
### O que verificar
Confirme que o Airbase-ng inicia sem erros no terminal.
Confirme que a saída mostra o nome de rede e o canal esperados.
Mantenha o terminal em execução enquanto o ponto de acesso estiver ativo.
### Resultado
O Airbase-ng mantém o ponto de acesso configurado ativo até o processo ser encerrado.
---
# 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/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.
