Skip to content
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

Open
jywarren opened this issue Oct 29, 2018 · 7 comments
Open

WiFi captive portal cross-platform access issues #41

jywarren opened this issue Oct 29, 2018 · 7 comments
Labels
help wanted Extra attention is needed

Comments

@jywarren
Copy link
Member

jywarren commented Oct 29, 2018

Different platforms treat the "captive portal" differently:

  1. iOS pops up a notification with the welcome page in a webView mini browser, and you can see through the camera, but if you dismiss the window, it disconnects from the network
  2. Android works fine with the welcome page in the prompt window (similarly a kind of mini browser instance) but Chrome and Firefox can't access http://pi.local until you turn of cellular internet data
  3. Mac OS pops up a mini browser window with the welcome page, and you can escape out or close the popup and use Chrome or another browser to open http://pi.local manually, but it's not redirected-to

I think as we collect information about these scenarios, we can refine the exact captive portal settings and add other solutions!

@jywarren jywarren added the help wanted Extra attention is needed label Oct 29, 2018
@jywarren
Copy link
Member Author

@jywarren
Copy link
Member Author

jywarren commented Nov 1, 2018

Is our approach using the 204 http response code as in the Wikipedia article?

@jywarren
Copy link
Member Author

jywarren commented Nov 1, 2018

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!

@jywarren
Copy link
Member Author

jywarren commented Nov 2, 2018

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:

http://www.digitalyachtamerica.com/index.php/en/support/support-manuals/support- technotes?download=458:tech-00065-2016-c… interesting document which says that the default IP address for an ad-hoc network may no longer be acceptable to iOS 10. Do you know which address range your network is using?

@jywarren
Copy link
Member Author

jywarren commented Nov 2, 2018

And it says:

Roland (maker of some very high-end, expensive mixers) gets around this because their wifi network is identified as a "device" rather than an actual network. Connecting to their mixer is only a matter of answering "ok" to the question about connecting to that device, even without an internet, and then I'm good.

@jywarren
Copy link
Member Author

Kind of cool, here's the message Chrome shows for Amtrak's captive portal:
image

@minanagehsalalma
Copy link

@jywarren hi mate were you able to solve it ?!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants