(RADIATOR) Problems with AuthLog SQL
Robert Blayzor
noc at inoc.net
Thu May 30 09:02:12 CDT 2002
Hi Hugh,
I have a small problem with AuthLog SQL. I posted a previous message
and just assumed to try putting the connect information in the config
file. It appears to work.
I get the results placed in the database, and trace 4 shows no errors...
Thu May 30 09:56:34 2002: DEBUG: Radius::AuthSQL looks for match with
kdelaet
Thu May 30 09:56:34 2002: DEBUG: Radius::AuthSQL REJECT: Bad Password
Thu May 30 09:56:34 2002: INFO: Access rejected for kdelaet: Bad
Password
Thu May 30 09:56:34 2002: DEBUG: do query is: EXEC sp_RadiusAuthLog
'0','kdelaet','kdelaet','64.246.152.18','','','Bad Password'
Thu May 30 09:56:34 2002: DEBUG: Packet dump:
*** Sending to 64.246.152.18 port 1812 ....
But, I'm getting these messages printed in the console I have run
Radiator from, quite frequently:
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 1 Bad Password
Radius::Radius=HASH(0x857924c)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 0
Radius::Radius=HASH(0x854949c)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 1 Bad Password
Radius::Radius=HASH(0x8571c24)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 0
Radius::Radius=HASH(0x8549784)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 0
Radius::Radius=HASH(0x8571c90)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 1 Bad Password
Radius::Radius=HASH(0x85711bc)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 1 Bad Password
Radius::Radius=HASH(0x85474d8)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 0
Radius::Radius=HASH(0x8571fb4)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 0
Radius::Radius=HASH(0x8571d20)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 1 Bad Password
Radius::Radius=HASH(0x8547430)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 1 Bad Password
Radius::Radius=HASH(0x857a03c)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 1 Bad Password
Radius::Radius=HASH(0x854dfcc)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 0
Radius::Radius=HASH(0x85474d8)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 0
Radius::Radius=HASH(0x8571d98)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 1 Bad Password
Radius::Radius=HASH(0x8571f6c)
AuthLogSQL log Radius::AuthLogSQL=HASH(0x83152b8) 0
Radius::Radius=HASH(0x85711f8)
My config section seems fine. If I comment out the use of my AuthLog,
these errors disappear.
<AuthLog SQL>
DBSource dbi:Sybase:server=SQL
DBUsername xxxx
DBAuth xxxx
Identifier SQL-AuthLog1
FailureQuery EXEC sp_RadiusAuthLog
'%{GlobalVar:ServerID}','%n','%{Class}','%N','%{Called-Station-Id}','%{C
alling-Station-Id}',%1
LogSuccess 0
LogFailure 1
</AuthLog>
--
Robert Blayzor, BOFH
INOC, LLC
rblayzor at inoc.net
Meets quality standaFrom owner-radiator at open.com.au Thu May 30 07:03:30 2002
Received: (from majordomo at localhost)
by server1.open.com.au (8.11.0/8.11.0) id g4UC3UZ13098
for radiatorzz-list; Thu, 30 May 2002 07:03:30 -0500
X-Authentication-Warning: server1.open.com.au: majordomo set sender to owner-radiator at open.com.au using -f
Received: from mx1.inoc.net (mx1.inoc.net [64.246.131.30])
by server1.open.com.au (8.11.0/8.11.0) with ESMTP id g4UC3T313095
for <radiator at open.com.au>; Thu, 30 May 2002 07:03:29 -0500
Received: from nimbus (unverified [10.0.0.111]) by mx1.inoc.net
(Vircom SMTPRS 5.2.204) with ESMTP id <B0004139906 at mx1.inoc.net> for <radiator at open.com.au>;
Thu, 30 May 2002 09:28:02 -0400
Reply-To: <rblayzor at inoc.net>
From: "Robert Blayzor" <noc at inoc.net>
To: <radiator at open.com.au>
Subject: (RADIATOR) AuthLog questions
Date: Thu, 30 May 2002 09:28:02 -0400
Organization: INOC, LLC
Message-ID: <004401c207dd$d2c025d0$6f00000a at z0.inoc.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-radiator at open.com.au
Precedence: bulk
List-Id: <radiator.list-id.open.com.au>
I've followed the Radiator manual for <AuthLog SQL>
Here are my config entries:
<AuthLog SQL>
Identifier SQL-AuthLog1
FailureQuery EXEC sp_RadiusAuthLog
'%{GlobalVar:ServerID}','%n','%{Class}','%N','%{Called-Station-Id}','%{C
alling-Station-Id}','%1'
LogSuccess 0
LogFailure 1
</AuthLog>
<Handler>
RewriteUsername s/^(P|C|S)//
RewriteUsername tr/A-Z/a-z/
RewriteUsername s/\s+//g
AuthByPolicy ContinueAlways
AuthBy Acct-SQL
AuthBy Auth-NAS
AuthLog SQL-AuthLog1
SessionDatabase Null-SDB
</Handler>
My questions is, how does AuthLog SQL know which database source to use?
Or will it assume to use the same source as the AuthBy? Or does it
accept DBSource, etc? The manual does not state so. All the manual
states is:
6.50 <AuthLog SQL>
The clause indicates to log authentication successes and failures to an
SQL database. You can define as many <AuthLog SQL> clauses as you wish
at the top level or within Realm or Handler clauses. Each clause can
specify different logging conditions and a different log database.
As well as the generic parameters described in Section 6.48 , AuthLog
SQL understands the following parameters:
Please advise.
--
Robert Blayzor, BOFH
INOC, LLC
rblayzor at inoc.net
If the automobile had followed the same development cycle as the
computer, a Rolls-Royce would today cost $100, get a million miles per
gallon, and explode once a year, killing everyone inside. - Robert X.
Cringely
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
rds: Compiles without errors.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
More information about the radiator
mailing list