(RADIATOR) Different usage rates for different hours of day.

Dear Sir, We want to use time based usage. A user should be charged different rates if he is logged at prime time say from 9:00 to 16:00 and should be charged lesser rate may be a percentage of the previous rate if he logs at other times. Can we do it using Radiator. Thanks and Regards. ===

RE: (RADIATOR) 2.16.1 LOG question (IMPORTANT)

On Mon, 17 Jul 2000, Ingvar Berg (ERA) wrote: [my message regarding leaving a password log with only fails and no encrypted strings] > Please don't forget that most failed pw entries are correct except for > one or two chars => this info can be quite interesting to an intruder > (extenal or "ins

Re: (RADIATOR) process sequence???

On Mon, 17 Jul 2000, Tuncay MARGILIC wrote: > Hi there, > > When is the record on the radonline table is deleted when the Raiator > recieves a stop record of a users disconnection. Does this record on > radonline still alive if the Radiator recieves the second or third stop > record from the NAS

(RADIATOR) Time based logging

Dear Sir, We want to allow a group of users to log only from say 10:00 to 18:00 hours. If a user belonging to this group is logged at 18:00 hours he should be disconnected. How can we do it in Radiator. Thanks & Regards. === Archive at http://www.starport.net/~radiator/ Announcements on [EMAI

Re: (RADIATOR) Different usage rates for different hours of day.

Hello - On Tue, 18 Jul 2000, cistron wrote: > Dear Sir, > > We want to use time based usage. A user should be charged different > rates if he is logged at prime time say from 9:00 to 16:00 and should be > charged lesser rate may be a percentage of the previous rate if he logs > at other times.

Re: (RADIATOR) Time based logging

Hello - On Tue, 18 Jul 2000, cistron wrote: > Dear Sir, > > We want to allow a group of users to log only from say 10:00 to 18:00 > hours. If a user belonging to this group is logged at 18:00 hours he > should be disconnected. How can we do it in Radiator. > You would specify the users like

(RADIATOR) dial-up error

Dear Sir,       I am having a problem setting a connection between the radiator server and cisco router, the main error I think is:   Acct-Terminate-Cause = Lost-Carrier   which is included in the logfile result listed below:     *** Received from 210.16.48.14 port 1645 Code:   Acce

(RADIATOR) What is the meaning of this?

*This message was transferred with a trial version of CommuniGate(tm) Pro* Hi. I got a little problem with a pair of netserver and Radiator 2.15. The netserver does not send authentication request, only accounting, and when I log the login and password of the dial-up users I found this: Tue Jul 1

(RADIATOR) FreeTDS and AIX

hi all, has anyone compiled FreeTDS on AIX? i have not been able to compile it on AIX. this is what i get: LD_RUN_PATH="" ld -o blib/arch/auto/DBD/FreeTDS/FreeTDS.so -bhalt:4 -bM:SRE -bI:/usr/local/lib/perl5/5.00502/aix/CORE/perl.exp -bE:FreeTDS.exp -b noentry -lc -L/usr/local/lib FreeTDS.o db

(RADIATOR) Simultaneous-use in 2.15

Hello everyone, I'm having problems getting the simultaneous-use check item to work. I've tried using the internal SessionDatabase and an external SessionDatabase (using mysql), but Radiator doesn't report a rejection on a second login session either way. I've attached my radius.cfg. Some samp

Re: (RADIATOR) dial-up error

Hello Benjamin - Thanks for sending the log file. The log shows that although you return a "Service-Type = Framed-User" to the NAS, it is starting up a session with "Service-Type = NAS-Prompt-User". And I am guessing that because there is no valid response the connection is dropped after 15 seco

Re: (RADIATOR) Simultaneous-use in 2.15

Hello William - I will need to see a trace 4 debug as well as what you have sent this time. thanks Hugh On Wed, 19 Jul 2000, William Hernandez wrote: > > Hello everyone, > > I'm having problems getting the simultaneous-use check item to work. I've > tried using the internal SessionDatabase

(RADIATOR) AddressAllocator SQL - "confirm" appears disabled

Was having a look through the code after having some 'out of IP Addresses' problems -- and noticed that the "confirmed" state doesn't seem to be implemented. Is there any ETA on this? It would be great when "No free IP addresses" occurs, it works through the 'unconfirmed' RADPOOL entries (STATE=

(RADIATOR) Using databases (efficiently) in Hooks

I've no doubt been coding messily to date - but am trying to tidy up and optimise our Radiator code. At the moment we (I) use code like: (as an excerpt from a Hook) -- my $dbh = DBI->connect("DBI:mysql::x","radius","x