3 Mar
2011
3 Mar
'11
9:57 a.m.
Chris Hellberg wrote:
I modified rlm_ippool.c to create a hash key against Calling-Station-Id, which is unique across my NAS.
Why? key = %{md5: %{Calling-Station-Id}}
However, I find radiusd goes up to 97% CPU when I use this IP allocation method. If I don't use any server-side IP allocation, I get CPU use hovering around 4%. I can't use an integer like Nas-Id to hash against because it's not a unique value on my NAS, hence I had to modify rlm_ipool.c. So I can't easily check whether the problem is in the rest of rlm_ippool.c or in the change of the hashing method that I've done.
If the problem isn't in the default code, then it's difficult for us to help. Alan DeKok.