User's Guide
What It Is
What's New
Key Features List
ClearBox Enterprise vs ClearBox
System Requirements
Purchasing Licenses
Getting Started
Quick Start
Understanding Server Components
Managing User Accounts
Configuring RADIUS Realms
Realm Settings
Realm Rules
Dynamic Realm Rules
Authentication Protocols Compatibility
Logging Authentication Packets
Logging Discarded Requests
Account Log Files
Realm Settings
Configuring SQL Queries
Private RADIUS Attributes
Regular Expressions Syntax
RADIUS Clients
RADIUS Client Settings
Dynamic Clients Settings
SQL Data Sources
SQL Data Source Settings
LDAP Servers
LDAP Server Settings
Remote RADIUS Servers
Remote RADIUS Server Settings
State Servers
State Server Settings
Meta Configuration
Meta Configuration
Meta Configuration Settings
Meta Base Schema
TLS Settings
Creating SSL Certificates
Creating Server Sertificate
Requesting Server Certificate
Creating Client Certificates
Revoking a Certificate or Renewing CRL
Exporting CA Certificate
Issuing a Certificate in Active Directory CA
Remote Configuration
Advanced ISP Billing Integration
DTH Billing Integration
Platypus Billing System Intergration
OnDO SIP Server Integration
How Do I...
Wi-Fi Security
Wireless Authentication
Wi-Fi and RADIUS
Supported EAP Authentication Types
Security Considerations
10 Tips for Wireless Network Security
Administering the Server
Debug Logs
Using Client Tool
List of Server Errors
Maintaining RADIUS Dictionary
Basic Concepts
Wireless Authentication
Authentication Protocols
RADIUS Attributes
Example of RADIUS Packet Transactions
List of Standard RADIUS Attributes
Technical Support
Purchasing Licenses

ClearBox Enterprise Server 2.0 Online Manual
Prev Page Next Page
ClearBox Enterprise Serverâ„¢ 2.0. User's Guide

RADIUS Clients

A RADIUS client is a network device or a software application that contacts ClearBox Server when it needs to authenticate a user or to record network connection accounting information. RADIUS clients are often referred as NAS, Network Access Servers. A client sends authentication or accounting request to ClearBox server. Then the server checks the authenticity of a user and replies with either accept or reject messages.

You may specify the list of authorized clients in several ways:

  • Plain list of clients known to the server. You should then manually create then a node for each client, define its IP address and a secret shared with the server.
  • List of clients stored in a database table. When defined, the server loads this list at startup. All you need it to select a database source where the list of clients is stored, and a SQL query retrieving them.
    This option may be useful when the number of clients is too high, or it's easier to manage them in a database table.
  • Client secrets and addresses queried dynamically by the server at run-time when it receives a request from unknown client. It may be used when clients are added to a database dynamically and are not known at the server startup.

A client may have a default realm. If no realm is chosen by realm selection rules, then this client's default realm is used for packet processing.

See how to configure a client.

How to add a new client:

1. Right-click the 'RADIUS clients' node in the left tree and select 'Add New Client':

2. Type the new client name instead of <new id> text:

3. Configure its settings and click 'Apply changes'.

© 2001-2007 XPerience Technologies.
Converted from CHM to HTML with chm2web Pro 2.7 (unicode)