Extra column in radpostauth
sudheer at techchorus.net
Tue May 7 18:03:56 CEST 2019
On 30/04/19 12:36 AM, Alan DeKok wrote:
> On Apr 29, 2019, at 8:06 AM, Sudheer S <sudheer at techchorus.net> wrote:
>> It would be nice to have an extra column in the |radpostauth |table to store the reasons for Access-Reject.
>> I came across this article, <https://www.dlineradio.co.uk/articles/logging-failure-reasons-in-freeradius/>. The article suggests adding a column to the radpostauth table.
>> I also remembered, Alan DeKok mentioned in one of the earlier threads that using standard tables for custom things is not preferred. Would you consider the extra column in the radpostauth table an exception to the rule of thumb? Or would you recommend using a custom table for this purpose?
> The server just inserts data into that table and never queries it. As a result, you can add an extra column without any issue.
I was hoping I could use reply|:|Reply-Message to store the reason for
reject and then use the message column in radpostauth table to store
Then I came across a reference to RFC3579 which states that sending
Reply-Message in EAP could cause problems. I am using PEAP. So, is there
another attribute I could use to set the reason for reject and
eventually store it in radpostauth table?
More information about the Freeradius-Users