Accounting response with attributes

[Chandan Kumar]

On 01/14/2015 04:01 PM, Alan DeKok wrote:
> On Jan 14, 2015, at 3:49 PM, Chandan Kumar <chandan.kumar at noviflow.com> wrote:
>> I am looking for a way to have the Accounting/Billing information [such as session time, reason for disconnection, packet transferred etc ] available at the NAS (Linux Client).
>    That statement makes no sense.
>
>    The NAS is supposed to track that information, and send it to the RADIUS server.  There is NO WAY for the RADIUS server to invent that information, and send it to the NAS.
Got it.
>
>> Thanks. I am using pam_radius_auth.so module. I will also explore "freeradius-client”.
>    The pam_radius_auth code should be used for PAM.  It’s fine.
>
>> Basically all accounting information is available on the RADIUS server, I am looking for a way if I could make those accounting information [session time, reason for disconnection, packet transferred etc] available at the NAS (Linux client). Including vendor specific attributes if available.
>    No.  Don’t do this.  It’s a TERRIBLE idea.  And it won’t work with pam_radius_auth.  The pam_radius_auth module is called ONLY when the user logs in.  And when the user logs in… he has no accounting data.
>
>    If you want to reject the user because he’s used too much data, implement that in FreeRADIUS.  The server has all of that information, and you can easily create policies there.
>
>    Doing this in the NAS is *completely wrong*.
Make sense. Thanks for your patience and prompt response, it was really 
helpful. So basically I won't change the pam_radius_auth at all for 
accounting related changes [I will use it only for authentication], 
rather if required will use the radius client for accounting related 
activities to keep the implementation[application] clean. Moreover, will 
write policies, if required, at the FreeRADIUS server side to Accept/Reject.

>
>    Alan DeKok.
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html