|
So far, this has confused eveyrone I've mentioned it to, but here goes.
My director has two NICs, one exposed to the internet, and the other
exposed to a private LAN. The public interface has many addresses bound
to it, so I have public interfaces eth0, eth0:1, ..., eth0:x. I use eth0
for load balancing between realservers on the private LAN. I use
eth0:1-eth0:13 to have direct access to certain machines. All my ipvsadm
rules are LVS-NAT. So if I have a machine on the private LAN with IP
address 192.168.1.10, I have a particular interface, eth0:n, on the
director with a bunch of LVS-NAT rules that all forward to 192.168.1.10.
No rules for eth0:n go to anywhere other private IP, and no rules for
any other interface eth0:m, where m != n, go to 192.168.1.10. So I have
some traffic load balanced, and can still access realservers directly.
All the realservers have the private (192.168.1.x) address of the
director as their default gateway, there is no other route outside of
the private lan.
Hope that didn't confuse you. :)
Jacob Coby wrote:
Can I have realservers respond on both the private 192.168. address for
load-balancing, and the public class-C ip address?
I'm assuming that lvs-dr will do this?
Sorry if this is a bad question, it has taken me all day to get lvs-nat
working because I didn't see the one line in the mini howto about
there must
be one and only one route to the director from the realserver :) Once
I got
that, it was real easy.
-Jacob
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
--
Justin Georgeson
UnBound Technologies, Inc.
http://www.unboundtech.com
Main 713.329.9330
Fax 713.460.4051
Mobile 512.789.1962
5295 Hollister Road
Houston, TX 77040
Real Applications using Real Wireless Intelligence(tm)
|
