Hi  @Cebujohn 

To better understand you request, why would you need to add so many auth-free clients?

Instead of adding them to the auth-free list, did you consider connecting those clients to a separe WLAN network?

Yes, we can configure Authentication Timeout on this page:

Hi  @Cebujohn 

I missed the screenshot of the timeout settings. Here is it:

Please check what's the config on your side.

As for the TVs, I would recommend create a new SSID in the same LAN, and don't configure portal authentication with the SSID for the TV. With this config, portal clients will also be able to access the TV, and the TV won't need to log in the portal. How do you think?

Cebujohn wrote

Hi Vincent, I manage a residential building where their TVs are on the same Portal and VLAN to the presently used Hotspot for Internet access. The TVs -- well some, randomizes mac address and doesnt have any option to use its own mac. Complaints were they keep on logging on to the Portal thru their TVs to authenticate. With authentication free list, it automatically connects the tv to the network. But really need more than 32 entries. Will there be any chances of extending the list into maybe unlimited? ... or i was really thinking some work-around on this problem. Any suggestion? I would really appreciate it. About the Authentication Timeout on the PORTAL section set to LOCAL USER, I am using OC300 using HOTSPOT - Local User. Clients will always complain they system keeps them logging-out and they keep on logging-in on a period of time. How am i going to go about this? Thank you very much, answers and very much appreciated. Thank you!

  @Cebujohn 

SSID examples would be:

One for guests with portal authentication, the other is for TV without portal auth.

@ThawHZin 

Similair as your situation. You may create a separate SSID without portal auth for the IoT devices.

Vincent-TP wrote

  @Cebujohn 

 

SSID examples would be:

 

One for guests with portal authentication, the other is for TV without portal auth.

Hi  @Cebujohn 

For SSIDs configured with a portal, when a client connects, it triggers the browser to redirect to the login page. Brief disconnections and reconnections don't require re-login because the browser cache is still valid. However, if the disconnection lasts several days, the cache will naturally be cleared when redirected to the login page again, so re-authentication is required. Currently, this scenario does not support login-free access.

Additionally, I personally believe it's completely reasonable to require re-login after being disconnected for several days.

As for the TVs, that screenshot shows two temporary SSIDs I created as examples – mainly to demonstrate the difference between having a portal and not having one. For simplicity, I chose "None" as the encryption method so I wouldn't need to enter passwords. In actual deployments, I recommend using WPA-Personal to encrypt your SSIDs.

Hi  @ThawHZin 

With oc200, er605 and es206gp Omada devices, unfortunately, there is no other workaround.