(RADIATOR) Realms and domain

[Hugh Irvine]

Hello Jack -

You can either do this with Handlers or with cascaded AuthBy clauses.

If you are already using Handlers, you can do this:

<Handler Realm = abc.com, Client-Identifier = ...>
	....
</Handler>

<Handler Realm = abc.com>
	....
</Handler>

If you are using Realms, you would do this:

# define AuthBy clauses

<AuthBy ...>
	Identifier NAS.abc.com
	.....
</AuthBy>

<AuthBy ...>
	Identifier PPP.abc.com
	.....
</AuthBy>

....

<Realm abc.com>
	....
	<AuthBy FILE>
		Filename %D/abc.com
	</AuthBy>
	...
</Realm>

....

Then the file %D/abc.com would contain something like this:

# abc.com

DEFAULT Client-Identifier = ...., Auth-Type = NAS.abc.com

DEFAULT Auth-Type = PPP.abc.com


Hope that helps.

regards

Hugh


On Thursday, Apr 3, 2003, at 02:08 Australia/Melbourne, jsingh wrote:

> Hi Everybody
> I have a little task, i wish to handle the domain "abc.com" with two 
> different realm handlers depending upon their point of entry one 
> coming in as a  PPP request and other from a NAS. Is this possible?
> Thanks
> jack
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1777 bytes
Desc: not available
URL: <http://www.open.com.au/pipermail/radiator/attachments/20030403/2e5f42be/attachment.bin>