Radiator is nicely designed to accept RADIUS accounting packets
and store them in an SQL database. The config is a little
tricky, but generally speaking:
-- skeleton config --
AuthByPolicy ContinueAlways
<AuthBy SQL>
# Disable authentication via SQL
AuthSelect
# [ follow instructions for AuthBy SQL for accounting ]
</AuthBy>
<AuthBy YOUR_PREFERRED_AUTHBY_METHOD>
# [ whatever you normally put here ]
</AuthBy>
----------------------
The trick is to use the AuthByPolicy ContinueAlways to let it
cascade from the <AuthBy SQL> on to your preferred <AuthBy>
method.
I posted my configuration for Oracle accounting not too
long ago. You can use it for hints. I think the best
hint is in the online documentation at
http://www.open.com.au/radiator/ref.html
At 08:40 AM 7/19/99 -0400, Jamie Orzechowski wrote:
>I am having a problem with spammers and need a way to track them down.
>
>what I need is a config that will send the:
>
>date
>start time
>stop time
>username
>ip address
>callerID
>
>and store this into an SQL database (MS SQL 6.5) ...
>
>I will then be able to make querys and pull up the info I need ... any ideas
>how I create the database table and the config to send to info into the
>database ??
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
