Many thanks for that telling! I didn't know for sure but started suspect that an SIGHUP doesn't work. Are u telling me that Freeradius (1.1.7) takes cares of the different formats of the key? Thx. On 25 sep 2007, at 01.47, freeradius-users- request@lists.freeradius.org wrote:
Dana 24/9/2007, "Piero Giobbi" <piero@news.fb.se> pi¹e:
Hi all.
I have got freeradius to rock with some equipment here just to get stuck again. I couldn't get radius to auth with some of our APs (Old Apple ones, yes i know sux but i have like 7 of them online now so..) and in the debug i saw that the keys where different from the ones that work. One type of AP wants XX:XX:XX:XX, other xxxxxxx.. third xxxx-xxxx. I really dont want to put all my users (150) in three times and im sure freeradius has a fix for it but i can't really figure it out or less find it (don't really know what to search for on the webb). So, i would like to put xxxxxxxx and get XX:XX:XX:XX and xxxx-xxxx out of it aswell when asked, possible yes? Im only using textfile users for credentials.
Anyone that points me to the right direction and throws in an example would make my day or night.
: )
thx.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html
First question; are you HUPing the daemon? If so, don't - it won't work well.
Second question; if this happens reliably can you recompile from scratch:
./configure --enable-developer make make install
...and when it happens do this:
gdb /usr/local/sbin/radiusd set pagination off set logging file /root/radiusd-wireless.txt set logging on attach $PID thread apply all bt full
...that'll give some details as to what the server is doing when it pegs the CPU. Other options are strace or (if your Linux system has it) SystemTap. The aim being to determine what it's doing when it goes wrong.