home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 35 Internet
/
35-Internet.zip
/
radius_2.txt
< prev
next >
Wrap
Text File
|
1996-06-11
|
3KB
|
93 lines
Archive Name: radius_2.zip
Description: Radius Port for Terminal Server Auth.
Operating System/Version: OS/2 2.x, 3.0
Proposed directory for placement: os2/unix
Replaces: first copy
Uploaded by: "John Landers" jcl@altair.csustan.edu
--------------------------------------------------
Os/2 Port Of Radius
----------------------------------------------
I did this port in hopes of learning Radius.
Also to do some C programming since I have been
recently learning Smalltalk I had a urge to do
some C programming.
Send email if you use it just for reference.
jcl@altair.csustan.edu
This will support all functions in the dictionary
file. I have considered this beta since I have only
tested it with a Computone Intelliserver. The code
is ported from the Livingston Code Base. I am
currently working on porting the Merit Radius code
which it far more complete. Accounting is also supported.
Multiple processes are also supported. If there was a
fork for gnu porting the Merit Code would be easier.
I will release another version once people have given me
feedback with fixes. I have included the code since it is
public domain. The port is not pretty but with out a good
fork command I had to resort to other steps and running in
a single process mode wasn't very timely.
The buildbdm is somewhat functional but I left it out since
the radius code doesn't fully use the database. You are welcome
to extend.
Installation:
----------------------------------
Should use hpfs. If your server name is less than 8 chars
things may be ok.
Create a directory called radius and unzip the
archive there.
Find out where environment variable etc points to
and create a directory call radacct and raddb.
In the raddb directory copy clients.example from the
radius directory and name it clients and edit it. Also
copy users.example and rename it to users and edit it.
Copy the dictionary file there also. If errors happen
check here for a file called logfile.
In the radacct a directory for each server will be created
by radius and a file called detail will be full of accounting
info.
You don't have to use these directories there are command line
options to put output some where else.
Also edit your services file and add the following lines:
radius 1645/udp radiusd
radacct 1646/udp
Support:
--------------------------
I have worked on this on my own time and will try to
respond to any problems as quickly as possible. But
only to Os/2 problems. As for radius info is info on
the net. I would like to know all who use it.
I have included source code just in case someone whats
to diverge from my base.
Email: jcl@altair.csustan.edu
Livingtion Info:
-----------------
* Permission to use, copy, modify, and distribute this software for any
* purpose and without fee is hereby granted, provided that this
* copyright and permission notice appear on all copies and supporting
* documentation, the name of Livingston Enterprises, Inc. not be used
* in advertising or publicity pertaining to distribution of the
* program without specific prior permission, and notice be given
* in supporting documentation that copying and distribution is by
* permission of Livingston Enterprises, Inc.