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

[Xen-users] How to solve ip conflict in Xen3.4 on CentOS5

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: KC LO <kclo2000@xxxxxxxxx>
  • Date: Sun, 20 Jun 2010 18:41:25 +0800
  • Delivery-date: Sun, 20 Jun 2010 03:42:48 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=fjOBpiVB2+sPpYAXD257j61GpT9w3RJKd+Y4E5VrdeHWF/ZfgXag/12jD2TqVYNA8n W7a5iMK/6xoj6voP9PnzeXk25d/3O6F3dru2xzMAPva1Q8DiCz7je1y8WxE2ppeFzRcq EF0DuXEHEVvehOKdGPHmNs9Ae8QNRp+eB3Ji4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I have install Xen3.4 into CentOS5.  I want to restrict the IP used in DomU Guest in order to solve IP conflict problem.  I search for Internet that I can include the IP address in the VIF setting like
vif = [ 'ip= , mac=00:16:36:40:10:de , bridge=eth0' ]
of the xen client configuration file.
However, after include this parameter, the DOMU guest OS can still change the IP address.
I have try Xen3.0 in the default package of CentOS5.4.  After I added this parameter, iptables will be updated to include
this rule like
ACCEPT     all  --  anywhere            PHYSDEV match --physdev-in vif1.0
Why the iptables not include this rule in Xen3.4

Xen-users mailing list



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