Android OS Captive Portal Issue & Solution

Issue

In the current Turnstyle configuration, across all hardware vendors, when some Android devices connect to the Wi-Fi their captive portal does not automatically pop-up. This document outlines the solution, configuration changes and implications of those changes.

Solution

To address this issue, the Walled Garden needs to be updated and is provided below.  Please refer to this link for device specific RADIUS configurations.

With Wildcard Characters (for Cisco Meraki):

*.getturnstyle.com
s3.amazonaws.com
*.nr-data.net
*.newrelic.com
*.bootstrapcdn.com
*.akamaihd.net
*.fbcdn.net
*.facebook.com
connect.facebook.net
*.twitter.com
*.twimg.com
*.linkedin.com
*.licdn.com

Without Wildcard Characters (for Open-Mesh, Aruba):

.getturnstyle.com
s3.amazonaws.com
.nr-data.net
.newrelic.com
.bootstrapcdn.com
.akamaihd.net
.fbcdn.net
.facebook.com
connect.facebook.net
.twitter.com
.twimg.com
.linkedin.com
.licdn.com

Implications

With the updated Walled Garden, Google+ sign-in method will not work. Any venue using the updated Walled Garden must remove Google+ from the authentication methods offered on the splash page, failure to do this will result in rejected Wi-Fi access.

For additional questions please email support@getturnstyle.com

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments