Re: (RADIATOR) Session-Timeout getting set too late

Hello Jeff - The first thing you should do is read the radius rfc's and the Radiator reference manual (both contained in the "doc" directory of the distribution). Then you should read the Radiator source code to find out how it works. And we also offer training courses if that is of interest.

(RADIATOR) Platypus LoginLimit Checking problems

We are having a problem setting up Simultaneous-Use restriction on our Radiator 3.2/Platypus 3/MS SQL 7 setup.  It appears that we can't get Radiator to stop if it finds the LoginLimit exceeding the DefaultSimultaneousUse value.  Am I just completely missing something or am I completely miss

Re: (RADIATOR) AuthByPolicy Question: ContinueUntilAccept

Hello Jon - If there is no AuthBy clause that "Accept"'s in your sequence, then the overall result will be "Reject" (you don't have to do anything special). What is the last AuthBy in your sequence doing? If it is just doing accounting, that may be your problem. regards Hugh

Re: (RADIATOR) Session-Timeout options

Hello Brian - You will probably want to write a hook to do this. regards Hugh On Tuesday, Jan 21, 2003, at 13:55 Australia/Melbourne, Brian Morris wrote: Hi All, Is it possible to set a session timeout to the lesser of (say) 4 hours or [TimeRemaining] Where [TimeRemaining] is however muc

(RADIATOR) Session-Timeout options

Hi All, Is it possible to set a session timeout to the lesser of (say) 4 hours or [TimeRemaining] Where [TimeRemaining] is however much time credit the customer has remaining on teir account. I know you can set it to one OR the other, but how about the lesser of the two? Regards, Brian Morris

Re: (RADIATOR) Alcatel SMC proxy radius -->Radiator issue (fwd)

Indeed, it works smoothly. Radiator is incredibly adaptative to cover a lot of possible situations Thanks Hugh for your fine support as always. Best regards --Abel On Fri, 17 Jan 2003, Hugh Irvine wrote: > > Hello Abel - > > Your problem is due to your use of "DefaultReply" which only adds th

Re: (RADIATOR) AuthByPolicy Question: ContinueUntilAccept

Couldn't you do some groups.       Identifier    AlwaysReject     DefaultResult   REJECT     Identifier    AlwaysIgnore     DefaultResult   IGNORE       AuthByPolicy ContinueWhileIgnore            AuthByPolicy ContinueUntilAccept         AuthBy  niiVispAuthClear        AuthBy  ni

(RADIATOR) Proxy RADIUS problem

-- Forwarded Message -- Subject: BOUNCE [EMAIL PROTECTED]:Non-member submission from [Richard Vander Reyden <[EMAIL PROTECTED]>] Date: Mon, 20 Jan 2003 12:33:19 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] >From [EMAIL PROTECTED] Mon Jan 20 12:33:19 2003 Received:

(RADIATOR) AuthByPolicy Question: ContinueUntilAccept

Hi, I am having a little bit of trouble with some complex AuthBy handling I am doing.  I have customers in various states of conversion to some new dialup settings and I am having to jump through 15 different hoops when authenticating them.  The problem I am having is when I set my AuthByP

(RADIATOR) Session-Timeout getting set too late

Two questions: 1. I have had Radiator thrown at me. I have no knowledge of the system and feel like I am in way over my head. Can anyone recommend good reading, courses or other ways to get educated? 2. The problem I have had thrown at me... I have been asked to set a session timeout based on

Re: (RADIATOR) Using AcctSQLStatement with integer-date format

Hi again, I'm trying to use something like AcctColumnDef CONNECTTIME,%b-0%{Acct-Session-Time},integer-date but it doesn't work. It gives a NULL value for the CONNECTTIME attribute. I have also tried AcctColumnDef CONNECTTIME,%{Timestamp}-0%{Acct-Session-Time},integer-date If I write AcctColumnD