Proxy response_window issue
jssv51997 at gmail.com
Mon Jun 13 19:51:28 UTC 2022
I think what you say makes sense to me. but I am not sure about it.
If I send three Access-Requests, each of them will have its
so, when the first packet arrives, the home_server have 20s before the
server is marked zombie?(this is the part that I may not fully
understand). and the two subsequent packages will have their own
I do not finish seeing clearly because if I define 20s as response_window
it is taking me 30s to mark as zombie
El lun, 13 jun 2022 a las 16:43, Alan DeKok (<aland at deployingradius.com>)
> On Jun 13, 2022, at 7:20 AM, JS SV <jssv51997 at gmail.com> wrote:
> > Hi, I'm having a behavior that I don't fully understand when using proxy
> > timers. I am using radclient to do the tests and I find that if radclient
> > sends, for example, 3 retransmissions (timeout) the timers do not add up.
> The timers operate as documented. The usual confusion is that people
> think all of the timers are global. They're not.
> The response_window is per-packet. It requires the client to keep
> resending packets for the timers to run. There is no global timer which
> tracks responses across all packets.
> As a result, if the client sends one packet and stops, the server never
> notices that "response_window" has been hit. The server has to receive
> multiple retransmissions from the client.
> So "response_window" doesn't work as most people think it does. But it
> does work as documented.
> There's no global response_window timer because it's difficult (and
> slow) to keep such a timer across multiple threads.
> Alan DeKok.
> List info/subscribe/unsubscribe? See
More information about the Freeradius-Users