search for: eound

...39;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 n...