Hello! I have several EAP245s and Raspberry Pi 4B (2GB) as Omada Controller (4.4.6). I have a guest-net with "click and go" authentication (i.e. "no authentication".) I used to set the timeout to be 3 days. But then realized that iPhones are not getting the portal automatically when it expires. Then I learned that iPhones deactivate Captive Portal Detect when the device is on a certain wifi network for certain length of time, like about 24 hours. It has to be asked for login every 24 hours.  I posted the hint on the wall that one should try to access h t t p : / / n e v e r s s l . c o m (I spaced out this way because otherwise I can't post!)  in case the portal doesn't come up automatically. It does work on iPhones, but the problem is nobody reads it ! So I decided to make timeout to be 20 hours. That was yesterday.

Then today, several other devices got a problem with getting back on-line again, and this time it's worse: n e v e r s s l . c o m  doesn't work either. Since they were in a meeting, I didn't want to check each device, I authenticated them manually on the controller, but one android still couldn't get back on-line.  As he restarted the device, it worked.

I don't want them to have to restart the device to get going upon auth-timeout.  What is the best practice of this matter? For now I changed the expiration to 20 days, because now I know that this way, the problem is only with iPhones, and n e v e r s s l . c o m  does work 100% on them. Could anyone also explain to me what might restarting of android have done?

I would appreciate your hints!