NetNITCO Systems Administration <[EMAIL PROTECTED]> wrote: > We converted our radius servers from merit/ldap to freeradius/mysql.
That's a good first step. I have nothing good to say about Merit. > We had setup a test environment and everything worked fine in all of > the tests and under much load. However, after several hours of > perfect operation, all of our freeradius servers now receive the > following from our Access Router Cards: > rad_recv: Status-Server packet from host 216.176.146.2:1645, id=252, > length=20 Ignoring request from client 216.176.146.2:1645 with > unknown code 12 FreeRADIUS doesn't do Status-Server messages. I've never seen a good reason for them. If the 3Com boxes stop authenticating users because FreeRADIUS doesn't support Status-Server, then the 3com boxes are *horribly* broken. I've never heard of this before, so it might be a local config issue. I'm not *opposed* to adding Status-Server support to FreeRADIUS, but I am opposed to adding functionality unless there's a real need for it. > The problem is that now the newly upgraded authentication servers > are unable to authenticate any user from any of our Total Control > chassis and for so me reason, the original Merit/LDAP servers now > receive the following in ther logs: <shrug> If Merit is broken, I cant help you there. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
