Sending Accounting Response
Padam J Singh
padam.singh at inventum.cc
Sat Dec 13 09:58:17 CET 2008
>From the RFC 2866:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
| Code | Identifier | Length |
| Response Authenticator |
| Attributes ...
The RFC doesn't categorically say that an accounting response packet SHOULD NOT have attributes.
The NAS is an application I have written - so I will be able to parse attributes in an accounting response.
If the standard postgres module cannot be used to send back attributes in an accounting-response packet,
can I do the same using any other module like JRadius? I have gone through the rlm_jradius source code,
and it looks like it doesn't differentiate between accounting and authorization responses when reading value pairs.
Alan DeKok wrote:
> Padam J Singh wrote:
>> According to the RFC 2866, it is possible to send back attributes to an
>> accounting update packet sent from a NAS.
> *Please* use the correct terminology. It makes it easier for us to
> understand your question.
> If I read what I *think* you mean, then no, RFC 2866 does not allow
> attributes in an Accounting-Response.
>> What I have done is this: The authorization and authentication queries
>> are basically calls to a stored procedure in postgres that returns a set
>> of table type which contains the attribute, operator and value.
>> I can write a stored procedure to return a set of attributes to send
>> back in an accounting start/update/stop, but all the queries given as
>> examples in the default dialup.conf are update queries that do not
>> return any attribute.
>> How do I configure the postgres module to return the attributes to the NAS?
> You don't.
> Please explain why you think this is necessary. Also be aware that
> any attributes you send in an Accounting-Response will be ignored by
> *every* NAS that anyone has ever made.
> Alan DeKok.
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
PGP Id 9EED2E09
More information about the Freeradius-Users