(RADIATOR) Re: UseAddressHInt Problems

['Tunde Ogedengbe]

 I have implemented UseAddressHint option to allow customers connect with
 specific Framed-IP-Address addresses on their machines.  However, the
system
rather than use the specified IPs is allocating from its pool to the
connect.  What can be wrong?  I am using Radiator 2.18

 'Tunde Ogedengbe
 Linkserve Limited
 22 Akin Adesola Street
 Victoria Island
 Lagos - Nigeria
 Tel: +234 1 2623900
 Fax: +234 1 2623906
 URL: http://www.linkserve.net
 ----- Original Message -----
> From: "Hugh Irvine" <hugh at open.com.au>
> To: "Kyle" <khultman at bnsi.net>; <radiator at open.com.au>
> Sent: Saturday, August 11, 2001 1:48 AM
> Subject: Re: (RADIATOR) Handler clause
>
>
> >
> > Hello Kyle -
> >
> > What you show below is not correct. Keep in mind that what is used in
> either
> > Realms or Handlers is the information received in the incoming request
> (for
> > the most part).
> >
> > If you want to send different attributes to different NAS clients, you
> should
> > use the PostAuthHook construct, perhaps in conjunction with a
StartupHook
> > and/or some information in a database.
> >
> > There are some example hooks that implement a scheme like this in the
file
> > called "goodies/hooks.txt" in the Radiator distribution.
> >
> > Alternatively you could do something like this:
> >
> > # define Client clauses with Identifiers
> >
> > <Client .....>
> > Identifier Ascend
> > ......
> > </Client>
> >
> > <Client .....>
> > Identifier Patton
> > ......
> > </Client>
> >
> > # define Handlers
> >
> > <Handler Realm = myRealm, Client-Identifier = Ascend>
> > ......
> > </Handler>
> >
> > <Handler Realm = myRealm, Client-Identifier = Patton>
> > ......
> > </Handler>
> >
> > Note that the above will work for a small number of Realms and NAS's,
but
> for
> > anything more you should consider the hooks.
> >
> > regards
> >
> > Hugh
> >
> >
> > On Saturday 11 August 2001 01:58, Kyle wrote:
> > > Hugh,
> > >   Is is legal in the realms.cfg file to place a <Handler> clause
indside
> > > of a <Realm> clause? Lets say if I wanted to do something like:
> > >
> > > <Realm myReal>
> > >
> > > ....
> > >
> > >   <Handler someNasAttribute>
> > >     // Make some replies
> > >   </Handler>
> > >   <Handler someOtherNasAttribute>
> > >     // Make some other replies
> > >   </Handler>
> > >
> > > ....
> > >
> > > </Realm>
> > >
> > > I remember reading something on this, but cant find it again.
Basicaly,
> > > I want to be able to take a single value, such as idle-timeout, and be
> > > able to pass it to a nas in its correct format. I.E, out Ascend would
> > > take the value as Ascend-Idle-Timeout where as our Patton would take
the
> > > value as just Idle-Timeout.
> >
> > --
> > 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.
> > ===
> > Archive at http://www.open.com.au/archives/radiator/
> > Announcements on radiator-announce at open.com.au
> > To unsubscribe, email 'majordomo at open.com.au' with
> > 'unsubscribe radiator' in the body of the message.
> >
>

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.