In article <[EMAIL PROTECTED]>,
Alan DeKok <[EMAIL PROTECTED]> wrote:
>Kostas Kalevras <[EMAIL PROTECTED]> wrote:
>> Here it goes. Try it and tell me how it works.
>> Here is a sample configuration
>>
>> dhcp {
>
> Looks good, but I'd call it 'ippool', and not 'dhcp'. Calling it
>'dhcp' means that many people will expect it to do DHCP, which is
>completely different than IP pools.
A few comments on this:
1. I have to agree, just call it "pool" as most other software does
2. Give each pool a name, allow for multiple instances
3. Make it possible to select a pool in the users file
(Radius-IP-Pool = "name" in reply item which is translated
to IP address ?)
4. Read todo/serverside-ip-pools about lost packets and how to
keep the pool(s) clean using periodic checking and checkrad,
that part *has* to be implemented for this to be reliable
Mike.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
