Hi,
I don't know how sought after this would be, but I'll raise it anyway...
We run Radiator as a front end to Portal's Infranet Terminal Server Manager
(crappy) RADIUS server. It doesn't support things like Alive records, and
(on a side issue) we have a number of issues with false duplicate sessions
due to temporary outages and lost accounting records in general.
What would be cool, would be if Radiator could maintain an internal active
session table, based on Alive records, and if it didn't receive one within a
configurable time period, it could mock up a Stop record and send that
through to the RADIUS server that it's configured to proxy everything
through to.
Did that make sense to anyone other than me?
Thoughts?
Andrew
------------------------------------------------------------
Andrew Pollock Systems Group Team Leader
[EMAIL PROTECTED] http://www.asiaonline.net/
Phone: +61 2 6243 0213
Fax: +61 2 6247 3316
Asia Online
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
