Anyone else having issues with iOS and OSX not showing the captive portal login?

  • 1
  • Question
  • Updated 6 days ago
  • Answered
I have a case open with support now but was wondering if anyone else has issues with the captive network login not popping up on iOS or OSX.  The iOS device was running version 12 and OSX High Sierra.  If I connect to the onboarding SSID (WISPr) on Windows, ChromeOS, or Android I get a notification that I need to sign into the network.  On OSX and iOS nothing happens.  I have made sure the bypass CNA checkbox is not checked on my SSID but still nothing.  Even tried removing everything from the Walled Garden but still nothing.
Photo of John Westlund

John Westlund

  • 20 Posts
  • 2 Reply Likes

Posted 6 months ago

  • 1
Photo of simantsg

simantsg

  • 9 Posts
  • 0 Reply Likes

HI John, Yes I am having the same issue with OSX but only intermitently with ios. I assumed this was an issue with our Captive Portal provider but if you are experinecing the same issue it would appear not.
what version of vsz are you running?

Regards
Gary
Photo of John Westlund

John Westlund

  • 10 Posts
  • 2 Reply Likes
I have a physical SmartZone appliance running 3.6.1.  It never works on OSX or iOS for us.  If I create a web auth portal and assign it to my onboarding SSID the portal pops up on OSX and iOS immediately but not using our WISPr portal.  We currently couldn't enroll an Apple device at all, good thing we are still in a testing phase with our deployment.
Photo of simantsg

simantsg

  • 9 Posts
  • 0 Reply Likes
We are using a virtual SZ and WISPr and this has been working fine on OSX for a number of years, so unsure why this has just started to be an issue.
If I find the problem i post an update.

Photo of John Westlund

John Westlund

  • 10 Posts
  • 2 Reply Likes
I just sent a packet capture from the OSX machine to support.  Hopefully they can see why it's not coming up.  We are close to being ready to roll this out but with over 50% of the devices on our wifi being Apple and no way to enroll them it's going to be a problem.
Photo of Electa Smith

Electa Smith

  • 8 Posts
  • 0 Reply Likes
Can anybody help me configure my ruckust r610 I cannot get the configure me come up under network
Photo of Michael Brado

Michael Brado, Official Rep

  • 2699 Posts
  • 376 Reply Likes
Does this have anything to do with iOS and OSX showing a captive portal login? 

If not, please start a new thread/topic.  Configure.me is the default SSID for Unleashed.
Photo of John Westlund

John Westlund

  • 20 Posts
  • 2 Reply Likes
I figured this out in my environment.  On the controller under the portal settings I had to enable smart client support.
Photo of Matt

Matt

  • 8 Posts
  • 5 Reply Likes
We are having this problem.  Changed smart client support, removed all entries in walled garden, created new one from scratch, but won't pop up in iOS.  I've had a case open for over a month and month and support won't even reply any more.  I think they've given up.
Photo of Gustavo Affonso

Gustavo Affonso

  • 1 Post
  • 1 Reply Like

Some iOS devices are not redirected to the Captive Portal when the user gets connected to WiFi network with iOS device. The Captive Portal is not triggered automatically when is the testing domain accessible. If the testing domain is not accessible, CNA (Captive Network Assistant) popup is shown.

The iOS and Mac OS X devices check for the following domains which are hosted on Akamai network: 
captive.apple.com 
www.airport.us 
www.thinkdifferent.us 
and other domains used for this purpose by Apple 

If the domain is accessible and returns "Success", the Captive Portal is not triggered automatically. "Success" response means the device is connected to the internet. 

How to test it on iOS:

1- Connect to your WiFi network 
2- Do not connect through Captive Portal
3-Open regular Safari browser and enter the "captive.apple.com" to the URL
4-If you get the "Success", the Apple's domain is accessible

Check your Walled Garden settings or your FirewallPolicy.

The akamaihd.net and akamai.net domains and IP addresses have to be inaccessible to unauthenticated users