This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 1 and 2
Revision 1 as of 2005-01-16 10:53:47
Size: 2247
Editor: 62
Revision 2 as of 2005-01-16 21:28:17
Size: 18
Editor: GuyHarris
Comment: Just redirect to RADIUS.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Radius is a server for remote user authentication and accounting. Its primary use is for Internet Service Providers, though it may as well be used on any network that needs a centralized authentication and/or accounting service for its workstations.

The package includes an authentication and accounting server and some administrator tools.

* Authentication Schemes
Radius supports a wide variety of authentication schemes. A user supplies his authentication data to the server either directly by answering the terminal server's login/password prompts, or using PAP or CHAP protocols. The server obtains the user's personal data from one of the following places:

* System Database
The user's login and password are stored in /etc/passwd on the server, i.e. they are a "normal" UNIX user on the system.
Internal Database
The user's login ID, password etc. are stored in the internal radius database. The user's password is stored in encrypted form using either MD5 or DES hash, whichever is appropriate. Alternatively, a plaintext password can also be used if CHAP protocol is being used, CHAP usage is strongly discouraged for security reasons.
SQL authentication
User's details are stored in an SQL database. The database structure is fully determined by the system administrator, Radius does not restrict it in any way. See Interaction with SQL Servers.
PAM authentication
User is authenticated via PAM (Pluggable Authentication Service) framework. See the Linux PAM homepage for more details.
Accounting Schemes
Radius has three built-in accounting schemes:

* Unix accounting
Accounting data are stored in radutmp/radwtmp files and can be viewed using radwho and radlast commands. Both commands are upward compatible with their Unix counterparts who and last.
Detailed accounting
The detailed accounting information is stored in plain text format. The resulting files can easily be parsed using standard text processing tools (grep, awk, etc.)

* SQL accounting
Upon receiving accounting information Radius stores it in an SQL database. This can then be processed using standard SQL queries.
Radius is extensible and new accounting methods can be added using the extension language.

see also:

Radius (last edited 2009-04-29 23:56:07 by KonradRoeder)