(RADIATOR) Accounting depending on RADIUS field value
Hugh Irvine
hugh at open.com.au
Mon Mar 13 03:19:42 CST 2006
Hello Emilio -
Could you please tell me the name of the registered company that has
purchased this copy of Radiator?
Please reply to me directly.
In answer to your question, you can do something like this:
<Handler Acct-Terminate-Cause = NAS-Error>
<AuthBy INTERNAL>
AcctResult ACCEPT
</AuthBy>
</Handler>
<Handler>
<AuthBy SQL>
AuthSelect select ---
AccountingTable ACCT_ADSL
AcctColumnDef ACADSL_ID_USUARIO,User-Name
AcctColumnDef ACADSL_TIPO_ACCOUNTING,Acct-Status-Type
AcctColumnDef ACADSL_NASIDENTIFIER,NAS-IP-Address
...
AcctColumnDef ACADSL_TERMINATECAUSE,Acct-Terminate-Cause
HandleAcctStatusTypes Start,Stop
NoDefault
</AuthBy>
</Handler>
And you are correct in your understanding regarding the processing of
the accounting requests - its just that some AuthBy clauses (like
AuthBy SQL) process accounting requests as well as authentication
requests. Check the manual for details ("doc/ref.html").
regards
Hugh
On 13 Mar 2006, at 19:56, Emilio Mira Alfaro wrote:
> Hi list,
>
> I have a couple of questions I haven't found an answer for in the
> documentation.
>
> Our authentication handler looks like this:
>
> <Handler>
> <AuthBy SQL>
> AuthSelect select ---
>
> AccountingTable ACCT_ADSL
> AcctColumnDef ACADSL_ID_USUARIO,User-Name
> AcctColumnDef ACADSL_TIPO_ACCOUNTING,Acct-Status-Type
> AcctColumnDef ACADSL_NASIDENTIFIER,NAS-IP-Address
> ...
> AcctColumnDef ACADSL_TERMINATECAUSE,Acct-Terminate-Cause
>
> HandleAcctStatusTypes Start,Stop
> NoDefault
> </AuthBy>
> </Handler>
>
> We would like to not log the accounting messages that have 'NAS-
> Error' in the 'Acct-Terminate-Cause'
> field. Those messages have 'Stop' as accounting status type. The
> way we've thought we could
> implement this is by using a prehandler hook to set the accounting
> type to something different than
> start or stop if the termination cause is 'NAS-Error', but I'm
> pretty sure there is a cleaner way to
> do this. Could you please advise?
>
> The other concerns the way accounting messages flow through the
> configuration file (I'm probably
> missing something here). My understanding is that, when an
> accounting message arrives, it gets
> through the client statement to check that the authenticator is
> correct and then to the handler. The
> thing is that I don't really understand why the accounting
> statements is placed inside the AuthBy
> section since this accounting message doesn't have any user-
> password attribute.
>
> Thanks in advance for your help.
>
> Regards,
> Emilio
>
> --
> Emilio Mira
> e-mail: emial at alumni.uv.es
> ------------------------------------------------------
> "Sure UNIX is user friendly; it's just picky about who
> its friends are."
> ------------------------------------------------------
>
> --
> 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.
NB:
Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/
radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.
--
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