The radius server port.
Please notice that RFC2138 assigns port 1812 and 1813
for authentication and accounting, respectively. Many
Radius servers still use the former assigned port 1645
and 1646 instead. The default value is 1812 and 1813.
The radius server with the lowest priority is the first
used for request. If there is no response (see also the
values Timeout and Retries) the radius server with the
next lowest priority will be used. Default value is 0.
When operational, the server state is active(1).
If the radius server does not respond, its state is set
to inactive(2). The administrator can set the state
manually to disabled(3), or delete(4) the entry.
If set to authoritative(1), a negative answer to a
request will be accepted. This is not necessarily
true when set to non-authoritative(2), where the
next radius server will be asked until there is
finally an authoritative(1) server configured.
This additional option is only used for bogus RADIUS
servers, which send response messages with a wrong
calculated MD5 checksum. All messages generated by
the brick, however, will always use the proper
authentication scheme. For security reasons, this
option should always be set to enabled(1).
This option provides a means for RADIUS dialout
When set to enabled(1), routing information is read
into the brick after system startup. This information
must be configured in the RADIUS server as dialout-1 to
dialout-n, where n is a value of range 1-99. The end is
automatically determined when the brick gets a negative
response. This means, all entrys must be consecutive.
The default value is disabled(2).
This is the default USER-PASSWORD the brick sends
where no password is available (for example, in
requests for the calling number or boot requests).
Some RADIUS servers rely on a configured USER- or
CHAP-PASSWORD for any RADIUS request.
The default value is an empty string.