1) cd to the ascendd directory.  Modify Makefile for the type of host and
   required options.  make.

	If SafeWord is selected you MUST obtain the the SafeWord header
	files and library from Enigma Logic.  SafeWord is a separately
	licensed product.

	If ACE is selected you MUST obtain the ACE header files and library
	from Security Dynamics.  ACE is a separately licensed product.
	Note: Due to limitations in the ACE library, versions of radius
	supporting ACE MUST run in single process mode if you wish Next
	Code processing to be functional (normal ACE authentication works
	correctly in multi-process mode).  That is, use the -s
	flag when starting radiusd.

	If DPI is selected you MUST obtain the Defender agent header files
	and library from Digital Pathways.  Defender is a separately licensed
	product.  Note: versions of radius supporting DPI MUST run in
	single process mode.  That is, use the -s flag when starting radiusd.

2) Create the directory /etc/raddb.  Place in this directory your
   - dictionary file. It should be owned by root and be mode 400.
   - clients file.  It should be owned by root and be mode 400.
   - users file.  It should be owned by root and be mode 400.

   The dictionary file and *example* clients and users files can be
   found in the ./raddb directory.

	If ACE is to be used, the ACE library linked to the RADIUS daemon
	uses the standard ACE "sdconf.rec" file (normally found in /var/ace)
	to determine how to contact the ACE server.

	If DPI is to be used, to configure the server to contact the DSS,
	you will need to create a file "agent.cf" in the raddb directory
	used by the RADIUS daemon.

	The agent.cf information is determined while configuring up the DSS.

	Sample agent.cf:

	agentkey = 0x01, 0x23, 0x45, 0x67, 0x89, 0xab, 0xcd, 0xef
	agentid = foobar
	dss_address = 10.11.12.13

	The five different variables that may defined in the agent.cf file are:
	NAME          TYPE     DESCRIPTION
	agentkey      key      The key used between the agent and DSS
	agentid       string   The agent identifier
	dss_address   string   The hostname or IP address of the DSS
	dss_port      integer  The port number used by the DSS
	dss_timeout   integer  The timeout in seconds to wait for a DSS response

3) Add radius to your /etc/services file.  A sample entry is:

	radius          1645/udp        radiusd
	radacct         1646/udp        radiusd-accounting

   Authentication Port 1645 is *not* required by the Max/Pipeline -- it
   may be any port you choose.

   Accounting Port 1646 is *not* required by the Max/Pipeline -- it may
   be any port you choose.  If no radacct port is defined accounting
   will use the port following the radius port.

   If you wish to use radipad for IP address allocation from global
   pools, add these lines to /etc/services on the hosts where both
   radipad and radiusd run (these can be the same host, or different
   hosts):

radipa		9992/tcp	# RADIUS IP Address Allocation from global pools

   The port number 9992 is the default.  Change it if you desire.


4) Install radiusd, and optionally radipad, in the directory of your
   choice.  Some put it in usr/local/bin, others in the /etc/raddb
   directory.  If you are using global pools, install radipad also.


5) Modify your startup scripts, e.g. /etc/rc.local for SunOS 4.1.x,
   to start radiusd when the system comes up.  Example:

	#
	# Start up radius for remote users
	#
	if [ -f /usr/local/bin/radiusd ]; then
	        /usr/local/bin/radiusd; echo -n ' radiusd'
	fi

   Radipad is started in a similar fashion.  Example:

	#
	# Start up radipad for remote users
	#
	if [ -f /usr/local/bin/radipad ]; then
	        /usr/local/bin/radipad; echo -n ' radipad'
	fi

   Note that whereas you might wish to have multiple hosts run
   radiusd, only one host on the network should run radipad.  Radipad
   is the central manager for global IP address pools on a network and
   is not designed to be replicated.  The IP address of the host
   running radipad must be present in the profile for the
   "radipa-hosts" psuedo-user in the users file.  See the file
   "users.example" for details.

6) Start radiusd (and optionally radipad) by hand the first time.  You
   MUST be root.


Notes:	See the sample users file for comments on how to set up users.

	A DBM version of the daemon can be created for faster access using
	the command "make dbm".  The make requires that libdbm exist
	on your machine.  Along with "radiusd.dbm" the file "builddbm"
	will be created.  This file converts the raddb/users file
	into DBM format that radiusd.dbm can read.  Change your startup
	scripts to invoke radiusd.dbm rather than radiusd.  Don't forget
	to re-convert your users file whenever you change any of its
	entries.

	The diffs directory is no longer maintained in the release.
	If you wish to generate diffs between the Livingston
	Enterprises version and the ascend version, use this command:

		diff -cN radiusd ascendd
