Overview
When using Splash Access with Cisco Meraki, certain domains and IP ranges must be added to the Walled Garden to ensure that authentication, social login, and payment gateways function correctly. The required entries depend on the features enabled within your Splash Access deployment (Standard, Social Media, or Payment Gateways).
If your Meraki dashboard does not allow hostname-based walled garden entries, you will need to contact Meraki Support and request that this feature be enabled.
1. Splash Access Without Social Media or Payment Gateways
Add the following domains and hosts:
*.splashaccess.com *.splashaccess.net *.splashaccess.us *.wifi.direct *.splash-access.com Server1.splash-access.com Server2.splash-access.com Server3.splash-access.com Server1.splashaccess.net
2. SplashAccess With Social Media Login
Add all entries from the Standard list, plus the following:
*.facebook.com *.facebook.net *.fbcdn.net api.twitter.com *.twitter.com *.twimg.com *.linkedin.com *.licdn.net *.licdn.com
3. Splash Access With Payment Gateways (Updated List)
Add all entries from the Standard list, plus the following:
*.paypal.com paypal.com *.paypalobjects.com paypalobjects.com www.paypalobjects.com.akadns.net akamaiedge.net *.akamaiedge.net e3694.a.akamaiedge.net *.a.akamaiedge.net akamaitechnologies.com *.akamaitechnologies.com deploy.static.akamaitechnologies.com *.deploy.static.akamaitechnologies.com www.paypal.com www.paypal.com.akadns.net ppdirect.paypal.com.akadns.net wlb.paypal.com.akadns.net www.paypal.com.edgekey.net amazonaws.com *.amazonaws.com api.paypal.com api-3t.paypal.com api-aa.paypal.com api-aa-3t.paypal.com api-s.paypal.com svcs.paypal.com notify.paypal.com reports.paypal.com ipnpb.paypal.com mobile.paypal.com m.paypal.com pointofsale.paypal.com api-m.paypal.com *.stripe.com stripe.com api.stripe.com