configure.texi

gnu 的radius服务器很好用的

@kwindex acct
@kwindex common
@kwindex input-format
@kwindex wait-reply

The @code{filters} statement configures user-defined external filters.
@xref{Filters}, for the detailed discussion of external filters.

@subheading Syntax

@smallexample
filters @{
        filter @var{ident} @{
                exec-path @var{path} ;
                error-log @var{filename} ;
                common @var{bool} [@var{max-wait}];
                auth @{
                        input-format @var{fmt} ;
                        wait-reply @var{bool} ;
                @};
                acct @{
                        input-format @var{fmt} ;
                        wait-reply @var{bool} ;
                @};
        @};
        @dots{}
@};
@end smallexample                        

@noindent
Each @code{filter} directive defines a new filter. The @var{ident}
argument declares the name of the filter. This string must be
used in @attr{Exec-Program-Wait} or @attr{Acct-Ext-Program} attributes
to trigger invocation of this filter (@pxref{Exec-Program-Wait}).

@subheading Usage

@table @asis
@item exec-path @var{path}
Absolute path to the filter program.

@item error-log @var{filename}
Redirect error output from the filter program to @var{filename}. If the
@var{filename} does not start with a slash, it is taken relative to
the current logging directory (@pxref{option,log-dir}).

@item auth
@itemx acct

These compound statements define authentication and accounting
parts of this filter. Any one of them may be missing. The two
statements allowed within @code{auth} and @code{acct} blocks are:

@table @asis
@item input-format @var{fmt}
Format of the input line for this filter. Usually this string
uses %C@{@} notations (@pxref{Macro Substitution}).

You can also use the return value from a @code{rewrite} function as
input line to the filter. To do so, declare:

@smallexample
        input-format "=my_func()";
@end smallexample

@noindent
where @var{my_func} is the name of the rewrite function to invoke. The
function must return string value.

@item wait-reply @var{bool}
If the filter prints a single line of output for each input line, set
this to @code{yes}. Otherwise, if the filter produces no output, use
@code{wait-reply no}.
@end table

@end table

@comment **L3***************************************************************
@node mlc
@subsection @code{mlc} statement
@kwindex mlc
@kwindex sql
@kwindex system

@subheading Syntax

@smallexample
mlc @{
        method (system|sql);  
        checkrad-assume-logged @var{bool};
@};
@end smallexample

@subheading Usage

@code{Mlc} statement configures multiple login checking subsystem
(@pxref{Multiple Login Checking}).

@table @asis
@item method
Sets the method of retrieving information about the currently open
sessions. Currently two methods are implemented. Setting @code{method}
to @code{system} will use system accounting database (@pxref{System
Accounting}). This is the default method. Setting it to @code{sql}
will use @sc{sql} database.

@item checkrad-assume-logged
@command{radiusd} consults the value of this variable when the @NAS{}
does not responds to checkrad queries (@pxref{Multiple Login Checking}).
If this variable is set to @code{yes}, the daemon will proceed as if
the @NAS{} returned ``yes'', i.e. it will assume the user is logged in.
Otherwise @command{radiusd} assumes the user @emph{is not} logged in.

@end table

@comment *L2****************************************************************
@node dictionary file
@section Dictionary of Attributes --- @file{raddb/dictionary}
@cindex Radius dictionary
@cindex @file{dictionary} file

The dictionary file @file{raddb/dictionary} defines the symbolic names
for radius attributes and their values (@pxref{Attributes}). The file consists
of a series of statements, each statement occupies one line.

In the detailed discussion below we use the following meta-syntactic
characters:

@table @var
@item number
Denotes a decimal, octal or hexagesimal number. Usual C conventions are
honored, i.e. if @var{number} starts with @samp{0x} or @samp{0X} it is
read as a hex number, if it starts with @samp{0} it is read as an
octal number, otherwise it is read as a decimal one.
@item type
Denotes an attribute type. These are valid attribute types:

