A client is not limited to 256 ongoing requests.
One client can (and will, if need be) use multiple source ports (for each source port, 256 requests can be ongoing), hence sending as many requests
as it needs at a given time.
This is not exact science.
You need to do is evaluate the maximum total requests/s rate your server will have to serve.
Multiply that by your max request time, and you have the max requests FreeRADIUS will be handling at a given time.
BTW, the following comment in radiusd.conf is misleading, it should probably be updated :
# max_requests: The maximum number of requests which the server keeps
# track of. This should be 256 multiplied by the number of clients.
# e.g. With 4 clients, this number should be 1024.
De : freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org [mailto:freeradius-users-bounces+nicolas.chaigneau=capgemini.com@lists.freeradius.org]
De la part de Arnaud .
Envoyé : vendredi 18 juillet 2014 09:36
À : FreeRadius users mailing list
Objet : RE: radiusd.conf max request ?
Hello
So
if I have 274
routers connected to Hotspot
Radius server,
I need to put in max-request:
70144 (256 queries
* number of clients)
Is this correct?
best Regards
> Date: Thu, 17 Jul 2014 16:43:45 -0400
> From: aland@deployingradius.com
> To: freeradius-users@lists.freeradius.org
> Subject: Re: radiusd.conf max request ?
>
> Arnaud . wrote:
> > Hello,
> >
> > How should settle in "radiusd.conf" max_request_time, cleanup_delay and
> > max_requests?
>
> The configuration files document what they're for, and what they do.
>
> > Currently I max_request_time = 30 cleanup_delay = 2 and max_requests =
> > 50432
> >
> > Is it set? If it is misconfigured what can happen?
>
> Don't change max_request_time or cleanup_delay. Set max_requests to
> some large value.
>
> If you get it wrong, error messages will appear in the log. The
> messages will tell you to increase max_request_time.
>
> Alan DeKok.
> -
> List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html