Peter Nixon wrote:
Sounds like a plan to me. My testing shows that cvs head it pretty close to stable, and it certainly has a LOT of new features compared with the current release branch. Lets get it out into the world as soon as possible :-)
OK. Re: proxying, it currently keeps track of number of outstanding packets to each home server (i.e. sent but not responded to). It can limit the number of outstanding packets to a maximum, but it doesn't use that counter for anything else. With a few lines of code changed, the "load-balance" method will be: 1. choose home server with lowest number of outstanding packets. 2. if multiple are found with that number, randomly choose among them. This means that when a home server goes down, any requests it hasn't responded to will count against it. Almost all traffic will go to the live home servers for that load-balanced pool. And the minimum number of packets possible will be lost. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog