[RADIATOR] Radius Feed to third party Billing Vendor

[Heikki Vatiainen]

On 01/24/2012 04:20 PM, Traiano Welcome wrote:

> I have a number of radiator servers (radiator 4.9) handling auth+acct and
> storing radius accounting data in local postgresql databases. At the same
> time I need to "feed" all the radius accounting data I'm receiving to a
> third party's data processing server using RADIUS protocol, so that it can
> be analysed independently from our own billing operations.
> 
> As a feed mechanism, I'm thinking of somehow proxying all accounting
> requests (in addition to handling them locally) but I can see a number of
> problems with that. My question is:
> 
> Is there a means of getting radiator to feed (using radius protocol) a
> copy of accounting requests to another radius system, while performing
> all necessary auth and accounting operations localy as normal ?

You can use AuthBy RADIUS for this. A couple of notes:
- Use NoForwardAuthentication or IgnoreAuthentication if you handle both
authentication and accounting with the same Handler. This will keep
authentication requests from getting proxied. See the manual for the
differences of the two options
- Note that when AuthBy RADIUS forwards the accounting request it will
return IGNORE. Depending on what other AuthBys you have and how your
AuthByPolicy has been set (defaults to ContinueWhileIgnore), you may
need to do accounting forwarding with the last AuthBy

Thanks!
Heikki

-- 
Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.