(RADIATOR) AllowInReply question

Hi, I've been looking at AllowInReply and it has saved some ReplyHook coding ;) What it doesn't seem to do is provide for checking of the assigned value in a variable. An example of this would be the cisco-avpair variable which can be assigned many variables. Is there a way to use

(RADIATOR) Spurious User has no time left

Radiator 2.18: Wed Aug 15 15:26:06 2001: DEBUG: Query is: select ENCRYPTEDPASSWORD, STATICADDRESS, TIMELEFT, MAXLOGINS, FRAMED_NETMASK, FRAMED_FILTER_ID from RADUSERS where USERNAME='access15' and VALIDFROM 997860366 and VALIDTO 997860366 Wed Aug 15 15:26:06 2001: DEBUG: User access15 has

Re: (RADIATOR) Global attributes

Hello Cliff - This is very easy to configure - something like this: # define AuthBy clauses AuthBy SQL Identifier CheckSQL . /AuthBy AuthBy RADIUS Identifier CheckAnotherRadiusServer . /AuthBy # define Realms or Handlers Handler ...

Re: (RADIATOR) Radiator 2.18.2 SYSLOG failing

Hello Colin - Have you installed the prerequisite Perl package? This is from section 6.11 in the Radiator reference manual: Log SYSLOG requires Sys::Syslog, which in turn requires syslog.ph to have been constructed on your system by the Perl utility h2ph. If you want to use Log SYSLOG, you

Re: (RADIATOR) AllowInReply question

Hello Gareth - On Wednesday 15 August 2001 16:38, Gareth Coco wrote: Hi, I've been looking at AllowInReply and it has saved some ReplyHook coding ;) What it doesn't seem to do is provide for checking of the assigned value in a variable. An example of this would be the cisco-avpair

Re: (RADIATOR) Global attributes

Hugh, First let me say thanks for the quick response which helped a great deal. Will I be able to add things such as session-limits and idle-timeouts and force them to the next radius server no matter what attributes they may have? We are worried that the customer we are passing through to

(RADIATOR) Shadow Perl module and Radiator

Hi, I'm trying to get a legacy realm working, it's a Solaris 2.6 SPARC system. I installed the Shadow module as indicated in the documentation (in fact, it's two modules: Shadowf.pm and Shadows.pm), but all auth fails: Wed Aug 15 13:07:11 2001: DEBUG: Handling with Radius::AuthSYSTEM Wed Aug 15

(RADIATOR) Removing admin users

Hello, What is the best way within an AuthBy SQL or Handler section to make sure that I do not put accounting stops from user 'admin' into my database. All they do is clutter up what is already a large database. I currently have the following Handler for Accounting packets: # Handle all

(RADIATOR) Writing a postAuthHook

Hugh, I am writing a postAuth Hook program in perl to be able to hand sending specific reply attributes based on the NAS type. Our mySql database has a RADCLIENTLIST table radiator pulls the authentication for the NAS's from, and in that, it has a NASTYPE column. Would the information in that

(RADIATOR) Writing to log file

Hi all, Is there a way to write a statement to the log file from a PostAuthHook? For example, when a user is authenticated, I'd like to log that. Thanks. Griff Hamlin, III === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL

Re: (RADIATOR) Removing admin users

Hello Griff - Try this: Handler User-Name = admin, Request-Type = Accounting-Request . /Handler Handler Request-Type = Accounting-Request .. /Handler hth Hugh On Thursday 16 August 2001 04:24, Griff Hamlin wrote: Hello, What is the best way within an AuthBy SQL

Re: (RADIATOR) Writing to log file

Hello Griff - On Thursday 16 August 2001 06:34, Griff Hamlin wrote: Hi all, Is there a way to write a statement to the log file from a PostAuthHook? For example, when a user is authenticated, I'd like to log that. Thanks. There are some examples of calling the log functions in the file

Re: (RADIATOR) Global attributes

Hello Cliff - On Wednesday 15 August 2001 22:41, Cliff Cole wrote: Hugh, First let me say thanks for the quick response which helped a great deal. Will I be able to add things such as session-limits and idle-timeouts and force them to the next radius server no matter what attributes

Re: (RADIATOR) Writing a postAuthHook

Hello Kyle - On Thursday 16 August 2001 06:51, Kyle wrote: Hugh, I am writing a postAuth Hook program in perl to be able to hand sending specific reply attributes based on the NAS type. Our mySql database has a RADCLIENTLIST table radiator pulls the authentication for the NAS's from, and

Re: (RADIATOR) Shadow Perl module and Radiator

Hello Pascal - It looks like you are using CHAP authentication? If so, it won't work. You can only use PAP authentication with encrypted passwords. hth Hugh On Thursday 16 August 2001 03:20, Pascal Robert wrote: Hi, I'm trying to get a legacy realm working, it's a Solaris 2.6 SPARC

(RADIATOR) Missing Attributes

Hi All, I am receiving the following error in our log file : ERR: Attribute number 87 (vendor ) is not defined in your dictionary Can anyone tell me what this attribute is and (ideally) the line to put into our dictionary file to stop these errors. We are using a Unisphere ERX for our ADSL

(RADIATOR) AuthLDAP2.pm patch

Just found a little bug in AuthLDAP2.pm from Radiator 2.18.2, so I'm supplying a fix. When processing AuthAttrDef request items, if the LDAP attribute was multi-valued (such as objectClass), Radiator would only store the first array value in the RADIUS attribute. This is inconsistent because