I have set up a guest wifi network with an access point on an ethernet port of the PAN firewall. The guest wifi network is unsecured. I am using a web-form to ensure the guests see our logo, terms, and type in the correct password to proceed.
The setup works most of the time. On occasion when using this setup via an Apple iOS device (iPhone, iPad) I don't get the portal page and instead receive an error on the idevice, "Hotspot login cannot open the page because the network connection was lost". I can then only press cancel and it disconnects me from that wifi network. If I hit cancel and try again, the same problem appears. When hitting cancel on this the second time, I get presented with "use without internet or use other network". Now if I click use without internet, and then open Safari and a website I do indeed get the captive portal.
I do not have this problem on any non iOS device (windows laptop, etc).
So, why sometimes does this happen to me? It is not always repeatable on an iOS device. I believe this is because the apple device is trying to initially open an HTTPS page. Does that require me to enable SSL decryption?
We battle this one quite often. Here are a couple thoughts:
So what I ended up doing is
I may not have the above 100% as it has been a while, but hopefully that will give you some starting points.
Sorry about that, please find the solution which I wanted to provide. Let me know if this helps.
"The way to get this to work is to whitelist the Apple URLs meaning exclude the list of Apple URLs that the iPad needs to connect to, from the CP policy
That the ipad can reach its apple specific urls and the user's ipad can work
For other websites, the user's will still have to rely on traditional CP
The way Cisco / Aruba / etc address this through their WLAN authentication is not currently supported in PAN"
I like the train of thought there, so I added a no-captive-portal rule in my Captive Portal policies for the CRL and OCSP URLS. Is that the only place I need to add it, or does it also need to be a security rule? I've only added it to Captive Portal policies, above my existing CP rule but no luck. For what its worth, the problem I am having is not consistent. I have an ipad that works most of the time and another one that does not most of the time.
I also can't understand why I'm not seeing something being blocked in the logs while troubleshooting this.
As I've mentioned, this problem only seems to happen after joining the wifi and the CP page auto-opens. If I cancel a few times and say "use without internet", then I can launch Safari, try an HTTP website and the captive portal correctly appears. If I try an HTTPS website initially then nothing loads.
Tijl, I think the problem started with iOS 7 and anything above. Current iPad I'm testing with is running 8.1.3. I do have security rules related to the captive portal, such as allowing DNS without requiring identity and regular http and https traffic for "known users" (which forces the CP). I have a captive portal rule with "web-form" as the action for http and https. I think the setup is fine as I don't seem to have a problem with windows based computers going through the CP.
Tijl, along the lines of your thinking with regards to HTTPS, I have read elsewhere that Apple's "Captive Network Assistant" has issues where the portal is HTTPS. Apple's initial HTTP GET request (for the success.html) then being redirected to an HTTPS captive portal is the problem here. But who in their right mind would have a captive portal that isn't HTTPS? I guess if I use wifi isolation (preventing wifi clients from talking to each other) could a sniffer still see plain text credentials of the portal? It would be easy to then sniff the portal password from other clients.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!