Hello Jaime -
On Friday 09 February 2001 06:51, Jaime Torres wrote:
> > Good afternoon, I'm looking for an advice. There's a big variety of
> authentication daemons to choose from but none of them seem to have all the
> characteristics I'm looking for. I want to install&configure a radius
> capable of mannaging access of pre-paid users. This users buy a limited
> quantity of hours of connection and I expect this radius to validate the
> time an user have been connected in the past and decide if the user can or
> can't connect depending on it.
>
> Let me give you a simple example. This client bought 10 hours of connection
> and he has been on-line for 9 hours and fifteen minutes. He dials our
> number and asks for access permission to the radius. The radius checks the
> user's on-line time and decide to give him access. Later that day, when the
> user have reached 10 hours of on-line time, he tries to connect again, but
> this time the radius won't let him access the service because the hours
> limit have been reached.
>
> I hope Radiator can help me on this. Does it? How does it mannage this
> cases?
>
This is very easy to set up with an SQL database for your user records.
There are examples in the documentation and in the goodies directory of the
distribution. This topic has also been discussed on the mailing list numerous
times, so you should also do a search on the archive site:
http://www.starport.net/~radiator
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.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
