|
Hi
Authentication works fine.
We are collecting multiple start and stop
records for all connections.
We are using MAX IOS 6.1.3 and Radiator 2.1.5
with Oracle8i as the AuthBy SQL database both on Linux 6.1
We are currently testing this setup with only 1
user. The MAX Ethernet->Mod Config->Accounting -> Act
Timeout = 30
Once the user has connected:
Every 30 secs a start record is logged
and stored in the Oracle database.
When the user disconnects
Every 30 secs a stop record (with the
same AcctDelaytime as each start record) is stored.
Only one of each is required!!!!
Using the MAX "radif" debug tool one can see the
Accounting-Response from the Radiator service is being received
RADIF: _radiusAcctRequest: type 1 id 237, user name
<6:iwata>
RADIF: _radiusAcctReq: socket 5 len 98 IP 203.17.8.8 port 1027=>1646, ID=237 RADIF: _radCallback: buf=B05748E0 from 203.17.8.45 1646 RADIF: _radCallback: can't find entry for id 236 RADIF: radius type Acct ID = 238 RADIF: _radiusAcctRequest: type 1 id 238, user name <6:iwata> Has this something to with the MAX not accepting
the Accounting-Response for some reason?? (the can't find entry for id xx
logged)
Here are the config file contents: # # Example Radiator configuration file that allows you to # authenticate from an SQL database. # With Radiator you can interface with almost any databse schema, # and there are many more configurable parameters that allow you # to control database fallback, select statements, column names # and arrangements etc etc etc. # See the reference manual for more details. # This is a very simple exmaple to get you started. It will # work with the tables created by the goodies/*.sql scripts. # # You should consider this file to be a starting point only # $Id: sql.cfg,v 1.3 1999/07/29 02:38:10 mikem Exp $ Foreground
LogStdout LogDir . DbDir . Trace 5
# You will probably want to change this to suit your site. <Client DEFAULT> Secret garth DupInterval 0 </Client> # You can put client details in a database
table
# and get their details from there with something like this: <ClientListSQL> DBSource dbi:Oracle:ispl DBUsername ******* DBAuth ********* </ClientListSQL> # This will authenticate users from
SUBSCRIBERS
<Realm DEFAULT> <AuthBy SQL> # Adjust DBSource, DBUsername, DBAuth to suit your DB DBSource dbi:Oracle:ispl DBUsername ****** DBAuth ******* AuthSelect select password, checkattr, replyattr from subscribers where username='%n' # You may want to tailor these for your ACCOUNTING table AccountingTable ACCOUNTING AcctColumnDef USERNAME,User-Name AcctColumnDef TIME_STAMP,Timestamp,integer AcctColumnDef ACCTSTATUSTYPE,Acct-Status-Type AcctColumnDef ACCTDELAYTIME,Acct-Delay-Time,integer AcctColumnDef ACCTINPUTOCTETS,Acct-Input-Octets,integer AcctColumnDef ACCTOUTPUTOCTETS,Acct-Output-Octets,integer AcctColumnDef ACCTSESSIONID,Acct-Session-Id AcctColumnDef ACCTSESSIONTIME,Acct-Session-Time,integer AcctColumnDef ACCTTERMINATECAUSE,Acct-Terminate-Cause AcctColumnDef NASIDENTIFIER,NAS-Identifier AcctColumnDef NASPORT,NAS-Port,integer AcctColumnDef FRAMEDIPADDRESS,Framed-IP-Address </AuthBy> </Realm> <SessionDatabase SQL> DBSource dbi:Oracle:ispl DBUsername ****** DBAuth ************ </SessionDatabase> |