@table @code
@item string
A string type. 
@item integer
An integer type.
@item ipaddr
@IP{} in a dotted-quad form.
@item date
A date in the format: "MON DD CCYY", where MON is the usual three-character
abbreviation, DD is day of month (1-31), CCYY is the year, including the
century.
@end table
@end table

@menu
* Comment::             Introducing a comment line.
* $INCLUDE::            Include a file.
* VENDOR::              Define a vendor-id.
* ATTRIBUTE::           Define an attribute translation.
* BEGIN::               Blocks of vendor-specific attributes
* ALIAS::               Define alternative name for an attribute.
* PROPERTY::            Define attribute properties.
* VALUE::               Define a value translation.
@end menu

@comment **L3***************************************************************
@node Comment
@subsection Comments
Comments are introduced by a pound sign (@samp{#}). Everything starting from
the first occurrence of @samp{#} up to the end of line is ignored.

@comment **L3***************************************************************
@node $INCLUDE
@subsection $INCLUDE Statement
@kwindex $INCLUDE (dictionary)

@subheading Syntax
@smallexample
$INCLUDE @file{filename}
@end smallexample

@subheading Usage
The @code{$INCLUDE} statement causes the contents of the file @file{filename}
to be read in and processed. The file is looked up in the Radius database
directory, unless its name starts with a slash. 

@comment **L3***************************************************************
@node VENDOR
@subsection VENDOR Statement
@kwindex VENDOR

@subheading Syntax
@smallexample
VENDOR  @var{vendor-name} @var{vendor-id}
@end smallexample 

@subheading Usage
A @code{VENDOR} statement defines the symbolic name @var{vendor-name}
for vendor identifier @var{vendor-id}.
This name can subsequently be used in @code{ATTRIBUTE} statements
to define Vendor-Specific attribute translations. @xref{Vendor-Specific}.

@subheading Example
@smallexample
VENDOR  Livingston  307
@end smallexample

@comment **L3***************************************************************
@node ATTRIBUTE
@subsection ATTRIBUTE statement
@kwindex ATTRIBUTE 
@subheading Syntax
@smallexample
ATTRIBUTE  @var{name}  @var{number}  @var{type} [@var{vendor}] [@var{flags}]
@end smallexample

@subheading Usage
The @code{ATTRIBUTE} statement defines the internal representation of
an attribute: its symbolic name, data type and syntactical usage.
Its parts have the following meaning:

@table @var
@item name
The attribute name.
@item number
The attribute @acronym{ID} (number).
@item type
The attribute type. 
@item vendor
Vendor name for vendor-specific attributes. For usual attributes this
field is empty or contains a dash (@samp{-}). The latter usage is
for compatibility with previos version of GNU Radius
@item flags
Flags, defining attribute properties (@pxref{Attributes}).
@end table

The @dfn{attribute property flags} consist of a sequence of letters,
whose meaning is determined by the following rules:
@footnote{The @var{flags} are optional for compatibility with previous
versions of GNU Radius. If they are omitted, the default is @samp{[LRLRLR]+}}

@enumerate 1
@item
The attribute usage is described by three pairs of symbols, enclosed
in square brackets. Each pair describes how the attribute can be
used in each of three configuration files. The first pair corresponds
to @file{raddb/users}, the second one corresponds to @file{raddb/hints},
and the third one corresponds to @file{raddb/huntgroups}. Within each
pair, the letter @samp{L} in first position means that the attribute
is allowed in @LHS{} of a rule. The letter @samp{R} in second position
means that the attribute is allowed in @RHS{} of a rule. The absence of
any of these letters is indicated by dash (@samp{-}). Thus, the
following usage specification:

@smallexample
        [L--RLR]
@end smallexample
@noindent

means that the attribute may be used in @LHS{} of a rule in @file{raddb/users},
in @RHS{} of a rule in @file{raddb/hints}, and in both sides of a rule
in @file{raddb/huntgroups}.
@item
The attribute additivity is described by one of the following letters:
@table @asis
@item =
Additivity = Replace
@item +
Additivity = Append
@item N
Additivity = None
@end table
@item
The presence of letter @samp{P} in property flags raises the propagation
bit.
@item
Letter @samp{l} (lower-case ell) enables logging the given attribute
in detail file (@pxref{Detailed Request Accounting}). This is meaningful
only for internal attributes, i.e. the ones whose decimal value is
greater than 255 (@pxref{Radius Internal Attributes}). By default such
attributes do not appear in detailed logs. The flag @samp{l} reverts
this behavior.
@item 
Letter @samp{E} marks attributes encrypted as described in RFC 2138.
Currently these are User-Password and CHAP-Password. 
@item 
Letter @samp{T} marks attribute encrypted according to RFC 2868.
@item
The characters from @samp{1} to @samp{9} denote nine user-defined flags
(@pxref{Extended Comparison}).
@end enumerate

@subheading Example

@smallexample
ATTRIBUTE  Service-Type  6 integer - [LR-RLR]=P 
@end smallexample

This statement declares that the attribute number 6 will be referred
to by the symbolic name @samp{Service-Type}. The attribute is of
integer data type and it may be used  in any part of matching rules,
except in @LHS{} of a @file{raddb/hints} rule. The
additivity of @attr{Service-Type} is set to @samp{Replace}. The
attribute will be propagated through the proxy chain.

@comment **L3***************************************************************
@node BEGIN
@subsection Blocks of Vendor-Specific Attributes
@kwindex BEGIN
@kwindex END
@kwindex BEGIN-VENDOR
@kwindex END-VENDOR

@subheading Syntax
@smallexample
@group
BEGIN VENDOR @var{vendor-name} [@var{vendor-id}]
@dots{}
END 
@end group
@end smallexample

@subheading Usage
The @code{BEGIN} keyword marks start of the block of definitions of
vendor-specific attributes. The block is terminated by @code{END}
keyword, optionally followed by an arbitrary number of words,
which are regarded as a comment. The block may contain any valid
dictionary declarations, except other blocks: nesting of declaration
blocks is not allowed.

If @var{vendor-id} is absent, the value of vendor ID is looked
up in the internal table of vendors; therefore, it must be
defined before @code{BEGIN} statement (@pxref{VENDOR}).

@code{BEGIN---END} block alters the handling of @code{ATTRIBUTE}
statements within it. If @code{ATTRIBUTE} statement does not
contain an explicit vendor-id specification, the value of 
@var{vendor-id} is used instead.

For compatibility with FreeRadius an alternative syntax is also
supported:

@smallexample
@group
BEGIN-VENDOR @var{vendor-name}
@dots{}
END-VENDOR @var{vendor-name}
@end group
@end smallexample

@noindent
Such compatibility blocks must appear only ater the declaration of
@var{vendor-name} (@pxref{VENDOR}).

@subheading Example

The following is the usual way of definig vendor-specific attributes:

@smallexample
@group
VENDOR          Livingston      307

ATTRIBUTE       LE-Terminate-Detail     2       string  Livingston
ATTRIBUTE       LE-Advice-of-Charge     3       string  Livingston
@end group
@end smallexample

@noindent
The following two examples show the alternative ways:
 
@smallexample
@group
VENDOR Livingston 307
BEGIN VENDOR Livingston
ATTRIBUTE       LE-Terminate-Detail     2       string  
ATTRIBUTE       LE-Advice-of-Charge     3       string
END
@end group
@end smallexample

@smallexample
@group
BEGIN VENDOR Livingston 307
ATTRIBUTE       LE-Terminate-Detail     2       string  
ATTRIBUTE       LE-Advice-of-Charge     3       string
END
@end group
@end smallexample

@noindent
These three examples are completely equivalent to each other.

@comment **L3***************************************************************
@node ALIAS
@subsection ALIAS statement
@kwindex ALIAS
@subheading Syntax
@smallexample
ALIAS @var{name}  @var{alt-name}
@end smallexample

@subheading Usage
The @code{ALIAS} statement defines an altenative name @var{alt-name}
for attribute @var{name}. The latter should already be defined,
otherwise an error occurs.