There is no information on the protocol where the clients stop to authenticate. There are some policies, but I don't know whether the device stopped on the authentication or authorization levels. I don't know whether it is getting the right certificate. I have to work on assumptions. If I want to go to the history to see what happened to a client the previous day or two days ago, it will be very hard because the server is used by multiple devices. For every device and user, macmon creates a file into the RADIUS appliance for deep troubleshooting. To troubleshoot, it creates a bunch of files. If I want to check what happened in the history, I have to check all the files. In some cases, there are 100 files. It is impossible for me to go to each file to see where it happens. It will be good to find the file my client authenticated based on the MAC address. Otherwise, the product must have one file for a specific date. I don't have any problem in terms of dates because it's normal. However, having hundreds of files per day is very hard to troubleshoot. The solution must allow users to filter files based on dates. It must provide deeper troubleshooting and reduced log. Also, the RADIUS logs are very huge.
