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
Thanks alot..
Okan ARISU
Basari Telekom
Network Specialist
>>> Hugh Irvine <[EMAIL PROTECTED]> 08/02 10:58 >>>
Hello Okan -
On Wed, 02 Aug 2000, you wrote:
> Hello Everybody,
>
> We are using Radiator-2.14.1. We have IP pool definition in our client
definitions. if NAS port ID is less then 255 than IP pool definition works
correct, but other case (NAS port ID is greater than 20000 which is the port
IDs of goverment's RAS server ) it gets dummy IP address like 6.0.0.0.
I would strongly suggest you upgrade to Radiator 2.16.1 so that you can make
use of the new AddressAllocator SQL and AuthBy DYNADDRESS clauses. These will
give you vastly superior IP address management capabilities.
Have a look at sections 6.38 and 6.39 in the 2.16.1 reference manual.
regards
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.
