(RADIATOR) Storing copies of proxied accounting packets
hugh at open.com.au
Wed Jul 24 18:01:12 CDT 2002
Hello Robert -
I don't recommend mixing Realms and Handlers in the same configuration file,
so Realms should be converted to Handlers, and your configuration would then
look something like this:
# convert Realm foo.bar to Handler
<Handler Realm = foo.bar>
# AuthBy SQL to store local accounting
# *MUST* appear first
# disable authentication
# configure accounting
# AuthBy RADIUS clause to forward requests
# *MUST* appear last
Have a look at section 6.28 in the Radiator 3.1 reference manual.
Also note that this topic (and many others) has been discussed on the mailing
list many times already, so you should also check the archive site:
On Thu, 25 Jul 2002 08:24, Robert G. Fisher wrote:
> I'm using AuthEMERALD within two handlers to deal with
> specific situations. However, before my Handler defs, I
> also have one REALM clause in which I am proxying the
> authentication and accounting data to a remote server.
> What I'd like to be able to do is to continue to relay
> these packets to the remote server, but at least on the
> Accounting packets to also retain a local copy. Is there
> any way I can do this? I should mention I need for these
> to be logged to a database, so utilizing a key word that
> logs to a detail file is not what I'm looking for.
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 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