rlm_sqlippool IPR (was: Automatic report from sources (radiusd) between 13.09.2005 - 14.09.2005 GMT)

Peter Nixon listuser at peternixon.net
Sat Sep 17 19:36:42 CEST 2005

On Saturday 17 September 2005 13:26, Ruslan A Dautkhanov wrote:
> Hello !
> >>> > =====================================================
> >>> > Combined list of identical log entries
> >>> > =====================================================
> >>> > Description:
> >>> > Add new SQL IPPool module to tree. Config files to follow
> >>> > shortly. The module appears to have been worked on my a number of
> >>> > people. Most recent version is thanks to Ruslan A Dautkhanov.
> >>
> >> Thanks for adding this module, I think it can be useful in a number
> >> of cases. However, I didn't see any licence information in the files.
> >>
> >> Perhaps I'm asking for obvious things because I'm not an expert in
> >> legal issues. If this is a module of FreeRADIUS, I think it must be
> >> under GPL, but the only information I found in the sources is this
> >> line:
> >>
> >> Copyright 2002  Globe.Net Communications Limited
> >>
> >> It's unclear for me whether it is a problem with the intellectual
> >> property rights. For example, the OpenLDAP project requires that
> >> a contribution includes a notice from the author.
> >
> > Yep. It is a very usefull module. We are actually in the process of
> > rewriting half of it so that it only needs one copy of itself to
> > server all IP Pools. That should make it scale linearly and mean that
> > FeeRADIUS' config files do not need to be touched to add a new pool.
> > (No reload)
> >
> > Cheers
> >
>  > -- > Peter Nixon About that copyright: First, initially they make it
> public in year 2002-2003, please search archives... I made many changes
> to this module, main of them is that sqlippool _not_ create different
> pool of sql connections for _each_ configured pool of ip-addresses.

Yes. This was a good change. My changes go further. They allow only one 
instance of the module to be configured and it will server ALL IP pools 
configured at the SQL level so new IP Pools can be added and removed from 
SQL on the fly and FreeRADIUS never has to be restarted nor configured for 
them at all. This is also more efficient as there dont need to multiple 
copies (potentially thousands in my case) of the module running which all 
return NOOP except for one. On the other hand each request to the module 
will always result in an SQL query but that is usually a decent tradeoff 
as if you are using IP Pools then you are probably using them for most if 
not all of your users..


Peter Nixon
PGP Key: http://www.peternixon.net/public.asc

More information about the Freeradius-Devel mailing list