As far as we dig into it, none of the following:
freeradius radiusclient radius-cistron radius-livingston
Implement 15 Failed
Following RFCs should not lead us falling over the cliff. Maybe 15 should be traded with something else understood by the radius servers found in the real-world?
Adrian
Begin forwarded message:
From: Juha Heinanen jh@tutpro.com Date: June 16, 2004 8:26:49 PM CEST To: Adrian Georgescu ag@ag-projects.com Cc: iancu@fokus.fraunhofer.de, serusers@lists.iptel.org Subject: 15 is a not a recognized RADIUS Packet
Adrian Georgescu writes:
Do you know by any chance what does it mean?
here are all official radius acct-status-types:
Values for RADIUS Attribute 40, Acct-Status-Type [RFC 2866]:
1 Start [RFC 2866] 2 Stop [RFC 2866] 3 Interim-Update [RFC 2866] 4-6 (unassigned) 7 Accounting-On [RFC 2866] 8 Accounting-Off [RFC 2866] 9 Tunnel-Start [RFC 2867]10 Tunnel-Stop [RFC 2867] 11 Tunnel-Reject [RFC 2867] 12 Tunnel-Link-Start [RFC 2867] 13 Tunnel-Link-Stop [RFC 2867] 14 Tunnel-Link-Reject [RFC 2867] 15 Failed [RFC 2866]
you can find definition of 15 from the above mentioned rfc, but if a fails before starting, then 15 is the right way to report it.
-- juha