> -----Original Message----- > From: netfilter-bounces@xxxxxxxxxxxxxxxxxxx > [mailto:netfilter-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Drew Leske > Sent: Wednesday, April 26, 2006 1:34 PM > To: netfilter@xxxxxxxxxxxxxxxxxxx > Subject: Login load balancing > > The only half-solution I have come up with so far is to define a 'director' > box with the 'bob' alias, and then periodically grab load metrics from the > participating hosts, determine of the 'bob's which is the least loaded, and > then *cough* update a DNAT rule to redirect requests coming in for 'bob' to > the least-loaded 'bobX'. Hi Drew, I believe the above is what you'll want to implement. As your research has probably already shown, the load balancers in the market are for HTTP. A good load balancer will need to communicate with the backend clients so it has data on load and other metrics necessary for it to make a decision on which server to serve. You could use wget to fetch metrics from all the servers (include a timestamp so you know when your data is stale) and have the director consider this information when it punches down new IPTABLEs rules. Cheers, -pablo
