Hello,
According to the RFC 2866, it is possible to send back attributes to an
accounting update packet sent from a NAS.
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
Hello Alan,
From the RFC 2866:
4.2. Accounting-Response
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
Padam J Singh wrote:
From the RFC 2866:
Yes, I have read the RFC's. They're even in the FreeRADIUS source
tree. They'are referenced from http://freeradius.org/rfc/, which was
built by me.
The RFC doesn't categorically say that an accounting response packet SHOULD
NOT have attributes.
You don't need Auth-Type Accept (it will let people in even if the
password is wrong). Processing of the users file stops with the first
match without Fall-Trough.
Ivan Kalik
Kalik Informatika ISP
Dana 12/12/2008, Tim Gustafson t...@soe.ucsc.edu piše:
Add: DEFAULT Auth-Type := Reject
Hi Alan,
OK, you pointed me in the right direction. I did run radius in debug
and came up with no errors as shown in a previous message to the list
that was cut from this continuation.
What I didn't realize nor think of, is that I could run radtest against
the debug run. Every reference to
kevin wrote:
What I didn't realize nor think of, is that I could run radtest against
the debug run. Every reference to debug mode simply indicated to run in
debug, check if there were errors, and the ctrl-X and run freeradius
again in standard mode.
The intent of the debug output is to run
Hello,
Are you aware of any radius client library which also implements
CoA/Packet of Disconnect?
I have checked radiusclient-ng and its earlier version - they do not
contain any such feature.
I saw that CoA is on the roadmap for FR (2007 announcement), any work
done on it yet?
Thanks,
Padam
7 matches
Mail list logo
