wifi-connect icon indicating copy to clipboard operation
wifi-connect copied to clipboard

Published 20 hours ago • verified publisher icon balena-os

[BUG] Android 11 devices won't open the wifi access point's UI

Open alexcastillo opened this issue 3 years ago • 5 comments

Hi!

I've been able to consistently reproduce an issue where Android 11 (and possibly other Android) devices won't open the wifi access point's UI when selecting the access point.

I did some research and found the Android 11 Captive Portal spec and docs:

Spec: https://datatracker.ietf.org/doc/html/draft-ietf-capport-rfc7710bis Documentation: https://developer.android.com/about/versions/11/features/captive-portal

  • My first guess is that wifi-connect is not serving the UI using SSL (port 443).
  • My second guess is that the wifi-connect endpoints are not advertising the captive portal API URL during the DHCP handshake (link).

Android 11 supports DHCP option 114 as described in RFC7710bis. We may add support for the router advertisement option in a future update. If the device gets a captive portal API URL through that option during the DHCP handshake, devices fetch the API contents immediately after connecting and prompt users to log in if the network is captive, as per the captive portal API. If the API is not available, or if no portal is advertised, the system will continue to detect portals and verify internet connectivity using HTTP/HTTPS probes, as before.

@majorz any ideas?

alexcastillo avatar Jan 31 '22 16:01 alexcastillo

I am actively working on fixing this and will update the ticket here once I have more information to share. One more reference for iOS 14: https://developer.apple.com/news/?id=q78sq5rv

majorz avatar Feb 02 '22 15:02 majorz

[majorz] This issue has attached support thread https://jel.ly.fish/09b416ba-49f6-451b-bd0b-e87dbcd9bf11

jellyfish-bot avatar Feb 02 '22 15:02 jellyfish-bot

I finally had success with this on Android. The new API uses HTTPS - I could not make it work with HTTP. Also self-signed certificates were not working for me - while I can use them to open the portal from a browser, the API calls from the phone OS fail. I was successful with certificates issued by Let's encrypt. More investigation is now needed on why the self-signed certificates fail.

majorz avatar Mar 21 '22 12:03 majorz

bumping this, I still can't make this work with android? on android 13 with Samsung S20

@majorz did you ever get this to work fully?

babourn avatar Sep 14 '23 23:09 babourn

What is the latest status on this bug @majorz , we seem to run into this issue as well

tekollt avatar Nov 21 '23 20:11 tekollt