Hello Dave -
On Tue, 07 Mar 2000, Dave Close wrote:
> We run two copies of Radiator on different systems. One is intended as
> our primary authentication server, the other as our only accounting
> server. The accounting server acts as a secondary authentication
> server, though that is not it
Hello Mark -
On Tue, 07 Mar 2000, Mark Jenks wrote:
> Has anyone used Radiator to send back the credit amount and credit time and
> return code in vsa's for the Cisco debit card platform ? We use an As5300
> and are currently authing using radiator 2.15. The Cisco radius debug says
> the pair is
Has anyone used Radiator to send back the credit amount and credit time and
return code in vsa's for the Cisco debit card platform ? We use an As5300
and are currently authing using radiator 2.15. The Cisco radius debug says
the pair is an invalid format for type 26, 26 referring to vendor specof
We run two copies of Radiator on different systems. One is intended as
our primary authentication server, the other as our only accounting
server. The accounting server acts as a secondary authentication
server, though that is not its intended purpose. For our own POPs, this
works quite well.
Hello Stephen -
On Tue, 07 Mar 2000, Stephen Chen wrote:
>
> Has anybody tried to cache user records when it is pulled into a proxy
> Radiator from a main Radiator server?
>
> We need to do this to prevent authentication system failure as result of our
> centralized database server failure. S
Hello Robin -
On Tue, 07 Mar 2000, Robin Vissers wrote:
> Hi all,
>
> short problem description :
> ---
> Accounting information is stored locally and not forwarded to
> the other radius server using Authby GROUP.
>
> Configuration overview
> --
>
Hello Juan -
On Tue, 07 Mar 2000, ARG-MENENDEZ, JUAN wrote:
> I been doing some tests with Radiator Demo Version 2.15 & some
> Ciscos 2511/5300 and everything went allright.
>
> We also have some MAX TNTs here and I noticed the MAX TNT unit is
> sending ´garbage´ to the radius server (I c
Title: user record cache?
Has anybody tried to cache user records when it is pulled into a proxy Radiator from a main Radiator server?
We need to do this to prevent authentication system failure as result of our centralized database server failure. Since this database server is in a remote
I been doing some tests with Radiator Demo Version 2.15 & some
Ciscos 2511/5300 and everything went allright.
We also have some MAX TNTs here and I noticed the MAX TNT unit is
sending ´garbage´ to the radius server (I can only see it if I configure
loglevel to trace 4), although
Hi all,
short problem description :
---
Accounting information is stored locally and not forwarded to
the other radius server using Authby GROUP.
Configuration overview
--
As a temporary solution during migration of user database;
users will first be
10 matches
Mail list logo
