Hello Chris -
On Tuesday 09 October 2001 12:49, Chris M wrote:
> For a given realm, I need to proxy the RADIUS requests off to a remote
> server not on our network. So <AuthBy RADIUS> will do that.
>
> But what I'd like to do is store the accounting records in a SQL database
> on the local RADIUS server, not just blindly forward them off.
>
> So would nesting AuthBy SQL clauses inside the AuthBy RADIUS clauses
> accomplish this, or would this filter out the accounting records without
> passing them to the remote radius server?
>
The answer depends on what else you are doing, but you could use something
like this (note that you *cannot* nest AuthBy clauses):
# define AuthBy clauses
<AuthBy RADIUS>
Identifier ForwardToProxy
.....
</AuthBy>
<AuthBy SQL>
Identifier SQLAccounting
.....
AuthSelect
AccountingTable .....
AcctColumnDef ....
.....
</AuthBy>
# define Realm
<Realm .....>
AuthByPolicy ContinueAlways
AuthBy SQLAccounting
AuthBy ForwardToProxy
.....
</Realm>
The above will copy the accounting into the database and also proxy it.
If you don't want to forward the accounting you would use
AuthByPolicy ContinueUntilAccept
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
