(RADIATOR) Re: Allocating IPs

[Hugh Irvine]

Hello Tunde -

You should do something like this:

# define Client clauses

<Client 1.1.1.1>
	Identifier LocationA
	.....
</Client>

<Client 2.2.2.2>
	Identifier LocationA
	.....
</Client>

<Client 3.3.3.3>
	Identifier LocationB
	.....
</Client>

<Client 4.4.4.4>
	Identifier LocationB
	.....
</Client>

.......

# define AuthBy clauses

......

# define Handlers

<Handler Client-Identifier = LocationA>
	# do whatever for LocationA
	.....
</Handler>

<Handler Client-Identifier = LocationB>
	# do whatever for LocationB
	.....
</Handler>


regards

Hugh


On Monday, July 29, 2002, at 07:26 PM, Ayotunde Itayemi wrote:

> Hi Hugh,
>  
> Thanks for the replies.
>  
> I would like to know if there is anyway to strip or ignore the pool 
> hint attribute
> for certain clients. The reason:
> We have NASes at two different locations. Most of the time clients 
> would be dialing in
> at a particular location and should get a certain range of IPs, but for 
> the second group
> of NASes, I have decided it would be simpler to just allocate a block 
> of static IPs to the
> NASes as each one has a single E1 connected to it (30 dial-in lines).
>  
> So if for example, client A dials into one of the E1 NASes, I would 
> like the NAS to allocate
> the IP from a pool defined on it, on the other hand if client A 
> dials-in to our "regular" NASes,
> (Windows 2000 server), I would like radiator to allocate the IP.
> The problem is that I am validating requests against the same database 
> which has to contain
> pool hints for each client for the second scenario to work.
>  
> Regards,
> Tunde I.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1691 bytes
Desc: not available
URL: <http://www.open.com.au/pipermail/radiator/attachments/20020730/1983408d/attachment.bin>