relay in background?
peter.pdudas at gmail.com
Thu Jan 5 01:38:59 CET 2017
I think it is somehow related with Duo Auth Proxy.
Whenever it is involved (before/after/post auth) with mschap the devices
are not connected.
I have a feeling, that the Freeradius and Duo Auth Proxy shares resources
somehow (Duo written in python) and this cause the strange behaviour.
Tomorrow I'll move the Duo to an independent linux server and this will
clears the situation.
This is the easiest test to avoid further issues with scripting.
On 5 January 2017 at 00:52, Alan DeKok <aland at deployingradius.com> wrote:
> On Jan 4, 2017, at 6:37 PM, Alan Batie <alan at peak.org> wrote:
> > A while back, I setup a couple of radacct relays for archiving using the
> > new mechanism, however occasionally the archive server is slow (the
> > reason we moved the archival process to another server to start with),
> > and it's impacting the primary because it doesn't respond until the
> > proxying is done. With radrelay, this is done independently and it
> > doesn't matter if it gets a little behind. Is there a way to make the
> > builtin mechanism behave in the same way? If not, I'm going to
> > resurrect radrelay...
> There's a sample config file:
> Alan DeKok.
> List info/subscribe/unsubscribe? See http://www.freeradius.org/
More information about the Freeradius-Users