Proxy response_window issue

[JS SV]

Ok, thank you very much for your explanation.

I only leave here last log

(0) Mon Jun 13 23:27:44 2022: Debug: Received Access-Request Id 139 from
127.0.0.1:47353 to 127.0.0.1:1812 length 236
...
(0) Mon Jun 13 23:27:44 2022: Debug: Sent Access-Request Id 118 from
0.0.0.0:42706 to 10.20.39.211:1812 length 237
(0) Mon Jun 13 23:27:44 2022: Debug: Expecting proxy response no later than
19.673733 seconds from now
...
(0) Mon Jun 13 23:27:49 2022: Debug: Sending duplicate proxied request to
home server 10.20.39.211 port 1812 - ID: 118
(0) Mon Jun 13 23:27:49 2022: Debug: Sent Access-Request Id 118 from
0.0.0.0:42706 to 10.20.39.211:1812 length 237
...
(0) Mon Jun 13 23:27:54 2022: Debug: Sending duplicate proxied request to
home server 10.20.39.211 port 1812 - ID: 118
(0) Mon Jun 13 23:27:54 2022: Debug: Sent Access-Request Id 118 from
0.0.0.0:42706 to 10.20.39.211:1812 length 237
...
(0) Mon Jun 13 23:28:04 2022: Debug: Expecting proxy response no later than
9.992814 seconds from now
(0) Mon Jun 13 23:28:14 2022: Debug: No proxy response, giving up on
request and marking it done
(0) Mon Jun 13 23:28:14 2022: ERROR: Failing proxied request for user
"000a0b0c0d0f", due to lack of any response from home server 10.20.39.211
port 1812


At 23:27:44 I understand that the response_window is started (we are
waiting for a response). then we receive the other two requests that we
mentioned (the client has a timeout in the first one so it sends another
and another)

After that, at 23:28:04 (20s after receiving the first req so that
"theoretically" the response_window has passed) it tells us that it waits
10s more and after those 10s the home_server is set to zombie.

so the total of 30s said.

Thanks Alan!

El lun, 13 jun 2022 a las 22:12, Alan DeKok (<aland at deployingradius.com>)
escribió:

> On Jun 13, 2022, at 3:51 PM, JS SV <jssv51997 at gmail.com> wrote:
> >
> > 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
> > response_window, right?
>
>   Yes.
>
> > 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
> > response_window timers?
> >
> > I do not finish seeing clearly because if I define 20s as response_window
> > it is taking me 30s to mark as zombie
>
>   The timers are drive by packets from the clients.  There is no timer
> started when the first packet is proxied.
>
>   i.e if the client sends packets at 0 seconds, 8, 16, and 24 seconds, the
> server will see at 24 seconds that the home server is not responsive.  The
> server won't fire a timer at 20 seconds exactly.
>
>   Alan DeKok.
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>