Hello Neale -
Having done a few of these, yes all you need is a Client clause.
Note that AuthBy LDAP2 implements LDAP version 1 - it just uses a different
Perl module to do it (perl-ldap), but yes you can use LDAP and log accouting
to a file. As for more sophisticated solutions, have a look at the "goodies"
directory and check the archive site: www.starport.net/~radiator.
There is nothing clever required for AuthBy RADIUS.
regards
Hugh
On Monday 30 April 2001 15:25, Neale Banks wrote:
> Greetings all,
>
> Regarding setting up Radiator for Authentication and Accounting for
> Telstra's DialConnect, is this simply a matter of configuring the
> DialConnect AAA server as a RADIUS client?
>
> Regarding AuthBy LDAP2, an obvious starting point is to use LDAP2 for
> Authentication and log Accounting to a file. Any tricks to adding more
> sophisticated Accounting methods (database, RADIUS-proxy)?
>
> Lastly, in the case of proxying RADIUS accounting, is there anything
> particularly clever required to log to file and proxy to another RADIUS
> server which may or may not be always available (i.e. ignore
> unreachability problems)?
>
> Thanks,
> Neale.
>
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
--
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.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
