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

[Xen-devel] [Xen 3.2]How to use NAT and bridge together?

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "pradeep singh rautela" <rautelap@xxxxxxxxx>
  • Date: Wed, 20 Feb 2008 15:43:38 +0530
  • Delivery-date: Wed, 20 Feb 2008 02:14:04 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=GcaZdZK1KmL9BlEaYoFMtVSbvUiHKiSDgFCxeSCizRruL/vAqD7Uv+L3PIWSZL5kppJlykozqFkPvzogD/LQy4UqEL5KdQ0FUmvH/8wIDWqcmr8kRMNdjP1LVzremwMZcEAANy+WbyiFSWnN5BOCGp9XilTVBjuosRxvL8gepLc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi All,

How does NAT work now in xen-3.2?
I am not at all able to write a custom script which will attache peth0
to bridge xenbr0(eth0 now) and make peth1 NAT for a dedicated HVM

This is what i write in my custom script.

dir=$(dirname "$0")

"$dir/network-bridge" "$@" bridge=eth0 netdev=eth0

"$dir/network-nat" "$@" netdev=eth1

Whats wrong this thing?

Can't i run one ethernet interface in NAT mode and other in bridged
mode at the same time in Xen-3.2?

How will i know that this NAT thing is working only for one NIC and
one HVM domainU?What should i look for in dom0?

$ brctl show gets me [without any domU working]
bridge name     bridge id               STP enabled     interfaces
eth0            8000.0000c0123300       no              peth0

Can someone explain me why xenbr0 was renamed to eth0 and so on?
It seems to beat shit out of poor soul like me :-).

On a side note, the eth1 device on domainU cannot be created, meaning
something wrong with the way i am using nat-script it seems. How do i
use it in this case.

I used the syntax after a look at network-nat under /etc/xen/scripts/ .

Any pointers.

ps:-  I have looked into shorewall and xen configuration link,
it works only for PV guests.

Pradeep Singh Rautela

Xen-devel mailing list



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