[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] iptables and ipvsadm in domU


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Fong Vang" <sudoyang@xxxxxxxxx>
  • Date: Tue, 1 May 2007 16:33:02 -0700
  • Delivery-date: Tue, 01 May 2007 16:31:39 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Yx1gWDhBH8Aq1MEJHWDGbLrP9Lp6lzoVxyX5d7pOhmANE9IAmDMcIdotfxRrfBnq8fGvGi5X4vz/bjUMytjIBWEjCzXZnJZUQga+iXC9Ldcnle/zZzwV6XLH+UcLYate2Yo4g/U6y6TVsJgzq2TAgroqCwzZ/v4aN2KG14Ii0wQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

The documentation for Xen mentions that iptables in dom0 may affect domUs.  If iptables and ipvsadm is heavily used in a domU, how does this impact dom0?

In my particular case, I want both dom0 and ONE domU (FW_domu) to be visible to the external network (eth1).  There will be several other domU's that will be behind FW_domU).  

as far as the domUs are concerned, this is the layout.

       FW_domU
          |
       LB_domU
          |
    +-----+--+--------+
    |        |        |
    domU1    domU2   domU3

what's the best way to set this up.  LB_domU runs LVS (ipvsadm).  Is this configuration even supported in Xen.

Thanks for any help.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.