that does help. can the first instance be named as well, or must there
always be an unnamed instance?
On 1/17/2011 22:06, Johan Meiring wrote:
On 2011/01/17 10:37 PM, Christ Schlacta wrote:
one more question: can there be multiples of ANY module specified? for
example, can I use two
On 18/01/11 14:45, Christ Schlacta wrote:
that does help. can the first instance be named as well, or must there
Yes
always be an unnamed instance?
I don't think so.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I've found something odd in regard to the modules directory. I ended up
needing to use checkval module for ldap authentication to work properly
for me. the documentation I found said to place the following in config
files:
checkval {
item-name = Calling-Station-Id
check-name
On 01/17/2011 03:37 PM, Christ Schlacta wrote:
one more question: can there be multiples of ANY module specified?
In general modules can be instantiated multiple times under different
names with configuration parameters unique to that name. Not sure if
this is true for *all* modules though,
On 2011/01/17 10:37 PM, Christ Schlacta wrote:
one more question: can there be multiples of ANY module specified? for
example, can I use two different ldap or sql modules if I were to need to
(just as a bad example, I propose: 1 radius server, 2 wlans with different
user bases that can't be
configuration files under the modules directory. As with the sites
directories, this allows me to make less modifications to radiusd.conf.
Also, I can easily split up the per-site module configurations into separate
module files. I do not know if something like
modules-available/modules-enabled
.
I have added
this to our servers and placed all of my custom module sections in
corresponding configuration files under the modules directory. As with
the sites directories, this allows me to make less modifications to
radiusd.conf. Also, I can easily split up the per-site module
7 matches
Mail list logo
