[lvs-users] ipvs or apache/mod_proxy/mod_balancer

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: [lvs-users] ipvs or apache/mod_proxy/mod_balancer
From: Olaf Krische <public@xxxxxxxxxx>
Date: Wed, 24 Jun 2009 06:37:53 -0700 (PDT)

i want to put a loadbalancer in front of several squids, which cache output
of content generators.

The first option is to use the apache/mod_proxy/mod_balancer combination.
Thats easy to configure, you even have a little backend to disable
BalancerMembers manually and also i dont need any special network
configuration. We are quite happy with it. Its simple

But there is this overhead of interpreting the content and to manage the

So the second option would involve IPVS, which just rewrites the packes and
forwards them to a chosen BalancerMember.

There are two ways: 

A) IPVS behaves like mod_proxy, the chosen Member will see a request coming
from the LoadBalancer's LAN-IP.

Bad: I lose the client IP on the Member/real server (in mod_proxy i have at
least "X-Forwarded-For")

B) IPVS forwards the packet to the chosen Member. The source address is

Bad: I need to change the default route, so that answers always go back
through the LoadBalancer. This complicates the otherwise so simple network
setup. People need to know about IPVS. Its not so obvious and self

So the question:  Is IPVS worth the trouble? 

Or is this an exaggeration, when i say apache/mod_proxy uses way more

What would you say?
View this message in context:
Sent from the LVS mailing list archive at

Please read the documentation before posting - it's available at: mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to

<Prev in Thread] Current Thread [Next in Thread>