How I can properly send error reasons for EAP requests Access-Reject?

[work vlpl]

On Wed, 3 Aug 2022 at 17:31, Matthew Newton <mcn at freeradius.org> wrote:
>


> So Reply-Message will never get to the user.
>

My requirement to provide an error reason does not care about users. I
need to access the error reason on the Access Point side.


> So there's no point worrying what any of the RFCs say. If the
> supplicants being used don't do it, then you can't do it.

Does this mean I can try to use 2 EAP-Message attributes or even
Reply-Message, and if this will work I can stick with that?