Re: (RADIATOR) evaluator questions...
Hi, I have been using Radiator, authenticating and accounting via SQL, for about a year now and it works very well. Depending on your perl skills you can have/make radiator do just about anything that you want. In answer to your questions (anyone else on the list, please feel free to correct me ;) 1) I believe the source would have to modified to calculate and add a "Session-Limit" which would cause your NAS to disconnect the user at your end-time, from a quick glance it looks like it would take 3 or 4 lines (ok, I know there is someone out there who can do it in one :) in AuthGeneric.pm. 2) The log files are standard livingston format detailing every attribute sent in the acct packet. Again, I believe you would need to modify the source to only log certain attributes to a flat file, however you can define the attributes to log if you are detailing to an SQL database as we do. 3) We have no regrets about purchasing radiator, it has to be the most flexable auth solution free or commercial, especially if you can modify perl code. Good luck with your project... Kevin Sofnet, Inc. -Original Message- From: Richard Barnes [EMAIL PROTECTED] To: Radiator List [EMAIL PROTECTED] Date: Tuesday, September 21, 1999 10:07 AM Subject: (RADIATOR) evaluator questions... I'm currently evaluating Radiator to be used as our radius server. I like what I see so far, but I do have three questions. 1) I'm trying to figure out if I can set a time limit an account is allowed to be on. I know that I can set "windows" when an account can connect, but suppose I have an account that can connect Mon-Fri 8am-5pm (normal business hours). What happens if that account connects on Wed at 4:55pm. Unless they hang up, there's no way to make them disconnect at 5pm. 2) Is there a way I can control what info gets written out to the detail file? I'm currently using an old version of Livingston radius, and the records written out to the detail file are not as detailed. I like many of the new entries I'm getting in the detail file using Radiator, but I don't really need to know details like: USR-Simplified-MNP-Levels = ccittV42 USR-Simplified-V42bis-Usage = ccittV42bis Acct-Input-Octets = 287 Acct-Output-Octets = 266 Acct-Input-Packets = 13 Acct-Output-Packets = 12 I'm using USR HiperARC chassis (and some older NetServs). I'm doing "AuthBy DBFILE" and have Nocache specified. Also, running on Solaris 2.5.1 (just trying to give as much info upfront ) 3) My final question is "Is there anybody on this list that regrets choosing Radiator". I've read through some of the archives, and I've seen some of the normal complaints I would expect to see with any product. I'm leaning heavily towards purchasing it, but I figure I should ask the community of users who use it everyday, and get their opinion. === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) evaluator questions...
1) I'm trying to figure out if I can set a time limit an account is allowed to be on. I know that I can set "windows" when an account can connect, but suppose I have an account that can connect Mon-Fri 8am-5pm (normal business hours). What happens if that account connects on Wed at 4:55pm. Unless they hang up, there's no way to make them disconnect at 5pm. Here is a fairly recent post from Mike McCauley = I have uploaded a new version of AuthGeneric.pm that understands a special format of Session-Timeout: Session-Timeout = until 1800 for example would compute a Session-Timeout in seconds until 6 pm. If its after 6pm, it will be 6pm the next day. Download from http://www.open.com.au/radiator/downloads/patches-2.14.1/AuthGeneric.pm and let me know if it works for you. Cheers. = 2) Is there a way I can control what info gets written out to the detail file? I'm currently using an old version of Livingston radius, and the records written out to the detail file are not as detailed. I like many of the new entries I'm getting in the detail file using Radiator, but I don't really need to know details like: Someone correct me if I'm wrong but I think you need to use SQL logging if you want to only record a subset of the results. 3) My final question is "Is there anybody on this list that regrets choosing Radiator". I've read through some of the archives, and I've seen some of the normal complaints I would expect to see with any product. I'm leaning heavily towards purchasing it, but I figure I should ask the community of users who use it everyday, and get their opinion. We like it :-) Stuart === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) evaluator questions...
On Tue, 21 Sep 1999, Kevin Wormington wrote: Hi, I have been using Radiator, authenticating and accounting via SQL, for about a year now and it works very well. Depending on your perl skills you can have/make radiator do just about anything that you want. In answer to your questions (anyone else on the list, please feel free to correct me ;) 1) I believe the source would have to modified to calculate and add a "Session-Limit" which would cause your NAS to disconnect the user at your end-time, from a quick glance it looks like it would take 3 or 4 lines (ok, I know there is someone out there who can do it in one :) in AuthGeneric.pm. Isn't there a new check item you can set that does that? I thought I saw something loke that a month or so back. 2) The log files are standard livingston format detailing every attribute sent in the acct packet. Again, I believe you would need to modify the source to only log certain attributes to a flat file, however you can define the attributes to log if you are detailing to an SQL database as we do. That is not true; actually you can define the detail log format and specify exactly what you want logged. I do this right now. 3) We have no regrets about purchasing radiator, it has to be the most flexable auth solution free or commercial, especially if you can modify perl code. I agree, it's the most flexible, yet easy to use, package I've ever seen. === David M. Lloyd mailto:[EMAIL PROTECTED] Administrator Internet Express, Inc. 802 W. Broadway, Suite 0101 Madison, WI. 53713-1866 Voice: (608) 663- http://www.inxpress.net Fax: (608) 663-5595 mailto:[EMAIL PROTECTED] Data: (608) 663-5551mailto:[EMAIL PROTECTED] === === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
