Title: Re: (RADIATOR) CalledStation.pm

Hello Tom -

You can do this very easily with multiple AuthBy clauses, as has been discussed many times on this mailing list.

# define AuthBy SQL for accounting
# note empty AuthSelect to disable authentication

<AuthBy SQL>
        Identifier SQLAccounting
        DBSource ....
        DBUsername ....
        DBAuth ....
        AuthSelect
        AccountingTable ACCOUNTING
        AcctColumnDef .....
        ......
</AuthBy>

# define CalledStationId's

<CalledStationId ......>
        AuthByPolicy ContinueAlways
        AuthBy SQLAccounting
        AuthBy ProxyToWhereever
</CalledStationId>

.....

hth

Hugh


At 16:19 -0400 01/7/9, Tom Daly wrote:
Hi All,
 
When using CalledStation.pm, is there a way to force accounting records to go to two different servers? In my situation, I let my wholesalers run thier own radius servers, which mine proxies to. This means that authorization and accounting packets travel to thier servers. However, for billing purposes, I need to get the accounting packets as well. Does anyone know of a way that I can get them to go to my MS-SQL DB as well at to the proxied radius server?
 
--Tom
 
Tom Daly
Network Operations Administrator
G4 Communications Corp. / Metro2000 Internet Services
E:
[EMAIL PROTECTED] / W3: www.metro2000.net

--
NB: I am travelling this week, so there may be delays in our correspondence.

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.

Reply via email to