At 02:52 PM 11/28/2002 +0200, you wrote:
The best place for the load balancing docs is /path/to/src/radiusd/raddb/proxy.conf.Angelos Karageorgiou wrote:
Well here is my wish , when the proxy module decides to mark a server as dead , it should mark
the pair (server:port) not the server as an entity . This way if a GRIC server is not reponding in time
another radius server , authenticating local hosts will not be marked dead.
Any ideas on where I could start looking into the code ?
Another idea is to have some servers never marked as dead.
BTW where is the load balancing configuration DOCs?
I ma proxying for a server that is authenticating both for NULL realm and another domain call it users.grYou may want to try increasing your retry_count to prevent the server from being marked dead too early (note: you may need to increase your current max_request_time setting after making such a change).
what is happening that this server sometimes loses packets so freeradius is marking it as dead. The server is still
ok and keeps sending packets but they are not credited to the NULL realm which is by far the hugest!
They are creditted to the USERS.GR domain which is activated upon receipt of a packet in the rad_recv functionThe solution was easy fix realm_findbyaddr to NOT stop at the first realm it finds , but to go through ALL the realms and activate those for which the originating server is active
Net result : flip flopping of the primary and secondary radius dropped to zilch !!
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
