[GH-ISSUE #37] Killing uspot session when session killed on radius server #22

New issue

Closed

opened 2026-03-04 14:52:27 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 14:52:27 +03:00

Owner

Originally created by @bmberni on GitHub (Jul 2, 2025).
Original GitHub issue: https://github.com/f00b4r0/uspot/issues/37

I use RadiusDesk and freeRadius to manage my vouchers and accounts. If I now “kill” a session in RadiusDesk, the session continues to run for the user. He can continue surfing.
Is it possible that the session is then also terminated by uspot? Possibly by cyclically querying Radius status requests?
Or further thought, if the user has a data quota, that the user is blocked as soon as the quota is exhausted.

Originally created by @bmberni on GitHub (Jul 2, 2025). Original GitHub issue: https://github.com/f00b4r0/uspot/issues/37 I use RadiusDesk and freeRadius to manage my vouchers and accounts. If I now “kill” a session in RadiusDesk, the session continues to run for the user. He can continue surfing. Is it possible that the session is then also terminated by uspot? Possibly by cyclically querying Radius status requests? Or further thought, if the user has a data quota, that the user is blocked as soon as the quota is exhausted.

kerem closed this issue

2026-03-04 14:52:27 +03:00

kerem commented

2026-03-04 14:52:28 +03:00

Author

Owner

@f00b4r0 commented on GitHub (Jul 3, 2025):

That's what RADIUS DAE DM messages are for and supported by uspot.

@f00b4r0 commented on GitHub (Jul 3, 2025): That's what RADIUS DAE [DM messages](https://datatracker.ietf.org/doc/html/rfc5176#section-2.1) are for and supported by uspot.