-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WiFi captive portal cross-platform access issues #41
Comments
Some documentation here: https://en.wikipedia.org/wiki/Captive_portal#Implementation Raspberry Pi specific info: https://andrewwippler.com/2017/04/07/captive-portal-overview/ with a LOT of info here: https://andrewwippler.com/2016/03/11/wifi-captive-portal/ |
Is our approach using the 204 http response code as in the Wikipedia article? |
Figured out that I have to turn off mobile/cellular internet on my Android (Pie) device to be able to load http://pi.local, then it works perfectly! |
iOS seems to really reject WiFi access points that have no real internet connection: https://serverfault.com/questions/709909/wifi-access-point-without-internet-access-ios-devices-disconnect These folks have found you can enter a static IP and a few other configs on the iOS device, and get it to work: https://discussions.apple.com/thread/7705927 although that seems like a not very ideal solution... In the same thread on p2 there is speculation that iOS is not accepting the IP address assigned by the ad-hoc network:
|
And it says:
|
@jywarren hi mate were you able to solve it ?! |
Different platforms treat the "captive portal" differently:
I think as we collect information about these scenarios, we can refine the exact captive portal settings and add other solutions!
The text was updated successfully, but these errors were encountered: