We converted our radius servers from merit/ldap to freeradius/mysql. 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
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
Thanks for the reply Alan.
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.
Is there a straight forward way that I can add Status-Server support into
FreeRadius 0.7.1 to see if it will correct the
In article [EMAIL PROTECTED],
Alan DeKok [EMAIL PROTECTED] wrote:
FreeRADIUS doesn't do Status-Server messages. I've never seen a
good reason for them.
Some clients use periodic status-server pinging to see if the
server is up.
That is useful with a server that has both local users and
