If you are happy with reliability then fix checkrad and it will clean
these random drops. That is the utility that radiusd calls to check
stale entries and in sql.conf you can enable deletion of such entries.
Just make sure that such users are not listed as active by the hotspot.
If NAS thinks they are still loged on, RADIUS can't do anything about

Ivan Kalik
Kalik Informatika ISP

Dana 12/4/2007, "PD" <[EMAIL PROTECTED]> piše:

>On 4/12/2007, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>>+ what cause of this problem ?
>>Either NAS thinks that users are still connected or your RADIUS server is
>>not receiving Stop packages. If NAS (NAS not radacct table) shows users
>>as connected you can add Idle-Timeout of about 5 minutes in user (or
>>group) configuration. If RADIUS packets are not being received have a
>>look at your network. NAS needs reliable connection to RADIUS server -
>>you shouldn't have firewalls and such in the way.
>Well... the problem only persist sometime.. let say once or two
>timeseveryday. The communication between Radius box and NAS using STP
>Currently we are still on development stage of hotspot system. Before
>implement them on big area, we found some problem, like explain above.
>When I log in and log out or shut the notebook down without logout, I
>can see both start and stop the record on radacct table,
>I could not find the problem sources.. perhaps someone else has face the
>same problem ?
>>+ how to delete this entry daily (perhaps with crontab)
>>Don't do that. Fix your server communication and then delete stale
>>entries once.
>Well.. with simultaneous-use:=1, the same user will not be able login
>anymore because radius see that he / she still online.
>List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to