Running ntlm_auth as a connection pool

Alan DeKok aland at deployingradius.com
Thu Aug 31 16:10:00 CEST 2017


On Aug 31, 2017, at 9:56 AM, Arnab Roy <arnabroy at mail.com> wrote:
> 
>   Just a small additional question, so as it stands unless I completely
>   re-do this whole piece , I am highly unlikely to get out of this hole.
>   So as a temporary suggestion I have got plenty of CPU , DISK IO and
>   Memory resources. Fr is barely using anything , any parameters I can
>   change so FR uses the spare hardware resources to process the
>   concurrent mschap requests ?

  Do LDAP lookups in FreeRADIUS.  That will help a bit.

  The real limitation is Samba / Winbind.  If their libraries allowed for ntlm_auth  / rlm_winbind to set the winbind path, it would be simple.  Since that path is hard-coded into their libraries, it's much more difficult.

  For v4, we're working on making it asynchronous.  So you should be able to run many, many, instances of ntlm_auth without having the server wait for each one.

  Alan DeKok.




More information about the Freeradius-Users mailing list