VENDORS(5)VENDORS(5)NAMEvendors - RADIUS vendor to vendor code mapping file
SYNOPSIS
../raddb/vendors
DESCRIPTION
The vendors file resides in the RADIUS configuration
directory (named .../raddb somewhere). It contains a list
of zero or more vendor entries. Each vendor entry con-
tains a vendor name and vendor number. The vendor numbers
are SMI Network Management Private Enterprise Code numbers
as described in the RADIUS DRAFT RFC and RFC 1700. Each
entry optionally contains an interim way of mapping exter-
nal (with respect to the RADIUS server) attribute numbers
to internal (with respect to the RADIUS server) vendor
specific attribute. This optional mapping is used both on
inbound and outbound, with respect to the server, RADIUS
requests. Comments are indicated by leading pound sign
('#') characters. All such comment lines are ignored (as
are blank lines).
The file contains a line of information for each vendor.
Each line has the following form:
[ <attribute-string> <value-string> ] <vendor-code>
<vendor-name>
[ ( [ <standard-value> <vendor-specific-
value> ... ] ) ]
For example:
61 Merit ( 211 211 213 213 )
The <attribute-string> and <value-string> are optional
strings which default to "Attribute" and "Value" when not
specified. Non-default strings may be used to specify
vendor specific attributes and values in the dictionary
file.
The <vendor-code> field is from the Assigned Numbers
(IANA) RFC 1700.
The <vendor-name> field is the vendor name. The vendor
name may appear in the clients file as a type=vendor:nas
entry or in vendor specific attribute names in the dictio-
nary and users files.
The <standard-value> field is the "external" or "common"
attribute number as seen in RADIUS requests on the net-
work.
The <vendor-specific-value> field is the "internal"
29 July 1996 1
VENDORS(5)VENDORS(5)
attribute number.
These last two optional fields may be repeated an optional
number of times within the optional parenthesis. These
numbers are used to map attributes from the common
attribute space defined in the DRAFT RADIUS RFC to inter-
nal non-conflicting vendor specific attributes. Some ven-
dors currently assign vendor specific attributes in the
standard attribute address space. As you can see, this is
somewhat of a kludge in order to get around this problem.
The vendors file is read by radiusd upon startup, or when
a HUP signal is received by a running RADIUS server. The
RADIUS server detects any out-of-date configuration files
upon receipt of a Status-Server (or Management-Poll)
request and re-reads all the configuration files. This
file is maintained by the RADIUS administrator using a
text editor.
FILES
../raddb/clients
../raddb/users
SEE ALSOclients(5), dictionary(5). users(5)
29 July 1996 2
