We're spinning up an Internet-only guest network that has no captive portal, no authentication, etc. Devices in our inventory database (MySQL) are banned from connecting to this SSID. This service is working fine from a user perspective.
When we look in Access Tracker, the inventory devices are listed with a login status of ACCEPT (which is logical since they were found in the database), while the unknown devices are considered a REJECT (since they were not in inventory.)
To a human reading Access Tracker it would make more sense to have these reversed, since the known devices are getting a role that has no network access while the unknown devices are geetting a role that does have access. Is there any way we can massage it so that Access Tracker shows the inventoried devices as REJECT, and the personal devices as ACCEPT?
Again, the service works as expected in terms of the behavior the user sees. I just want to change what is considered a denied login status and what is a rejected login status in Access Tracker.
Thanks!