I already have IgnoreAccountingResponse in my AuthBy RADIUS below, is
that the correct place for it?
Jim.
On 02/05/2013 00:38, Hugh Irvine wrote:
> Hello Jim -
>
> Just add "IgnoreAccountingResponse" to your AuthBy RADIUS clauses.
>
> See section 5.32.30 in the Radiator 4.11 reference manual ("d
Agreed. The ultimate plan is to use a session database. But for now I need to
integrate Radiator into our current platform using the easiest and simplest
approach. I am also exploring options for configuring NavisRadius to use a
session database instead of USS. So whichever I am able to accompli
Hello Jim -
Just add "IgnoreAccountingResponse" to your AuthBy RADIUS clauses.
See section 5.32.30 in the Radiator 4.11 reference manual ("doc/ref.pdf").
regards
Hugh
On 2 May 2013, at 04:49, Jim Tyrrell wrote:
> Hi,
>
> I have a default accounting handler which currently formats a few
>
Hello Rohan -
As far as I can see from the online documentation, NavisRadius uses USS as a
session database.
This being the case, I think you would need to set up Radiator to proxy to
NavisRadius which in turn would use USS.
Note that Radiator also has its own support for one or more session
Hi,
I have a default accounting handler which currently formats a few
attributes via a hook, updates a MySQL database with session info, and
then relays the RADIUS packet onto a couple of Cisco management servers
(so they can maintain a mapping of user to IP).
We have always had a few "Unknown
The plan is to replace NavisRadius but want to integrate Radiator into the
production environment as a test run.
NavisRadius servers are configured to use a USS (NavisRadius Universal State
Server installed on a separate server). I was hoping to get Radiator to use the
USS. Eventually we would
