(RADIATOR) ERR: Attribute number 1 is not defined in your dictionary

-- Forwarded Message -- Subject: BOUNCE [EMAIL PROTECTED]:Non-member submission from [buck [EMAIL PROTECTED]] Date: Fri, 8 Mar 2002 17:50:19 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] From [EMAIL PROTECTED] Fri Mar 8 17:50:19 2002 Received: from

Re: (RADIATOR) Restricting login by NAS

-- Forwarded Message -- Subject: BOUNCE [EMAIL PROTECTED]:Non-member submission from [Japheth Cleaver [EMAIL PROTECTED]] Date: Fri, 8 Mar 2002 21:58:58 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] From [EMAIL PROTECTED] Fri Mar 8 21:58:58 2002 Received: from

Re: (RADIATOR) ERR: Attribute number 1 is not defined in your

-- Forwarded Message -- Subject: BOUNCE [EMAIL PROTECTED]:Non-member submission from [neil d. quiogue [EMAIL PROTECTED]] Date: Mon, 11 Mar 2002 02:35:32 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] From [EMAIL PROTECTED] Mon Mar 11 02:35:31 2002 Received: from

(RADIATOR) AuthByPolicy and INFO messages

Hi! I use a configuration like this: AuthByPolicy ContinueWhileReject AuthBy SQL ... /AuthBy SQL AuthBy FILE ... /AuthBy Nearly all of our users can be authenticated using SQL, but there are 3 special accounts in the FILE defined. Not the problem is, that with Trace 4, the INFO records always

RE: (RADIATOR) unknown ports

Ah, thanks for the note. My thoughts are that, although there might be times when it might be useful to know the SOURCE port, I think that the large majority of times it's much more useful to know the local (server's) port where the requests are coming into. This is particularly true for those

(RADIATOR) have I missed something in the documentation?

Hello All, I have an impression that I've missed something in the Radiator's documentation.. Let me explain : we have the following configuration of Radiator (the extraction from the config file): AuthBy RADIUS

Re: (RADIATOR) Logging to MSSQL 7.0

Hugh Irvine writes: BTW - you say that Radiator is *almost* perfect - we would be keen to hear any suggestions for improvements. regards Hugh Hi Hugh, AuthLog Pipe: I'd like to be able to fork an external program, and pipe the log data to it for logging, instead of logging

RE: (RADIATOR) Logging to MSSQL 7.0

Here is my conf: # radius.cfg # # You should consider this file to be a starting point only # $Id: linux-radius.cfg,v 1.2 2001/08/30 03:41:02 mikem Exp $ #Foreground #LogStdout LogDir /var/log/radius DbDir /etc/radiator DictionaryFile %D/dictionary # Use a low trace level in

Re: (RADIATOR) Recording Disconnect causes

Hello Brian - This is very simple to do - just specify multiple AcctColumnDef's AcctColumnDef TERMINATECAUSE, Acct-Terminate-Cause AcctColumnDef TERMINATECAUSE, Ascend-Disconnect-Cause regards Hugh On Mon, 11 Mar 2002 18:20, Brian Morris wrote: Hi all, We are currently

Re: (RADIATOR) AuthByPolicy and INFO messages

Hello Roland - It is probably easiest to do what you suggest below and reverse the order of the AuthBy clauses. Keep in mind that the AuthBy FILE caches the file contents in memory at startup time, and you are only talking about a couple of memory lookups, so performance will not be impacted

Re: (RADIATOR) have I missed something in the documentation?

Hello Slava - The simplest way to do what you require is to use a NoReplyHook in the AuthBy RADIUS clauses. There is an example NoReplyHook in the examples in the file goodies/hooks.txt in the Radiator distribution. regards Hugh On Tue, 12 Mar 2002 00:57, Rimdenok, Sviatoslav wrote:

Re: (RADIATOR) Cisco/Altiga - Cannot obtain an IP address for remote peer

Hello Bob - I think you are correct - it sounds like the tunnel setup is not happening because there is no IP address specified for the remote end of the tunnel. You should check the Cisco web site for some examples of VPN tunnel configuration via radius. There is also an example in the

(RADIATOR) Radar: call for beta testers

Hello All, This is a call for Beta testers for our new Radar product. Radar is a real time inreractive GUI for remotely monitoring multiple Radiator servers. In summary, the features are: Runs on Unix and Windows Perl TK GUI (requires Tk 800.023) Monitor any number of Radiators. Visual

Re: (RADIATOR) Strange Problem, no billing data

Hello Marcel - Thanks for sending the trace. As far as I can see everything is working correctly. Here is what is happening with the accounting requests: Tue Mar 12 05:03:14 2002: DEBUG: Packet dump: *** Received from 202.65.74.130 port 1646 Code: Accounting-Request Identifier:

Re: (RADIATOR) Strange Problem, no billing data

Hugh, Thanks for looking at the files. This dose not explain why there is no billing data on the database though. So from this you can see that the accounting data is sent back and acknowleged by the radius server is that correct ? So am i right in assuming that my problem lies between