(RADIATOR) Different Realm Authentication with Radiator RAIUS

[Anuj]

Hi,
We have Radiator RADIUS running here in production for our ISP dialup 
customers.
This RADIUS is primarily being used for following services:
1. Dialup customers from our own NAS (Realm hecl.com and Realm oneconnect).
2. Dialup customers from our ISP partner's NAS. Our Radius and our ISP 
Partner's Radius are configured as a client (Realm hecl.com)

When we receive the request from hecl realm users (either from our NAS or 
from our ISP Partner's Radius) it is getting authenticated and the Realm 
@hecl is being stripped off by the help of RewriteUsername attribute. 
These users are getting authenticated.

When we receive the request from oneconnect realm users (only from our 
NAS), we don't want to strip off Realm as the user database contains Realm 
along with Username attribute, therefore I have commented the 
RewriteUsername attribute in radius.cfg. These users are not getting 
authenticated, because when we see the log file the username is not 
accompanied with the Realm.

I tried to attach the Radius.cfg and Trace 4 Logfile but the message exceeded the 400 character mark, please advise how can I send these files..

The main aim of oneconnect Realm is to send Realm details along with 
Username for authentication and at the same time we don't want hecl Realm 
to accompany the Username.

Kindly help us.
Cordially,
Anuj

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20011107/46f85046/attachment.html>