Re: (RADIATOR) Logging to MSSQL 7.0

2002-03-10 Thread Hugh Irvine
Hello Dan - On Sun, 10 Mar 2002 06:04, Dan Melomedman wrote: First, let me add my praise about this product to the already long list. We're evaluating Radiator. This is the best commercial server product I have ever dealt with, great job! Finally a RADIUS server that's almost, if not,

Re: (RADIATOR) Restricting login by NAS

2002-03-10 Thread Hugh Irvine
Hello Barry - The best way to do this is by setting the Identifier tag in each of your Client clauses, then using the Client-Identifier check item. For example: Client . Identifier x . /Client Client . Identifier x . /Client Client

Re: (RADIATOR) Restricting login by NAS

2002-03-10 Thread Hugh Irvine
Hello Barry - Yes you can use the same Identifier in different Client clauses - that is why it is so useful to do it this way. regards Hugh On Mon, 11 Mar 2002 09:26, Barry Andersson wrote: Thanks Hugh, Can you have the same Identifier for different clients as your example suggests?

Re: (RADIATOR) Multiple database failover

2002-03-10 Thread Elias
Hi Hugh, The configuration I'm testing works if I remove the ClientListSQL clause. Any ideas why this is causing the config to not work? If I understand correctly, this query is only done once when Radiator first starts up right? - Elias - - Original Message - From: Hugh Irvine

Re: (RADIATOR) Multiple database failover

2002-03-10 Thread Hugh Irvine
Hello Elias - This is most odd. Does the configuration work correctly without the ClientListSQL clause for both authentication and accounting to the same database? thanks Hugh On Mon, 11 Mar 2002 15:01, Elias wrote: Hi Hugh, The configuration I'm testing works if I remove the

Re: (RADIATOR) Strange Problem, no billing data

2002-03-10 Thread Hugh Irvine
Hello Marcel - It sounds like the 2611 is not configured correctly for radius accounting. You should do a debug on the 2611 to see what it is doing. You might also check your access lists and filters, as the accounting port number is different from the authentication port (1645/1812 and

Re: (RADIATOR) Strange Problem, no billing data

2002-03-10 Thread Marcel Welschbillig
Hugh, Thanks for the reply. I have attached the config and debug info, i have looked at this for many days and found nothing obvious (my knowlege on radius is limited) and tried many different things and come to no conclusion. If you can see anything wrong please let me know. Also i have

Re: (RADIATOR) Multiple database failover

2002-03-10 Thread Elias
Hi Hugh, We don't log acct to the database but auth with the multiple failovers work without the clause. - Elias - - Original Message - From: Hugh Irvine [EMAIL PROTECTED] To: Elias [EMAIL PROTECTED]; Radiator Mailing [EMAIL PROTECTED] Sent: Monday, March 11, 2002 1:58 PM Subject: Re:

Re: (RADIATOR) Strange Problem, no billing data

2002-03-10 Thread Hugh Irvine
Hello Marcel - Thanks for sending the debug. It appears that you are sending the radius accounting to 202.65.68.8:1646 and the authentication to 202.65.68.8:1645. There is a response from the radius server in both cases. Could you please send me a copy of your configuration file (no

(RADIATOR) Recording Disconnect causes

2002-03-10 Thread Brian Morris
Hi all, We are currently recording the Acct-Terminate-Cause in our stop records which is very useful for diagnosing problems. We now have another NAS which is sending us Ascend-Disconnect-Cause instead of Acct-Terminate-Cause in the Stop record. Is there any way of configuring Radiator to

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

2002-03-10 Thread Bob Shafer
We're using Radiator to authenticate a Cisco VPN 3000. I would like to assign an IP address to the client on the basis of the user. The user file looks like this: DU_Users_Test Password=XXX Class=OU=DU_Users_Test;, Altiga-IPSec-Authentication-G=RADIUS,