Am 19.01.2013 um 21:35 schrieb Boris Epstein <borepstein at gmail.com>: > > Hello all, > > > > The question is not necessarily CentOS-specific - but there are lots of > > bright people on here, and - quite possibly - the final implementation > will > > be on CentOS hence I figured I'd ask it here. Here is the situation. > > > > I need to configure a Linux-based network load balancer (NLB) solution. > The > > idea is this. Let us say I have a public facing load balancer machine > with > > an public IP of, say, 50.50.50.50. It is to receive the traffic (let's > say, > > HTTP traffic) and then route it to two private HTTP servers, let's say, > > 192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be > > state- and session-aware. If for whatever reason one of the servers goes > > down the remaining pool shares all the traffic in some fashion (be it > eound > > robin, saturation based, whatever). > > > > We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell ( > > http://www.zeroshell.org/ ) and both are very good but their NLB seems > to > > be externally facing (i.e., you have several internet connections and are > > trying to divide your traffic between them). What we need is an > "internally > > facing" one, if I may say so. > > > > Any advice on what may help us would be greatly appreciated. I've had pretty good luck with Barracuda load balancers.. You can configure them to keep a user session on a single server, which is often desired, and spread new connections to other servers as they arrive. The only problem I had with them, ironically, was they would crash if I purchased their "Live Updates" feature. It's some sort of auto updating black-list service you can buy which helps protect the device and your resources. But after I disabled that, the device has been rock solid. Been working great since about 2006. If life gives you lemons, keep them-- because hey.. free lemons. "~heart~ Sticker" fixer: http://microflush.org/stuff/stickers/heartFix.html