|
My setup is LVS-NAT.
There is a VIP on either side of the box one on eth0 and one on eth1 so
that I can have another director standing by for fail over and it can take
the IPs. The .50 ips are fixed for me to ssh into the director.
I read I didn't need to setup masquerading for 2.4 but try as I might I
couldn't ping 192.168.1.100 from the real server until I added some
IPTABLES rules.
> ken price wrote:
>>
>> You're absolutely correct in manually setting up
>> masquerading on the director. It's not handled by
>> LVS/Keepalived.
>
> whoa. You don't have to set up masquerading at all in 2.4 kernels
> for LVS to work.
>
>> > The purpose of this setup is to test an LVS cluster
>> > on my private network.
>
> you don't say if this is LVS-NAT or LVS-DR
>
>
>> > ---------------
>> > | Client |
>> > | (My Laptop) |
>> > |192.168.1.100|
>> > ---------------
>> > |
>> > ----------------
>> > | 192.168.1.50 | < Virtual IP 192.168.1.250
>> > | Director |
>> > | 192.168.2.50 | < Virtual IP 192.168.2.250
>> > ----------------
>
> I don't understand why you have 2 VIPs and why you have
> x.x.x.50 and x.x.x.250 pairs
>
> Joe
>
> --
> Joseph Mack PhD, High Performance Computing & Scientific Visualization
> SAIC, Supporting the EPA Research Triangle Park, NC 919-541-0007
> Federal Contact - John B. Smith 919-541-1087 - smith.johnb@xxxxxxx
> _______________________________________________
> 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
>
|
