(RADIATOR) Radiator - Config & results

Goboxe goboxe at gmail.com
Fri Jun 13 23:13:48 CDT 2008


Hi,

I need your help to verify that I am in the right track for Radiator
installation on Windows 2003 & using PostgreSQL.

I have 3 observations below, pls scroll down.

1. Below is my radiator.cfg

#----------------------------------------------------------------------------------------------------
# windows.cfg
#
# Example Radiator configuration file.
# This very simple file will allow you to get started with
# a simple system on Windows. You can then add and change features.
# We suggest you start simple, prove to yourself that it
# works and then develop a more complicated configuration.
#
# This example is expected to be installed in
#   c:\Program Files\Radiator\radius.cfg
# It will authenticate from a standard users file in
#   c:\Program Files\Radiator\users
# it will log debug and other messages to
#   c:\Program Files\Radiator\logfile
# and log accounting to a file in
#   c:\Program Files\Radiator\detail
# (of course you can change all these by editing this config file if you
wish)
#
# It will accept requests from any client and try to handle requests
# for any realm.
# And it will print out what its doing in great detail to the log file.
#
# See radius.cfg for more complete examples of features and
# syntax, and refer to the reference manual for a complete description
# of all the features and syntax.
#
# You should consider this file to be a starting point only
# $Id: windows.cfg,v 1.1 2003/03/27 09:41:28 mikem Exp $
Foreground
LogStdout
LogDir  c:/Program Files/Radiator
DbDir  c:/Program Files/Radiator
# This will log at DEBUG level: very verbose
# User a lower trace level in production systems, typically use 3
Trace   4
# You will probably want to add other Clients to suit your site,
# one for each NAS you want to work with. This will work
# at least with radpwtst running on the local machine
<Client DEFAULT>
 Secret mysecret
 DupInterval 0
</Client>

# Authenticate all realms with this
<Realm DEFAULT>
 <AuthBy SQL>
  DBSource dbi:Pg:dbname=radiator
  DBUsername sa
  DBAuth vision2020
  AuthSelect select PASSWORD from SUBSCRIBERS \
  where USERNAME=%0
 # store accounting records in RADUSAGEyyyymm table
 AccountingTable ACCOUNTING
 # maybe update if this is a duplicate
 AcctInsertQuery update or insert into %0 (%1) values (%2)
 # Log all accounting to a single log file in LogDir
 AcctFailedLogFileName %L/misseddetails

 </AuthBy>
</Realm>


2. Next, I run "perl radpwtst -user mikem -password frjhjlkhlo" and got the
log below.
I still wondering why I do not see any SQL statement like SELECT, INSERT in
the log.


Sat Jun 14 02:53:19 2008: DEBUG: Finished reading configuration file
'C:\Program Files\Radiator\radius.cfg'
Sat Jun 14 02:53:19 2008: DEBUG: Reading dictionary file 'c:/Program
Files/Radiator/dictionary'
Sat Jun 14 02:53:19 2008: DEBUG: Creating authentication port 0.0.0.0:1645
Sat Jun 14 02:53:19 2008: DEBUG: Creating accounting port 0.0.0.0:1646
Sat Jun 14 02:53:19 2008: NOTICE: Server started: Radiator 4.2 on
MYCBJ01T600022 (LOCKED)
Sat Jun 14 02:53:53 2008: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 2471 ....
Code:       Accounting-Request
Identifier: 154
Authentic:  d<241><165><201>{<197><214>W+<234>d<27>WT<145>]
Attributes:
 User-Name = "mikem"
 Service-Type = Framed-User
 NAS-IP-Address = 203.63.154.1
 NAS-Identifier = "203.63.154.1"
 NAS-Port = 1234
 NAS-Port-Type = Async
 Acct-Session-Id = "00001234"
 Acct-Status-Type = Start
 Called-Station-Id = "123456789"
 Calling-Station-Id = "987654321"
 Acct-Delay-Time = 0
Sat Jun 14 02:53:53 2008: DEBUG: Handling request with Handler
'Realm=DEFAULT'
Sat Jun 14 02:53:53 2008: DEBUG:  Adding session for mikem, 203.63.154.1,
1234
Sat Jun 14 02:53:53 2008: DEBUG: Handling with Radius::AuthSQL:
Sat Jun 14 02:53:53 2008: DEBUG: Handling accounting with Radius::AuthSQL
Sat Jun 14 02:53:53 2008: DEBUG: AuthBy SQL result: ACCEPT,
Sat Jun 14 02:53:53 2008: DEBUG: Accounting accepted
Sat Jun 14 02:53:53 2008: DEBUG: Packet dump:
*** Sending to 127.0.0.1 port 2471 ....
Code:       Accounting-Response
Identifier: 154
Authentic:  d<241><165><201>{<197><214>W+<234>d<27>WT<145>]
Attributes:
Sat Jun 14 02:53:53 2008: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 2471 ....
Code:       Accounting-Request
Identifier: 155
Authentic:  <27><225><9><214><29><254><200><247><197><172><195>'9<186>"<166>
Attributes:
 User-Name = "mikem"
 Service-Type = Framed-User
 NAS-IP-Address = 203.63.154.1
 NAS-Identifier = "203.63.154.1"
 NAS-Port = 1234
 NAS-Port-Type = Async
 Acct-Session-Id = "00001234"
 Acct-Status-Type = Stop
 Called-Station-Id = "123456789"
 Calling-Station-Id = "987654321"
 Acct-Delay-Time = 0
 Acct-Session-Time = 1000
 Acct-Input-Octets = 20000
 Acct-Output-Octets = 30000
Sat Jun 14 02:53:53 2008: DEBUG: Handling request with Handler
'Realm=DEFAULT'
Sat Jun 14 02:53:53 2008: DEBUG:  Deleting session for mikem, 203.63.154.1,
1234
Sat Jun 14 02:53:53 2008: DEBUG: Handling with Radius::AuthSQL:
Sat Jun 14 02:53:53 2008: DEBUG: Handling accounting with Radius::AuthSQL
Sat Jun 14 02:53:53 2008: DEBUG: AuthBy SQL result: ACCEPT,
Sat Jun 14 02:53:53 2008: DEBUG: Accounting accepted
Sat Jun 14 02:53:53 2008: DEBUG: Packet dump:
*** Sending to 127.0.0.1 port 2471 ....
Code:       Accounting-Response
Identifier: 155
Authentic:  <27><225><9><214><29><254><200><247><197><172><195>'9<186>"<166>
Attributes:


3. After that, I check PostgreSQL log and only see the following entry which
I believe call from Radiator.
And still wondering why no new records created in Accounting table

2008-06-14 02:56:24 LOG:  statement: SELECT count(*) FROM public.accounting
WHERE false
2008-06-14 02:56:24 LOG:  duration: 0.000 ms
2008-06-14 02:56:24 LOG:  QUERY STATISTICS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20080614/8ed840b6/attachment.html>


More information about the radiator mailing list