Hi Nataniel,
If you have a NASty which doesn't send accounting-off when rebooting, I guess you have three options: 1) use "checkrad" script to test if the user is indeed logged in. The NASty should have a way to check for connected users or sessions by using snmp/telnet/etc. If you have many auth requests and many "NASty"s, it will consume a lot of CPU on both sides. Result: no angry customers, but high cpu usage and no billing 2) run every N minutes a script to get the list of connected users for every NASty. compare that list with the db entries and delete lost sessions from db. Result: low cpu usage, better billing (if your customers pay by time usage, you can still charge now() - N minutes - acct_start), but 'already logged in' will last N minutes (at most) 3) use petitiononline.com service to management with a subject "Network.Access.Server.TY must be replaced with Network.Access.Upgraded.Good.Hardware.TY". Result: no problems at all. using good hardware is always the best option. You can implement all three options IN THE SAME TIME to minimize the impact. Best regards, Claudiu Filip @: [EMAIL PROTECTED] Http://www.globtel.ro T:+40344880100 F:+40344880113 Monday, July 16, 2007, 7:37:08 PM, you wrote: > Hello all, > I have a question: when a nas restart without sending client logout > to the freeradius server the clients stay connected in radacct table > (AcctStopTime=0). What can I do to solve this kind of problem? What > could happen is that when a nas reboot my clients keep logged and when > the nas start again they will get "You are already logged in" > (simultaneous-use). - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html