Re: [lvs-users] LVS + Xen + NAT

To: " users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [lvs-users] LVS + Xen + NAT
From: Josh Mullis <josh.mullis@xxxxxxx>
Date: Wed, 17 Sep 2008 13:38:58 -0400
The only thing I see that I don't have is a dip ( or secondary ip )
setup on the physical OS interface to run the ipvsadm commands against.

As it is now, the ip is the real ip of the physical OS

Do I need to add secondary ip on eth0 and then redo the ipvsadm commands
to listen on that ip?

On Wed, 2008-09-17 at 13:29 -0400, David Dyer-Bennet wrote:
> On Wed, September 17, 2008 12:22, Josh Mullis wrote:
> > I actually expected to see some different rules than what I have.
> > Not sure what I need to add.
> >
> > Here are my current tables.
> > (Spaces replaced with -'s for formatting)
> >
> > iptables -L
> Try iptables-save to see *all* the tables (in an incompatible format).
> I'm still struggling with my own setup (with similar goals and
> constraints, xen + lvs NAT), but once I got packets directed in, they
> came
> back out okay.
> The default route on each of the realserver "systems" (quotes to
> remind us
> that they may be xen guests not physical systems) needs to be set to
> the
> private net virtual IP of the LVS system -- I've deleted enough
> reading up
> to here that I can't now go back and check if you have that set right.
> And the LVS NAT works *only* for packets routed in by the LVS; the
> realservers can't initiate outgoing connections beyond the private LAN
> (unless you turn on ordinary NAT on the LVS, which is not the same
> thing
> as LVS NAT).
> --
> David Dyer-Bennet, dd-b@xxxxxxxx;
> Snapshots:
> Photos:
> Dragaera:
> _______________________________________________
> mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to

<Prev in Thread] Current Thread [Next in Thread>