By now the main issue it's the problem of android redirecting to the index
1.) Default URL in the chrome is a "httpS" URL for anything entered manually
2.) CaptivePortal detection can't be tricked by the router and the message "limited network" stays.
2.a) This also means, that the device stays connected but uses mobile network in the chrome.
3) can we block the use of mobile data on the phone, after connecting to the wifi signal to force the connection??
What did I do?
a) Together with the access.logs, I understand the different ways devices and apps (Firefox, too) are checking the internet.
b) I understood, that the router might answer wrongly to the generate_204 request by Android phone, which results into the "limited internet" message
c) I used the Android debugging interface to gather the log messages from the captive portal test. It is not much, but it helped to line up a few thoughts.
*** should work an authentication portal? for both apple/android
By now the main issue it's the problem of android redirecting to the index
1.) Default URL in the chrome is a "httpS" URL for anything entered manually
2.) CaptivePortal detection can't be tricked by the router and the message "limited network" stays.
2.a) This also means, that the device stays connected but uses mobile network in the chrome.
3) can we block the use of mobile data on the phone, after connecting to the wifi signal to force the connection??
What did I do?
a) Together with the access.logs, I understand the different ways devices and apps (Firefox, too) are checking the internet.
b) I understood, that the router might answer wrongly to the generate_204 request by Android phone, which results into the "limited internet" message
c) I used the Android debugging interface to gather the log messages from the captive portal test. It is not much, but it helped to line up a few thoughts.
*** should work an authentication portal? for both apple/android