> For the complete documentation index, see [llms.txt](https://docs.radiusaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiusaas.com/es/configuracion/access-point-setup/proxy-needed/meraki.md).

# Meraki

{% hint style="warning" %}
A partir de la versión de firmware **MR 30.X**, los AP de Meraki son compatibles con RadSec. Por lo tanto, recomendamos actualizar su versión de firmware y seguir la [guía de RadSec para Meraki](/es/configuracion/access-point-setup/radsec-available/meraki.md) en su lugar.
{% endhint %}

## Configuración de Meraki 

1. En su **Dashboard** ve a **Wireless > SSID**
2. Active un nuevo SSID y asígnele el nombre que desee
   1. Guarde los cambios

      ![](https://content.gitbook.com/content/SWU1DQ4UGkqER7uGNUOm/blobs/HHH0BV5GfPQKlckfIOUN/image.png)
3. Edite la configuración de su SSID
   1. En **Acceso a la red** seleccione **Empresarial con mi servidor RADIUS**![](https://content.gitbook.com/content/SWU1DQ4UGkqER7uGNUOm/blobs/7jgPgS9AnRFXvx9OKIMU/image.png)
4. Después de eso, vaya a **Servidores RADIUS** y añada sus servidores RADIUS. Use la **dirección IP** de su [**Proxy**](/es/portal-de-administracion/settings/settings-server.md#properties-1), el **Puerto** 1812 y el **Secreto compartido** de su [**Configuración del servidor**](/es/portal-de-administracion/settings/settings-server.md) página![](https://content.gitbook.com/content/SWU1DQ4UGkqER7uGNUOm/blobs/FUN8zTvBZAiRhNL4j4uh/image.png)
5. Configure **parámetros y tiempos de espera de EAP** según [este ](https://docs.radiusaas.com/other/faqs/general)la guía de referencia yendo a **Inalámbrico** > **RADIUS** > **Configuración avanzada de RADIUS.** Una vez configurado, debería verse similar a la captura de pantalla a continuación. 

   <figure><img src="https://1614783686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWU1DQ4UGkqER7uGNUOm%2Fuploads%2FaQH5hQujnvBcG5H96zWi%2F2024-05-17_11h10_26.png?alt=media&amp;token=834dd96d-dfb3-42b9-baca-58dd8873aad5" alt=""><figcaption><p>Mostrando <strong>parámetros y tiempos de espera de EAP</strong></p></figcaption></figure>
6. Para **prueba** que la configuración funciona, puede agregar un usuario en su [Portal](/es/portal-de-administracion/usuarios/users.md#add-a-new-user) y usar la función de prueba de Meraki

   ![](https://content.gitbook.com/content/SWU1DQ4UGkqER7uGNUOm/blobs/vS67zRsPtNO9uDYp8bw2/image.png)
7. **Guardar** sus cambios.


---

# 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://docs.radiusaas.com/es/configuracion/access-point-setup/proxy-needed/meraki.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.