(RADIATOR) Needs expet's opinion

[Ingvar Berg (LI/EAB)]

Maybe task 1 can be accomplished by SessionTimeout, if you can set it to a large enough value. If you can't set it to the full month (2678400 sec), it might be acceptable to disconnect the user a bit more frequent.

And task 2 can be accomplished by using the interim accounting to check the limit and disconnect the user when he goes above it. That would have to be done in a hook and/or an DIY AuthBy method.

/Ingvar

> -----Original Message-----
> From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au]On
> Behalf Of Hugh Irvine
> Sent: den 9 augusti 2004 13:00
> To: MJ
> Cc: radiator at open.com.au
> Subject: Re: (RADIATOR) Needs expet's opinion
> 
> 
> 
> 
> Hello MJ -
> 
> For both of these applications you will need to run a cron job that 
> checks the user accounts, disables the account (sets STATUS to 0 or 
> whatever) and then disconnects the user using whatever method 
> your NAS 
> equipment supports.
> 
> You should do some experiments and some downloads to check 
> what values 
> you get back in the accounting requests.
> 
> Set up a test call and do a 1 megabyte download then disconnect - and 
> then check the values sent by the NAS in the accounting stop.
> 
> BTW - you will probably need to enable interim accounting on your NAS 
> equipment (also called accounting alives).
> 
> regards
> 
> Hugh
> 
> 
> On 9 Aug 2004, at 20:48, MJ wrote:
> 
> > Hi Hugh,
> > Thanks, it is working fine. I have two more question, sorry 
> for lots of
> > questions
> >
> > 1- we are planning to use Radiator mostly for ADSL customers who 
> > usually
> > keep connected for weeks without disconnection, now users who has 
> > monthly
> > subscription will keep connected even after their expiry 
> dates until 
> > they
> > disconnect and then radiator will not allow them to 
> re-connect. How we 
> > can
> > disconnect such users at the moment they reaches to their 
> expiry dates?
> >
> > 2- we want to bill our ADSL customers based on their 
> downloads, I have 
> > gone
> > through the a discussions on mailing archive and RFCs you copied in 
> > reply,
> > but still didn't get exact answer, my understanding is that 
> > ACCTOUTPUTOCTETS
> > is the "bytes downloaded by user" and ACCTOUTPUTOCTETS is the "bytes
> > uploaded by user". Please confirm. Here also we need to 
> disconnect the 
> > user
> > once he reaches to his download limit.
> 
> 
> 
> NB: have you included a copy of your configuration file (no secrets),
> together with a trace 4 debug showing what is happening?
> 
> -- 
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. Available on *NIX, *BSD, Windows, MacOS X.
> -
> Nets: internetwork inventory and management - graphical, extensible,
> flexible with hardware, software, platform and database independence.
> -
> CATool: Private Certificate Authority for Unix and Unix-like systems.
> 
> --
> 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.
> 

--
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.