Hi there
I am using freeradius 1.0.0-pre3 with rlm_ippool managing the ip addresses
for a cisco NAS. I have several address pools with 254 IPs each. When I
started the radius 2 days ago, the rlm_ippool_tool showed me the correct
number of active IP addresses, but today I saw that the output does not
match the number of ip addresses that are active on the cisco. The
rlm_ippool_tool shows only about 120 active addresses and there are about
254 active addresses (the pool is full) on the cisco. Strangely it all
still seems to work, the radius does not assign the addresses that are
active on the cisco, even if they are not listed in the output of the
rlm_ippool_tool.
The pool in radiusd.conf looks like this:
ippool adsl_pool1 {
range-start = 192.168.156.1
range-stop = 192.168.156.254
netmask = 255.255.255.255
cache-size = 800
session-db = ${localstatedir}/radius/db.adsl1.ippool
ip-index = ${localstatedir}/radius/db.adsl1.ipindex
override = no
}
Has anyone an idea what could be wrong? Is rlm_ippool_tool enough stable to
be used in a production environment with about 3000 users?
Regards, Daniel
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
