Kastus wrote:
On Sun, Aug 27, 2006 at 02:55:02PM +0200, Per Jessen wrote:
The reason I assign it to 'lo' is that 'lo' does not respond to arp requests. There is more to this than meets the eye - if you to know more, check out the documentation for setting up a linux virtual server with direct routing (LVS-DR).
It does not respond to arp requests but it adverises your IP alias from 'lo' interface on the 'eth' interface. Please keep that in mind.
Yes, but I can take care of that using the arp_ignore and arp_announce settings (see "sysctl -a | grep arp").
That's why you either have to put your cluster members on a routed subnet
The cluster members are all on public addresses, but I do not have great control over which subnets they're on.
or use static arp tables on the clients talking to the cluster.
Also not a possibility - I have no control over the clients. As it happens, I'll probably not be using the LVS direct route setup, but use LVS tunnelling instead. /Per Jessen, Zürich