On Mon, Jul 4, 2011 at 3:02 PM, Tom De Vylder <tom@penumbra.be> wrote:
On 01 Jul 2011, at 19:44, Alan DeKok wrote:
pool1.conf: ippool main_pool { range-start = 192.168.10.1 range-stop = 192.168.10.254 [ ... ] } pool2.conf ippool secondary_pool { range-start = 192.168.11.1 range-stop = 192.168.11.254 [ ... ] }
Source: http://wiki.freeradius.org/Rlm_ippool, section custom configuration.
Loading the config files itself is not a problem, however placement of the include statement is.
Uh... no. The $INCLUDE statement includes the files or directory you name, in the place of the $INCLUDE statement.
According to the log file it doesn't look that way. So I assumed it wasn't the case. Hence the question.
I've tried to put the following line in several places:
$INCLUDE /etc/freeradius/ippool.d/
E.g.: - At the end of modules {}, - Below a working ippool main_pool {}, which resides inside modules {} - Inside instantiate {} - authorize {) - ...
Nothing seems to work.
Wonderful. You didn't follow the existing examples or documentation, and you tried a bunch of random things in the hope that they might work.
Being all-knowing as you are you also should've know I actually did rtfm. Couldn't find anything useful and indeed tried a bunch of random things, thankyouverymuch.
Each module configuration goes into the "modules" section. This is documented, and numerous examples are given. There are even examples of configuring multiple instances of a module. There are even examples of *using* multiple instances of a module.
Judging by the look of radiusd.conf and the examples there I wouldn't even guess needing multiple instances of ippool. See example above. Both ip pools are configured in a single instance in a single module{} section.
The config you wrote defines two instances of ipool:
ippool main_pool {
that's the first instance
ippool secondary_pool {
... and that's the second instance. It doesn't really matter (functionality-wise) whether they're on the same or different files, or even directly inside modules section of radiusd.conf.
What I wanted to accomplish was to simply split both ippool $name {} sections into a separate ippool-$name.conf file.
Well, just split it. As long as it's included inside modules section of radiusd.conf, it should work. Try using something like this on radiusd.conf: modules { ... $INCLUDE ${confdir}/modules/ $INCLUDE ${confdir}/ippool.d/ ... } An additonal note, I don't think you can use "ippool main_pool" on pool1.conf, as the instance "main_pool" of ippool module is already defined on modules/ippool.conf. -- Fajar