Hi Neale -
On Sat, 07 Aug 1999, Neale Banks wrote:
> On Sat, 7 Aug 1999, Wim Biemolt wrote:
>
> > I experienced some troubles with the suggested configuration. If you use
> > NoForwardAuthentication RADIUS Authentication-Requests are not forwarded
> > but ACCEPTED. I noticed that if the first A
On Sat, 7 Aug 1999, Neale Banks wrote:
> Thanks for that - ACCEPTing everybody is definitely not what we want 8-O
>
> What's the trick to doing this with a ?
I used to make a copy of all accounting by simply running "Trace 4". But
now that I am monitoring radiusd with MRTG my logging really ex
On Sat, 7 Aug 1999, Wim Biemolt wrote:
> I experienced some troubles with the suggested configuration. If you use
> NoForwardAuthentication RADIUS Authentication-Requests are not forwarded
> but ACCEPTED. I noticed that if the first AuthBy failed the user would be
> granted access anyway because
On Sat, 7 Aug 1999, Neale Banks wrote:
> On Sat, 7 Aug 1999, Hugh Irvine wrote:
>
> [...]
> > I would suggest something like this:
> >
> >
> > # Force all clauses to be executed
> > AuthByPolicy ContinueAlways
> > # Do our normal processing
> >
> > ..
> >
On Sat, 7 Aug 1999, Hugh Irvine wrote:
[...]
> I would suggest something like this:
>
>
> # Force all clauses to be executed
> AuthByPolicy ContinueAlways
> # Do our normal processing
>
> ..
>
> # Set up a proxy for Accounting only
>
Hi Neale -
On Sat, 07 Aug 1999, Neale Banks wrote:
> Hi,
>
> Currently we have Radiator logging accounting records to flat file. This
> works and needs to stay that way.
>
> We now need to also relay (proxy?) the accounting records to another
> machine (whilst retaining the logging to file)
Hi,
Currently we have Radiator logging accounting records to flat file. This
works and needs to stay that way.
We now need to also relay (proxy?) the accounting records to another
machine (whilst retaining the logging to file).
Does anyone have a recipe for this?
Our current configuration i