Radius copy accounting

[Fajar A. Nugraha]

Please do NOT send, forward, or reply an entire digest mail. It's
rude, useless, and will only make others unwilling to help you.

On Wed, Aug 8, 2012 at 3:19 PM, BELLIERE Eric
<Eric.BELLIERE at mail.mobistar.be> wrote:
> Thanks but with sql I can send the attribute to Oracle DB without any
> problem?

If you included excerpts of messages from the ORIGINAL thread (instead
of the digest), it would help others understand what you're talking
about.

Anyway, you should spend some time to understand how radius works.

In short, do you have the list of attributes in the original
accounting request? I'm not talking about the detail file, but rather
the accounting packet that FR receives. If you PROXY that packet to
another radius, then by default you'd get (roughly) what's in the
original packet. Which doesn't include REALM attribute.

You COULD add an attribute (e.g. using unlang, see
http://freeradius.org/radiusd/man/unlang.html), probably in pre-proxy
section. However if you want to do that, you need to use another
attribute (i.e. NOT realm, since it's FR's internal attribute), and
the destination radius server also needs to understand that attribute.
It's easy enough if the destination server is also FR (in which case
you can just create a custom attribute in both servers, or hijack one
of the ununsed vendor-spesific attributes), but it might not be so
easy with other radius servers.

Logging to an oracle db does not involve proxying the accounting
packet, so you can pretty much use whatever attributes or variables
that FR recognizes, including internal attributes.

-- 
Fajar