[radsecproxy] Re: dynamic lookups are not blocking, causes first auth to fail with fallback

Hi, On 24.03.21, 08:49, "Fabian Mauchle" <fabian.mauchle(a)switch.ch> wrote: This first request is implicitly placed in the queue for the dynamic server (before the lookupCommand has even been called). I have to corret myself here. Seems I've misunderstood that code block, and Pauls log (thanks!) clearly shows this. Reading it the right way, it looks quite intentional, not a bug. The first request is _not_ placed on the dynamic servers queue. I read that one wrong, it only triggers the dynamic lookup, but the server selection is run again after the new realm structures have been set up. On this second (and any subsequent) passes, the dynamic server is ignored until its connection is established. On 23.03.21, 13:04, "Paul Dekkers" <paul.dekkers(a)surf.nl> wrote: and whether we can have the dynamic lookup blocking for the request? I will add it as a feature request. However, this might have quite some implications: if the lookup and connection setup is slow, this might block a realm for quite some time. That would allow fallback "as documented". Could you point me to that documentation? (I couldn’t spot it in the manpages; just so I can keep any documentation up to date). Best regards, Fabian