Home server failure messages
aland at deployingradius.com
Thu Nov 21 14:26:54 CET 2019
On Nov 21, 2019, at 7:44 AM, FRANKS, Andy (SHREWSBURY AND TELFORD HOSPITAL NHS TRUST) <andy.franks1 at nhs.net> wrote:
> Indeed it seems to in some circumstances; here's one where one server proxies to another, which in turn can't reach another external one, and the failure message is passed across:
> Server where the request is received (from radtest):
> I've edited it a bit for brevity, hopefully that's ok
> .. but if it can't connect at all the next server in line for example because FR is down and the port is closed it seems to miss out the post-proxy bit (probably by design?) and then there's no available Module-Failure-Message attribute value.
The answer is that the Module-Failure-Message attribute isn't always created.
> Again, maybe my intuition is a bit off and I expect something which for some reason is designed a different way!
Patches are welcome. :)
It's worth going thru src/main/process.c, and adding calls:
module_failure_msg(request, "foo", ...);
In order to add more module failure messages.
More information about the Freeradius-Users