On Nov 24, 2025, at 3:03 PM, Alexandre Le Noir <muhanadali27@gmail.com> wrote:
You don't understand me. I know that Disconnect a user with Coa is very easy.
If I don't understand you, it's because you're not asking good questions. You asked how to disconnect a user, and I pointed you to a file which contains complete instructions for doing that. You then asked where the instructions were. This is not productive.
But the problem is how to make the termination happen after the user's time is expire.
You can use a cron job to find expired sessions and delete them from the SQL database. As I said in my first message, you can use SQL queries to update the SQL database. However, this only deletes the sessions from the SQL database. If the user is still online, the NAS will send accounting packets, and the SQL database will again show an open session for that user. If you're sending Session-Timeout in the Access-Accept to enforce expiry, then the NAS should enforce that. If you're not sending Session-Timeout, fix your configuration to send it. If the NAS is ignoring Session-Timeout, then throw the NAS in the garbage, and buy one that implements RADIUS properly. Session-Timeout has been defined for about 30 years, so any NAS which ignores it is completely broken.
What I am doing now is using an external tool
through disconnect.conf in mods-enabled.
That might work, but it's fragile. Part of the problem here is that it's now taken 3 messages for you to explain what you're actually doing. This is not helpful. If you ask a vague question, we can only reply with a vague answer. If you ask a GOOD question with details, the answer is likely to be more helpful. So your question is how to disconnect a user. You seem to have a solution in hand. Does it work? If so, you don't need to change it. If the solution doesn't work, then ask a question about WHY the solution doesn't work. Post the debug logs (as suggested in ALL of the documentation). Alan DeKok.