[Bug] Omada Controller, EAP245 AP not sending Access-Request to Radius Server
Dear Team,
We have observed a bug with the EAP245 Firmware configured to Authenticate the WiFi Users using Mac Based Authentication Radius Profile with Dynamic VLAN Assignment.
When a user tries connecting to the WiFi SSID the AP properly sends a "Access-Request" and the Radius Server successfully authenticate the request and gives a "Access-Accept" packet to the AP with VLAN ID and we observe that Connection is assigned the VLAN Properly but if the client disconnects the WiFi and Tries to connect back within 5 seconds the AP successfully allow that user connection with no vlan assigned back and also don't send a "Access-Request" again to the Radius Server seems it uses some kind of cache but looses the information about the Assigned VLAN ID and if user tries connecting back after about 1 minute it properly asks the Radius Server about the authentication and properly assign the defined VLAN ID.