Hello Okan -
Depending on your existing configuration, you can either use Handlers for each
Client and configure a different PoolHint for each Handler, or you can use a
new feature that we have added in a patch to Radiator 2.16.1 that allows you to
use special formatting of the form:
%{Client:param}
So you could do something like this:
# define Clients with Identifiers to indicate IP address pool to use
<Client x.x.x.x>
Identifier pool1
....
</Client>
# configure AuthBy DYNADDRESS to use the Client Identifier for PoolHint
<AuthBy DYNADDRESS>
Identifier Allocate_IP_Address
PoolHint %{Client:Identifier}
.....
</AuthBy>
I will send you a copy of the new Util.pm module in a seperate mail.
regards
Hugh
On Mon, 07 Aug 2000, OKAN ARISU wrote:
> i am using Radiator-2.14.1 and IP pool definition inside the <Client...> part.
We are giving IP address to a requester (Dial-up) by looking their client NAS
IP addess.
> Now i want to upgrade Radiator-2.16.1 to solve our subnet problem. Is there
way to give IP address to a client by looking where the request coming from(NAS
IP address). >
> Thanks a lot.
>
> Okan ARISU
> Basari Telekom
> Network Specialist
>
>
> >>> Hugh Irvine <[EMAIL PROTECTED]> 08/03 1:51 >>>
>
> Hello Okan -
>
> On Thu, 03 Aug 2000, OKAN ARISU wrote:
> > Thank alot Hugh. I look at that sections.
> >
> > I have a question in mymind;
> > if i define two or more <AddressPool poo1>, <AddressPool poo2>..
> in our <AddressAllocator> section, what is the command i should write in our
> <AuthBy DYNADDRESS> to use pool1 or pool2 for one of my <AuthBy FILE> or
> <AuthBy SQL> in our <AuthBy GROUP> sections.
> >
> > There is a line saying
> > #PoolHint %{Reply:PoolHint}
> >
> > For example, if i want to say use pool 1; is the correct command
> >
> > PoolHint %1
> >
>
> There is an example in the file "goodies/addressallocator.cfg" in the
> distribution. However, what happens is this: you will set up your AuthBy
> DYNADDRESS clause(s) as the last step in whatever authentication processing you
> are doing. In a previous AuthBy to the AuthBy DYNADDRESS you would do something
> like this:
>
> <AuthBy ....>
> ......
> AddToReply PoolHint = class1
> </AuthBy>
>
> <AuthBy DYNADDRESS>
> .....
> </AuthBy>
>
> In other words, you add an attribute called PoolHint to the reply packet, the
> value of which is used to identify which address pool to allocate the address
> from. As shown in the example file, don't forget to remove the PoolHint
> attribute before actually sending the reply packet.
>
> hth
>
> Hugh
>
> --
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
> Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
>
>
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
