|
Robinson, Eric wrote:
> Is there a way to make LVS handle this scenario?
Possibly.
The reason your situation doesn't work is that the realserver responds
directly to client B, thus avoiding the director on the way back. This
happens because the realserver and client B are both on the same logical
network, 192.168.5.0/24 (assuming a /24 netmask).
You may be able to force it to work by removing the route to
192.168.5.0/24 from the realserver. That means *all* traffic from the
realserver will go via the default gateway (the director), whether it's
replies to clients or realserver-sourced traffic like backups or DNS
lookups.
that's not guaranteed to work, but it's about all you've got.
Graeme
|
