# WiFi-based check-in: Cisco Meraki
### Setup
Before you configure the controller make sure you have set up your [RADIUS server and have purchased a license](/platform/settings/integrations-and-apps-1/wifi-based-check-in/setting-up-wifi-based-check-in-using-radius-servers.md).
### Configuring a Meraki controller to use the external Captive Portal authentication.
Use the guide below to configure your Meraki virtual controller and the external Captive Portal with RADIUS authentication. When users connect to it and open their browser, a login screen appears where users can type their email and pin-code to connect to your network.
### To configure your Meraki controller
1. Sign-in to the Meraki cloud portal.
2. Go to **Wireless** > **Configure** > **SSIDs** and define a network that you should configure to use the Captive Portal with RADIUS authentication.
3. In the **Association requirements** section, select **Open (no encryption)**.
4. In the **Splash page** section, select **Sign-on with** and then select **my RADIUS server** from the drop-down list.
5. Add new RADIUS authentication servers by clicking **Add a server** and enter the following:
* IP address in the **Host** section.
* Your RADIUS ports in the **Port** section.
* In the **Secret** section, the shared Secret from the details of the RADIUS server that you received when you created the server.
6. In the **Walled garden** section, type the following ranges:
* XYZ.spaces.nexudus.com, where **XYZ** is the default domain name you can find in **Settings** > **Webiste** > **General** on your Nexudus account.
* 107.178.250.42/32
* 216.239.32.0/19
* 64.233.160.0/19
* 72.14.192.0/18
* 209.85.128.0/17
* 66.102.0.0/20
* 74.125.0.0/16
* 64.18.0.0/20
* 207.126.144.0/20
* 173.194.0.0/16
7. Go to **Wireless** > **Configure** > **Splash page** and add [http://XYZ.spaces.nexudus.com/en/splash](http://xyz.spaces.nexudus.com/en/splash) to the **Custom splash URL** section. **XYZ** is the default domain name you can find in **Settings** > **Webiste** > **General** on your Nexudus account.
You need to contact Meraki support to enable adding domain names to the **Walled garden** section.
You can use the screenshot below to help you with steps three, four, five and six
| Number | Description |
| ------ | ----------- |
| 1 | Step 3 |
| 2 | Step 4 |
| 3 | Step 5 |
| 4 | Step 6 |
You can use the screenshot below to help you with step seven
The default splash page:
### Configuring a Meraki Controller for WPA-Enterprise
Accounting servers are disabled by default when using splash pages for Meraki devices. This means that Nexudus does not receive regular updates when users are in the space. Use WPA-Enterprise authentication to support RADIUS accounting. You can also contact Meraki support to enable this feature when using splash pages.
Users need to type their email and pin-code to connect to your WiFi network when using this authentication method. Otherwise, they cannot gain network access.
Sign-in to the Meraki cloud portal and go to **Wireless** > **Configure** > **SSIDs** and define a network that you should configure to use the Captive Portal with RADIUS authentication.
In the **Association requirements** section, select **WPA2-Enterprise with** and then select **my RADIUS server** from the drop-down list.
In the **Splash page** section, select **None (direct access)**.
Add new RADIUS authentication servers by clicking **Add a server** and enter the following:
* IP address in the **Host** section.
* Your RADIUS ports in the **Port** section.
* In the **Secret** section, the shared Secret from the details of the RADIUS server that you received when you created the server.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://legacydocs.nexudus.com/platform/settings/integrations-and-apps-1/wifi-based-check-in/setting-up-wifi-based-check-in-using-radius-servers/network-based-check-in-cisco-meraki.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.