"retry_count" and "retry_delay" configuration in "proxy.conf"

Arka Sharma arka.sharma1988 at gmail.com
Mon Sep 24 06:44:42 CEST 2012

On Sat, Sep 22, 2012 at 5:37 PM, Alan DeKok <aland at deployingradius.com>wrote:

> Arka Sharma wrote:
> >       I am using freeradius-2.1.11 and I have a requirement like I am a
> > proxy free radius server which communicate to a remote PPS with PPAC and
> > PPAQ. Now my question is that how can I identify that it responded back
> > successfully or not.I mean I have a condition like if it doesn't respond
> > back then I have to perform some task in the code.
>   Read raddb/sites-available/default.  Look for post-proxy-type Fail.
> > Now I have written the
> > comments for "zombie_period","response_
> > window" etc in "proxy.conf" file.My observation for radius debug log is
> > that it sends 3 proxy request within 5 min interval before marking the
> > remote server as dead.
>   No.  It *proxies* packets.  FreeRADIUS doesn't originate packets.
> Only the client does.
> > Actually I have configured an unreachable ip in
> > proxy.conf.Now I was doing hit and trial by changing the parameter
> > values but no such changes I found in radius debug log.I have old style
> > realm configuration in proxy.conf that is "accthost = <ip> authhost =
> > <ip>" in realm element.I tried with different values of retry_count and
> > retry_delay both in "proxy server " element and "realm" element.
>   Those configuration options don't do anything.
>>          Then is there any way that I can ensure through code not from
the debug log that my freeradius server proxied the request to remote PPS
and remote PPS successfully responded back

>   Because the server is just proxying packets from the client.
>   Read the debug log.  The server receives a packet from the client, and
> then proxies it.  It never "wakes up" and originates a packet.

Yes.server doesn't generates it.I meant to say that it is duplicating the
proxy request in 5 secs interval twice.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20120924/d67f0cc0/attachment.html>

More information about the Freeradius-Users mailing list