Hello Juan Mar�a -
On Thu, 17 Feb 2000, Reina Ortiz, Juan Mar�a wrote:
>
> Hi
>
> We are analysing your Radiator radius server and we have some doubts with
> the IP address assignation mechanism.
> As we understand, the IP address given is the FramedGroupBaseAddress plus
> the NAS port number from the request arrives.
> Our problem is that our NASes have port numbers like 2403, or even higher,
> so Radiator gives one IP address out of the Class C assigned to this client
> (we supossed one class C per client basis).
>
> Is there any way to keep the given IP address in the Class C defined for the
> client?.
> Is it necessary to reserve one Class C per client in order to avoid
> duplicate IP address in two different NASes?
>
At the present time Radiator only does limited IP address allocation in the
manner you describe, although there have been quite a few requests for more
sophisticated IP address management. We do have a project in mind to build into
Radiator support for a back-end DHCP server which will allow very sophisticated
IP address management, but it has not yet reached the top of the list (although
now that Radiator 2.15 has been released, it is much closer).
Two comments on your problem above: first, most of our customers use the NAS's
themselves to do the address allocation out of locally defined pools (ie within
the NAS itself)., second the FramedGroupBaseAddress is a Class C but you could
write a PreHandlerHook to rewrite the NAS-Port attribute modulo whatever you
need to bring them back to 0 base.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
