|
"Lizambri, Todd" wrote:
> Still having this problem, I'll send you the output off-line.
OK
> OK. I'll buy that...but I don't want it to do that :-).
> I would like connections initiated from my realserver to clients to NAT
> to the VIP. I want the LVS to appear as one IP address to the outside
> world (or my DB teir or whatever). My client is seeing the RIP addresses
> and doesn't know how to route packet back to it. Is there a way to
> accomplish what I want inside of the LVS framework?
you can NAT out clients from the realservers, but it's not connected to
the operation of the LVS. You have to do it so that it doesn't affect the LVS.
Here's how it's done for VS-DR. You can do the same thing for VS-NAT.
http://www.linuxvirtualserver.org/Joseph.Mack/HOWTO/LVS-HOWTO-13.html#ss13.10
the source address will be the primary IP on the outside of the director,
which for my script will not be the VIP.
Since the machine on the internet is only replying to calls initiated
at the realservers, does it need to see the IP as the same as the VIP?
You can hack my script to put
the VIP on eth0 rather than an alias if you like, but you will have to use
iproute2 tools to fail out the VIP then (if you're going to do failout).
My script is more for setting up simple LVS's for people who are new to
LVS.
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
