Cisco Meraki MR external splash page, explained
Meraki MR access points can send guests to a splash page you host, and Cisco documents the hand off in unusual detail. This guide walks through it, and is clear that VoqadoWiFi does not support Meraki today.
Not supported by VoqadoWiFi. Written from Cisco documentation read on 7 October 2026.
What Meraki MR is and who runs it
Meraki MR is Cisco’s cloud managed access point line, run from the Meraki dashboard. Splash pages are configured per SSID in the dashboard, and Meraki MX security appliances have a smaller set of splash options of their own. Meraki Go is a different product with its own app; see the Meraki Go guide if that is what you have.
How a custom splash URL grants access
In the splash page settings you can configure a custom splash URL that users are redirected to if you do not want the Meraki hosted pages. If the walled garden is enabled, Meraki says the IP and/or URL of the custom splash page must be added to it.
On a click-through network, Meraki appends parameters to your splash URL: base_grant_url (the URL the client uses to authenticate), user_continue_url (where the guest was trying to go), node_mac (the access point), client_ip and client_mac, plus node_id and gateway_id, which Meraki marks as not used.
To let the guest through, your page redirects the browser with a GET to base_grant_url. Two optional parameters shape the result: continue_url, where the guest lands after login, and duration, the number of seconds of access, up to a maximum of 2592000 (30 days). Pass user_continue_url as continue_url to send guests where they meant to go.
Two details trip people up. Meraki says the grant URL is dynamic, so it must never be hard coded; always use the value that arrived with the guest. And Meraki asks you to make sure the splash frequency set in the dashboard matches the duration you send.
Guest WiFi you can run on Cisco Meraki MR today
| Option | What it does | Source |
|---|---|---|
| Click-through | Guests accept a Meraki hosted page. | Vendor docs |
| Sponsored guest login | A sponsor approves the guest. | Vendor docs |
| Sign-on with Meraki Authentication, RADIUS, LDAP, Active Directory or Google | Guests sign in with credentials checked by the chosen system. | Vendor docs |
| Sign-on with SMS Authentication | Guests verify by text message. | Vendor docs |
| Billing (paid access) | Guests pay for access. | Vendor docs |
| Custom splash URL | Guests are redirected to a page you host instead of a Meraki hosted page. | Vendor docs |
Meraki’s list also includes None (direct access), Cisco ISE authentication and Systems Manager Sentry enrollment. If the built in click-through page covers what you need, there is no reason to host your own.
How often guests see the splash page again
Splash frequency defaults to one day. On RADIUS networks, the RADIUS session timeout governs it, with an upper limit of 90 days. Meraki stores a cookie in the guest’s browser that marks when the access period expires, so a returning guest inside that window is not asked again.
If you host your own click-through page, keep the duration you send and the dashboard splash frequency in step, as Meraki asks, or guests may be asked again earlier or later than you expect.
VoqadoWiFi and Cisco Meraki MR: the honest status
VoqadoWiFi does not support Cisco Meraki MR today. VoqadoWiFi works with two controller platforms: TP-Link Omada and Ubiquiti UniFi. On those, the controller sends each new guest to the VoqadoWiFi login page as an external captive portal, and VoqadoWiFi asks the controller to open the network once the guest signs in.
This page describes what Cisco documents, so you can decide what to do with the hardware you have. It is not a setup guide for VoqadoWiFi, and nothing on it means VoqadoWiFi works with Cisco Meraki MR.
| Question | Answer |
|---|---|
| VoqadoWiFi status | Not supported by VoqadoWiFi yet |
| What the vendor calls the external portal | Splash page, custom splash URL |
| How access is granted, as documented | Redirect grant. After the guest signs in, the portal sends the browser to a grant address the vendor provides, and the access point opens the network. |
The click-through contract is well documented, which makes Meraki MR a reasonable candidate. Supporting it would still mean building and testing the grant against real MR access points with a licence, and checking the grant host before redirecting to it. That has not shipped, and there is no date.
If you are choosing hardware now, the TP-Link Omada setup guide and the Ubiquiti UniFi setup guide show exactly what VoqadoWiFi needs. If you are keeping your current hardware, its own options above work today without us.
Cisco Meraki MR questions
What is base_grant_url on Meraki?
continue_url and duration, to grant access. Meraki says it is dynamic and must not be hard coded.What is the maximum duration on a Meraki grant?
How long is the default Meraki splash frequency?
Does a custom splash page need the walled garden?
Does VoqadoWiFi work with Meraki?
Sources
Every Cisco fact on this page comes from these official pages, read on 7 October 2026. Menus and features change between releases, so check them against your own version.
Keep reading
Cisco and Meraki are trademarks of Cisco Systems. VoqadoWiFi is not affiliated with, endorsed by, or sponsored by Cisco.