Skip to main content
Portal on Meraki uses an open SSID with a Wiacom splash URL and RADIUS-based per-session authentication. When a guest connects and opens a browser, Meraki redirects them to the Wiacom portal.
API mode users: If you integrated Wiacom via the Meraki API, all SSID settings — splash URL, RADIUS servers, and walled garden — are pushed automatically. No manual configuration is required. You can skip to Walled Garden if you need to add social login providers or whitelist other destinations.

Authentication Model

Wiacom uses per-session generated credentials for RADIUS authentication — not the guest’s MAC address. A unique username and password are generated for each portal session and sent to the Wiacom RADIUS server.

Manual Configuration (Legacy / Non-API Mode)

If you are not using API mode, configure the SSID manually in the Meraki Dashboard as follows.
Portal URL, RADIUS server details, and shared secrets are region-specific. Obtain all values from the Wiacom admin panel or the Wiacom team before proceeding.

Access Control

Log in to dashboard.meraki.com, navigate to Wireless → Access Control, and select your SSID from the dropdown.
SettingValue
SSID statusEnabled
SecurityOpen (no encryption)
Splash pageSign-on with “my RADIUS server”
Advanced splash settings > Captive portal strengthBlock all access until sign-on is complete
Advanced splash settings > Walled gardenEnabled — see Walled Garden below
Advanced splash settings > Simultaneous loginsAllow
Advanced splash settings > Controller disconnection behaviourDefault
Client IP and VLANAs preffered, per your network config

RADIUS Authentication Servers

Under RADIUS, click Add server and add two entries:
#HostAuth PortSecret
1<RADIUS_SERVER_1>1812<RADIUS_SHARED_SECRET>
2<RADIUS_SERVER_2>1812<RADIUS_SHARED_SECRET>

RADIUS Accounting Servers

Under RADIUS accounting, click Add server and add two entries:
#HostAccounting PortSecret
1<RADIUS_SERVER_1>1813<RADIUS_SHARED_SECRET>
2<RADIUS_SERVER_2>1813<RADIUS_SHARED_SECRET>
Set Accounting interim interval to 4 minutes.

Advanced RADIUS Settings

If the Advanced RADIUS settings section is present, configure:
SettingValue
Called-Station-IDAP MAC address (remove any others)
NAS IDremove any others
Server timeout5 seconds
Retry count3
Click Save Changes.

Splash Page

Navigate to Wireless → Splash Page and configure:
SettingValue
Custom splash URL<PORTAL_URL>
Where should users go after the splash page?The URL they were trying to fetch, or a specific redirect URL provided by Wiacom
Click Save Changes.

Walled Garden

The walled garden allows unauthenticated devices to reach the portal and social login providers before completing sign-on. In API mode this is configured automatically. In legacy mode, add the following domains under Wireless → Splash Page → Walled garden:
CategoryDomains
Required*.wiacom.ai , *.wiacom.io
CDN*.akamaitechnologies.com, *.akamaiedge.net, *.akamaized.net, *.amazonaws.com, *.fastly.net
Facebook / Instagram*.facebook.com, *.fbcdn.net, *.akamaihd.net, connect.facebook.net, *.instagram.com
Googleaccounts.google.com, *.googleapis.com, *.gstatic.com
Twitter / X*.twitter.com, *.twimg.com
LinkedIn*.linkedin.com, *.licdn.net, *.licdn.com
Please note, other Walled Garden entries may be requiered - Ask Wiacom for details

Troubleshooting

Confirm the SSID is set to Open and a custom splash option is selected. Try http://neverssl.com — HTTPS traffic is not intercepted by the captive portal mechanism.
Check RADIUS Accounting is enabled at the Meraki organisation level. In legacy mode, verify the RADIUS server addresses and shared secret match what was provided by Wiacom. In API mode, check the RADIUS settings pushed by Wiacom under Inventory → Controllers → [SSID row].
Ensure the relevant social provider domains are present in the Meraki splash walled garden. In API mode, Wiacom pushes the core walled garden — social login domains may need to be added manually if not already present.