(RADIATOR) Current Logged in Users

[Hugh Irvine]

Hello Rolando -

On Tue, 12 Feb 2002 01:03, Rolando Riley wrote:
> When I say 'fairly accurate' - if your NAS fails to deliver a STOP record
> to radiator, the user will not be removed from the online users database.
>
>
> The above  seems to be very common to happen. That is
>
> 1) hanged users which can't auth  because of a Max Sessions reached and no
> STOP record sent by the NAS has been taken
> 2) Sometimes hanged RADIUS. That still happens to us when we change all the
> auths to LDAP. And it is due to the same cause in point 1)
>
> My question is:
> 1) what is the accurate way to use scripts like scripts like
> goodies/cleanup.txt or checksessiondb.txt

These scripts are designed to be run periodically from cron or similar.

> 2) do you know what are the frequent causes that  make NAS don't send the
> STOP record ?
>

The two most frequent causes are congested links dropping UDP packets or NAS 
software bugs that don't send them at all.

regards

Hugh


-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.