from what I've seen on the lists, sqlippool is full of bugs and holes. If you're planning to put it into a production environment, I'd strongly suggest booking a coder for a couple of days :-) Such is the nature of open-source I guess. There is no other truly feasable way of leasing IPs over multiple servers, other than Rsync'ing the pool files, or manually assigning different RADIUS servers for different pools - the second means that you are basically splitting your system into multiple independent groups - several NASes to one RADIUS server. However, both of these are hacks. I'm using rlm_ippool at the moment on a multi-nas basis, as I have had both two NASes getting IPs assigned to users from a single shared pool, and also one-pool-per-NAS. Both work fine. It's your choice really - you can always just use one-pool-per-NAS and manually assign each NAS to a RADIUS server responsible for maintaining the pool, while you're getting sqlippool up to production standards. Hope this helps, Jan On 07/12/06, Paul Khavkine <paul.khavkine@distributel.ca> wrote:
Hi folks.
I'm looking into ways to implement a "global address pool" for multiple NASes and multiple RADIUS servers.
I see that there's 2 possible ways of doing it with FreeRADIUS.
1) use rlm_ippool 2) use rlm_sqlippool
I'm leaning towards rlm_sqlippool since it can be used to "lease" an address to a subscriber for a period of time so they get same ip address for the duration of the "lease".
Is there any other ways to implement NAS independent address pool and be able to "lease" same address to a subscriber ?
Is anyone using sqlippool in production ?
Thanx Paul
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html