99 |
Request-Authenticator = Unverified |
Request-Authenticator = Unverified |
100 |
@end smallexample |
@end smallexample |
101 |
|
|
102 |
|
Notice that @command{radiusd} always adds two pseudo-attributes to |
103 |
|
detailed listings. Attribute @attr{Timestamp} shows the UNIX timestamp |
104 |
|
when @command{radiusd} has received the request. Attribute |
105 |
|
@attr{Request-Authenticator} shows the result of checking the request |
106 |
|
authenticator. Its possible values are: |
107 |
|
|
108 |
|
@table @asis |
109 |
|
@item Verified |
110 |
|
The authenticator check was successful. |
111 |
|
|
112 |
|
@item Unverified |
113 |
|
The authenticator check failed. This could mean that either the |
114 |
|
request was forged or that the remote @NAS{} and @command{radiusd} |
115 |
|
do not agree on the value of the shared secret. |
116 |
|
|
117 |
|
@item None |
118 |
|
The authenticator check is not applicable for this request type. |
119 |
|
@end table |
120 |
|
|
121 |
|
Notice also that the so-called @dfn{internal attributes} by default are not |
122 |
|
logged in the detail file. Internal attributes are those whose decimal |
123 |
|
value is greater than 255. Such attributes are used internally by |
124 |
|
radius and cannot be transferred via @RADIUS{} protocol. Examples of |
125 |
|
such attributes are @attr{Fall-Through}, @attr{Hint} and |
126 |
|
@attr{Huntgroup-Name}. @xref{Radius Internal Attributes}, for detailed |
127 |
|
listing of all internal attributes. The special attribute flag |
128 |
|
@code{l} (lower-case ell) may be used to force logging of such |
129 |
|
attributes (@pxref{ATTRIBUTE}). |
130 |
|
|
131 |
@comment *L2**************************************************************** |
@comment *L2**************************************************************** |
132 |
@node SQL Accounting |
@node SQL Accounting |
133 |
@section @acronym{sql} Accounting |
@section @acronym{sql} Accounting |